Interview Coach
Software Engineer Interview Questions
Software Engineer loops are weighted toward problem-solving under observation. Most companies run two coding rounds, one system design round, and one behavioural round; the coding rounds screen for correctness and communication in roughly equal measure, and the design round is where mid-level and senior candidates are separated. Your CV is read for evidence that you have owned something in production, not just shipped features.
Build your story bank freeWhat software engineer interviews are scored on
Coding under observation
Data structures and algorithms applied to a problem you have not seen, narrated aloud. Interviewers score how you clarify ambiguity and test your own solution as much as whether you reach the optimal complexity.
System design
Designing a service end to end — API surface, data model, caching, failure modes. Expected from mid-level upward; at junior level it is replaced with a code-extension exercise.
Production ownership
What broke, how you found it, what you changed so it could not recur. This is where on-call experience and postmortem habits show.
Code review and collaboration
How you give and take review feedback, and how you handle disagreement about technical direction.
Technical software engineer interview questions
Questions of this shape recur across software engineer loops. Practise them aloud — interviewers score how you reason, not only where you land.
- Walk me through what happens between typing a URL and the page rendering.
- Design a URL shortener. How do you generate keys, and what breaks at 10x traffic?
- You have a service whose p99 latency tripled overnight with no deploy. How do you investigate?
- Explain the difference between optimistic and pessimistic locking, and when you would pick each.
- How would you migrate a heavily-read table to a new schema with zero downtime?
- When would you choose a message queue over a synchronous call, and what new failure modes does that introduce?
- Given a large log file that does not fit in memory, find the top 10 most frequent entries.
Behavioural questions for software engineer roles
Prepare one STAR story per theme. A single strong story usually answers two or three of these prompts.
- Tell me about a production incident you caused. How did you find it and what did you change afterwards?
- Describe a time you disagreed with a technical decision your team made. What did you do?
- Tell me about code you inherited that you had to significantly change. How did you de-risk it?
- Describe a project where you had to cut scope. How did you decide what to drop?
- Tell me about a time you were blocked by another team.
Numbers that make software engineer answers credible
A STAR answer without a result is a story. These are the measures that carry weight in this role.
Questions worth asking your interviewer
- What does on-call look like here, and how often does the rotation page?
- How long does it take from merged PR to production?
- What is the test and review culture — what stops a bad change reaching users?
- What is the largest source of technical debt the team is carrying right now?
Software Engineer interview FAQs
How many rounds does a Software Engineer interview usually have?+
Four to six. A recruiter screen, one or two technical phone screens, then an onsite loop of two coding rounds, one system design round (mid-level and above), and a behavioural or hiring-manager round. Larger companies add a values or bar-raiser round. The whole process typically runs two to five weeks, and the system design round carries the most weight in levelling decisions.
Do I still need to grind LeetCode for Software Engineer interviews?+
You need fluency in the common patterns rather than volume. Roughly 150 well-understood problems covering arrays and hashing, two pointers, sliding window, binary search, trees and graphs, and dynamic programming will cover the large majority of what gets asked. Practising aloud matters more than practising more — interviewers score communication, and candidates who solve silently frequently fail rounds they technically passed.
What should a Software Engineer CV lead with?+
Systems you owned and their measurable effect. A line like "Cut checkout API p99 from 1.2s to 240ms by replacing N+1 queries with a batched loader, supporting 40k RPS at peak" outperforms a list of languages, because it demonstrates scale, diagnosis, and outcome at once. Keep the languages and frameworks in a compact skills block for the ATS, and spend the bullets on impact.
How much system design do I need at junior level?+
Less than you fear, but not zero. Junior loops rarely include a dedicated design round; instead you are asked to extend the code you just wrote, which tests the same instinct at smaller scale. Being able to explain why you split a class, where you put validation, and what happens when the downstream call fails is enough. Formal design rounds usually start at the two-to-four-year mark.
Need the CV before the interview?
See software engineer CV examples, before/after bullets, and the metrics reviewers look for.
Other interview guides
Turn your experience into answers
CVEdge reads your CV, drafts STAR stories from what you actually did, and matches them to the software engineer job you're interviewing for.
Start building free