L3 Software Engineer (New Grad) Interview Prep
New grad / entry-level prep for Google's SWE loop, calibrated to L3 expectations.
About this loop
Google's L3 is the entry-level SWE rung - new grads, recent bootcamp finishers, and engineers with under two years of experience. The loop drops the system design round (you get a lighter, optional version at most) and weights coding more heavily: typically two to three coding rounds plus a Googleyness round. The coding bar is high but the difficulty is more bounded than at L4 - expect Medium problems with one or two clean follow-ups, not Hard problems with chained optimizations. The Googleyness round still matters at L3 - they're screening for engineers they'd want to grow into the L4 ladder, not just close-to-graduation interns. Practice talking out loud, ask clarifying questions before coding, and have 4-5 STAR stories ready (school projects, internships, side projects all count at L3).
The interview loop
- 1Recruiter screen30 minutes. Background, university timeline, motivation. Light technical at most.
- 2Phone screen (technical)45 minutes, one coding question. Algorithms or data structures, Medium difficulty. Expect at least one follow-up probing depth.
- 3Onsite: Coding round 145 minutes, one to two algorithmic problems. Strings, arrays, hash maps, basic trees. Edge cases evaluated explicitly.
- 4Onsite: Coding round 245 minutes, second coding round with a different interviewer. Often a graph, BFS/DFS, or recursion problem.
- 5Onsite: Coding round 3 (sometimes)45 minutes. Some L3 loops include a third coding round in place of system design. May skew problem-solving / open-ended over algorithmic.
- 6Onsite: Googleyness & leadership45 minutes. Structured behavioral. School projects, group work, conflict, learning from failure. STAR format scored.
What Google actually evaluates
- →Working code with edge cases handled before being asked
- →Clear narration of your approach - silent coding scores poorly even at L3
- →Asking clarifying questions before jumping into code
- →Honest 'I don't know' when applicable - confident BS gets flagged
- →Curiosity and willingness to learn (Googleyness, scaled to a new-grad bar)
- →Solid CS fundamentals: complexity analysis, recursion, basic data structures
Topics tested
Algorithms
Two to three coding rounds focus here. Mostly Medium difficulty. Strong coverage of arrays, strings, hash maps, two-pointer, sliding window, basic DP.
Data Structures
Trees, graphs, hash tables, stacks, queues. Tree traversals (in-order, BFS, DFS) come up constantly. Know them cold.
Behavioral
Googleyness still scored at L3. Prepare 4-5 STAR stories from school projects, internships, side projects, or part-time work. Specific incidents beat generic 'I'm a hard worker' answers.
Object-Oriented Design
Sometimes appears in a coding round (parking lot, library system). Lighter expectation than at L4 - clean class boundaries are enough.
System Design
Not always required at L3. If it shows up, expect a very bounded design (URL shortener, basic chat) with the interviewer guiding more actively than at L4.
Databases
Rarely standalone at L3. Knowing SQL basics, indexes, and normalization is enough.
System design topics tested in this loop
Curated walkthroughs for the bounded designs that show up in Google's system design rounds. Capacity estimation, architecture, deep-dives, and trade-offs.
URL Shortener
MediumThe canonical bounded system design problem. Read-heavy, hot-key prone, and a great vehicle for hashing, caching, and capacity estimation.
Chat
HardLong-lived connections, ordering guarantees, presence, and the difference between 1:1 chat and a 50K-member group.
Rate Limiter
MediumFive algorithms, three sharding strategies, one fail-open vs fail-closed decision. The bounded design that surfaces in every backend interview loop.
Behavioral themes tested in this loop
Sample STAR answers, common prompts, pitfalls, and follow-up strategies for the behavioral themes that decide Google's loop.
Googleyness
GoogleNot a soft round. Structured questions about collaboration, ambiguity, learning, and motivation - scored against rubrics, not vibes.
Learning from Failure
MicrosoftMicrosoft's Growth Mindset core. Also tested at Google, Anthropic, and any company that screens for self-awareness. The signal is whether you actually changed.
Ambiguity
GeneralTested at Google, Anthropic, OpenAI, and any senior+ loop. Strong candidates show how they get curious; weak candidates show how they get anxious.
Compensation at Google BETA
Total comp ranges, base, equity, and bonus across the levels tested in this loop. Aggregated from public sources.
Google compensation by level
5 SWE levels covered. Updated 2026-04-29.
Curated practice questions
333 MCQs and 100 coding challenges, grouped by topic. Free preview shows question titles - premium unlocks full content.
Algorithms · 77 MCQs
Browse all in Algorithms →Data Structures · 44 MCQs
Browse all in Data Structures →Behavioral · 63 MCQs
Browse all in Behavioral →Object-Oriented Design · 32 MCQs
Browse all in Object-Oriented Design →System Design · 68 MCQs
Browse all in System Design →Databases · 49 MCQs
Browse all in Databases →Algorithms - Coding challenges · 71 challenges
Browse all coding challenges →Data Structures - Coding challenges · 29 challenges
Browse all coding challenges →Practice in mock interview format
Behavioral and system design rounds reward practice with a live AI interviewer that probes follow-ups, not silent reading.
Start an AI mock interview →Frequently asked questions
Do I need to know system design as a new grad?
Not deeply. Most L3 loops skip system design or include a very bounded version (URL shortener, basic chat) where the interviewer guides actively. You should know caching, load balancing, and database basics at a vocabulary level - enough to follow along - but you won't be expected to drive a full design conversation.
How is L3 hiring different from internship hiring?
Internship interviews are typically one technical round (45 minutes, one or two problems) plus light behavioral. The L3 full-time loop is significantly heavier - 3-4 onsite rounds with the same coding bar but more total signal expected. Many former Google interns get fast-tracked through a shortened L3 loop.
What counts as a STAR story for a new grad?
School projects (especially group projects), internships, hackathons, side projects, club leadership, part-time work, even significant volunteer work. Pick stories where you had a real role and a real outcome. 'I led a team of 4 in our database systems class to build X, which got Y grade and taught us Z' is fine. Generic 'I'm passionate about Google' answers score poorly.
How do I prepare without prior internship experience?
Build something real and ship it. A side project with users, a published open source contribution, or a substantive academic project all give you concrete material for behavioral stories. Combined with strong LeetCode practice (focus on Medium with thoughtful follow-ups), it's a viable path. Recruiters at Google know not every L3 candidate has FAANG internships.
What is the L3 to L4 promo timeline?
Typically 2-3 years of strong performance. L3 to L4 is the easiest promo step at Google because L4 is the 'expected end state' - Google does not promote from L3 to L4 expecting it; they expect it. Engineers who plateau at L3 for 4+ years often face PIP risk. The bar shifts at L5 (Senior) where many engineers career-stall.
Can I retry if I get rejected as a new grad?
Yes. Standard cooldown is 6-12 months. If you were close, the recruiter will sometimes give pointed feedback on which round was the weak signal. Many engineers get hired on attempt two or three after gaining post-graduation experience.