🎯 QA Skill Acquisition Framework

Based on the Dreyfus Model of Skill Acquisition

Find your path, discover your level, and plan your growth journey
📚 View Learning Plan & Courses →

🧭 Find Your Path — Which QA Are You?

Select your profile to get a personalized learning roadmap based on Dreyfus levels

Collapse
👤 Step 1 Who Are You?
📊 Step 2 Assess Level
🗺️ Step 3 Your Roadmap
🚀 Step 4 Take Action!
1 Novice
2 Beginner
3 Competent
4 Proficient
5 Expert
🎓
The Fresh Graduate
Just landed my first QA job!
💭 "I don't know what I don't know"
View Path

📍 Where You Are

You're at Level 1 — Novice in most areas. This is normal! Everyone starts here.

🎯 Your Goal

Build a strong foundation. Move to Level 2 — Advanced Beginner within your first 6-12 months.

🗺️ Your Learning Path

  • Priority 1: Master Test Design basics — learn to write clear test cases
  • Priority 2: Build System Understanding — know your product inside-out
  • Priority 3: Develop Bug Reporting skills — write bugs developers can fix
  • Priority 4: Learn Communication basics — update status, ask questions

🏷️ Focus Competencies

Test Design System Understanding Bug Reporting Reliability

✅ Next Actions

  • Shadow a senior QA for 1 week — observe how they think
  • Write 10 test cases daily — build the habit
  • Read every bug report in your backlog — learn patterns
  • Keep a learning journal — document what you don't understand
⚡ Quick Start Courses
🎯 Software Testing Fundamentals Coursera
📝 Intro to Selenium WebDriver Free
🐛 Bug Reporting Best Practices LinkedIn
View all 8+ courses →
😐
The Stuck Mid-Career
3-5 years in, feeling plateaued
💭 "I'm doing the same thing, not growing"
View Path

📍 Where You Are

You're likely at Level 2 or Level 3 — competent at daily tasks but stuck in a comfort zone.

🎯 Your Goal

Break the plateau! Move to Level 3 — Competent (own outcomes) or Level 4 — Proficient (see the big picture).

🗺️ Your Learning Path

  • Problem: You're executing tasks but not owning outcomes
  • Fix: Take ownership of a feature end-to-end — from requirements to production
  • Stretch: Lead a QA improvement initiative — automate something, fix a process
  • Level-up: Start mentoring juniors — teaching forces growth

🏷️ Focus Competencies

PIC Behavior Risk Assessment Process Improvement Dev/PM Alignment

✅ Next Actions

  • Volunteer to own a complex feature no one wants
  • Propose one process improvement this quarter
  • Ask for a stretch assignment outside your comfort zone
  • Start 1:1 mentoring with a junior QA
⚡ Recommended Courses
📊 Test Automation for Beginners Free
🎯 Risk-Based Testing Udemy
🧠 Leadership for Testers LinkedIn
View all 10+ courses →
🎖️
The Senior/Expert QA
7+ years, highly skilled
💭 "What's next? Lead? Architect? Switch?"
View Path

📍 Where You Are

You're at Level 4 — Proficient or Level 5 — Expert in technical areas. But you're facing a career crossroads.

🎯 Your Options

Three paths available: Technical Expert (stay deep), People Leader (lead teams), or Quality Strategist (influence org-wide).

🗺️ Path Options

  • Technical Expert: Specialize (Performance, Security, Automation Architecture). Become THE authority.
  • People Leader: Develop coaching, team building, and organizational skills. Lead a QA team.
  • Quality Strategist: Shape org-wide quality vision. Influence beyond QA to product & engineering.

🏷️ Focus Competencies

QA Strategy Standards & Frameworks Stakeholder Trust Prevention Mindset

✅ Next Actions

  • Reflect: What energizes you? Coding? People? Strategy?
  • Talk to leaders in each path — learn their reality
  • Try leading a cross-functional initiative to test leadership
  • Write/speak externally — build your industry reputation
⚡ Recommended Courses
🏗️ Test Architecture Principles Udemy
👥 Engineering Management 101 Coursera
🎤 Technical Speaking LinkedIn
View all 12+ courses →
🧗
The Ambitious Climber
Junior/Medior, hungry for growth
💭 "How do I level up faster?"
View Path

📍 Where You Are

You're at Level 2 trying to reach Level 3. You have energy and drive — now you need direction.

🎯 Your Goal

Reach Level 3 — Competent in your core areas. Become someone others rely on.

🗺️ Fast-Track Strategy

  • Visibility: Volunteer for high-impact projects — get noticed
  • Depth: Go deep on one area (automation, API testing, domain expertise)
  • Initiative: Don't wait to be asked — propose improvements
  • Relationships: Build trust with developers and PMs

🏷️ Focus Competencies

Test Design PIC Behavior Root Cause Analysis Dev/PM Alignment

✅ Next Actions

  • Tell your manager your career goals explicitly
  • Identify one senior QA to learn from — shadow them
  • Take ownership of something others avoid
  • Learn one new skill this quarter (automation, performance, etc.)
⚡ Recommended Courses
🔍 Advanced Test Case Design Udemy
📈 ISTQB Advanced Level ISTQB
🚀 Cypress End-to-End Testing Free
View all 10+ courses →
🔄
The Career Switcher
From Dev/BA/Support to QA
💭 "I have skills but need QA context"
View Path

📍 Where You Are

Mixed levels! You might be Level 3 in Communication but Level 1 in Test Design. Your existing skills are assets!

🎯 Your Goal

Level up QA-specific skills while leveraging your transferable expertise.

🗺️ Your Learning Path

  • From Developer: Your coding helps with automation. Focus on Test Design thinking & user perspective.
  • From BA/PM: Your requirements skills help with risk assessment. Focus on technical testing skills.
  • From Support: Your user empathy is gold. Focus on systematic test approaches.

🏷️ Focus Competencies

Test Design Bug Analysis System Understanding QA Standards

✅ Next Actions

  • Take an ISTQB Foundation course — learn QA vocabulary
  • Document how your previous skills translate to QA value
  • Pair with an experienced QA for first 3 months
  • Keep a "QA mindset" journal — document your learning
⚡ Recommended Courses
📜 ISTQB Foundation Level ISTQB
🎯 Software Testing Fundamentals Coursera
🐛 Bug Hunting Techniques Udemy
View all 9+ courses →
🤖
Manual → Automation Seeker
Manual QA wanting to automate
💭 "Everyone says learn automation"
View Path

📍 Where You Are

You're Level 3 in manual testing but Level 1 in automation. That's okay — automation is a new skill!

🎯 Your Goal

Don't abandon manual skills! Add automation to your toolkit. Become a hybrid QA who knows when to automate.

🗺️ Your Learning Path

  • Week 1-4: Learn a scripting language (Python or JavaScript)
  • Week 5-8: Learn one automation tool (Cypress, Playwright, or Selenium)
  • Week 9-12: Automate 5 of your existing manual test cases
  • Ongoing: Automate strategically — not everything needs automation

🏷️ Focus Competencies

Process Improvement Prevention Mindset Standards & Frameworks

✅ Next Actions

  • Pick ONE automation tool — don't try to learn everything
  • Find a small, stable feature to automate first
  • Join an automation study group or course
  • Remember: good test design > automation speed
⚡ Recommended Courses
🤖 Selenium WebDriver with Python Free
🎭 Playwright Complete Guide Udemy
🐍 Python for Test Automation Coursera
View all 12+ courses →
🦸
The Solo QA in a Startup
Only QA in the company
💭 "I need to do everything, where to start?"
View Path

📍 Where You Are

You need to be a generalist! Being solo is challenging but accelerates growth. You're building multiple competencies simultaneously.

🎯 Your Goal

Create maximum impact with limited time. Focus on high-risk areas. Build processes that scale.

🗺️ Survival Strategy

  • Week 1: Map the system — understand the riskiest areas
  • Week 2: Create a lightweight QA process — don't over-engineer
  • Week 3: Establish communication norms with dev/PM
  • Ongoing: Test smart, not exhaustive — prioritize ruthlessly

🏷️ Focus Competencies

Risk Assessment PIC Behavior Stakeholder Trust Process Improvement

✅ Next Actions

  • Create a "Definition of Done" with the team
  • Set up smoke tests for critical paths only
  • Build relationships with every developer
  • Document as you go — you'll need to scale later
⚡ Recommended Courses
Agile Testing Essentials LinkedIn
📊 Risk-Based Testing Udemy
🔧 Setting Up CI/CD for Testing Free
View all 8+ courses →
👔
The New QA Lead/Manager
Just promoted to lead a team
💭 "How do I grow my team?"
View Path

📍 Where You Are

You're Level 4 in QA skills but Level 1 in people leadership. Leadership is a new skill to develop!

🎯 Your Goal

Shift from doing to enabling. Your job is now to make your team successful.

🗺️ Leadership Transition

  • Let go: You can't test everything anymore — trust your team
  • Focus on: Removing blockers, coaching, setting standards
  • Learn: 1:1s, feedback, career development conversations
  • Build: Team culture, processes, growth paths

🏷️ Focus Competencies

Stakeholder Trust QA Strategy Standards & Frameworks Humility & Learning

✅ Next Actions

  • Set up regular 1:1s with every team member
  • Use this framework to assess and develop your team
  • Find a leadership mentor outside your team
  • Read "The Manager's Path" or similar leadership book
⚡ Recommended Courses
👥 New Manager Foundations LinkedIn
📈 Building High-Performing Teams Coursera
💬 Giving Effective Feedback LinkedIn
View all 10+ courses →
🔬
The Specialist Seeker
Generalist QA wanting to specialize
💭 "Should I focus on perf/security/mobile?"
View Path

📍 Where You Are

You're Level 3 in general QA. Now you want to go deep in one area to stand out.

🎯 Your Options

Choose based on what your company needs AND what excites you:

🗺️ Specialization Paths

  • Performance Testing: JMeter, Gatling, load testing, profiling
  • Security Testing: OWASP, penetration testing, vulnerability scanning
  • Mobile Testing: iOS/Android specifics, device labs, Appium
  • API Testing: REST/GraphQL, contract testing, Postman/Newman
  • Automation Architecture: Framework design, CI/CD integration

🏷️ Focus Competencies

Standards & Frameworks System Understanding Process Improvement

✅ Next Actions

  • Talk to specialists in each area — understand daily reality
  • Check job market — which specialty is in demand?
  • Get a certification in your chosen area
  • Volunteer for projects in that specialty
⚡ Recommended Courses
Performance Testing with JMeter Udemy
🔐 Web Security Testing (OWASP) Free
📱 Mobile Testing with Appium Udemy
View all 15+ courses →
🔥
The Burnout Recovery
Tired, lost passion for QA
💭 "I used to love QA, now I'm just tired"
View Path

📍 Where You Are

Burnout doesn't mean lack of skill. You might be Level 4 but feeling like Level 1. This is a recovery journey, not a skill journey.

🎯 Your Goal

Recover first. Rediscover what you loved about QA. It's okay to slow down.

🗺️ Recovery Path

  • Step 1: Identify what's burning you out (workload? politics? boredom?)
  • Step 2: Set boundaries — say no to extra commitments
  • Step 3: Reconnect with purpose — why did you choose QA?
  • Step 4: Find one small thing that sparks joy in your work

🏷️ Focus Competencies

Humility & Learning Professionalism Reliability

✅ Next Actions

  • Talk to your manager about your workload — be honest
  • Take your vacation days — actually rest
  • Consider if a role change would help (team, company, specialty)
  • Remember: your worth isn't defined by your productivity
⚡ Recommended Courses
🧘 Managing Stress at Work LinkedIn
Time Management Fundamentals Coursera
🌱 Career Pivot Strategies LinkedIn
View all 6+ courses →

📚 What is the Dreyfus Model of Skill Acquisition?

Expand

📖 Origin & Background

The Dreyfus Model of Skill Acquisition was developed in 1980 by brothers Stuart Dreyfus (mathematician) and Hubert Dreyfus (philosopher) at the University of California, Berkeley.

Originally created to study how pilots and chess players develop expertise, the model has since been widely adopted in education, nursing, software development, and professional training across industries.

🎯 Why Use It for QA?

The Dreyfus Model is ideal for QA competency assessment because:

  • QA is judgment-based — not just following rules, but knowing when to break them
  • Pattern recognition matters — experienced QA sees risks others miss
  • Context is everything — same test approach doesn't work everywhere
  • Intuition develops over time — experts "feel" where bugs hide

📊 The Five Stages of Skill Acquisition

1

Novice — "Tell me what to do"

Characteristics: Relies on rules and checklists. Needs clear instructions. Cannot adapt to context. Makes decisions based on explicit guidelines only.

QA Example: Follows test cases exactly as written. Asks "what should I test?" Cannot prioritize without guidance. Reports bugs but doesn't analyze patterns.

2

Advanced Beginner — "I recognize this situation"

Characteristics: Starts recognizing patterns from experience. Can handle routine situations independently. Still needs help with complex scenarios. Begins to see similarities across tasks.

QA Example: Writes test cases independently for familiar features. Recognizes common bug types. Can identify when something "feels wrong" but may not know why.

3

Competent — "I can plan and prioritize"

Characteristics: Can create plans and set priorities. Takes responsibility for outcomes. Sees work as part of larger goals. Handles complexity but may be slower than experts. Emotionally invested in results.

QA Example: Owns feature quality end-to-end. Creates test strategies based on risk. Identifies gaps in requirements proactively. Drives issues to resolution.

4

Proficient — "I see the big picture"

Characteristics: Sees situations holistically, not as fragments. Intuition guides decision-making. Knows what's important without being told. Adapts approach to context. Can mentor others effectively.

QA Example: Immediately spots high-risk areas. Designs test strategies tailored to the project. Mentors junior QA. Influences development practices to improve quality.

5

Expert — "I just know"

Characteristics: Works from intuition, not rules. No longer "thinks" about basics — they're automatic. Sees what others cannot. Innovates and shapes practices. Transcends standard approaches. Others seek their judgment.

QA Example: Predicts where bugs will be before testing. Defines quality standards for the organization. Innovates testing methodologies. Is consulted for critical go/no-go decisions.

💡 Key Insight

The biggest shift happens between Competent (3) and Proficient (4). At Level 3, you consciously analyze situations and apply rules. At Level 4, you start to "see" the right answer intuitively — pattern recognition becomes automatic.

"The expert doesn't solve problems and doesn't make decisions; they do what normally works." — Hubert Dreyfus

🌍 Dreyfus in Everyday Terms (For Non-QA Audiences)

🚗 Think of Learning to Drive

The Dreyfus Model is like learning to drive a car:

  • Level 1 (Novice): You consciously think about every action — "Press clutch, shift gear, release slowly, check mirror..." You need explicit rules.
  • Level 2 (Advanced Beginner): You can drive around your neighborhood. You recognize familiar situations but still think about what to do.
  • Level 3 (Competent): You can drive in traffic, plan routes, and handle normal situations. You make decisions but still need to concentrate.
  • Level 4 (Proficient): Driving becomes natural. You "feel" when something's wrong with the car. You adapt to rain or traffic without thinking.
  • Level 5 (Expert): You can teach others. You anticipate problems before they happen. You could be a driving instructor or race car driver.

👨‍💻 For Engineering Teams

Think about coding:

  • Novice: Copies code snippets, follows tutorials step-by-step
  • Beginner: Writes simple functions, recognizes common patterns
  • Competent: Designs modules, debugs independently, estimates work
  • Proficient: Architects systems, mentors juniors, sees performance issues instantly
  • Expert: Creates frameworks others use, shapes industry practices

📚 For HR & L&D Teams

Think about hiring interviews:

  • Novice: Follows a script of questions exactly
  • Beginner: Asks follow-ups, recognizes good vs bad answers
  • Competent: Adapts questions based on responses, assesses fit
  • Proficient: Reads between the lines, spots red flags intuitively
  • Expert: Can assess a candidate in 5 minutes, trains other interviewers

🎯 Why Dreyfus Matters for Any Skill Development

1. Not all experience is equal

10 years doing the same thing ≠ 10 years of growth. You can be stuck at Level 2 for years without deliberate practice.

2. Different levels need different training

Novices need rules & checklists. Experts need case studies & mentoring opportunities. One-size-fits-all training fails.

3. Intuition is earned, not magic

When experts say "I just know," they're using pattern recognition built from thousands of experiences. It looks like intuition but it's learned.

4. Context matters more at higher levels

Novices apply rules universally. Experts know when to break rules because they understand context deeply.

💬 How to Explain Dreyfus in 30 Seconds

"The Dreyfus Model describes how people go from beginner to expert in any skill. At first, you need explicit rules and checklists. As you gain experience, you start recognizing patterns. Eventually, you develop intuition — you just 'know' the right answer without consciously thinking. The model has 5 levels: Novice, Advanced Beginner, Competent, Proficient, and Expert. Most people in any profession are at Level 2-3. True experts are rare because reaching Level 4-5 requires years of deliberate practice and varied experiences."

1 Novice
2 Advanced Beginner
3 Competent
4 Proficient
5 Expert

🎯 QA Skill Acquisition Framework — 6 Buckets & 15 Sub-Competencies

Collapse

Click on each bucket to explore sub-competencies. Click on sub-competencies to view detailed "I can..." statements for each Dreyfus level.

🔬

Functional Excellence

3 Sub-Competencies

Test Design & Coverage

View Levels
📘 Level 1 — Novice
  • I can create test cases by copying and modifying existing TCs
  • I can follow a test case template to document my tests
  • I can identify happy path scenarios from requirements
  • I need guidance to determine what scenarios to test
  • I execute test cases step by step as written
📗 Level 2 — Advanced Beginner
  • I can write test cases independently for assigned features
  • I can identify basic positive and negative test scenarios
  • I can apply simple equivalence partitioning for input fields
  • I can create test cases from user stories and acceptance criteria
  • I understand the difference between functional and non-functional tests
📙 Level 3 — Competent
  • I can apply boundary value analysis systematically
  • I can create decision tables for complex business logic
  • I can design state transition test cases
  • I can identify edge cases and corner cases proactively
  • I can prioritize test cases based on risk and impact
📕 Level 4 — Proficient
  • I can design risk-based test strategies for complex features
  • I can identify test scenarios that others might miss
  • I can optimize test suites for maximum coverage with minimum cases
  • I can mentor others on test design techniques
  • I can review and improve test cases written by others
📓 Level 5 — Expert
  • I can innovate new test design approaches for emerging technologies
  • I can define test design standards for the organization
  • I can teach advanced test design workshops
  • I am consulted as the authority on test design decisions

System & Domain Understanding

View Levels
📘 Level 1 — Novice
  • I understand the basic functionality of my assigned feature
  • I can navigate the application UI for my testing scope
  • I need help understanding how my feature connects to others
  • I rely on documentation to understand system behavior
📗 Level 2 — Advanced Beginner
  • I understand how my feature integrates with adjacent modules
  • I can identify basic dependencies between components
  • I can explain the business purpose of features I test
  • I recognize when a change might affect related features
📙 Level 3 — Competent
  • I understand the end-to-end flow of major business processes
  • I can identify integration points and potential failure modes
  • I understand the data flow across system components
  • I can predict impact of changes on downstream systems
📕 Level 4 — Proficient
  • I have deep knowledge of system architecture and design patterns
  • I can identify performance bottlenecks and scalability concerns
  • I am the go-to person for system knowledge in my area
  • I can onboard new team members on system understanding
📓 Level 5 — Expert
  • I have comprehensive mental model of the entire ecosystem
  • I influence architectural decisions with quality perspective
  • I am consulted for critical system decisions
  • I can identify opportunities for system-wide improvements

Bug Analysis & Reporting

View Levels
📘 Level 1 — Novice
  • I can report bugs with basic information (title, steps, actual/expected)
  • I follow the bug report template provided
  • I include screenshots to support my bug reports
  • I need help determining bug severity and priority
📗 Level 2 — Advanced Beginner
  • I can write clear, reproducible bug reports
  • I can determine appropriate severity and priority
  • I can isolate bugs to specific steps or conditions
  • I can identify if a bug is a duplicate of existing issues
📙 Level 3 — Competent
  • I can identify the probable component/module causing the bug
  • I can suggest potential root causes to developers
  • I can identify patterns across multiple bugs
  • I can write bugs that developers can fix without clarification
📕 Level 4 — Proficient
  • I can trace bugs to code level (with logs/debugging)
  • I can analyze bug trends to identify quality hotspots
  • I can mentor others on effective bug reporting
  • I can facilitate bug triage meetings effectively
📓 Level 5 — Expert
  • I can predict defect-prone areas before testing begins
  • I can design defect prevention strategies
  • I drive quality improvements based on defect insights
  • I am consulted for critical production issues
🧩

Problem Solving

3 Sub-Competencies

Root Cause Analysis

View Levels
📘 Level 1 — Novice
  • I can describe what went wrong (the symptom)
  • I can gather basic information about the problem
  • I escalate issues when I cannot solve them
  • I need guidance on how to investigate issues
📗 Level 2 — Advanced Beginner
  • I can ask 'why' to dig deeper into problems
  • I can check logs and error messages for clues
  • I can compare working vs non-working scenarios
  • I can rule out common causes systematically
📙 Level 3 — Competent
  • I can apply 5-Whys technique systematically
  • I can use fishbone diagrams for complex problems
  • I can document RCA findings for knowledge sharing
  • I can propose solutions that address root cause
📕 Level 4 — Proficient
  • I can connect root causes across multiple incidents
  • I can lead RCA sessions with cross-functional teams
  • I can design experiments to validate hypotheses
  • I can mentor others on RCA techniques
📓 Level 5 — Expert
  • I can design RCA frameworks for the organization
  • I can build systems that prevent problems from recurring
  • I am the escalation point for critical RCA
  • I influence engineering practices based on RCA insights

Risk Assessment

View Levels
📘 Level 1 — Novice
  • I am learning to identify what could go wrong
  • I follow risk checklists when provided
  • I report concerns to senior team members
  • I focus on completing my assigned tasks
📗 Level 2 — Advanced Beginner
  • I can identify obvious risks in my testing area
  • I understand the difference between high and low risk
  • I can identify risks related to new functionality
  • I ask about risks during requirement discussions
📙 Level 3 — Competent
  • I proactively identify and document risks
  • I can assess likelihood and impact of risks
  • I can prioritize testing based on risk levels
  • I can propose mitigation strategies for risks
📕 Level 4 — Proficient
  • I can quantify business impact of quality risks
  • I can create risk matrices for complex releases
  • I can influence release decisions based on risk
  • I can design risk-based testing strategies
📓 Level 5 — Expert
  • I can shape release strategy based on holistic risk view
  • I can establish risk management frameworks
  • I can advise leadership on quality risk decisions
  • I am consulted for critical go/no-go decisions

Prevention Mindset

View Levels
📘 Level 1 — Novice
  • I find bugs during testing (reactive)
  • I report issues I discover
  • I follow the testing process defined by the team
  • I focus on my immediate testing tasks
📗 Level 2 — Advanced Beginner
  • I suggest fixes for bugs I find
  • I share learnings from bugs with the team
  • I understand the value of early testing
  • I participate in requirement reviews when invited
📙 Level 3 — Competent
  • I propose process improvements to prevent bugs
  • I actively participate in requirement/design reviews
  • I suggest automation for repetitive checks
  • I create checklists to prevent common issues
📕 Level 4 — Proficient
  • I implement automated quality gates in CI/CD
  • I design shift-left testing strategies
  • I coach developers on testing practices
  • I lead initiatives to reduce defect injection
📓 Level 5 — Expert
  • I create a culture where quality is everyone's responsibility
  • I design organization-wide defect prevention programs
  • I am a thought leader on quality engineering
  • I drive industry best practices adoption
🎯

Impact & Ownership

2 Sub-Competencies

PIC (Person-In-Charge) Behavior

View Levels
📘 Level 1 — Novice
  • I complete tasks assigned to me
  • I ask for help when I am stuck
  • I wait for instructions on what to do next
  • I am learning the team processes
📗 Level 2 — Advanced Beginner
  • I take ownership of my assigned test areas
  • I proactively update status without being asked
  • I identify blockers and escalate appropriately
  • I take initiative on small improvements
📙 Level 3 — Competent
  • I own the quality of features end-to-end
  • I drive issues to resolution, not just report them
  • I coordinate with developers and PMs proactively
  • I am accountable for release quality of my features
📕 Level 4 — Proficient
  • I own quality for my product area across releases
  • I take ownership of problems even outside my scope
  • I am accountable for outcomes, not just activities
  • I am trusted to handle ambiguous situations
📓 Level 5 — Expert
  • I own organizational quality standards and practices
  • The buck stops with me for critical quality decisions
  • I am accountable for quality strategy and direction
  • I own the quality reputation of the organization

End-to-End Accountability

View Levels
📘 Level 1 — Novice
  • I test the specific scenarios assigned to me
  • I verify my test cases pass or fail
  • I focus on my assigned scope
  • I need guidance on what 'done' looks like
📗 Level 2 — Advanced Beginner
  • I consider how my feature affects adjacent areas
  • I verify basic integration points work
  • I follow up on bugs until they are fixed
  • I validate fixes before closing bugs
📙 Level 3 — Competent
  • I validate complete user journeys, not just features
  • I verify production readiness (logs, monitoring)
  • I consider non-functional aspects (performance, security)
  • I validate deployment and rollback procedures
📕 Level 4 — Proficient
  • I ensure production readiness across teams
  • I validate cross-system dependencies work
  • I consider customer experience end-to-end
  • I coordinate quality across multiple teams
📓 Level 5 — Expert
  • I ensure business outcomes are protected by quality
  • I ensure quality across the entire value stream
  • I am accountable for customer satisfaction
  • I validate strategic initiatives deliver value
💬

Communication

2 Sub-Competencies

Dev/PM Alignment

View Levels
📘 Level 1 — Novice
  • I report bugs and test results
  • I ask developers for help with issues
  • I attend team meetings
  • I am learning team communication norms
📗 Level 2 — Advanced Beginner
  • I explain the impact of bugs clearly
  • I discuss test scenarios with developers
  • I clarify requirements with PMs when unclear
  • I participate in sprint ceremonies actively
📙 Level 3 — Competent
  • I negotiate bug priorities with dev and PM
  • I provide quality input during planning
  • I challenge requirements that are unclear or risky
  • I represent quality perspective in discussions
📕 Level 4 — Proficient
  • I influence sprint planning with quality insights
  • I am a trusted partner to dev and PM leads
  • I facilitate quality discussions across functions
  • I coach others on effective communication
📓 Level 5 — Expert
  • I shape product roadmap with quality perspective
  • I influence product strategy and priorities
  • I represent quality at leadership discussions
  • I am a trusted advisor to product leadership

Stakeholder Trust

View Levels
📘 Level 1 — Novice
  • I provide basic status updates when asked
  • I attend meetings I am invited to
  • I am building credibility with the team
  • I follow through on my commitments
📗 Level 2 — Advanced Beginner
  • I provide clear and honest status updates
  • I escalate blockers proactively
  • I am transparent about what I don't know
  • I meet my commitments consistently
📙 Level 3 — Competent
  • I build confidence through consistent delivery
  • I provide context and recommendations, not just status
  • I am trusted for accurate quality assessments
  • Stakeholders rely on my judgment for my areas
📕 Level 4 — Proficient
  • I am a trusted advisor to stakeholders
  • Stakeholders seek my opinion on quality matters
  • I can deliver difficult messages to senior stakeholders
  • I build trust with new stakeholders quickly
📓 Level 5 — Expert
  • I am the go-to person for critical quality decisions
  • Leadership trusts my quality assessments implicitly
  • I can influence decisions at executive level
  • I build organizational trust in quality function
⚙️

Process & Strategy

2 Sub-Competencies

QA Process Improvement

View Levels
📘 Level 1 — Novice
  • I follow the QA processes defined by the team
  • I learn and adopt team practices
  • I ask questions about why we do things
  • I am open to feedback on my practices
📗 Level 2 — Advanced Beginner
  • I suggest small improvements to processes
  • I identify inefficiencies in my daily work
  • I share ideas in retrospectives
  • I help document team processes
📙 Level 3 — Competent
  • I propose and implement process improvements
  • I measure the impact of process changes
  • I introduce automation for manual processes
  • I drive improvements in my area of responsibility
📕 Level 4 — Proficient
  • I lead QA improvement initiatives
  • I design and implement QA frameworks
  • I benchmark practices against industry standards
  • I influence practices beyond my immediate team
📓 Level 5 — Expert
  • I design QA strategy for the organization
  • I establish QA centers of excellence
  • I set the vision for quality engineering
  • I am recognized as a thought leader

Standards & Frameworks

View Levels
📘 Level 1 — Novice
  • I am learning about QA standards
  • I follow standards and guidelines provided
  • I am getting familiar with testing frameworks
  • I complete training on team tools
📗 Level 2 — Advanced Beginner
  • I consistently follow team standards
  • I understand the purpose of our standards
  • I use testing frameworks effectively
  • I can explain our standards to new joiners
📙 Level 3 — Competent
  • I contribute to creating team standards
  • I ensure standards are applied in my area
  • I evaluate and recommend tools/frameworks
  • I help onboard others to our standards
📕 Level 4 — Proficient
  • I own quality standards for my product area
  • I establish frameworks adopted by multiple teams
  • I lead standards adoption across teams
  • I mentor others on applying standards
📓 Level 5 — Expert
  • I set quality vision and standards for the organization
  • I design frameworks used organization-wide
  • I establish quality governance models
  • I am the authority on quality standards
💎

Culture & Values

3 Sub-Competencies

Professionalism

View Levels
📘 Level 1 — Novice
  • I am learning workplace norms and expectations
  • I arrive on time and meet basic commitments
  • I am respectful to colleagues
  • I am building my professional reputation
📗 Level 2 — Advanced Beginner
  • I meet expectations consistently
  • I communicate professionally
  • I handle feedback constructively
  • I represent the team positively
📙 Level 3 — Competent
  • I exceed expectations regularly
  • I maintain high standards for my work
  • I handle difficult situations professionally
  • I take pride in quality of my deliverables
📕 Level 4 — Proficient
  • I am a role model for professionalism
  • I set high standards for others to follow
  • I represent the organization positively
  • I am trusted with sensitive matters
📓 Level 5 — Expert
  • I define the standard for professional excellence
  • I am an ambassador for the organization
  • I shape organizational culture
  • I inspire others through my example

Reliability & Dependability

View Levels
📘 Level 1 — Novice
  • I am learning to manage my commitments
  • I sometimes need reminders on deadlines
  • I ask for help when I might miss a deadline
  • I am learning to estimate my work
📗 Level 2 — Advanced Beginner
  • I meet my commitments most of the time
  • I communicate if I might miss a deadline
  • I am becoming predictable in my delivery
  • I am improving my estimation skills
📙 Level 3 — Competent
  • I consistently deliver on my commitments
  • I am reliable and predictable
  • I manage my workload effectively
  • I follow through without being reminded
📕 Level 4 — Proficient
  • I am trusted with critical and ambiguous work
  • I deliver reliably even under pressure
  • I help others become more reliable
  • I am the go-to person for important tasks
📓 Level 5 — Expert
  • I am trusted with organization-level commitments
  • I am the ultimate backstop for critical delivery
  • Leadership depends on my delivery
  • I am the standard for reliability

Humility & Learning

View Levels
📘 Level 1 — Novice
  • I am learning and absorbing information
  • I acknowledge when I don't know something
  • I am open to learning from others
  • I ask questions to understand better
📗 Level 2 — Advanced Beginner
  • I accept feedback and try to improve
  • I acknowledge my mistakes
  • I learn from my errors
  • I recognize there is much to learn
📙 Level 3 — Competent
  • I actively seek feedback
  • I admit gaps in my knowledge openly
  • I credit others for their contributions
  • I help others without seeking credit
📕 Level 4 — Proficient
  • I model humility for others
  • I learn from junior team members
  • I celebrate team success over personal achievement
  • I create safe spaces for others to learn
📓 Level 5 — Expert
  • I am known for humility despite expertise
  • I inspire a culture of learning
  • I elevate others over myself
  • I am a servant leader

📊 Framework Summary

6

Competency Buckets

Core areas of QA expertise

15

Sub-Competencies

Specific skills to develop

5

Dreyfus Levels

Novice → Expert progression

300+

"I Can..." Statements

Clear behavioral indicators