The Interview Pipeline

Every stage of a tech interview — from hitting "Apply" to signing an offer. What actually happens at each step.

1
Application
You submit your resume through a job portal. Most applications are filtered by ATS (automated tracking systems) before a human ever sees them.
  • Tailor resume keywords to the job description
  • Apply early — many companies review on a rolling basis
  • Referrals skip the ATS entirely (ask upperclassmen, LinkedIn connections)
Takes: 5–15 min per app
2
Online Assessment (OA)
A timed coding challenge — usually 2-3 LeetCode-style problems on HackerRank, CodeSignal, or a custom platform. Some companies send these to everyone who applies.
  • Practice on LeetCode (Easy + Medium) and CodeSignal
  • Time yourself — OAs are typically 60-90 minutes
  • Don't Google during the OA (many have proctoring)
  • Partial solutions still score points — don't leave problems blank
Takes: 1–2 hours
3
Recruiter / Phone Screen
A 15-30 minute call with a recruiter. They're checking if you can communicate clearly, have basic qualifications, and are genuinely interested in the role.
  • Have your "tell me about yourself" ready (30 seconds, max)
  • Know the company's product — what it does, who uses it
  • Ask 1-2 questions: team size, intern project scope, return offer rate
  • This is a vibe check, not a technical grilling
Takes: 15–30 min
4
Technical Interview(s)
1-3 rounds of live coding with an engineer. You'll solve problems on a shared editor while explaining your thought process. Data structures, algorithms, and system design (for senior roles).
  • Think out loud — interviewers care about your process, not just the answer
  • Clarify constraints before coding (input size, edge cases, time expectations)
  • Start with brute force, then optimize — never jump to the "clever" solution
  • Practice mock interviews (Pramp, interviewing.io, or friends)
Takes: 45–60 min per round
5
Behavioral Round
Questions about teamwork, conflict resolution, and past projects. Common at larger companies (Amazon's Leadership Principles, Google's Googleyness). Some companies embed this in the technical rounds.
  • Use STAR format: Situation, Task, Action, Result
  • Prepare 3-4 stories that cover: leadership, conflict, failure, impact
  • Be specific — "I led a team of 4 to ship X in 3 weeks" beats "I'm a team player"
  • For interns: class projects, hackathons, and clubs all count
Takes: 30–45 min
6
Offer (or Rejection)
If you pass, you get an offer email or call within 1-2 weeks. You can negotiate (even for internships). If rejected — ask for feedback, it sometimes comes.
  • You can (and should) negotiate: start date, location, team preference
  • Ask for the deadline in writing — most offers give 2-4 weeks
  • If you have competing offers, let recruiters know (respectfully)
  • A rejection isn't final — many people reapply next cycle and get in
Decision: 1–2 weeks after final round

What Most People Get Wrong

Prep Resources

LeetCode
Start with Blind 75 or NeetCode 150 — covers every pattern you'll see
Pramp
Free mock interviews with other candidates — practice thinking out loud
Levels.fyi Internships
See what companies actually pay interns — useful for negotiation