AMA with Fábio Oliveira, Managing Director @ YLD

Join us on October 18th, at 6pm (GMT+1).

Save your spot

The Best Software Developer Interview Questions You Should Do

An overview of the most common interview questions.

When you’re going through a hiring process, you should prepare yourself for the most common interview questions in order to move on to the next stage.

The Most Common Interview Questions

  1. What are you looking for in this job?

    This is an important question, as you want to know why they are looking for a new job and why they applied to your particular company. Did they do research about your company? Try to find out what they know about your company’s mission, what your values are, and what your company culture is like.

    If they did not do research about your company and are simply looking for a new job because they need the money, they might not end up being a good fit for your team. You want to make sure that their values align with your own and that they will be dedicated to your mission.

    You want to hire a software engineer who is passionate about your values and goals and wants to help you reach them.

  2. Tell us about a mistake you have learned from.

    Every software engineer who is passionate about engineering and has worked on personal and business projects will have made some mistakes. Perhaps they worked on a project that ended up failing. That is not a bad thing, however, as it allows them to learn important lessons from those failures.

    During the interview process, try to find out what mistakes the software engineer made and what lessons they learned from those mistakes.

    This allows you to get an insight into their work ethic, their willingness to admit mistakes and learn, and how they work on improving their skills while working on projects.

  3. Did you ever face a bug / problem that you couldn't solve? What was the final outcome? How did you solve that problem?

    This question will allow the candidate to explain how they approach problems and their methodology for solving them. It will show whether they have the skills to hold up to pressure and use their problem-solving skills to arrive at a solution.

    This does not have to be a software engineering problem, though it may be. It can also be a problem with teamwork. For example, they can explain how they had a disagreement with a colleague on how to properly approach a specific problem and how they came to an agreement with that colleague.

    This will show that they have the teamwork skills to work with someone else, even when there is a conflict.

  4. How do you come up with estimates?

    Software engineers often come up with estimates that are entirely off the mark. Although they may want to think that they can deliver an end result within a specific time frame, new issues and bugs often come up that cause them to be late on their estimate.

    Ask the candidate how they come up with estimates to find out how accurate they are and whether they have realistic expectations about what it will take to complete a project.

  5. What are you working on right now?

    Find out what the software engineer is working on at the moment. Even if they are not currently working for a specific company, a good software engineer who is passionate about development will usually be working on a side project of their own.

    If they are indeed working on a private project, ask them why they chose that project, what their goals are, what they enjoy about that project, and what they are learning from the process of working on that project.

  6. How do you assure software quality?

    When working on a project, it is important to conduct a quality control process to ensure that the end results come out great.

    Ask the developer what their quality control process looks like and whether they use any specific tools to test their results.

    Any engineer can end up having bugs in the software they are working on, but it is important that they have a process to test for bugs and a method for fixing them.

  7. What’s important when checking a team member’s code?

    While this question does not have a right or wrong answer it will give you insight into their thought processes on coding. What are the really important things when writing code? Do they focus on functionality or simplicity? Is security something there concerned with?

  8. What are your career goals?

    You may be looking for a developer who has higher aspirations, or you may be looking for someone who prefers to do what they are doing now and not have any sort of management position.

  9. How do you keep your skills sharp and up to date?

    A software engineer needs to stay on top of changes that occur in the industry and keep their skills fresh for new and emerging technologies.

  10. What questions do you have for us?

    When interviewing a potential software engineer, it is important not just to ask them questions but to allow them to ask their own questions.

    If an engineer doesn’t really care about your company and is just interested in making money, they probably won’t have a lot of questions.

    In addition, a good software engineer who cares about their work is in high demand, and cares about working with a great team will probably have a few questions for you as well.

    They might want to ask about the company culture, the work-life balance, your company values, the goals you are trying to reach, what you are looking for in a software developer and more to figure out whether you would make a good fit for them and how they will fit in with your overall company goals.

    Questions like:

    1. Can you describe the regular day in the office in your company?
    2. How are teams organized?
    3. What methodologies do you use for software development?
    4. What’s the potential career path for someone in this role?
    5. What are the biggest challenges for people who have recently started at your company?


These are just some questions that are important to ask software engineers. There may be other specific questions that are specific to your company such as your tech stack and the programming languages you use.

Adriana Correia
Written by Adriana Correia

Tech hiring insights in your inbox

From engineers to engineers: helping founders and engineering leaders hire technical talent.

We will only ever send you relevant content. Unsubscribe anytime.