Skip to content
CareersAble

Interview questions

Software Engineer interview questions

Software Engineer interview questions for each round, from the recruiter screen to the system design, with what each round is scoring.

Answer one Software Engineer question out loud today and time yourself.

All software engineering questions

How Software Engineer interviews are scored

Software engineer interviews score how you narrow a problem before you solve it. Candidates who ask about scale and constraints first get credit for judgement, even if their final design is simpler.

What hiring managers check in Software Engineer interviews

  • Whether you ask about scale, users and constraints before you draw anything, because that is how real designs go wrong.
  • Whether you can name the trade-off you chose and what it cost, not just the option you picked.
  • Whether you explain your thinking while you code, because the pairing round scores how you would work beside the team.

Pick the check you are weakest on and prepare one Software Engineer story for it tonight.

Questions Software Engineer candidates get

On top of the questions every role in this field is asked, these come up for this title in particular.

Screening interview questions

Usually a recruiter or talent partner, 15 to 30 minutes, often by phone or video.

  1. What is the most complex system you have worked on, and which part was yours?
  2. How much of your time goes on new features versus maintenance?
  3. How big is the codebase you work in, and how many engineers commit to it?
  4. Have you worked on backend services, data pipelines or both?
What this round scores

Hiring manager interview questions

The person you would report to, 45 to 60 minutes, sometimes with a team member.

  1. Tell me about a design you changed after it was already in production.
  2. How do you decide what to test, and what do you leave untested?
  3. Tell me about an API you designed. Who used it, and what would you change now?
  4. How do you handle a dependency on another team that keeps slipping?
What this round scores

Final round questions

Senior leaders, a panel, or a case task, 60 minutes to half a day.

  1. Walk me through how you would design a rate limiter for a public API.
  2. Pair with us: extend this small codebase to support a new requirement.
  3. This service needs to handle ten times its current load. Where does it break first?
  4. Talk us through how you would split one service out of a monolith.
What this round scores

Plus the software engineering questions every round asks

  • Walk me through your engineering background in two minutes.
  • What languages and frameworks have you used most in the last two years?
  • What kind of team and codebase are you working in now?
  • Tell me about a technical project you are proud of and your part in it.
  • Tell me about a production incident you helped fix.
  • Describe a time you disagreed with a technical decision.
  • Design a URL shortener that handles millions of requests a day.
  • How would you find out why an API got slow last week?
  • Walk me through the trade-offs of the architecture in your current system.
See all 24 software engineering questions, with scored example answers

Get the software engineering question pack by email

Every question on this page in one email, grouped by round. Plus three things that are not on the page:

  • 12 more questions, 4 per round, that only go out by email
  • What a strong answer covers in each round, to check yourself against
  • A 7-day prep plan that matches where you are in your search
Where are you in your search?

We email you the pack once. We never sell or share your details. Privacy policy

Hiring manager interview

One question, three answers, three scores

The same question answered three ways, scored the way an interviewer would mark it.

“Tell me about a design you changed after it was already in production.”

Weak30
“We refactor things all the time. I'm always looking for ways to improve the code and keep it clean.”
Why: No system, no change and no reason. It sounds like a habit, not a decision.
OK58
“We stored order events in one big table and queries got slow, so I moved them to a separate events store. Reporting got a lot faster after that.”
Why: A real change with a cause, but "a lot faster" is vague and the migration risk is not mentioned.
Strong85
“Our order events lived in the main Postgres table, and by 40 million rows the reporting queries were timing out. I proposed an append-only events table with a nightly rollup, and we migrated by writing to both for two weeks before switching reads. Report time went from 90 seconds to under three, and I'd now design for the rollup from day one.”
Why: Names the trigger, the migration plan, a measured result and what the engineer learnt.

Example scores on the 0 to 100 scale CareersAble uses. Your own answer gets its own score.

Reading the questions is not the same as answering them.

CareersAble writes the questions your actual job ad will ask, records your answers, scores each one three times and tells you plainly what to fix.

Free to start. No card needed.