1
Recruiter Screen
Whether your motivation, role fit, and logistics line up before the loop invests real engineering time.
Be concrete on motivation, keep logistics tight, don't leave interest ambiguous.
Prep for your role
Software Engineer Interview Prep
SWE loops test a specific set of skills across distinct rounds. Know what each round is grading, bring the right structure, and practice the parts that break under pressure.
A software engineer interview usually spans five stages: a recruiter screen, a coding screen testing LeetCode-medium problems under time pressure, system design for scale and trade-offs, onsite coding rounds that probe LeetCode-hard problems and code clarity, and a behavioral round. The behavioral round rewards structure, so STAR is the highest-leverage prep.
1644
companies with real interview data
5
interview rounds, decoded
8
real questions shown below
Watch the Software Engineer interview breakdown
A short video walkthrough of the rounds, the questions companies really ask, and what a strong answer sounds like.
Eighty-one percent of the companies in our bank interview software engineers. Counted across 101,000+ real interview questions from 1,900+ companies, by role and round. Measured, not surveyed. Chapters: 0:00 The Software Engineer interview 0:10 Where the questions come from 0:39 The Software Engineer interview: Same shape everywhere 0:54 Coding Screen · Algorithmic: a real question 1:26 System Design · System Design: a real question 1:59 Onsite Coding · Code Clarity: a real question 2:29 The danger zone 2:46 Get the full guide
The five SWE rounds, decoded
2
Coding Screen
Whether you can solve a LeetCode-medium algorithmic problem cleanly under real time pressure.
Clarify constraints out loud, state your complexity, test edge cases before you call it done.
3
System Design
How you reason about distributed systems, trade-offs at scale, and architecture under real constraints.
Name the trade-offs explicitly, state scale and latency assumptions, commit to a design.
4
Onsite Coding
Whether you can solve a LeetCode-hard problem while reasoning about defects, code clarity, and edge cases out loud.
Narrate defects as you spot them, keep edge cases explicit, don't rely on a silent solve.
5
Behavioral / Leadership
Whether you can back up ownership, influence, and conflict resolution with real, specific evidence.
Real software engineer interview questions, from real companies
Pulled directly from our corpus of researched interview loops - not invented for this page.
Type · Behavioral
Why Google? Tell me about a time you demonstrated 'Googleyness' by putting the user first or helping a teammate without being asked.
See all Google SWE questions
Meta
Type · Algorithms
Find the $k$ closest points to the origin $(0,0)$ given a list of points on a 2D plane.
See all Meta SWE questions
Netflix
Type · System Design
Design the Netflix backend architecture to support global video streaming for 200M+ users.
See all Netflix SWE questions
Amazon
Type · Algorithms
Warehouse Robot Pathfinding: Given a 2D grid representing a warehouse with obstacles, find the shortest path for a robot to travel from point A to point B.
See all Amazon SWE questions
Apple
Type · Behavioral
Tell me about a time you had to maintain a high bar for quality under a very tight deadline.
See all Apple SWE questions
ByteDance
Type · motivation
ByteDance operates in the fast-paced media and content space. What specifically about our products (like TikTok, Douyin, or Toutiao) and the challenges of scaling them excites you as a Software Engineer?
See all ByteDance SWE questions
Goldman Sachs
Type · Motivation
Why are you interested in a software engineering role at Goldman Sachs, and what aspects of our work in financial technology particularly appeal to you?
See all Goldman Sachs SWE questions
J.P. Morgan
Type · motivation
Why does the transition from monolithic legacy banking systems to microservices architecture at J.P. Morgan specifically interest you as an engineer?
See all J.P. Morgan SWE questionsBehavioral rounds run on STAR
SWE behavioral rounds are where strong engineers most often lose an otherwise-winning loop, because they ramble or give credit-vague answers instead of a clear account of what they actually did. STAR turns 'tell me about a time' into a structured, gradeable answer: Situation, Task, Action, Result.
Read the full STAR framework guidePrep for the company you are actually interviewing with
SWE bars differ sharply: some companies grind LeetCode-hard rounds, others lean on a take-home project, and some weight system design above everything else. Browse real SWE questions and the round structure for real companies.
Browse SWE interview guides by companySWE interview FAQ
What does a software engineer interview involve?
Most SWE loops run a recruiter screen, a coding screen (LeetCode-medium problems under time pressure), a system design round for mid-to-senior candidates, one or more onsite coding rounds (LeetCode-hard problems plus code-quality and edge-case reasoning), and a behavioral round.
What is the best way to prepare for coding-screen and onsite rounds?
Practice out loud, not silent reading. Talk through your approach, state your time and space complexity, and walk through edge cases before you call a solution done, since a correct answer delivered in silence still reads as weak communication in a live loop.
How deep should system design prep go?
Match the depth to the level you are targeting. Junior loops rarely include a dedicated round at all, mid-level candidates need to reason clearly about one service's trade-offs, and senior candidates are expected to design a multi-component distributed system and defend scale, consistency, and cost decisions under questioning.
How do I prepare for a SWE behavioral interview?
Prepare 6 to 8 STAR stories covering ownership, a technical disagreement you navigated, a production incident, and a time you influenced a decision without formal authority. SWE behavioral rounds especially probe how you handle ambiguity and conflict on a team.
How should I practice for a SWE interview?
Rehearse coding and behavioral answers out loud against a timer, since structure and clarity under pressure are exactly what gets graded. A voice mock interview can pose a coding-screen or behavioral prompt and score whether your explanation stayed clear and complete.
More role interview guides
Product Manager Interview PrepSupply Chain & Operations Interview PrepSales Interview PrepMarketing Interview PrepInvestment Banking Analyst Interview PrepConsulting Case Interview PrepTechnology Consulting Interview PrepBrand Manager Interview PrepCustomer Success Manager Interview PrepSolutions Architect Interview Prep
Clean reasoning under pressure is a muscle. Train it out loud.
Run a free voice mock interview and practise talking through a coding or behavioral prompt in real time, with feedback on whether your reasoning stayed clear.
Start a free mock interviewNext step in your career strategy
You've got the resume. Now build the stories that back it up.
Interview
Go to Interview Prep