Skip to content
TryHired.
Interview questions · Software Engineer

Software engineer interview questions: practice design, debugging and judgment, not memorized answers.

Original practice questions built around what the occupation involves, with answer guidance. We don't claim to know what any employer will ask.

Updated Nov 15, 2026
Quick answer

Software engineer interviews usually mix three things: solving coding problems, reasoning about how a system should be designed, and showing how you work with other engineers. Prepare by practicing out loud, because interviewers judge your reasoning as much as your final answer. Have stories ready about an incident, a hard bug, a review disagreement and a design you would change. The questions below are practice prompts written by TryHired around the work the occupation involves.

Practice

Software engineer questions to practice

Advice
  1. Sketch the design of a service that shortens long links and redirects visitors. Where would it break first under heavy traffic?

    Start with the requirements you would confirm out loud: reads versus writes, how long links live, whether analytics matter. Then draw the pieces: an API, an id generator, a store, a cache in front of reads. The 'where does it break' part is the real test. Name a bottleneck, such as hot keys or id collisions, and the trade-off you would accept to fix it.

  2. Tell me about a production incident you were part of. What did you change afterwards?

    Pick one you can describe honestly: how it was noticed, what you checked first, how it was mitigated, and the follow-up that stopped it happening again. Engineers who describe a blameless review and a concrete fix, such as an alert or a test, score better than heroics.

  3. How do you decide what to test, and at which level?

    Explain your reasoning, not a slogan. Unit tests for logic with many edge cases, integration tests where components meet, a few end-to-end checks for the paths users cannot lose. Give one example of a bug a test caught, or one you wish you had tested.

  4. Walk me through a pull request you reviewed where you pushed back. How did it end?

    Show judgment and tone together: what you flagged (correctness, readability, risk), how you phrased it, and whether you changed your mind after the author explained. Reviews are collaboration, so a story where you were persuaded is fine.

  5. A feature request arrives that would add a lot of complexity for a small gain. What do you do?

    Interviewers want to see that you engage with the goal behind the request. Describe asking what problem it solves, proposing a simpler option, and making the cost visible to whoever decides. Close with what you would build if the answer was still yes.

  6. Given a slow endpoint, how would you find out why?

    Talk through measurement before guessing: reproduce it, look at timings or traces, check the database queries, then form a hypothesis and test one change at a time. Mention how you would confirm the fix and keep it from coming back.

  7. What is a technical decision you made that you would make differently now?

    Choose a real decision with a real cost, explain what you knew at the time, what changed, and what you learned about making that kind of call. Self-awareness is the point.

  8. How do you keep a large codebase understandable for the next person?

    Concrete habits beat principles: naming, small functions where they help, comments that say why, docs next to the code, and deleting dead paths. Give one example of leaving code clearer than you found it.

Data

What the work involves, and so what interviews probe

Data

O*NET lists core duties for software developers that include analyzing user needs and requirements to judge whether a design is feasible, developing or directing testing and validation, conferring with analysts and engineers on system limits and interfaces, and modifying existing software to fix errors or improve performance.

That maps neatly onto interview rounds: requirements and design questions, testing and debugging questions, and collaboration questions. Prepare for all three, not only the coding round.

Method

How to handle a system design question

Advice

Spend the first minutes on requirements and scale, then draw the simplest design that works, then stress it. Say your assumptions out loud and invite the interviewer to change them. Name trade-offs plainly, for example consistency against speed, or cost against redundancy, and pick one with a reason.

Common traps are diving into a database choice before knowing the read and write pattern, and drawing every component you have heard of. A clear, smaller design you can defend beats a crowded diagram.

Method

How to handle a coding question

Advice

Restate the problem, ask about edge cases, and describe a plan before typing. Write readable code, run through an example by hand, then improve it. If you get stuck, say what you are trying; interviewers can only give hints to a candidate who is thinking out loud.

Practice in the language you are strongest in, and know its standard collections and their costs well enough to explain your choice.

Advice

Questions to ask the interviewer

Advice
  • How does code get from a pull request to production here?
  • What happens after an incident, and who joins the review?
  • How are technical decisions made and written down?
  • What would a strong first quarter look like for this role?

Practice a short introduction with the elevator pitch generator, and refresh your resume with the software engineer resume guide and the resume summary generator. They use only the details you enter.

FAQ

Common questions

What should I study for a software engineer interview?
Data structures and algorithms in your strongest language, the basics of system design, and stories about incidents, bugs, reviews and decisions from your own work.
Do junior software engineers get system design questions?
Some do, usually lighter ones. Even then, show that you ask about requirements first and can explain the trade-offs in a simple design.
How do I answer when I don't know the solution?
Say what you do know, try a simpler version of the problem, and keep talking through your reasoning. A clear partial approach is better than silence.
Method

How this page is built

Practice questions are original to TryHired and organized around O*NET's task list for software developers.

What this page can't tell you
  • What a particular employer will ask: we don't know, and we don't claim to.
  • Your answers: build them from your own work.
Sources
  1. O*NET 31.0, Software Developers (15-1252.00), U.S. Department of Labor, Employment and Training Administration, used under the CC BY 4.0 license. TryHired selected and combined the data; O*NET is not responsible for this page.
Keep exploring

More for Software Engineers

More careers

Similar careers to explore