What does a software engineer do?

A software engineer designs, builds, tests and maintains software. The Bureau of Labor Statistics says software developers "design computer applications or programs," and its duties list starts with analyzing users' needs and then designing software to meet them. Testing, maintenance and documentation are listed as part of the same job.

The BLS page on software developers, quality assurance analysts and testers, last modified August 27, 2026, gives a median pay for software developers of $135,980 per year in May 2025. It projects employment for the three jobs combined to grow 10 percent from 2025 to 2035, "much faster than the average for all occupations."

O*NET OnLine's profile for Software Developers (15-1252.00) adds tasks such as modifying existing software "to correct errors, adapt it to new hardware, or upgrade interfaces and improve performance." Its top transferable skills are programming, judgment and decision making, systems analysis and complex problem solving. Those four skills map closely to the rounds most loops run.

In Canada, Job Bank files this work under NOC 21231, software engineers and designers. Its national summary page, modified September 24, 2026, lists a median wage of $56.49 an hour and says the occupation "usually requires a university degree." Job prospects there vary by province or territory.

How were these software engineer questions chosen?

They come from the job's published duties, mapped to the question each duty tends to produce. They do not come from a survey of real interviews, and no list here claims to be the most asked or to match what any named company asks. Use them to practise the skills each duty implies.

The IEEE Computer Society's SWEBOK Guide, now at version 4.0, splits the field into 18 knowledge areas, including software requirements, design, construction, testing and maintenance. The table uses the duties from BLS and O*NET and notes which of those areas each one draws on.

Duty (BLS and O*NET)Question it tends to produceWhat the interviewer is checking
Analyze users' needs and design software to meet them"How would you design a system that does X?"Whether you ask about users and limits before you draw boxes
Write and modify code to correct errors and improve performanceA live coding problem, then "can you make it faster?"Working code, clear naming, and whether you can reason about cost
Develop testing or validation procedures"How would you test what you just wrote?"Edge cases, failure paths and what you would automate
Confer with analysts, engineers and others to design systems"Tell me about a time you disagreed on a technical decision"How you argue with evidence and settle on a decision
Maintain software and document it for future upgrades"Tell me about the worst code you inherited"Whether you improve old code safely and leave notes behind
Determine system performance standards"How would you know this service is healthy?"Whether you define measurable targets before you build

Which behavioral questions should you expect?

Behavioral questions ask about past work, so answer them with one real project in STAR order: situation, task, action, result. Interviewers listen for your own part in a team effort, a decision you made with incomplete information, and what you changed afterwards. Keep each answer near two minutes and name the technology only where it matters.

The guide to the STAR method shows the structure in detail. These four questions follow from the duties in the table.

1. Tell me about a time you disagreed with a teammate on a technical approach.

What they listen for: the evidence you used, whether you listened to the other side, and how the decision got made. A good answer ends with the team moving forward, even if your idea lost.

Made-up example answer. Situation: our team needed a cache for a slow reporting endpoint, and a teammate wanted to add a new caching service. Task: I was the engineer on the endpoint and thought a database index might be enough. Action: I asked for one day to test my idea, measured the query before and after the index on a copy of production data, and shared the numbers in our design doc with both options laid out. Result: the index alone brought the response time inside our target, so we skipped the new service for now and wrote down the load at which we would revisit it.

2. Tell me about a bug you shipped to production.

What they listen for: ownership, how you found the cause, and what you changed so it would not recur. Blaming the reviewer or the tests is the answer that hurts most.

3. Describe a project where the requirements changed halfway through.

What they listen for: how you found out, what you asked the product owner, and how you cut or re-planned work. The page on competing priorities covers the wider version of this question.

4. Tell me about code you inherited and improved.

What they listen for: whether you added tests before changing it, how you kept it working for users, and what you documented. BLS lists documentation "as a reference for future maintenance and upgrades" as part of the job.

What role-specific software engineer questions come up?

Role-specific questions test the work itself: a coding problem, a design discussion and a review of real or sample code. Interviewers check whether you clarify the problem first, talk through your reasoning, and test your own answer. Saying what you would trade away, such as memory for speed, matters as much as reaching a solution.

5. Walk me through how you would solve this coding problem.

What they listen for: questions about inputs and edge cases before you type, a simple working version first, and then an improvement. Say the time and space cost of each version out loud.

Made-up example of thinking out loud: "Before I start, can the input list be empty, and can it contain duplicates? I'll write the simple version that checks every pair first, which is quadratic. Then I'll try a hash set to get it to one pass, at the cost of extra memory. Let me test it with an empty list, one item, and a list where the answer is the last pair."

6. Design a URL shortener, a rate limiter or a notification service.

What they listen for: who uses it, how much traffic, what happens when a part fails, and which piece you would build first. A clear diagram with named tradeoffs beats a crowded one.

7. How would you test the function you just wrote?

What they listen for: normal cases, boundaries, bad input and failure of anything it depends on. Mention which tests you would automate and run on every change.

8. What do you look for when you review someone else's code?

What they listen for: correctness, readability, tests and whether the change fits the system. Google's published code review standard says reviewers should favor approving a change once it "definitely improves the overall code health of the system," and adds that "there is no such thing as 'perfect' code."

9. How do you decide when code is good enough to ship?

What they listen for: a link between quality and risk. A payment flow and an internal script deserve different bars, and you should say who you check with.

Which situational questions test judgment?

Situational questions describe a problem you have not faced yet and ask what you would do. Interviewers want an order of steps: protect users first, gather facts, tell the right people, then fix and follow up. Say what you would ask before acting, because a confident answer with no questions often signals guessing.

The guide to situational interview questions explains how these differ from behavioral ones.

10. Production goes down an hour after your deploy. What do you do?

What they listen for: rolling back or turning off the change first, telling the on-call channel, and only then looking for the cause. A short written review afterwards shows you learn from it.

Made-up example answer: "First I'd check whether my change lines up with the start of the errors. If it does, I'd roll it back or switch off its feature flag, and post in the incident channel what I did and when. Once users are safe, I'd find the cause on a copy of the data, add a test that fails on the bug, and fix it. Then I'd write a short review of how it got past our checks."

11. A product manager asks for a feature by Friday that you think needs two weeks.

What they listen for: a smaller version you could ship by Friday, the risk of rushing the rest, and a clear message to the person who asked. The page on what to do when you disagree with your manager has wording that fits here too.

12. You find a security flaw in a teammate's merged code.

What they listen for: reporting it through the right channel quickly, without blame, and helping fix it. Keeping quiet to protect a colleague is the answer that fails.

What follow-up questions tend to come next?

Follow-ups test whether your first answer holds up under detail. Expect the interviewer to change one condition, ask for numbers you used, or ask what you would do differently now. Prepare by asking yourself "why" twice about every story, then trimming the answer so the follow-up has somewhere to go.

  • "What would change if traffic grew ten times?"
  • "How did you measure that the change worked?"
  • "What did your teammate say when you disagreed?"
  • "If you had one more week, what would you add?"
  • "Which part of this were you personally responsible for?"

How should you prepare for a software engineer interview?

Pick four or five real projects and write one STAR story for each, so you can reuse them across behavioral questions. Practise coding out loud with a timer, because silence is hard for an interviewer to score. Read the posting again and match each listed skill to a story or a project you can describe.

The free interview question generator lets you paste the job and pick the round, and it returns likely questions, why they come up, and what the interviewer listens for. If you also interview for adjacent roles, compare this page with the questions for a data analyst, a product manager or a business analyst, since many teams interview engineers alongside those roles.

Before the loop, check that your resume bullets show results you can talk through. The guide to resume bullet points shows how. Prept's Mock room lets you answer out loud on a clock, scores each answer out of 10 and checks it against your resume, and it is included in the free plan.