about questions: Anything to show that you are interested in working with them - ask them what are they looking for - and not just a short version of the job description but actual needs - do they need a person more involved with design or functionality? What is the team like - small/big? What technologies/methodologies are they using? Ask about their social activities - maybe there will be something you find interesting and you can show that to them so they know you won't be socially awkward and hard to deal with.
Ask about future opportunities/training/certificates - show that you are not looking to stay there a month or two but that you are interested in developing yourself.
Of course any other question you might have like not being sure about salary/working time/dress code etc are always welcome.
about selling yourself - I know this can be hard but I think the best way to do this is to be honest with them and very confident. If you don't know something - its ok just say you are not sure or that you haven't had the chance to look into that. If you know it - great - speak with confidence.
One tip from my interviewer I got was that he liked the fact that I did not just answer with "yes/no" to most questions but rather explained a bit more.
Another thing I would say is that the more interviews you do - the better you will become in answering the questions. You might not feel as good because of more and more rejection but if you manage to accept that it is for the better it should help you :)
I love this reply. Thank you so much. I've had a couple interviews and being rejected but not knowing why. They don't ask me technical questions but more about asking who I am and what I do. I show passion because I love to what I do but something isn't selling so I figure it could be the questions I ask. The questions I ask is mostly about the position such as "Are we building websites or fixing the functionality of it?" I think my questions are more focused on "getting the job done" rather than "what do you need from me"
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
about questions: Anything to show that you are interested in working with them - ask them what are they looking for - and not just a short version of the job description but actual needs - do they need a person more involved with design or functionality? What is the team like - small/big? What technologies/methodologies are they using? Ask about their social activities - maybe there will be something you find interesting and you can show that to them so they know you won't be socially awkward and hard to deal with.
Ask about future opportunities/training/certificates - show that you are not looking to stay there a month or two but that you are interested in developing yourself.
Of course any other question you might have like not being sure about salary/working time/dress code etc are always welcome.
about selling yourself - I know this can be hard but I think the best way to do this is to be honest with them and very confident. If you don't know something - its ok just say you are not sure or that you haven't had the chance to look into that. If you know it - great - speak with confidence.
One tip from my interviewer I got was that he liked the fact that I did not just answer with "yes/no" to most questions but rather explained a bit more.
Another thing I would say is that the more interviews you do - the better you will become in answering the questions. You might not feel as good because of more and more rejection but if you manage to accept that it is for the better it should help you :)
I love this reply. Thank you so much. I've had a couple interviews and being rejected but not knowing why. They don't ask me technical questions but more about asking who I am and what I do. I show passion because I love to what I do but something isn't selling so I figure it could be the questions I ask. The questions I ask is mostly about the position such as "Are we building websites or fixing the functionality of it?" I think my questions are more focused on "getting the job done" rather than "what do you need from me"