Software developer interview questions: what each one tests, and how to answer from your own code.
Original practice prompts built around the developer work described in the parent guide's postings. We don't claim to know what any employer will ask.
A software developer interview tests whether you can write correct code, change existing code safely, reason about a design and work well with other developers. Prepare two or three changes you shipped that you can explain from ticket to production, practice solving a problem out loud, and be ready to talk about tests, code review and debugging. The prompts below are practice questions written by TryHired around the work the job involves; use them to rehearse, not to memorize.
Software developer questions to practice
- Walk me through a change you shipped, from the ticket to production.
Pick a real change of moderate size and tell it in order: what problem the ticket described, the code you read first, the approach you agreed with teammates, how you split the work into reviewable pull requests, the tests you added, and what you watched after release. End with one thing you would do differently. A clear, honest small story beats a vague big one.
- Here is a function with a bug and no tests. How would you fix it safely?
Say that you would first write a test that reproduces the bug, then make the smallest change that turns it green, then add tests for the edge cases nearby (empty input, boundaries, bad types). If the code is tangled, explain how you would add characterization tests before refactoring, so you can prove you did not change behavior you did not mean to change.
- You are reviewing a teammate's pull request. What do you look for, and how do you write the comments?
Cover correctness first (logic, error handling, edge cases), then tests, readability and naming, and whether the change fits the design of the surrounding code. On tone, explain how you separate blocking issues from suggestions and how you phrase a comment as a question or a concrete alternative. If you have changed your mind after a review discussion, say so.
- An endpoint became noticeably slower after the last release. How do you find out why?
Show a method, not a guess: confirm the regression with metrics, compare the releases to narrow the suspect commits, reproduce it, then profile to find where time goes (database queries, a new loop over large data, lock contention, a slow external call). Close with how you would stop it recurring, such as a benchmark or performance check in the pipeline.
- Design a feature that lets users export all their data as a downloadable file.
Clarify scope first: how much data, which formats, how fresh. Then sketch the parts: an API to request the export, a background job so the request does not time out, storage for the file, a notification when it is ready, and access control so only the owner can download it. Talk about what fails (a job that dies halfway, huge accounts, repeated requests) and how you would make the job safe to retry.
- A test in the CI pipeline fails now and then, with no code change. What do you do?
Treat it as a real bug, not noise. Explain how you would collect failing runs, look for shared state, timing assumptions, test ordering or external dependencies, and reproduce it by running the test repeatedly. Say what you would do while you investigate, such as quarantining the test with a ticket, so the team keeps trusting the pipeline.
- How do you get productive in a large codebase you did not write?
Describe your actual routine: run it locally, read the tests and entry points, trace one request end to end, and ask a teammate for the history behind odd parts. Mention a first small change you shipped to learn the review and release process.
- Tell me about a time you disagreed with a teammate about a technical approach.
Use a real disagreement and keep it about the work: the two options, the trade-offs (speed, risk, maintenance), how you tested or measured the question, and how the decision was made. A strong answer shows you can disagree, commit to the decision and keep the working relationship healthy.
- Solve this coding problem while talking through your thinking.
Restate the problem and confirm the inputs and outputs, work one small example by hand, say a simple solution and its cost before optimizing, then write clean code and test it against your example and an edge case. If you get stuck, say what you are trying; silence is harder to assess than a wrong first idea you then correct.
What the job involves, and so what interviews probe
One of the parent guide’s postings describes a company that code-reviews every change and decides big things by consensus, so be ready to explain how you give and take review feedback.
A developer-experience posting describes scaling CI pipelines across thousands of daily builds and managing pre-merge checks and test executions, the kind of work behind questions on tests and flaky builds.
A performance posting describes profiling system behavior to find bottlenecks and keeping benchmarks and regression detection in place, the skills a “why is this slower” question checks.
A principal posting describes improving a cloud service’s reliability, availability and scalability and making decisions on product architecture, which is what a design question explores at a smaller scale.
A prep plan for developer interviews
Pick the language the posting names and solve a handful of practice problems in it out loud, timing yourself and writing tests for your own answers. Review the core data structures you reach for every day, such as lists, maps, sets and queues, and be able to say why you chose one.
Write down three stories with the same shape: a change you shipped, a bug you tracked down, and a review or design disagreement. For each, note the problem, what you did, how you checked it worked and what you changed afterwards. For language-specific practice, our Python, Java and JavaScript question pages go deeper.
Rehearse your introduction with the elevator pitch generator and tighten your resume with the resume summary generator. They use only what you enter.
Common questions
What do software developer interviews cover?
How do I prepare for a coding interview as a developer?
Are software developer and software engineer interviews different?
How this page is built
Duties are summarized from the employer postings sampled for the parent Software Developer guide; questions and guidance are original TryHired practice material. The sample skews toward senior and principal roles at software companies, so treat the duties as a picture of the work rather than of every level.
- What a specific employer will ask: these are practice prompts.
- Your answers: build them from your own code and projects.
- Robinhood, “Senior Software Developer, Developer Experience (DevX)” job posting, read Nov 14, 2026. Posting
- Elastic, “Principal Software Developer - Performance Tuning - Elasticsearch” job posting, read Nov 14, 2026. Posting
- Elastic, “Principal Software Developer - Query Engine, Database Internals - Elasticsearch” job posting, read Nov 14, 2026. Posting
- Zscaler, “Principal Software Development Engineer” job posting, read Nov 14, 2026. Posting
More for Software Developers
What the job is, how to get in and how to get hired.
Open →ResumeSoftware Developer resumeKeywords, bullets and a checklist.
Open →SkillsSoftware Developer skillsThe skills to prove, and how.
Open →Cover letterSoftware Developer cover letterWhat to say and how to structure it.
Open →