Startup vs Enterprise QA

Startup QA (< 50 eng)

• No dedicated QA team initially.
• 1st QA hire at ~10-15 dev.
• Generalist: manual + light automation.
• Build process from scratch.
• Move fast, tolerate some bug.

Enterprise QA (500+ eng)

• Specialized roles (manual, automation, perf, security).
• Established process.
• Heavy compliance.
• Slower but consistent quality.

Hiring profile

Tools

• Startup: SaaS, free/cheap.
• Enterprise: enterprise SaaS, in-house custom.

Process maturity

• Startup: lightweight, agile.
• Enterprise: heavy gates, ITIL-like.

Scaling QA from startup → enterprise

• Founder/dev QA — 0-10 eng.
• First QA hire — 10-30 eng.
• QA team forms — 30-100 eng.
• Specialization — 100-300 eng.
• Org structure — 300+ eng.

Common transition pain

• Process introduce too early → slow startup.
• Process introduce too late → quality erode mid-scale.
• Sweet spot: introduce process when 2-3 incident in quarter trace to process gap.

QA Leader profile shift

• Startup: hands-on, scrappy, T-shape.
• Mid-stage: builder, process-design.
• Enterprise: strategist, stakeholder mgmt.

VN context

• Startup ecosystem HCMC: VNG, Tiki, Be, MoMo (now enterprise-scale).
• Mid-stage: 2-5 year old startup (Topica, Base.vn).
• Enterprise: FPT, Viettel, banks.

Career path

• Some engineers love early-stage scrappy.
• Others love enterprise depth.
• Both legitimate — match preference to environment.