Interview processes
What a hiring process usually looks like by role, stage by stage, so an unfamiliar one is not a surprise.
- Last reviewed
- Length
- About 5 minutes
- Scope
- Maintained, not published. Corrections welcome.
Interview performance follows from preparation more than talent. The candidates who land offers are not always the most experienced — they are the ones who arrive prepared with specific stories, researched questions, and rehearsed answers to predictable questions. This guide covers behavioral preparation (the STAR format and 6–8 stories that map to multiple competencies), technical preparation (30–50 problems plus 5 system designs), the universal opening question, the questions you should ask the interviewer, and how to follow up after.
Where it applies.
Preparing for behavioral rounds
Write 6–8 stories from the last 3 years using STAR (Situation, Task, Action, Result). Each story should map to multiple competencies. Practice telling each in 90 seconds out loud. Record on phone video and watch playback for filler words and run-ons.
Preparing for technical rounds
Solve 30–50 problems in your target language. Focus on patterns: two pointers, BFS / DFS, dynamic programming, sliding window, top-K. For systems: practice 5 common designs (URL shortener, news feed, chat, rate limiter, file storage).
Nailing "tell me about yourself"
Use a 60–90 second structure: present role and scope, two or three career highlights tied to skills the role needs, the reason you are interested in this specific role. Skip childhood, school, and unrelated jobs unless directly relevant.
Asking questions that signal genuine interest
Ask 2–3 of: "What does success in this role look like at 6 / 12 months?", "How is performance measured?", "What is the team's biggest current challenge?", "How would you describe the manager's style?". Avoid questions Google can answer.
Following up so you stay top of mind
Thank-you email within 24 hours referencing one specific topic from the conversation. Restate one reason you are a fit. Confirm interest. Under 150 words. If the timeline they gave passes, follow up once.
How it works.
Build the story portfolio first
6–8 stories spanning leadership, conflict, ambiguity, failure, mentoring, deadline pressure, cross-team work. Tag each story with the competencies it covers so you can reuse stories across questions.
Write each story in STAR format
Situation (1 sentence context), Task (1 sentence what you owned), Action (3–4 sentences what you specifically did), Result (1–2 sentences with metrics). Action is the longest; Situation is the shortest.
Practice out loud and time-boxed
Record yourself answering on phone video. Watch the playback for filler ("um", "like"), run-ons over 2 minutes, and missing context. Re-record until each answer lands cleanly in 90 seconds.
Prepare 3–5 specific questions per interviewer
Generic questions ("what is the culture like?") signal generic preparation. Specific questions ("how did you decide to spin off the platform team last year?") signal real research.
Send the thank-you within 24 hours
Reference one specific topic. Restate one reason you are a fit. Confirm interest. Under 150 words. Sent same-day if the interview was in the morning, next-day if late afternoon.
Worked illustrations.
Constructed to show the shape of the decision, not reported cases. The figures are illustrative.
A candidate with strong experience but inconsistent interview performance
Builds 8 stories, records each on video, watches playback, re-records, and lands offers at 4 of 6 final-round companies — up from 1 of 5 the prior cycle. The change is preparation, not skill.
A candidate doing 30 minutes of pre-interview research
Reads recent news, leadership posts, and one engineering blog post. Mentions one specific recent shift in the conversation. Interviewer flags them as "clearly did the work" in feedback.
A candidate who prepared six stories and was asked about a seventh competency
Asked about handling ambiguity, which they had not prepared for, they reused the migration story they had built for conflict and led with the part where the requirements were unclear. It worked because the story was known well enough to be re-cut, which is the argument for depth over coverage.
Questions people bring here.
- How many stories do I actually need prepared?
- Six to eight, chosen so each one can answer several different questions. Interviewers ask about conflict, failure, leadership, ambiguity and influence, and a single well-chosen project usually contains at least three of those. Preparing twenty shallow stories is worse than preparing six you can tell precisely, because under pressure you will reach for whichever one you know best anyway.
- What makes a STAR answer good rather than merely complete?
- The result, stated specifically, and the part where you say what you did rather than what the team did. Most answers spend too long on situation and task — the setup — and run out of time before the outcome, which is the only part the interviewer is actually assessing. Aim for roughly a quarter of the answer on context and the rest on action and result.
- Should I rehearse answers out loud or just think them through?
- Out loud, and timed. Thinking an answer through feels complete and takes about a third as long as saying it, which is why rehearsed-in-your-head answers run to four minutes in the room. Saying it aloud also surfaces the sentences that do not survive contact with speech, and those are the ones that make an answer sound recited.
- What should I ask my interviewer?
- Something only that person could answer. A question about the team's biggest current disagreement, or what they wish they had known before joining, gets you information and signals you have been listening. Questions answerable from the careers page cost you the slot and tell the interviewer you did not prepare, and the last five minutes are the part of the conversation you control most.
- Does a thank-you note actually matter?
- It matters at the margin, and the margin is where most decisions between two good candidates get made. Send it within a day, reference something specific from the conversation rather than thanking them generally, and keep it short. It will not rescue a bad interview; it occasionally tips a close one, which is a reasonable return on ten minutes.
- How do I answer a question about a gap or a short stint?
- Say what happened in one sentence, say what you did with the time, and move on. The length of the answer is the signal — a brief, unembarrassed explanation reads as a closed subject, and a long one invites more questions. Interviewers are checking whether it is a pattern and whether you can discuss it calmly, not looking for a reason to stop.
Small things that help.
- "Tell me about yourself" opens most interviews. Have a tight sixty-second answer ready rather than discovering it live.
- Record yourself answering questions on phone video. Playback reveals patterns you cannot hear live.
- Prepare 3–5 questions per interviewer; specific beats generic every time.
- Thank-you email within 24 hours; one specific topic; under 150 words; no exceptions.
- If the timeline they gave passes, follow up once — not twice. Two follow-ups is the cutoff.
Written to be corrected. If something here is wrong, say so and it changes.