Understanding the Hiring Journey

The full funnel, stage by stage

Almost every tech company — from a 30-person startup to a trillion-dollar giant — runs some version of the same pipeline. The names vary, a stage or two might be skipped, but the shape is remarkably consistent. Think of it as a funnel: a lot of people pour in at the top, and each stage narrows the pool. Here is the full path an application travels.

The numbers on the diagram are an illustration, not a law of physics — a startup with five applicants and a giant with five thousand both still narrow at every step. What matters is the order and the purpose of each gate. Let's walk through them one at a time, because each one is testing something different, and the strategy that gets you through one stage is often useless for the next.

1. Application & résumé screen

This is the top of the funnel. Your résumé lands in an applicant tracking system (ATS), and a recruiter — sometimes assisted by automated keyword filters — spends an average of six to eight seconds deciding whether to keep reading. They're scanning for a quick signal: does this person plausibly match the role? Relevant experience, recognizable skills, a clean format, no obvious red flags.

The brutal truth is that most rejections happen right here, before a human has any real sense of who you are. That's also why this is the highest-leverage stage to improve: a referral can lift your résumé out of the pile entirely, and a sharper résumé can double your callback rate without you writing a single line of new code. We devote whole lessons to both later in the course.

2. Recruiter screen

If your résumé passes, a recruiter schedules a short call, usually 20 to 30 minutes. People often misread this stage: the recruiter is generally not a deep technical interviewer. They are checking three things — that you're a real, reasonable human; that the basics on your résumé hold up under a few questions; and that the logistics line up (location, visa, salary range, timeline, genuine interest in the role).

You pass this stage by being clear, friendly, and prepared. Have a crisp 60-second summary of who you are, know why you want this company, and don't fumble the basic facts of your own résumé. A surprising number of strong engineers stumble here simply because they sound bored or can't explain their own projects.

3. Online assessment (OA)

Many larger companies insert an automated coding test before they spend an engineer's time on you. You'll get a link, a timer (often 60–90 minutes), and one to three problems to solve in a browser-based editor. It's graded automatically against hidden test cases, so partial, "looks-about-right" code won't save you the way it might with a human.

This stage tests raw problem-solving under time pressure and clean, correct code. A tiny taste of what that looks like:

def two_sum(nums, target):
    seen = {}                      # value -> index
    for i, n in enumerate(nums):
        need = target - n
        if need in seen:
            return [seen[need], i] # passes the hidden tests
        seen[n] = i
    return []

Notice it isn't enough to be "almost right" — the autograder wants the correct answer on every edge case, fast. That's exactly the skill the DSA section of this course builds. Not every company uses an OA, but when one does, it's a pure filter, and practice is the only thing that gets you through it.

The interviews: technical & behavioral

If you clear the early gates, you reach the heart of the process — live interviews with actual engineers. This is the part most people picture when they imagine "interviewing," and it usually splits into two flavors.

4. Technical rounds

Expect anywhere from two to six of these, often bundled into a single "onsite" or "virtual onsite" day at bigger companies. Each round is 45–60 minutes with one or two engineers, and they fall into a few buckets:

• Coding / DSA: solve an algorithm problem live while explaining your thinking. They care as much about how you reason as whether you get the answer.
• System design: usually for mid-level and above — "design a URL shortener," "design a news feed." Tests how you handle scale, trade-offs, and ambiguity.
• Practical / domain: debugging, an API design, or a take-home-style task relevant to the team.

The single biggest mistake here is silence. Interviewers are evaluating your communication and collaboration, not just your final code. Talking through your approach — even a wrong one — is the behavior they're trained to reward.

5. Behavioral round

At some point — sometimes its own round, sometimes folded into a technical one — you'll be asked questions like "Tell me about a time you disagreed with a teammate," or "Describe a project you're proud of." This isn't filler. Companies are testing whether you'll be a good colleague: how you handle conflict, ownership, failure, and ambiguity.

The reliable way to answer is the STAR structure — Situation, Task, Action, Result — telling a concrete story instead of vague generalities. "I'm a great team player" means nothing; a 90-second story about how you unblocked a stuck project means everything. We dedicate a full section to building a library of these stories later on.

The hiring committee & the decision

Here's the stage almost nobody warns you about — and the reason a candidate can ace every interview and still stall.

6. The hiring committee

At many large companies (Google made this famous, and others run similar versions), the engineers who interviewed you do not make the final call. Instead, each interviewer writes detailed written feedback with a rating, and that "packet" goes to a hiring committee — a group of senior engineers who never met you. They read the packets, compare you against the company's bar, and vote.

Why does this exist? To reduce individual bias and keep the bar consistent. One overly harsh or overly generous interviewer shouldn't decide your fate. But it has consequences for you:

• Written feedback is everything. If an interviewer liked you but wrote a thin, vague review, the committee has nothing to act on. This is another reason to make your reasoning visible during the interview — you're feeding the notes.
• "Good but not clearly above the bar" can mean no. A committee can decline a perfectly solid candidate simply because the written case wasn't strong enough, even if every interviewer "liked" you.
• It's slower. Committee review, plus possible level/compensation calibration, is a big reason offers can take weeks after your last interview.

7. The offer

Clear the committee and you reach the finish line: an offer, including level, base salary, equity, sign-on, and bonus. Crucially, the offer is the beginning of a negotiation, not the end of the journey. The first number is rarely the best number, and a single well-handled conversation here can be worth more than months of extra grinding. We cover negotiation in detail in a later section — for now, just know that an offer is an invitation to talk, not a take-it-or-leave-it verdict.

The conversion reality (and why it's okay)

Now the part that protects your sanity. Look back at the funnel: hundreds enter, a handful get offers. That is not a sign that you're uniquely unqualified — it's the normal physics of the process. A popular role at a big company can draw a thousand-plus applicants for a single seat. Even a brilliant engineer faces long odds on any one application.

This reframe changes how you should behave in three concrete ways:

• Play the numbers, but smartly. One application almost never lands a job. A thoughtful pipeline of many targeted applications, plus referrals, is what produces offers. Volume with quality, not spray-and-pray.
• Expect rejection as the default. Most engineers — including ones now at top companies — collected a stack of rejections first. The people who succeed aren't the ones who never get rejected; they're the ones who keep going.
• Mine every "no" for data. Did you stall at the recruiter screen? Your résumé or pitch needs work. Failing the OA? Drill DSA. Strong technicals but no offer? Look at communication and your behavioral stories. The funnel tells you exactly where to invest.

Further reading

• Levels.fyi blog — real-world levels, compensation, and hiring-process data.
• Blind — anonymous discussions where engineers share interview and committee experiences (read critically).