Software engineer interview questions: 25 to prepare, by stage
Software engineer interview questions come in four stages: recruiter screen, coding, system design and behavioral. Below are 25 typical questions with notes on how to approach each, and a four-week plan to get ready.
What are the stages of a software engineering interview?
Formats differ by company and level, so treat this as a common shape and not a rule.
| Stage | What it covers | What they judge |
|---|---|---|
| Recruiter screen | Background, motivation, logistics, pay range | Fit, communication, clarity about what you want |
| Coding | One or two problems on data structures and algorithms | Problem solving, code quality, testing, communication |
| System design | Design a service or feature at scale | Trade-offs, structure, depth where it matters |
| Behavioral | Past teamwork, conflict, ownership | Judgment, collaboration, learning |
Some processes add a take-home task, a pair programming session or a code review exercise. Ask what to expect so nothing surprises you.
What are common interview questions for software engineers?
Common interview questions for software engineers fall into four groups: background (tell me about yourself, a project you built), coding problems on arrays, strings, hash maps and trees, system design for mid-level and senior roles, and behavioral questions about teamwork and mistakes. The lists below cover all four. In the UK, the last group is often called competency based questions, and employers ask for a CV rather than a resume.
Which software engineer interview questions does the recruiter ask?
This call is short, but it filters. Keep answers to about a minute.
- Tell me about yourself. Current role, one result, why this job. See tell me about yourself answers.
- Why are you looking to move? Stay positive and specific. Name what you want more of.
- What stack have you worked in most recently? Name languages, frameworks and the kind of system. Be honest about depth.
- What are you looking for in your next role? Tie it to the posting.
- What are your salary expectations? Research the range first and answer with a range, or ask what the budget is.
Which technical interview questions come up in coding rounds?
These technical interview questions are typical to prepare for. They are not a record of what one company asked. For each one, the approach note says where to start.
- Two sum: find two numbers that add to a target. Start with the nested loop, then improve with a hash map for one pass. Tests whether you reach for a hash map.
- Check whether a string is a valid palindrome or anagram. Clarify case and punctuation. Two pointers or a character count work. Tests edge cases.
- Reverse a linked list. Walk through pointers on paper first. Tests pointer care and testing on empty and one-node lists.
- Detect a cycle in a linked list. Fast and slow pointers. Say why it works.
- Validate balanced brackets. A stack. Tests choosing the right structure.
- Merge two sorted arrays or lists. Two pointers. Tests clean loops and ends of input.
- Find the longest substring without repeating characters. Sliding window with a set or map. Tests window logic.
- Traverse a binary tree (in order, level order). Recursion for depth, a queue for breadth. Tests comfort with trees.
- Count islands in a grid. Depth-first or breadth-first search with a visited set. Tests graph thinking in disguise.
- Design an LRU cache. A hash map plus a doubly linked list. Tests combining structures and stating time complexity.
- Climb stairs or make change (dynamic programming). Start with recursion, notice repeated work, then cache. Tests moving from brute force to optimized.
- Explain the time and space complexity of your solution. Say it in plain words, such as "one pass, so linear, with a map of the same size."
The same questions appear as software developer interview questions at smaller companies, often with a more practical flavor such as parsing a log file or building a small feature. For habits that help in all of them, see live coding interview tips and technical interview tips.
How should you approach a coding question?
- Clarify. Repeat the problem, ask about input size, duplicates and empty input.
- Give an example. Work one small case by hand.
- Say the brute force. Name it and its cost, then look for a better way.
- Code in small steps. Use clear names. Talk as you type.
- Test. Walk your code through your example, then an empty or edge case.
- State complexity. Time and space, and what you would change with more time.
Which system design questions are typical?
Mid-level and senior roles usually get one of these. Juniors may get a lighter version or none. Spend the first few minutes on requirements and scale before you draw anything.
- Design a URL shortener. Cover ID generation, storage, reads far above writes and caching. Tests the basics.
- Design a chat or notification system. Cover delivery, ordering, retries and fan-out. Tests trade-offs in messaging.
- Design a rate limiter. Cover token bucket or sliding window, where the counter lives and what happens on failure.
- Design a news feed or timeline. Compare computing the feed on write versus on read.
- How would you scale a service that is getting slow? Measure first, then caching, indexing, queues and horizontal scaling. Tests method over buzzwords.
A simple frame: requirements, rough numbers, a high-level diagram, data model, one deep dive, then failure and trade-offs. Say what you would pick and why.
Which behavioral questions do software engineers get?
Prepare stories with the STAR pattern. See STAR method interview examples and behavioral interview questions.
- Tell me about a project you are proud of. Pick one you can discuss in depth, including what you would change.
- Tell me about a disagreement with a teammate on a technical choice. Show you listened, used evidence and committed to the outcome.
- Tell me about a bug or outage you caused or fixed. Show calm, root cause thinking and what changed afterward.
Also be ready for how you give and take code review feedback, how you handle unclear requirements and how you learn a new codebase.
A sample answer: "Tell me about a bug you caused"
"At [company] I shipped a change to [service] that skipped a null check, and [number] requests failed before an alert fired. I rolled it back within [time], then wrote a short post-incident note: the cause, the gap in our tests and the fix. I added a test for that case and a check to our review template. Since then I look for what happens with empty input before I open a pull request."
Why it works: it owns the bug, stays calm and ends on a habit. Use a real incident and real figures, and never blame a teammate.
How do software engineer interview questions change by level?
The same four stages apply at every level. What changes is the weight. Juniors get more fundamentals, mid-level engineers get more ownership and design, and seniors get more judgment. These are general patterns, not any company's process.
Junior software engineer interview questions
This also covers freshers and new graduates, the term some countries use for people applying with no full-time experience. Expect fundamentals and learning ability. Typical questions: explain a project from a course or internship and your own part in it, what an array is compared with a linked list, what big-O means, how you debug a failing test, and how you use version control (branches, merges, a pull request). Coding rounds lean on easy and medium problems. Prepare one story about learning something fast.
Mid-level software engineer interview questions
Here the question is whether you can own a feature from start to finish. Typical questions: walk me through a feature you built and the trade-offs you made, how you review a teammate's code, how you estimate a task and what you do when it slips, and one smaller design prompt such as a rate limiter or a notification service. Bring a story about handling an unclear requirement.
Senior software engineer technical interview questions
Seniors still code, but the weight moves to design and judgment. Typical questions: design a service with scale, failure and cost in mind, describe a technical decision you later reversed, how you would plan a migration with no downtime, how you decide when to pay down technical debt, and how you lead a project across teams. Interviewers listen for trade-offs said out loud and for how you grow other engineers. Practice with the system design interview framework.
What mistakes cost the most?
The costly ones in a software engineer interview are claiming skills you lack, because anything on your CV can become a deep question, and answers you memorized that fall apart when the problem changes. The habits that lose points in the coding round (silence, skipping tests, ignoring hints) are in technical interview tips.
What should you ask the interviewer?
Good questions show you think like an engineer. Ask how the team ships and reviews code, how on-call works, what the first three months look like and what the team finds hardest right now. Avoid asking anything you could have found on their careers page.
How do you prepare in 4 weeks?
This is a general plan, not a guarantee. Adjust it to the time you have.
- Week 1: foundations. Review arrays, strings, hash maps, stacks, queues and big-O. Solve two or three easy problems a day in your interview language.
- Week 2: core patterns. Two pointers, sliding window, binary search, trees and graph search. Solve medium problems and write down the pattern each one used.
- Week 3: design and depth. Study basic system design: caching, databases, queues, load balancing. Do two design prompts out loud. Prepare your project walk-through.
- Week 4: simulate. Do timed mock interviews with a friend or a platform. Rehearse three behavioral stories. Review mistakes from earlier weeks and rest the day before.
Practice in the same editor, language and conditions you will face. Say your thinking out loud every time. It is a skill, and it feels odd until you have done it twenty times.
If you get stuck mid-answer
Practice is the real fix, and no tool replaces it. Check any employer rules on tools before a live interview. Hintly is a desktop app for Mac and Windows that listens during a call and shows a suggested answer in a small overlay, built from your own notes such as your CV or resume. A keyboard shortcut answers what is on your screen, such as a coding problem. The overlay is hidden from screen share. It is pre-launch, so you can join the waitlist. See the AI coding interview assistant page.
Questions
What are the most common software developer interview questions?
Tell me about yourself and a project, a coding problem on arrays or strings, a question on hash maps or trees, a system design prompt, and a behavioral question such as a time you disagreed with a teammate. The exact mix depends on the company and level.
How long should I prepare for technical interview questions?
Four weeks of steady practice, about an hour or two a day, is a workable plan for many people. Start earlier if you have not coded under time pressure in a while.
What are the 5 C's of interviewing?
There is no official list, and sources use the phrase for different checklists. A useful version for a coding round is clarify, code in small steps, check with a test, calculate complexity and communicate throughout. It matches the approach in this guide.
What is the 30-60-90 question in an interview?
It usually means: what would you do in your first 90 days? A modest engineer's answer is to learn the codebase and team habits in the first 30 days, fix small bugs and ship a small feature by day 60, and own a piece of work by day 90. Tie it to the job posting.
What if I get stuck on a coding question?
Say what you know, try a smaller example, and offer the brute force approach. Interviewers usually care more about how you reason and respond to hints than about a perfect first try.