JobInterview AI

Software Engineer interview questions

A software engineering interview is rarely about syntax. The hiring manager wants to hear how you reason about trade-offs, how you behave when production breaks, and whether a teammate could follow your thinking out loud.

Questions to expect

  1. Walk me through a system you built or changed recently. What would you do differently now?

    What they listen for

    A clear picture in under two minutes: what it does, your part in it, one real constraint. The second half matters most: a specific regret shows judgment, 'nothing' shows none.

  2. Tell me about a production incident you were involved in.

    What they listen for

    Order under pressure: how you found the cause, what you did first, how you told others. Then what changed afterwards so it could not happen the same way again.

  3. Describe a time you disagreed with a technical decision.

    What they listen for

    That you argued with evidence rather than opinion, and that you can commit to a decision you lost. Blaming the other person ends the answer badly.

  4. How do you decide when code is good enough to ship?

    What they listen for

    A real rule you apply, tied to risk: what you test, what you leave, how you would roll back. Not 'it depends' with nothing after it.

  5. Tell me about something you had to learn quickly to deliver a project.

    What they listen for

    How you learn, in steps, and how you checked you had understood. The deadline and the result should both be in the answer.

One answer, before and after

Tell me about a production incident you were involved in.

You said

Yeah, so we had this outage once, it was pretty bad, the database was slow or something and everyone was panicking. We looked at a lot of things and eventually someone found it was a query, and we fixed it and it was fine after that.

Try

Last spring our checkout went down for forty minutes on a Friday. I was on call. I saw database CPU at 100 %, traced it to a new report query with no index, and killed it: we were back in six minutes. On Monday I added the index and a query timeout, so one slow report can no longer take checkout down.

What happened, what you did yourself, and what changed afterwards, with the numbers.

What a report scores for this role

Technical judgment
You name the trade-off you made and what it cost.
Ownership
You say 'I' for your part and follow the work to its result in production.
Clarity
Someone outside your team could repeat your explanation.

Examples: each report picks the competencies that fit the role and the interview.

Rehearse this interview out loud

Reading these questions is a start. Saying your answers to someone who follows up is the rehearsal.

Download on the App Store

Other roles