New Grad SWE Interview: A 2-Week Plan

New Grad SWE Interview: A 2-Week Plan

A new grad SWE interview in two weeks is a triage problem, not a finish-the-curriculum problem. You will not learn every pattern. You can raise signal on the patterns that appear most, plus communication and one solid behavioral set.

This plan assumes ~3–5 focused hours per day. If you have less, cut volume—not sleep. If you have more time before the loop, stretch Week 1 patterns instead of adding random hard problems.

Outcomes to optimize

  1. Reliable easy→medium DSA with spoken complexity
  2. Freeze recovery habit (clarify → brute force → improve)
  3. 4 STAR stories (conflict, failure, teamwork, learning)
  4. Résumé fluency: every bullet explainable
  5. 2–3 timed mocks
  6. Logistics ready (accounts, environment, ID)

Week 1 — foundations and patterns

Daily template (≈4 hours)

BlockTimeFocus
Warmup20m1 easy you already know—narrate out loud
Core90m2 mediums in one pattern family
Review40mRe-solve yesterday’s miss cold
Behavioral30mOne STAR out loud
Light20mComplexity flashcards / edge-case checklist

Pattern order (Week 1)

DayPattern
1Arrays / hashing
2Two pointers / sliding window
3Stacks / intervals
4BFS / DFS on trees & grids
5Binary search (boundaries)
6Heaps / top-k
7Mixed review + 1 mock (45–60m)

Skip exotic DP topics until Week 2—and only if your mocks show need. Silent grinding without narration wastes the scarce resource: interview communication. After each medium, speak complexity and one edge case even if the code “worked.”

Week 2 — mocks, gaps, behavioral polish

DayFocus
8Mock #2 + gap list (max 3 topics)
9Gap topic A + behavioral set run-through
10Gap topic B + system design lite (if required)
11Gap topic C or rest-of-patterns triage
12Mock #3 (full loop simulation if possible)
13Light review + story polish + logistics
14Rest / light warmup only—do not cram new topics

Cap your gap list at three topics. A long gap list is how candidates panic-cram and arrive exhausted. Prefer re-solving missed problems cold over collecting new bookmarks.

Communication rules (every problem)

  1. Restate + ask 2 clarifying questions
  2. Brute force first in one sentence
  3. Optimize with a named idea
  4. Complexity before coding deep
  5. Dry-run one example + an edge

Talk track when stuck:

“I’m going to lock a correct O(n²) approach, then see if hashing gets me to expected O(n).”

Behavioral minimum set for new grads

Internship and project stories count. Use:

STAR with long Action—even if the “org” was a class team. Course projects are fine when Action is specific (you owned the API, you wrote the load test, you resolved the git conflict process). Avoid “we built an app” with no personal verbs.

What to cut without guilt

Company-flavored add-ons

If loop includes…Add
OA only firstTimed OA pacing drills
System design for new grad2 sessions: capacity + API basics
Hiring manager chatWhy-this-team + internship deep dive
Take-homeCalendar block + README quality pass
Pairing roundPractice thinking aloud with a friend

Energy and logistics

Soft practice note

Two-week ramps fail when practice is silent. If you want a Chrome side panel to rehearse narration and freeze recovery while you grind patterns, Luna Interview is built for calm, structured practice—not for skipping learning or for violating interview rules.

Day-of checklist (interview morning)

Triage ruthlessly—then show clear thinking under time.