Skip to main content

Interview questions

Questions and answers about all kind of interviews

The Interview Process

Before the interview

Before the interview

  • Search informations about the company. Know about the company culture and visit the website, portfolio, job description, github account and social networks profiles like Linkedin or the Facebook page.
  • Prepare some questions to the interviewer.
  • Search the web and see if there is someone who made the same interview.
  • Know who will be interviewing you, and learn a bit about their background.
  • Know your strengths and weakness.
  • Know about the SOARA technique and RSA. Be ready to answer a question about some situations at work.
  • Prepare for the different types of interviews: behavior, experiential, or combination.
  • Sleep well the day before the interview and try to be relaxed.
  • Turn off your cell phone (even for skype interviews).
During the interview

During the interview

  • Shake the interviewer's hand.
  • Keep eye contact.
  • Go straight to the point. Quick and short answers are better than talking too much. This will give the interviewer\s exactly what they need to know.

The followings hints seems simple to follow but they are not! It depends on your personality, your skills on interviews and many other things.

  • Don't talk too quickly.
  • Don't use slang.
  • Don't use words you don't know the meaning of.
  • Don't talk about your personal life.
  • Don't fidget or act nervous. You probably will be, but it is best if you take a few seconds and clear your mind.
  • Don't get defensive. Try to answer technical questions but don't be afraid to skip a question you don't know the answer.
Technical interview

Technical interview

A technical interview can be a difficult step during the hiring process. We often know some concept but we cannot explain some mechanism because we simply apply it in practice.

The Joel test

On stackoverflow job section, you will always see if a company follow all the points of the Joel test.
The company don't necessarily follow all points.

  1. Do you use source control?
  2. Can you make a build in one step?
  3. Do you make daily builds?
  4. Do you have a bug database?
  5. Do you fix bugs before writing new code?
  6. Do you have an up-to-date schedule?
  7. Do you have a spec?
  8. Do programmers have quiet working conditions?
  9. Do you use the best tools money can buy?
  10. Do you have testers?
  11. Do new candidates write code during their interview?
  12. Do you do hallway usability testing?

Books

Some essential books about the whole interview process.