I am a product engineer and have helped build software from small startups, to manipulating hundreds of millions of data points. I write API's and make tools that make developers lives easier.
Realize that the interview is two ways. You are interviewing them as much as they are interviewing you. You want to ask questions that give you an idea on how it is to work for them. How does management actually manage employees. Do each developer have 10 bosses? Just one? Do you like or get along with interviewers?
Ask them questions that you would want to know as a new employee. What would your day be like, how do you do agile development? How do teams work on parts of the product?
Some of my favorite questions are:
Where do you see the ideal candidate in 6 no the? A year? 3 years?
Is there room to grow into higher level positions?
Why did the last developer leave (if you think you can get away with asking).
Take what you would normally get as an interview question, and find out how to reverse that and ask them the same.
I like to take a notebook, like a moleskine or something, and write downy questions, then keep that open on the table with the pen. As they interview you, write responses in your book. Or ideas for new questions or responses to ones you had and they answered. Don't be afraid to ask for clarification for a question you had in order to get the answer you want.
When you take notes, it shows you are prepared, are attentive, and care about the interview.
Two more tips:
Do research on the company. Find out what problems they are solving. Figure out what problems they have that they are hiring for. Try to be the person that fills those roles and are the person they want to hire
Send a thank you letter ASAP! Always send a follow up email that king them for their time and be confident they will choose you. I always tell them that I hope to hear back soon on when I can start and help them solve their problems. Remember, as a developer you are a problem solver.
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.
Realize that the interview is two ways. You are interviewing them as much as they are interviewing you. You want to ask questions that give you an idea on how it is to work for them. How does management actually manage employees. Do each developer have 10 bosses? Just one? Do you like or get along with interviewers?
Ask them questions that you would want to know as a new employee. What would your day be like, how do you do agile development? How do teams work on parts of the product?
Some of my favorite questions are:
Take what you would normally get as an interview question, and find out how to reverse that and ask them the same.
I like to take a notebook, like a moleskine or something, and write downy questions, then keep that open on the table with the pen. As they interview you, write responses in your book. Or ideas for new questions or responses to ones you had and they answered. Don't be afraid to ask for clarification for a question you had in order to get the answer you want.
When you take notes, it shows you are prepared, are attentive, and care about the interview.
Two more tips: