What to prioritize
Where to spend your first weeks of prep.
Focus first
- Data structures + Big-O
- One language, cold
- Easy problems by pattern
- HTTP / REST basics
Don't skip
- Narrating while you code
- Knowing your own resume
- 2–3 STAR stories
- Questions to ask them
1How interviews actually work
0/4▶Early on, half the battle is knowing what each round is testing so you prepare the right thing.
The typical loop
2Data structures
0/7▶You must be fluent in the core data structures: their operations, costs, and when to reach for each.
3Algorithms & Big-O
0/5▶Every answer ends with "…so it's O(n)". Be able to state and justify the complexity.
The essentials
4Your language — core
0/6▶Pick one strong language and know its fundamentals without hesitation.
5Your language — async & a bit deeper
0/4▶Async shows up even in junior live coding. Know the mental model and the common trap.
6Web fundamentals
0/6▶Full-stack juniors are expected to know how the web works end to end.
7Basic SQL & data
0/4▶Even junior full-stack rounds check that you can query a database.
8Git & dev tools
0/4▶You'll be asked how you work day to day — version control fluency is assumed.
Everyday workflow
9Live coding & approach
0/5▶The bar is clean code + thinking out loud, not tricks. Narrate before you type.
Practice + narration
10Behavioral & logistics
0/5▶Junior behavioral rounds check communication and coachability. Prepare stories and know your resume.
Be ready to talk
Draft answer
Shape (60s) — present → past → why here. "I'm a [role] who most recently built [project/thing] using [stack]."
Then one line on a highlight: "The part I'm proudest of is [specific outcome]." Close with "I'm looking for [what this role offers]." Keep it under a minute and don't recite your whole resume.
Draft answer
S/T — one sentence of situation + your task. A — the bulk: what you did, decisions and why. R — the result, ideally a number.
Prep three: [a project you shipped], [a hard bug], [a teamwork/conflict moment]. Time each at ~90 seconds.