Software Engineer interview questions in the US
Last updated August 2026 · Written by the HappyHire team
Short answer
Software Engineer interviews in the US typically run through 5 stages, from a recruiter screen to a final interview, and are structured around STAR, delivered with the Result first if you can manage it. Expect questions such as "Walk me through a system you designed end to end." and "Tell me about a production incident you caused or resolved." The assessment stage is where the role is really decided: a live coding round of 45–60 minutes on data structures and algorithms, or a take-home exercise of a few hours, followed by a system design round for anyone above entry level. Talking continuously while you code is scored — silent correctness frequently loses to narrated near-correctness. The single most common reason qualified candidates are rejected is narrower than most people expect: describing what the team shipped instead of what you personally built. Interviewers cannot level a candidate they cannot locate in their own story.
The questions software engineers actually get asked
These six come up in almost every software engineer process, in the US and elsewhere. What differs by country is not the question but the delivery — covered further down. The right-hand column is the part most preparation guides leave out: what the interviewer is scoring while you answer.
| Question | What the interviewer is scoring |
|---|---|
| Walk me through a system you designed end to end. | Whether you can hold a whole system in your head — data model, failure modes, what you traded away and why. Candidates who only describe the happy path get levelled down. |
| Tell me about a production incident you caused or resolved. | Ownership without defensiveness. The strongest version names the mistake plainly, describes the fix, and ends with the guardrail you added so it could not recur. |
| How do you decide when a piece of code needs a test? | Judgement rather than dogma. 'Everything gets tested' and 'we move too fast for tests' are both weak; the interviewer wants your actual risk calculus. |
| Describe a time you disagreed with a technical decision. | Whether you can dissent and then commit. The ending matters more than the argument — what happened after the decision went against you. |
| How would you scale this feature to a hundred times the traffic? | That you ask about the bottleneck before answering. Jumping straight to caching or sharding without establishing what breaks first is the single most common miss. |
| What have you learned recently, and how? | Genuine curiosity and a real mechanism. Naming a specific thing you built badly, then rebuilt, beats naming a course you watched. |
The mistake that costs software engineers the most offers: Describing what the team shipped instead of what you personally built. Interviewers cannot level a candidate they cannot locate in their own story.
How an American interview process is structured
Fast, enthusiastic and heavily behavioural, with far more rounds than most countries. Energy is read as interest; a flat delivery is read as not wanting the job, even when the content is excellent.
A typical software engineer process in the US runs through these stages:
- Recruiter screen, 20–30 minutes, including work authorisation and compensation expectations
- Hiring manager screen
- Technical screen, take-home exercise or case study
- An 'onsite' loop — typically four to six back-to-back interviews, now usually over video
- Reference and background check after a verbal offer
The assessment stage for this role specifically: A live coding round of 45–60 minutes on data structures and algorithms, or a take-home exercise of a few hours, followed by a system design round for anyone above entry level. Talking continuously while you code is scored — silent correctness frequently loses to narrated near-correctness.
How to structure your answers in the US
STAR, delivered with the Result first if you can manage it. US interviewers reward candidates who lead with the outcome and then explain how they got there. Ownership language is essential: 'I owned', 'I drove', 'I decided'. What reads as boastful in much of Asia and Northern Europe reads as normal competence here.
The delivery norms below are where internationally experienced candidates lose interviews they were qualified for — not on the content of the answer, but on how it lands in the US.
- Self-promotion is the baseline expectation, not a personality flaw. Understating your contribution does not read as humble — it reads as junior.
- 'Tell me about yourself' is a pitch, not a biography. Ninety seconds, present role, relevant proof, why this job.
- Interviewers expect visible enthusiasm about the specific company. Generic answers about 'a great opportunity' land badly.
- Following up with a thank-you email within 24 hours is a genuine convention, not a nicety, and its absence is noticed.
Work authorisation, and when it comes up
Every application asks two questions: are you legally authorised to work in the US, and will you now or in future require sponsorship. Many companies filter automatically on the second. Students on OPT have a window of unsponsored work and should say so explicitly — it changes a recruiter's calculation entirely.
| Route | What it means for you |
|---|---|
| OPT / STEM OPT | Post-study work authorisation for F-1 students, extended for qualifying STEM degrees. No employer sponsorship required, which makes you meaningfully cheaper to hire. |
| H-1B | The main specialty-occupation route. Employer-sponsored and subject to an annual lottery, so timing dominates strategy. |
| L-1 | Intra-company transfer. If your current employer has a US entity, this is often the fastest realistic path. |
| O-1 | For individuals with extraordinary ability. Evidence-based rather than lottery-based, and more attainable than its name suggests. |
Rules and thresholds change regularly, so check the current position at uscis.gov and travel.state.gov rather than relying on any guide, including this one.
Getting to the interview in the first place
In the US the document is a resume. 'CV' means specifically an academic curriculum vitae — long, publications-first — and is used only for university, research and some medical roles. Sending a two-page European-style CV to a US corporate recruiter signals unfamiliarity before they read a word. One page is the strong default under roughly ten years of experience. Two pages is acceptable for senior and technical profiles; beyond that you are asking a recruiter for a favour.
Applicant tracking systems screen on vocabulary before a human reads anything. For software engineer roles in the US, mirror the wording of the advert and make sure these terms appear naturally in your experience section where they are true of you:
- software engineer · backend · frontend · full stack · Python · Java · JavaScript · TypeScript · React · Node.js · SQL · REST API · microservices · AWS · Docker · Kubernetes · CI/CD · unit testing · Git · Agile
Beyond the CV, the evidence that moves a software engineer application forward is specific: A GitHub profile with at least one repository that has a real README, or a deployed project with a URL. For engineers whose best work sits behind an employer's firewall, a written architecture summary works as a substitute.
One detail that quietly costs applications: use American spelling — organize, analyze, program, center, specialized.
The salary conversation
Compensation is discussed early and openly, and is quoted as a total package — base, bonus, equity. A growing number of states require a pay range in the advert. Several states and cities prohibit asking your salary history, so you can decline that question without friction; give a target range instead.
References and background checks come after a verbal offer. Notice periods are short — two weeks is the norm — and employers expect fast starts, so a three-month overseas notice period is worth flagging early.
Frequently asked questions
How many interview rounds should a software engineer expect in the US?
5 stages is typical: recruiter screen, 20–30 minutes, including work authorisation and compensation expectations; then hiring manager screen; then technical screen, take-home exercise or case study; then an 'onsite' loop — typically four to six back-to-back interviews, now usually over video; then reference and background check after a verbal offer. A live coding round of 45–60 minutes on data structures and algorithms, or a take-home exercise of a few hours, followed by a system design round for anyone above entry level. Talking continuously while you code is scored — silent correctness frequently loses to narrated near-correctness.
What is the biggest difference between interviewing in the US and interviewing elsewhere?
Self-promotion is the baseline expectation, not a personality flaw. Understating your contribution does not read as humble — it reads as junior. STAR, delivered with the Result first if you can manage it. US interviewers reward candidates who lead with the outcome and then explain how they got there. Ownership language is essential: 'I owned', 'I drove', 'I decided'. What reads as boastful in much of Asia and Northern Europe reads as normal competence here.
Will employers in the US sponsor a software engineer?
Every application asks two questions: are you legally authorised to work in the US, and will you now or in future require sponsorship. Many companies filter automatically on the second. Students on OPT have a window of unsponsored work and should say so explicitly — it changes a recruiter's calculation entirely. The routes worth knowing by name are OPT / STEM OPT, H-1B, L-1, O-1. Check the current requirements at uscis.gov and travel.state.gov.
What should I ask at the end of a software engineer interview in the US?
Ask something only this employer can answer — how the team decides priorities, what happened to the last person in the role, what would make the first six months a success. Questions you could have asked any company signal that you are running a process rather than pursuing this job. Interviewers read the absence of questions as a lack of interest.
How do I talk about salary as a software engineer in the US?
Compensation is discussed early and openly, and is quoted as a total package — base, bonus, equity. A growing number of states require a pay range in the advert. Several states and cities prohibit asking your salary history, so you can decline that question without friction; give a target range instead.