Quality Engineer Competency Self-Assessment
Metadata
| Field | Value |
|---|---|
| Worksheet title | Quality Engineer Competency Self-Assessment |
| 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 | 45–60 minutes |
| Version | 0.1.0 |
| Status | Draft |
Purpose
Help a learner identify current evidence, capability gaps, and next actions across the competencies relevant to a QA-to-QE transition. This is an MSQE educational self-assessment. It is not an industry certification, employee performance rating, hiring standard, promotion rubric, or maturity model.
QE Capability Developed
Evidence-based self-assessment, deliberate learning prioritisation, and practical professional-development planning.
Prerequisites
- Read Chapter 8 and the QA to Quality Engineering Transition Framework (not available in this preview).
- Review the Quality Engineer Competency Model.
- Gather safe examples from your work, learning projects, mentoring, or feedback. Do not include confidential information.
MSQE Educational Capability Levels
Use the approved MSQE educational levels to describe observable capability, not years of experience or title.
| Level | Meaning |
|---|---|
| Foundation | Understands core concepts and vocabulary; can recognise relevant problems and follow an established approach. |
| Practitioner | Applies a capability with guidance in a defined context; can use established practices and explain choices. |
| Engineer | Independently designs and implements appropriate, context-sensitive solutions; states limitations and trade-offs. |
| Advanced / Leadership | Improves systems of work, mentors others, defines strategy, and makes cross-team engineering decisions under uncertainty. |
Instructions
1. Record capability evidence
Assess the current capability areas established in the Transition Framework. Choose a target level that is relevant to your intended contribution, not an assumed requirement to reach Advanced / Leadership in every area.
| Competency area | Current level | Current evidence | Target level | Capability gap | Next practical action |
|---|---|---|---|---|---|
| Quality & Testing Foundations | |||||
| Programming Foundations | |||||
| Test Automation Engineering | |||||
| API & Integration Engineering | |||||
| Data & Database Quality | |||||
| CI/CD & DevOps | |||||
| Cloud Fundamentals | |||||
| Observability & Reliability | |||||
| Performance Engineering | |||||
| Security Awareness | |||||
| Systems Thinking & Architecture | |||||
| AI Quality & AI-Assisted Engineering | |||||
| Quality Strategy & Risk Engineering | |||||
| Communication, Leadership & Influence |
2. Select a balanced priority set
Choose no more than three priorities for the next review period.
| Priority type | Chosen capability | Why it matters now | Applied activity | Evidence to produce | Review date |
|---|---|---|---|---|---|
| Foundation or technical depth | |||||
| Delivery, systems, or operational learning | |||||
| Influence, leadership, or collaboration |
3. Obtain useful feedback
Ask a mentor, peer, manager, or collaborator to review one or two claims in your assessment. They need not agree with your target level; the goal is to improve the evidence and next action.
| Assessment claim | Feedback requested | Feedback received | Adjustment to plan |
|---|---|---|---|
Expected Outputs
- a 14-domain evidence-based capability profile;
- three prioritised development actions;
- evidence-production and review dates; and
- feedback that has improved at least one assessment claim.
Portfolio Relevance
The self-assessment is primarily a private development artefact. The evidence it identifies may become Portfolio Candidates when it is refined, safely anonymised, and accompanied by context, risk, contribution, result, and learning.
Reflection Questions
- Which claimed strength has the strongest observable evidence?
- Which gap would most improve your contribution to a current customer or engineering problem?
- Where are you relying on a tool, title, or course completion rather than applied evidence?
- What capability should remain broad literacy rather than become a deep specialisation?
Completion Criteria
- All fourteen competency areas have a current level, evidence, target, gap, and next action.
- No capability level is presented as a performance rating or certification result.
- Three or fewer priorities are selected for the next review period.
- At least one assessment claim is tested through peer, mentor, or manager feedback.