Skip to main content

Section 1 Solutions

These are the answers to the Section 1 Review's Knowledge Check. If you haven't attempted the five scenarios yet, do that first.

Scenario 1: The Ambiguous Promotion​

Correct answer: Before accepting, they should have asked specific questions — the actual weekly split of technical versus people work, whether the role includes direct reports, and how success is measured in six months — per QA Career Roadmap: IC vs. Technical Lead vs. Manager.

Explanation: This is the module's own opening scenario restated — accepting a title change without confirming what it actually involves risks ending up in a genuinely different job than expected.

Alternative approaches considered: Assuming "QA Lead" has a consistent, predictable meaning across organizations is exactly the mistake the module warns against — the title alone doesn't reliably indicate the track.

Real-world reasoning: Tests whether the specific clarifying questions were understood as the actual first step, not just "think it over."

Scenario 2: The Overruled Lead​

Correct answer: Technical credibility built before the title, not the title itself, per Developing Leadership Skills and Technical Credibility — the room hasn't seen this person's judgment demonstrated on anything difficult yet.

Explanation: This is the module's own opening scenario restated — a title alone doesn't grant the credibility it's meant to reflect.

Alternative approaches considered: Assuming the developers were simply being difficult or political misses the module's actual point — credibility has to be earned through visible, repeated demonstration, not assumed from a title.

Real-world reasoning: Tests whether "credibility must be built before the title, not assumed from it" was understood as the core lesson, not just a fact about one meeting.

Scenario 3: The Unshared Fix​

Correct answer: A personal-branding gap — genuinely valuable work that stayed invisible outside their own team, per Personal Branding for Test Engineers.

Explanation: This is the module's own opening scenario restated — excellent work that nobody outside the immediate team learns about builds no reputation, no matter how good it is.

Alternative approaches considered: Concluding the work itself wasn't valuable enough misses the actual lesson — the problem was visibility, not the quality or difficulty of the work.

Real-world reasoning: Tests whether "strong work must be made visible beyond your team to build reputation" was understood as the takeaway, not just "work harder."

Scenario 4: The Generic Post​

Correct answer: A specific, real example is missing — the substance-first principle says only work genuinely useful to someone else facing a similar problem is worth sharing, and generic advice with no real case behind it doesn't clear that bar.

Explanation: This directly restates the module's substance-first principle — content without a specific problem attached reads as filler.

Alternative approaches considered: Concluding the engineer simply needs to promote the post more misses the actual gap — the content itself, not its distribution, is the problem.

Real-world reasoning: Tests whether the substance-first principle was understood as a content requirement, not a distribution or marketing problem.

Scenario 5: The IC Who Feels Like a Fallback​

Correct answer: This section explicitly rejects that assumption — the Individual Contributor track (Staff/Principal QA Engineer, QA Architect) is a legitimate, equally senior destination, not a consolation prize for not becoming a manager.

Explanation: This connects directly to QA Career Roadmap's core point — none of the three tracks is a "higher" version of another.

Alternative approaches considered: Accepting the "less senior" framing as accurate is exactly Mistake 3 from that module, treating the IC track as a fallback rather than an equally valid choice based on genuine fit.

Real-world reasoning: Tests whether "the three tracks are different jobs, not a hierarchy" was understood as this section's throughline, not just a fact about one module.

Section 1 Complete​

Across three modules, this section established the foundation every later section builds on: recognizing which career track is actually on offer, building the technical credibility every track depends on, and making genuinely valuable work visible beyond your own team. From here, continue to Section 2 — Test Strategy, starting with What Is Test Strategy?