Skip to main content

Career guide

The Tech Interview Storytelling Playbook

Make Your Stories Land at FAANG Scope

By James Bugden, Career Coach. Senior Recruiter at Uber.

45 min read

Based on "Mastering Behavioral Interviews: The Guide to Storytelling in Tech" by Austen McDonald.

Sign in to save your progress and access all guides

I have screened thousands of candidates for Uber. The ones who fail tech behaviorals are rarely the ones with thin experience. They are usually the ones who built the right thing, in the right scope, with the right impact, and then told the story in a way that buried the signal.

  • They use "we" when they mean "I."
  • They open with company context when they should open with stakes.
  • They give the interviewer a mural to look at through a straw.

The story is there. The interviewer cannot find it in time.

This guide fixes that.

How to Read This Guide

  • 10 minutes. Read the Why, the 8 Signal Areas, and the Quick Reference.
  • 30 minutes. Add the Story Catalog and Delivery Craft sections.
  • Full read (75 minutes). Work through every section and do the catalog exercise. The Story Catalog you build is the deliverable.

Why Tech Behaviorals Are a Different Game

The bar at FAANG and big tech is different. Four things change the equation:

  • Scale
  • Pace
  • Measurement
  • Leveling

Interviewers are looking for signal, a specific word with a specific job: did we get strong evidence in each scored area in 45 minutes.

STAR alone is not enough at senior levels. I have seen smart engineers from solid mid-sized companies lose loops at Uber not because they were not smart enough, but because they drilled questions instead of building a system for delivering signal.

Recruiter take

The hiring manager debrief at a tech company is not "did the candidate seem nice." It is "did we get a strong, mixed, or weak signal in each area." If the interviewer cannot point to evidence, your score drops, even if you talked for 45 minutes.

Decode, Select, Deliver

The mental model that runs every behavioral question. Most candidates only practice Deliver. Signal-strong candidates run all three on every question, in real time.

Decode, Select, Deliver

1. Decode

Spot the signal area behind the literal question. A favourite-project question is rarely about affinity. A conflict question is rarely about drama.

2. Select

Pull the strongest story from your catalog for that signal area, applying Scope > Relevance > Uniqueness > Recency.

3. Deliver

Open with stakes, sequence Actions, name Results, close with Learnings. Adjust depth to trunk, branch, or leaf.

I can tell within two answers whether a candidate is running this loop or just talking. Loop-runners sound calm and on-topic. Non-loop-runners ramble until the time runs out, then run out of time.

The 8 Signal Areas Tech Interviewers Score On

Every tech behavioral interview maps to some subset of these eight areas. Levels (L3 to L7) shift what counts as evidence in each area. A "led a project" answer at L4 is a "led without authority across three teams" answer at L6.

The 8 Signal Areas

What tech interviewers score on. Sample candidate plot shown for reference.

ScopeOwnershipAmbiguityPerseveranceConflict ResolutionGrowthCommunicationLeadership

Scope

Team size, blast radius, revenue, user count.

Ownership

Did you drive the outcome or get carried by the team.

Ambiguity

Did you reduce ambiguity or wait for it to clear.

Perseverance

Did you ship through a hard quarter.

Conflict Resolution

Did you resolve it, or did it linger.

Growth

Did you change your approach based on a hard lesson.

Communication

Did the interviewer understand the technical decision in 30 seconds.

Leadership

Did you grow other people, not just yourself.

Self-score the 8 Signal Areas

Rate each signal area from 1 to 5. The lowest 2 are your story-bank gaps. Fix those first.

1 = no story ... 5 = strong story with metrics and Learnings

Scope
OK
Ownership
OK
Ambiguity
OK
Perseverance
OK
Conflict Resolution
OK
Growth
OK
Communication
OK
Leadership
OK

Your story-bank gaps

These two signal areas scored lowest. Fix them before your next loop.

  • Scope — 3/5
  • Ownership — 3/5

The 3 Question Types and How to Answer Each

Most candidates pattern-match every question to CARL. That works for one of three question types and fails for the other two.

1. "Tell me about a time"

The default. Pick a story, deliver in CARL. Most predictive of future performance per industrial psychology research.

2. Values questions ("What is your approach to X")

Lead with a framework, then back with a short CARL example. Frameworks signal systematic thinking, which is what senior interviewers score.

Common patterns:

  • Communication by frequency or formality
  • Prioritization by impact vs effort
  • Conflict by stakes scale
  • Learning by observe-do-teach

3. Hypotheticals ("How would you handle X")

  1. Ask one or two clarifying questions.
  2. Frame your approach.
  3. Walk through two or three likely scenarios.
  4. Ground with a real example.
  5. Avoid endless hedging.

Recruiter take

Half the candidates I see treat "What is your approach to cross-team comms" as a story question and ramble through one project. The hire-signal answer is a framework plus one short story, in that order.

Build Your Story Catalog

The shift is from "stories I have" to "a catalog I built and rehearsed." Build the catalog to this shape:

  • Three to four core stories
  • Five to seven supporting stories

Tag each story by signal area.

Source the stories from career artifacts:

  • Perf reviews
  • Old PRDs
  • Calendar archives
  • Slack DMs to peers
  • Retros

Recruiter take

The catalog is the deliverable. Interviewers do not give you credit for stories you remembered. They give you credit for stories you can deliver cleanly under pressure.

Your Story Catalog

Enter 3 to 10 career stories. Tag each one with a signal area, scope, and outcome. Copy as a printable cheat sheet to bring to interviews.

1.
2.
3.

Fill in at least one story before copying.

Story Selection Priority

The book lays out a strict priority order and most candidates get it backwards.

  1. 1.
    Scope first. Pick the highest-scope story even if the literal question fits a smaller story better. "Tell me about a conflict with your manager" with only minor manager conflicts? Use the high-stakes conflict with the PM. You still deliver conflict signal and add more repeatable actions.
  2. 2.
    Relevance second. Match the signal area requested.
  3. 3.
    Uniqueness third. As the interview progresses, avoid retelling the same story. Vary signal areas across stories.
  4. 4.
    Recency fourth. Recent stories carry more weight, but a standout from two years ago beats last month's routine work.

Recruiter take

Picking the right story is half the score. I have seen candidates burn a leadership question on a small story because the prompt mentioned "small team." Scope first, every time.

From STAR to CARL: Why Learnings Earn Senior Points

STAR (Situation, Task, Action, Result) is the foundation most candidates already know. The upgrade is one letter: replace STAR with CARL (Context, Actions, Results, Learnings). The Learnings section is the senior-level differentiator most candidates skip.

STAR vs CARL+Learnings

STAR

  • S Situation
  • T Task
  • A Action
  • R Result

Solid foundation. Misses senior-level signal.

CARL + Learnings

  • C Context (stakes-led)
  • A Actions (60% airtime)
  • R Results (numbers)
  • L Learnings (the senior-level differentiator)

Same skeleton, plus what you would do differently.

At Uber, senior candidates who skip the Learnings section sound junior, even when their actions were senior. Adding two sentences at the end about what you would do differently is one of the highest-leverage edits you can make.

Upgrade a STAR answer to CARL+Learnings

Fill the four fields. The output below is a structured CARL draft you can copy into interview notes.

Fill all four fields to produce the draft.

Raise the Stakes: The Man in a Hole Opening

Kurt Vonnegut's "Man in a Hole" arc applied to behavioral stories. The shape: setup, fall into trouble, climb out. "We had a project, it had some challenges, we shipped it" loses every time. Open with stakes: customer trust, revenue, timeline, technical fragility.

Man in a Hole: the behavioral story arc

SetupHole (stakes)Resolution

Vonnegut's shape. Open with stakes. The hole is what made the work matter.

Before

"We had a checkout flow that needed work. I was on the team. We rewrote it and it shipped."

After

"Checkout was leaking 8% of cart starts at the payment step. At our volume, that was eight figures a year. The team had tried two fixes that did not move the metric. I led the third attempt as the SWE on point."

Delivery Craft

Five delivery techniques that separate offers from "good but did not quite get there." All mechanical. All learnable. Almost no one prepares for them.

Merchant vs Miner

Merchant

Best work in the front window

Miner

Buries the gold in the mountain

Lead with your strongest 2 actions. Do not make the interviewer dig.

The Project Mural

Verbal communication is low bandwidth. The interviewer is looking at your project through a straw. Open with a Table of Contents and signpost as you go. "I will cover the constraint, the two options we considered, and the rollout plan, in that order."

The Menu Technique

When you have two or three viable stories, offer the menu. Always describe the signal each option delivers. "I have one on driving alignment across PM, design, and infra, and one on shipping under a hard regulatory deadline. Which would be more useful?"

Trunk, Branch, Leaf

Trunk

Full CARL story. Two to four minutes. "Tell me about a time you led a migration."

Branch

Direct answer plus a short structured story. 60 to 90 seconds. "How did you handle the rollback risk?"

Leaf

One sentence. "Did you use feature flags?" Answer: "Yes, we shipped behind a 5% canary."

Match depth to the question. Defaulting to CARL on a leaf question is over-talking.

The Halo Effect

Use lists to convey breadth when individual stories are weak or when you want to communicate scope fast. Works in TMAY, inside Actions, and when stories repeat. Coined by Thorndike in 1920.

Tuning Detail: Jargon, One-Breath Explanations, Pace

Calibrating depth is one of the hardest behavioral skills. Too shallow looks non-technical. Too deep loses the room.

  • Go deep once per response. Pick the one place to establish technical credibility. The rest stays high level.
  • Explain complex things simply. The Google Docs simile beats the CRDT vector clock walkthrough every time.
  • One-Breath explanation. Drop a subordinate clause that defines jargon in three seconds, then return to the point. "AWS IoT Greengrass, the local-runtime version of Lambda, ..."
  • Skip the obvious. AWS, Docker, REST need no explanation. Technical debt, P0 outages, build vs buy need no explanation. Internal company systems do.
  • The 30-second rule. If you have not moved on to your next action in 30 seconds, you are over-detailing one point.

Think Defensively: Plug Holes Before Interviewers Dig Them

Behavioral interviewers fill gaps with assumptions, and those assumptions rarely favor you. Senior candidates face higher scrutiny, so this matters more the more senior you are.

Elide

"My manager assigned me the ticket" becomes "I came out of the sprint meeting with this high-impact task." Not a lie. A pruning.

Proactively frame

Explain the rationale before the interviewer infers a flaw. "We chose to rewrite rather than refactor because two prior attempts had failed at the integration boundary."

Acknowledge mistakes

Own them, then share what you changed. The Learnings section is the safest place to do this.

Sticky Career Situations

These situations come up again and again in behavioral interviews:

  • Layoffs
  • Gaps
  • Firings
  • Mental health breaks
  • Job hopping
  • Failed startups

Each has a clean rule. Be honest. Never lie. Adjust framing and skip volunteering compromising details.

Sticky Situation Scripts

Pick a tough situation. The recommended script comes from the book's framework.

When to raise

Bring up proactively in TMAY.

Script

'After leaving X in [month], I took a few months to reset and skill up on Y. The market for Z roles tightened through that window, and I used the time to ship [side project / certification / open-source work]. I am back at full pace and focused on roles where I can apply that work.' Always pair the gap with a what-you-did-during line. Blame the market, not yourself.

The Builder Translation: Reframing Stories for Big Tech

Same story, different language for FAANG vs traditional enterprise vs startup. The Builder archetype:

  • Out of the Garage
  • Lone Hacker
  • Move Fast, Fail Fast
  • Embrace Conflict
  • Change the World

Enterprise framing (loses)

"My manager assigned me the feature, and we followed the SDLC process to deliver it within the agreed governance framework."

Builder framing (wins)

"I took on the feature because it unblocked our biggest customer. I shipped a working version in two weeks behind a flag, learned from real usage, and iterated."

Candidates from traditional industries or smaller companies often have the experience. They lose the offer because their language signals "I am not one of you." This section fixes the language layer.

The Big Three Questions

Three questions you will be asked in every loop. If you cannot deliver all three cleanly without thinking, you are not ready.

TMAY (Tell Me About Yourself)

Personal Summary + 2 to 3 Accomplishments + Forward-Looking Statement. Under 2 minutes.

Tell me about your most impactful project

Open with stakes, deliver in CARL, close with Learnings. Two to four minutes. Pick something where you can defend technical, people, process, and strategic dimensions.

Tell me about a conflict you resolved

The pattern: name the stakes, name your part in the disagreement, name the resolution behaviour (not just the outcome), close with Learnings. Pick a conflict you actually resolved, not one that resolved itself.

Practice Ladder

Most candidates either do not practice or practice badly. The progressive ladder closes the cognitive load gap.

  1. 1. Solo. Record yourself on three to five core stories. Check pacing (10/60/30), I-vs-we count, verbal fillers, energy, organization.
  2. 2. AI. Generate company-value-specific questions. Practice follow-ups. AI cannot replicate facial reactions or pressure, so do not stop here.
  3. 3. Peer mock. Pressure plus follow-ups plus encouragement. Hand them a rubric. Record with permission.
  4. 4. Professional mock. Two sessions, spaced. First covers Big Three and storytelling structure. Second covers company values and on-the-fly story selection.

Quick Reference

Tick each item as you build your catalog. Progress saves locally on this device. Go to any section, or open the example for a one-paragraph illustration.

1. Know the signal areas

Go to section
Go to section

2. Build the story system

Go to section
Go to section

3. Run the loop on every question

Go to section
Go to section
Go to section

4. Sharpen delivery craft

Go to section
Go to section
Go to section
Go to section
Go to section

5. Handle hard moments

Go to section
Go to section

This guide is based on "Mastering Behavioral Interviews: The Guide to Storytelling in Tech" by Austen McDonald, adapted through James Bugden's 15+ years of recruiter experience at Uber and Netskope.

Did you find this guide helpful?

Put this guide into practice

Free

Get full access, for free

Create your free account to unlock every guide, tool, and template on this site.

  • 10+ career & interview guides
  • Resume Builder & AI Analyzer
  • Job research & salary tools
Create a free account

No credit card required

Share

Found this guide helpful?

Share it with a friend who's job hunting. Good content deserves to be passed on.

Keep reading free

Create your free account to read the rest of this guide and save your progress.

Already have an account?

SOAR
© 2026 SOAR. All rights reserved.Privacy PolicyHelpTerms of Service