Section 1 Review

Section 1 set the foundation for everything else in this path: recognizing which career track you're actually being offered, building the technical credibility every track depends on, and making genuinely valuable work visible beyond your own team.

Knowledge Check

Work through these five scenarios before checking the Section 1 Solutions.

Scenario 1: The Ambiguous Promotion

A Senior QA Engineer is told, "We'd like to move you into a QA Lead role." They accept immediately, excited about the recognition. What should they have done first, and why?

Scenario 2: The Overruled Lead

A newly titled QA Lead pushes back on a developer's proposed testing shortcut in a cross-team meeting and is overruled without much discussion. What's most likely missing, given this section's own reasoning?

Scenario 3: The Unshared Fix

An engineer spends three months diagnosing and fixing a long-standing, notoriously flaky test suite. No one outside their own team ever learns about it. A year later, they're passed over for a Staff role at a different part of the org. What's the most likely gap?

Scenario 4: The Generic Post

An engineer writes an internal post titled "5 Tips for Better Testing," with general advice but no specific real example behind it. It gets little engagement. What's missing, per this section's substance-first principle?

Scenario 5: The IC Who Feels Like a Fallback

A Staff QA Engineer privately feels their track is "less senior" than their peers who went into management, despite similar tenure and compensation. What does this section say about that assumption?

Next: Check your answers against the Section 1 Solutions, then continue to Section 2 — Test Strategy.