L3 / IC2 · 2–4 years
Software Engineer interview prep, what to expect
If you're heading into a Software Engineer loop, the shape is predictable at most tech companies: a recruiter screen, a technical phone screen, an onsite with two or three coding rounds, one system design round, and a behavioural / hiring-manager round.
The bar is technical correctness, code quality, and the ability to discuss trade-offs out loud. You'll be evaluated against an L3 / IC2 calibration, solid execution on bounded tasks, with some ownership over a feature or component.
Personalised version
This guide covers the general bar at Software Engineer. The Chrome extension runs the same prep on every JD you open, predicted questions for that company, voice practice with your AI coach on each answer, comp benchmark, gap analysis, plus cover-letter and intro drafts. Free to install with a preview on every posting; unlock the full report from $3.99. Or run a one-off scan on a single JD without installing.
2026 update
This guide covers the general bar at Software Engineer. A few things have changed in 2026, AI is now allowed in coding rounds at Canva and Meta, detection has improved at companies that still ban it, comp has split at staff+, and the post-onsite wait got longer. Read what changed in 2026 →
What you'll be expected to do
- Implement features end-to-end against a defined spec, with manageable scope
- Write tests, fix bugs, and respond to code-review feedback efficiently
- Participate in on-call rotations and incident response for your team's services
- Estimate work, break down tasks, and ship within a sprint cadence
- Collaborate with a tech lead or staff engineer on design decisions
Typical interview process
Most companies follow a similar shape for Software Engineer interviews. Total calendar time: 3–5 weeks from recruiter screen to offer.
Sample questions you should be ready for
Representative of what companies ask at this level, not a complete list. Run the free scan above for predicted questions tied to a specific job posting. The Chrome extension adds voice practice with AI coaching on every answer (technical, system design, behavioural, motivation).
- “Given a list of integers, find the longest subarray with sum equal to a target value.”
- “Implement an LRU cache. Walk through the data structure choices and trade-offs.”
- “Reverse a linked list iteratively. Then do it recursively. Compare space complexity.”
- “Design a URL shortener (bit.ly). Cover the encoding scheme, storage, and caching layer.”
- “Design a rate limiter. What algorithm, token bucket, sliding window, fixed window? Why?”
- “Design the back-end for an autocomplete service that handles 100k QPS.”
- “Tell me about a project you're proud of. What was your specific contribution?”
- “Describe a time you disagreed with a code reviewer. How did you resolve it?”
- “Tell me about a time you missed a deadline. What did you learn?”
Compensation benchmark
Median compensation for Software Engineer at major US tech companies, headline numbers in USD. Pay in markets like London, Berlin and Singapore tends to be meaningfully lower in base terms, and equity ratios vary by company stage.
FAANG L3 / Google L3 / Meta E3 / Amazon L4 / Apple ICT2. London Software Engineer median ~£60–80k base. Berlin / Stockholm ~€55–75k.
How to prep, five tactical tips
Lead behavioural answers with the STAR method, Situation, Task, Action, Result. The tactical tips below build on that structure for this specific role.
- Drill 100+ LeetCode mediums focused on arrays, strings, hashmaps, trees, graphs
- Practice talking through your approach BEFORE coding, interviewers grade communication
- Time yourself: optimal solution + edge cases + tests in 25 minutes
- For system design, master one canonical problem (URL shortener) cold, pattern-match the rest
- Prepare 5 specific past-project stories using STAR format, ready to redirect to any behavioural prompt
Where Software Engineer candidates fail
A few common mistakes that get Software Engineer candidates rejected even when they're otherwise strong. Worth spotting in a mock interview before they show up in a real one.
Hearing the problem, then jumping straight into typing code without asking any questions.
Why it fails
At L3 the bar isn't just "can you code". Interviewers are watching whether you scope the problem before solving it. Questions like "are inputs guaranteed sorted?" or "should this handle empty arrays?" are part of the grade. Skipping that step makes you look like someone who builds the wrong thing and has to redo it.
Fix
Take 30 seconds at the start to restate the problem in your own words and ask one or two clarifying questions. Even something simple like "should this be in-place or can I use extra space?" tells the interviewer you're thinking before doing.
Describing a project with no numbers, no users, no scale, no specific contribution.
Why it fails
Interviewers at L3 are calibrating against the IC2 bar, and they need something concrete to peg you against. "I built a feature for the dashboard" tells them nothing. "I built the export feature used by around 5k users a week and cut report-generation time from 30 seconds to under 2" lets them place you immediately.
Fix
Before the interview, write down 3-4 projects with three numbers each: scope, scale, impact. Rough numbers are fine. If you don't know the scale, ask your tech lead before the loop. The goal is to never get caught describing work in adjectives.
Telling the same polished success story for every behavioural prompt, including the ones asking about failure.
Why it fails
Interviewers want to see how you handle imperfect projects: bugs you caused, deadlines you missed, code reviews that taught you something. A loop where every story is a clean win signals either no self-awareness or no real experience. Both downlevel you.
Fix
Prep at least two stories about things that didn't go to plan: a bug you shipped that broke prod for 20 minutes, a feature you over-scoped and had to cut down, a code review where you defended bad code and were wrong. The recovery is the signal, not the original mistake.
Recommended resources
Books, courses, and tools that come up most often in Software Engineer prep. No affiliate links.
- 01LeetCode, Top 150 Interview Questions →The canonical practice list. Cover the array, string, hashmap, tree, and graph problems, most loops draw from this surface area.
- 02Cracking the Coding Interview (McDowell) →Reference text for the L3 bar. Data structures, algorithms, and the behavioural framework all worth re-reading.
- 03Grokking the System Design Interview →For the light system design round. Walk through URL shortener, rate limiter, and a chat feature cold before the loop.
- 04A Philosophy of Software Design (Ousterhout) →Short Stanford book on code hygiene. Pattern-match the deep-cut design questions on naming, complexity, and simple-vs-clever code.
- 05Designing Data-Intensive Applications (Kleppmann) →Worth starting now even at L3. Chapters 1–3 cover the foundation you'll keep referencing at every senior+ level.
Frequently asked questions
Is this guide useful if I'm a recent grad or self-taught?
Yes, the L3 / IC2 bar described here applies whether you came through a bootcamp, CS degree, or self-study. The interview tests skills, not credentials. The biggest delta for new grads is having 3–5 substantive past projects ready as STAR stories, the technical content of this guide applies regardless.
How long should I prep before my Software Engineer onsite?
The process itself takes 3–5 weeks from screen to offer. Add 4–6 weeks of prep if you've been heads-down at work; 2–3 weeks if you're actively practising. LeetCode mediums + 5 STAR stories is the priority order.
What's the most common mistake candidates make at the Software Engineer bar?
Coding in silence. Even with the correct answer, interviewers grade your thought process out loud. Narrate trade-offs, edge cases, and complexity as you go, that's the bar at L3 / IC2.
What if my interview process is different from what's listed?
Most variation is at the edges. Major tech companies (FAANG, scale-ups, mid-size SaaS) follow processes within 1–2 rounds of what's described. Smaller startups often run fewer rounds (3–4) but the bar at each round is similar; less-tech-mature companies sometimes skip system design or behavioural rounds entirely. Read the JD and ask the recruiter at the screen, they'll tell you what's coming.
How does this guide compare to running a free scan?
This guide covers the general bar at L3 / IC2. The free scan reads your specific job description and returns predicted questions for that exact role + company, a calibrated comp benchmark, and (with your CV) experience-gap analysis and an ATS resume check. PDF emailed.
Ready to prep for a real role?
Paste any Software Engineer JD, meet your coach in under 30 seconds.
Drop a LinkedIn, Greenhouse, Lever, or Levels.fyi link, or paste the JD text. Your coach predicts the questions for that company, surfaces your specific experience gaps, and calibrates a compensation benchmark to the role and location. PDF emailed to you. Voice practice with AI feedback on each answer lives in the Chrome extension.
Free to start · Free reports + first mock free · Paid plans from $3.99