1.2The Typical QA Interview Process
Understanding the full interview pipeline helps you prepare for each stage rather than just the "interview" in isolation.
Stage 1: Resume Screen (Before the Interview)
Your resume passes through an Applicant Tracking System (ATS) and then a human reviewer. This stage is covered in detail in Chapter 16 (Resume Optimization). Key point: if your resume does not pass the ATS, nothing else in this book matters. Get the resume right first.
Stage 2: Recruiter Screen (15-30 minutes)
The recruiter validates basic fit: years of experience, salary expectations, location/remote preferences, and visa status. This is not a technical assessment, but it is an elimination round.
Pro Tip: When the recruiter asks about salary expectations, use the deflection script from Chapter 14: "I am focused on finding the right fit in terms of role and team. I would love to hear what the budgeted range is for this position." Do not anchor yourself with a number before you understand the role.
Stage 3: Technical Phone Screen (45-60 minutes)
A QA engineer or engineering manager evaluates your technical baseline. This might include:
- "How would you test X?" questions
- Basic coding or pseudocode exercises
- Questions about your experience with specific tools and frameworks
- Discussion of your testing philosophy and approach
Stage 4: On-Site / Virtual On-Site (3-5 hours)
The comprehensive evaluation. Typically includes:
- 1-2 behavioral interview rounds
- 1-2 technical rounds (live coding, system design, or "test this" exercises)
- 1 culture fit / hiring manager round
- Sometimes: a presentation of your portfolio or a past project
Stage 5: Offer and Negotiation
Covered in detail in Chapter 14. The key insight: the interview is not over when you get the offer. Negotiation is the final interview stage.
Stage 6: The First 90 Days
Covered in Part VI. This is where you prove that the interview version of you is the real you.