As interviewers, we often deal with a large number of talented candidates who rock coding questions but are still unable to properly describe a project that they have done recently. Interviewers are encouraged to ask behavioral questions and go over the past experiences at the beginning of interviews so that the candidates become comfortable before jumping to the technical part.

It makes the behavioral part even more important since failing on the simple non-technical questions at the beginning can lead to the bad first impression on the interviewer and more stress on the candidate’s shoulder.

In this post, we have tried to gather some popular behavioral questions in software engineering interviews which every candidate should be prepared to answer:

  • Tell me about one of the most technically challenging projects you have done.
  • What will you do differently if you are given the same project again.
  • Tell me about the project that you are most proud of.
  • Tell me about the time that you had conflicts with your teammate/manager, how you resolved it, and what you learned.
  • Tell me about a time that you were behind a deadline and you knew that you could not meet it.
  • Tell me about a time that you had to implement a workaround (vs. a solution) for a critical issue to meet a deadline. What did you do with the issue after the deadline?
  • Tell me about a time that you introduced a technical debt in your work.
  • Could you mention some general issues in your current job?
  • Have you taken any action to mitigate/resolve those issues?
  • Why do you want to leave your current job? Why do you want to join us?
  • What do you know about our company?
  • If you have worked in many companies for short periods of time (< 2yrs), why do you switch your jobs so quickly?
  • What is your weakness? (seriously, I don’t like it so as many others. But for some reasons people are still asked this question!)
  • How do you see yourself in whatever years? (another one that I don’t like personally).

The list can go larger and larger. What you should do is to read your resume very well and know the details of projects you have mentioned. Interviewer might go deep to any of those projects and you are still required to answer the related questions.

Important tip for experienced candidates: On onsite interviews, you are interviewed by multiple people and they ask behavioral questions the same as or similar to questions mentioned in this post. Always try to bring a different project (or mention that you have explained the same project to another interviewer) while describing a situation. Otherwise, in debrief after the interviews, interviewers might argue that you have done very few projects so you are not able to mention more.

At TechMockInterview, interviewers are also encouraged to ask some behavioral questions at the beginning before they go to the technical part. Please let us know if you know any other popular question missing in our list.

Leave a Comment

Your email address will not be published. Required fields are marked *