QA to QE Personal Transition Plan
Metadata
| Field | Value |
|---|---|
| Worksheet title | QA to QE Personal Transition Plan |
| Related chapters | Chapter 8 — The Modern Quality Engineer; Chapter 10 — The Future of Quality Engineering |
| Related project document | QA to Quality Engineering Transition Framework |
| Part | Part I — Foundations of Modern Software Quality Engineering |
| MQE-BOK domain | Domain 1 — Foundations of Modern Software Quality Engineering |
| Difficulty | Foundation |
| Estimated time | 30–45 minutes |
| Version | 0.1.0 |
| Status | Draft |
Purpose
Translate an aspiration to move from QA into Quality Engineering into a measurable, evidence-based development plan. The plan focuses on capability and contribution, not a required job-title sequence.
QE Capability Developed
Career-direction setting, deliberate practice, evidence planning, and reflective professional development.
Prerequisites
- Read the QA to Quality Engineering Transition Framework (not available in this preview).
- Review the QA to Quality Engineering Transition Journey.
- Optionally complete the Quality Engineer Competency Self-Assessment first.
Instructions
1. Set your direction
| Planning prompt | Your response |
|---|---|
| Current Role | |
| Target Capability | |
| Existing Strengths | |
| Capability Gaps | |
| Priority Domains | |
| Support Needed: mentor, pairing, project, or training |
2. Define measurable goals
| Time horizon | Goal | Applied activity | Evidence to produce | Collaborator or feedback source | Progress review |
|---|---|---|---|---|---|
| 90-Day Goals | |||||
| 6-Month Goals | |||||
| 12-Month Goals |
3. Plan portfolio and interview evidence
| Planning prompt | Your response |
|---|---|
| Portfolio Projects | |
| Evidence to Produce | |
| Interview Preparation | |
| Learning Resources | |
| Progress Review |
4. Test goal quality
Weak goal:
Learn APIs.
Better goal:
Build an API quality project that validates status codes, schema, business rules, authentication, negative scenarios, and CI execution; document the risk addressed, evidence produced, and feedback used to improve it.
Rewrite one of your goals so that it identifies an applied activity, evidence, feedback source, and review point.
| Initial goal | Revised evidence-based goal | What makes the revised goal observable? |
|---|---|---|
Expected Outputs
- current role and target capability direction;
- 90-day, 6-month, and 12-month goals;
- applied learning activities and evidence;
- portfolio and interview preparation; and
- named support and review points.
Portfolio Relevance
The plan itself is usually private. Its planned outputs may become Portfolio Candidates when they demonstrate a safe, reviewable contribution. Remove confidential employer, customer, and system information before publishing any resulting artefact.
Reflection Questions
- Which existing QA strength can you apply immediately in a broader engineering context?
- Which capability gap will most improve a real decision or customer outcome?
- Which goal still describes consumption rather than evidence of applied capability?
- What support must be agreed with a manager, mentor, or team rather than assumed?
Completion Criteria
- Current role, target capability, strengths, gaps, and priority domains are recorded.
- 90-day, 6-month, and 12-month goals have applied evidence and review points.
- At least one goal has been rewritten as an observable, evidence-based activity.
- Portfolio and interview preparation are connected to real capability, not title or certification alone.