11 / 14 · Book 23 · QA Team Models and Organizational Design← prev⊞ allnext →Get the book →
1.11Question 1
Prompt: You are joining a Series C startup with 80 engineers, 6 product teams, and currently no QA organization. The VP of Engineering asks you to design the QA team from scratch. Walk me through your approach. What a strong answer should cover:
- Starting with assessment before design
- Choosing an org model based on context, not preference
- A hiring plan that prioritizes the first hire profile carefully
- A realistic timeline with phased growth Example answer:
- "I would start with assessment, not design. Week 1-2: understand the product architecture, deployment frequency, regulatory requirements, current test coverage, and escaped defect history. This data determines the org model and headcount."
- "For 80 engineers across 6 teams with likely microservices, I would recommend a hybrid model: 1 centralized QA platform engineer for tooling and standards, and 4-5 embedded QA engineers across the highest-risk product teams."
- "First hire: a senior generalist who can work independently, build the automation foundation, and communicate with leadership. This person sets the culture for everyone who follows."
- "Hiring plan: Hire 1 (month 1), second hire (month 3-4 after the first person has mapped the landscape), remaining 3-4 hires over months 5-9 as the strategy crystallizes."
- "By month 12: 5-6 QA engineers, a working automation framework, CI integration, and a documented test strategy."