Software Engineer mock interview questions
19 questions a Software Engineer panel actually asks, with what each one tests and what a strong answer contains, then practice any of them live. Coding, system design and behavioral rounds for software engineer interviews.
Answer one real Software Engineer question now
A question a Software Engineer panel actually asks, answered out loud, scored on what you said and how you said it. Under two minutes, and nothing to sign up for.
“Design a URL shortening service. Start with the API, then tell me how it stores data, how it scales for reads, and what happens when it grows.”
We never store the audio. Your answer is deleted within 24 hours unless you save the result.
- Adaptive follow-ups, not a fixed question list
- Rubric scorecard with evidence from your answers
- Voice or text, with delivery coaching on voice sessions
Thinking past the interview? Carmen can help with your whole Software Engineer career: a switch, a raise, or what comes next.
19 software engineer mock interview questions
The questions a Software Engineer panel actually asks, with what each one is testing and what a strong answer contains. Click any question to run it in a live session: your AI interviewer will cover it and score how you answer.
- 1.
Design a URL shortening service. Start with the API, then tell me how it stores data, how it scales for reads, and what happens when it grows.
Why they ask it: A classic system design question. The interviewer wants structured thinking, sensible tradeoffs and awareness of scale, not a memorised diagram.
A strong answer: Clarify requirements and rough scale first. API for creating and resolving links. Key generation using a counter with base encoding or random ids with collision checks, discussing the tradeoffs. A key-value store suits the lookup pattern. Reads vastly outnumber writes, so add caching and a CDN or edge layer for redirects. Cover analytics as an asynchronous pipeline, abuse prevention, custom aliases, expiry, and how to partition data as it grows.
- 2.
Given a stream of events with timestamps, return the number of events in the last five minutes at any query time. Design the data structure.
Why they ask it: A practical algorithm question testing choice of data structure and complexity reasoning.
A strong answer: A queue or deque that evicts events older than the window on each insert or query, giving amortised constant time. Discuss memory if the event rate is high, and a bucketed approach with fixed-size time buckets as an approximation that bounds memory. State assumptions about ordering and handle out-of-order events or explain why they are excluded.
- 3.
An API endpoint that used to respond quickly now has occasional multi-second delays. How do you investigate?
Why they ask it: Debugging production performance is real day-to-day work.
A strong answer: Look at latency percentiles over time rather than averages, correlate with deploys, traffic or data growth, and use tracing to find which span is slow. Common causes: a slow query or lock contention, a downstream dependency, garbage collection pauses, connection pool exhaustion, or cache misses. Form a hypothesis, test it, and fix with measurement before and after.
- 4.
How do you decide how much to test a piece of code, and at what level?
Why they ask it: Tests engineering judgment about quality and speed.
A strong answer: Test by risk: core business logic and tricky edge cases get thorough unit tests, integration tests cover boundaries with databases and services, and a few end to end tests cover critical user journeys. Tests should verify behaviour, not implementation details. Consider how costly a bug would be and how often the code changes.
- 5.
Tell me about the most technically complex project you have worked on. What was your part?
Why they ask it: Assesses depth, ownership and communication. Interviewers probe to find out what you personally did.
A strong answer: Explain the problem and why it was hard, your specific contribution using I rather than we, key decisions and alternatives considered, what went wrong and how you adapted, and the outcome. Be ready for follow-up questions at any level of detail.
- 6.
Tell me about a time you disagreed with a technical decision made by a senior engineer or your team.
Why they ask it: Collaboration and handling conflict is scored in every loop.
A strong answer: A real disagreement, how you raised it with evidence, how you listened to their reasoning, how the decision was made, and how you committed to the outcome even if it was not your preference. Showing you changed your mind in some cases is a plus.
- 7.
When would you choose a relational database over a document store, or the reverse?
Why they ask it: A fundamentals question that reveals whether choices are made from access patterns.
A strong answer: Relational databases suit structured data with relationships, transactions and flexible querying. Document stores suit data read and written as whole aggregates with varying shape, and can scale horizontally more simply for some workloads. Decide from access patterns, consistency needs and team familiarity. Noting that many modern relational databases handle semi-structured data too is a good nuance.
How the Software Engineer interview runs
A typical loop is a recruiter screen, a technical phone screen with a coding problem, then an onsite or virtual loop of four or five interviews: two or three coding rounds on data structures and algorithms or practical problems, a system design round for mid-level and above, and a behavioral round about past projects and collaboration. Some companies replace algorithm rounds with practical tasks such as extending a small codebase. Interviewers score problem solving, code quality, communication and ownership.
What the panel scores
Problem solving and coding
Whether you can turn a problem into correct, efficient code.
- Clarifies before coding
- Chooses data structures deliberately
- Tests and analyses complexity
System design
Whether you can design systems that work at scale.
- Starts from requirements and scale
- Discusses tradeoffs explicitly
- Identifies bottlenecks and failure points
Engineering practice
Whether you ship maintainable code and debug methodically.
- Tests by risk
- Uses data when debugging
- Writes readable code
Collaboration and ownership
Whether you make your team more effective.
- Describes personal contributions clearly
- Handles disagreement constructively
- Takes ownership of outcomes
Common questions in every interview
These come up in almost every Software Engineer interview regardless of the company or the round.
- 8.
Tell me about yourself.
Why they ask it: Opens the interview and sets the frame. The interviewer is checking whether you can select what matters for this job rather than narrate your whole history.
A strong answer: A 60-90 second arc: where you are now, one or two proof points that match the posting, and why this role is the logical next step. Present, past, then future.
- 9.
Why do you want this role?
Why they ask it: Tests whether you read the job description or mass-applied. Weak answers are about what the candidate gets; strong answers connect to the work itself.
A strong answer: Two specifics from the posting or the company's actual work, plus an honest line about what you want to get better at here.
- 10.
Walk me through your resume.
Why they ask it: Checks that your story holds together and that the transitions were deliberate rather than accidental.
A strong answer: Chronological but fast, with a reason attached to each move and more time on the roles closest to this one.
- 11.
Tell me about a time you failed.
Why they ask it: Tests self-awareness and whether you own outcomes. Interviewers are listening for a real failure, not a disguised strength.
A strong answer: A genuine miss, what you specifically got wrong, the cost, and the concrete thing you changed afterwards that has since held up.
- 12.
Tell me about a conflict with a coworker or manager.
Why they ask it: Predicts how you behave when the team disagrees. The trap is blaming the other person.
A strong answer: The substance of the disagreement, what you did to understand their position, how it resolved, and what the working relationship looked like after.
- 13.
What's your greatest strength?
Why they ask it: Checks whether you know what you're actually good at and can prove it.
A strong answer: One strength that maps to the posting, plus a short example where it produced a measurable result.
- 14.
What's your greatest weakness?
Why they ask it: Tests honesty and whether you're actively working on something. Rehearsed non-answers ('I work too hard') read as evasive.
A strong answer: A real limitation that isn't core to the job, the system you built to manage it, and evidence it's improving.
- 15.
Tell me about a time you had to influence someone without authority.
Why they ask it: Almost every role depends on getting people who don't report to you to change course.
A strong answer: What you wanted, why they resisted, the evidence or framing that moved them, and what actually shipped as a result.
- 16.
Where do you see yourself in five years?
Why they ask it: Tests whether this job fits your trajectory, which is a retention question in disguise.
A strong answer: A direction rather than a title, and a line about the skills this role would build toward it. Vague ambition and rigid title-chasing both land badly.
- 17.
Why are you leaving your current job?
Why they ask it: Screens for red flags. Interviewers listen for how you talk about people you no longer work with.
A strong answer: Forward-looking and specific about what you're moving toward. Criticism of a former employer costs you more than it gains, even when it's deserved.
- 18.
What are your salary expectations?
Why they ask it: Checks whether you've done market research and whether you're in range before anyone spends more time.
A strong answer: A researched range with your target near the bottom of it, framed against the scope of the role. Deflect once if the posting has no band, then answer.
- 19.
Do you have any questions for us?
Why they ask it: The most under-prepared question in the interview, and the one that most changes the final impression.
A strong answer: Two or three questions about how the team actually works: what the first 90 days look like, how success is measured, what the hardest part of the job is.
Every round ends in a scorecard like this
Your Software Engineer answers, quoted back, scored on what this role is judged on, with the line to say instead.
Real screen from the app. Sample from a product design round.
Related roles
All Engineering →No spam. Unsubscribe anytime.
Ready to practice as a Software Engineer?
Sign up free, no card. 30 voice minutes and unlimited typed interviews, each ending in the complete scorecard: rubric scores, strengths, and what to fix next. Nothing is blurred.
- ✓ Predefined role or paste any job description
- ✓ Rubric scores with evidence quotes
- ✓ 888+ roles to choose from
Questions & answers
- Is the Software Engineer mock interview free?
- Yes. 30 voice minutes and unlimited typed Software Engineer interviews, no card. You get the complete rubric scorecard every time, with the evidence quoted from your own answers. Nothing is blurred.
- Can I use my own job description instead?
- Yes. Predefined roles are starting points. Paste any JD in the setup form and your AI interviewer will tailor questions to that posting.
- How is scoring tailored to this role?
- We pre-fill a realistic Software Engineer job description and interview format so questions and the scorecard match how this role is actually interviewed.
- Should I tailor my resume before practicing?
- Run a resume fit check against a Software Engineer job description first, then practice the interview with the same JD for a tighter loop.