Library
Quality engineering career path, levels and ladder
Updated
5 levels, from Junior QA Engineer to Principal Quality Engineer. Each one is rated on the same 38 skills — what changes between the rungs is how good you have to be at each. A QA ladder from junior QA engineer to principal, covering test analysis, automation, specialist testing and quality leadership.
- Level 1 of 5
Junior QA Engineer job description
Runs scripted and exploratory tests and logs defects under guidance.
Read the job description - Level 2 of 5
QA Engineer job description
Designs and runs tests for a feature with little day-to-day direction.
Read the job description - Level 3 of 5
Senior QA Engineer job description
Owns test strategy for a service and automates its critical paths.
Read the job description - Level 4 of 5
QA Lead job description
Sets automation and quality standards for a team and coaches others.
Read the job description - Level 5 of 5
Principal Quality Engineer job description
Sets quality strategy and release gates across the organization.
Read the job description
QA engineer levels and job titles
QA, test and quality engineer titles are used for much the same work. This table maps each level on this ladder to the titles you will commonly see elsewhere. For how these titles line up across departments, see the job title hierarchy.
| Level on this ladder | Common job titles |
|---|---|
| Junior QA Engineer | Junior QA Engineer, Junior Test Engineer, Associate Test Engineer, Graduate QA Engineer |
| QA Engineer | QA Engineer, Test Engineer, Quality Engineer, Test Automation Engineer |
| Senior QA Engineer | Senior QA Engineer, Senior Test Engineer, Senior Quality Engineer, Senior QA/QE Engineer |
| QA Lead | QA Lead, Lead Test Engineer, Lead Test Automation Engineer, Staff Quality Engineer |
| Principal Quality Engineer | Principal Quality Engineer, Principal Automation Engineer, Principal Test Engineer |
Individual contributor or manager?
These are individual contributor (IC) titles. QA Lead can mean a hands-on technical lead or a person who manages a team, depending on the company, so check which one a posting means. Many companies also run a separate manager track, such as QA Manager and Head of Quality, that branches off around Senior.
Skills matrix
38 skills and 3 certifications across 5 levels.
| Skill/Certification 41 | Junior QA Engineer | QA Engineer | Senior QA Engineer | QA Lead | Principal Quality Engineer |
|---|---|---|---|---|---|
| Test Analysis5 | |||||
| NoviceYou can run a time-boxed exploratory session against a charter someone else wrote, and note what you tried and what you found. | BasicYou can write your own charter for a small area, time-box the session, and turn what you find into clear bug reports. | ProficientYou can charter and run exploratory sessions across an unfamiliar feature, adapting your mission as you learn, and separate a real defect from a misunderstanding of intent. | AdvancedYou can plan a charter set that covers a feature area by risk rather than by habit, coach others in chartering, and fold session notes back into the test approach. | AdvancedYou can plan a charter set that covers a feature area by risk rather than by habit, coach others in chartering, and fold session notes back into the test approach. | |
| NoviceYou can follow a stated test order and explain, when asked, why the riskiest case on the list is being run first. | BasicYou can rank the tests for a small piece of work by likely impact with some support, and say which case you would drop first if time ran out. | ProficientYou can prioritize testing across a feature from a risk assessment you built yourself, and defend a decision to under-test a low-risk area. | AdvancedYou can set the risk-based approach for a team's whole test effort, and re-rank it when new information, such as a production incident, changes the picture. | ExpertYou can set how risk is assessed and weighted across the organization's test effort, and arbitrate when two teams disagree about where the risk actually sits. | |
| BasicYou can review acceptance criteria for a piece of work and flag missing edge cases or ambiguous wording before development starts. | ProficientYou can analyze requirements across a feature, working with stakeholders to fill gaps, and turn vague criteria into testable statements. | ProficientYou can analyze requirements across a feature, working with stakeholders to fill gaps, and turn vague criteria into testable statements. | AdvancedYou can lead requirements analysis across several teams, coach others in spotting untestable criteria, and get analysis engaged earlier in the lifecycle. | AdvancedYou can lead requirements analysis across several teams, coach others in spotting untestable criteria, and get analysis engaged earlier in the lifecycle. | |
| NoviceYou can run test cases someone else designed using equivalence classes and boundaries, and explain in your own words why each case is there. | ProficientYou can design a boundary and equivalence case set for a complex business rule or multi-field form, keeping the case count small without losing coverage. | AdvancedYou can teach the technique to others, review their case sets for gaps, and combine it with other techniques where equivalence classes alone miss real risk. | AdvancedYou can teach the technique to others, review their case sets for gaps, and combine it with other techniques where equivalence classes alone miss real risk. | AdvancedYou can teach the technique to others, review their case sets for gaps, and combine it with other techniques where equivalence classes alone miss real risk. | |
| BasicYou can triage a defect against the team's agreed process, with a senior tester checking your severity and priority calls. | ProficientYou can decide which defects to escalate and when, and track the dependencies they carry across teams. | ProficientYou can decide which defects to escalate and when, and track the dependencies they carry across teams. | AdvancedYou can use defect patterns to recommend where your team should invest in prevention. | AdvancedYou can use defect patterns to recommend where your team should invest in prevention. | |
| Automation5 | |||||
| NoviceYou can add a test to an existing automation framework following the patterns already there, with a reviewer checking your work. | BasicYou can extend a framework with a new helper or fixture that fits its existing conventions, and explain why the convention exists. | AdvancedYou can set the automation framework standards a team builds on, evolve a framework without breaking the suite that depends on it, and judge when a framework should be replaced rather than patched. | ExpertYou can set automation framework strategy across the organization, including build-versus-adopt decisions for shared tooling, and be the final call when teams disagree on approach. | ExpertYou can set automation framework strategy across the organization, including build-versus-adopt decisions for shared tooling, and be the final call when teams disagree on approach. | |
| NoviceYou can run an existing API automated test and read its result, and adjust a request payload for a case someone else designed. | ProficientYou can automate API tests for a service end to end, including authentication, error cases and data setup, without being shown how. | AdvancedYou can set the API automation approach for a product, including how tests handle test data, environments and flaky dependencies, and coach others in it. | AdvancedYou can set the API automation approach for a product, including how tests handle test data, environments and flaky dependencies, and coach others in it. | AdvancedYou can set the API automation approach for a product, including how tests handle test data, environments and flaky dependencies, and coach others in it. | |
| NoviceYou can run an existing UI automated test and read a failure screenshot or trace to say roughly where it broke. | ProficientYou can automate UI tests for a complex flow, choosing stable locators and waits so the test does not flake under normal timing variation. | AdvancedYou can set the UI automation approach for a product, including where UI automation is the right layer versus API or unit level, and coach others in writing stable tests. | AdvancedYou can set the UI automation approach for a product, including where UI automation is the right layer versus API or unit level, and coach others in writing stable tests. | AdvancedYou can set the UI automation approach for a product, including where UI automation is the right layer versus API or unit level, and coach others in writing stable tests. | |
| NoviceYou can update a failing regression test once shown which product change broke it, and ask before deleting a test you cannot explain. | BasicYou can triage a run of regression failures on your own and tell a real break from a test that has fallen behind the product. You fix the tests in your team's area and flag the ones that need a wider decision. | ProficientYou can keep a regression suite trustworthy across a release: retiring tests that no longer earn their run time, re-scoping the ones that have drifted, and saying what each remaining test still protects. | AdvancedYou can rebuild a suite that has lost the team's trust, cutting run time and duplication without losing coverage that matters, and decide which tests survive a large refactor. | AdvancedYou can rebuild a suite that has lost the team's trust, cutting run time and duplication without losing coverage that matters, and decide which tests survive a large refactor. | |
| NoviceYou can review a small test change and spot a missing assertion or a test that would pass whatever the code did. You raise what you notice and leave the merge call to a more experienced reviewer. | BasicYou can review test code against the conventions your team has agreed, catching brittle selectors, fixed waits and assertions that only cover the happy path. You say what you want changed, not just that you dislike it. | ProficientYou can review test code you did not write and judge whether it will still be readable and diagnosable when it fails in six months. You block a merge over a weak test and name the coverage gap you found. | AdvancedYou can review tests across unfamiliar components and complicated setups, and catch the coverage gap nobody had framed as one. Your reviews teach: the same problem stops appearing in that author's next pull request. | AdvancedYou can review tests across unfamiliar components and complicated setups, and catch the coverage gap nobody had framed as one. Your reviews teach: the same problem stops appearing in that author's next pull request. | |
| Test Engineering5 | |||||
| NoviceYou can trigger an existing pipeline run and open its logs to see why a test job failed. | BasicYou can add a test job to an existing pipeline configuration, with some support, and set it to run on the trigger the team already uses. | ProficientYou can configure a pipeline's test stages from scratch, including parallelization and caching, so feedback comes back in a reasonable time. | AdvancedYou can set the CI test pipeline strategy for a product, including what blocks a merge versus a deploy, and diagnose pipeline-level flake that automated-test fixes cannot reach. | AdvancedYou can set the CI test pipeline strategy for a product, including what blocks a merge versus a deploy, and diagnose pipeline-level flake that automated-test fixes cannot reach. | |
| BasicYou can create test data for a simple scenario yourself, and mask or avoid using real customer data while doing it, with some support. | ProficientYou can design test data for a complex scenario spanning several entities, keeping it isolated between parallel test runs so tests do not interfere with each other. | ProficientYou can design test data for a complex scenario spanning several entities, keeping it isolated between parallel test runs so tests do not interfere with each other. | AdvancedYou can set the test data strategy for a product, including how production-like data is generated or masked safely, and fix data-related flake others cannot trace. | AdvancedYou can set the test data strategy for a product, including how production-like data is generated or masked safely, and fix data-related flake others cannot trace. | |
| NoviceYou can bring up a test environment from an existing script or runbook and tell whether it came up healthy. You ask for help when a dependent service will not start rather than testing around it. | BasicYou can provision an environment with the configuration and stubbed dependencies a given test run needs, then tear it down cleanly. You notice when an environment has drifted from the configuration it claims. | ProficientYou can build and maintain the environments your team's test runs need, seeded data and dependent services included, without a runbook. You keep them reproducible, so a failure is the product's fault and not the environment's. | AdvancedYou can design provisioning for test runs that span several services and awkward third-party dependencies, and decide what to stub rather than run. | AdvancedYou can design provisioning for test runs that span several services and awkward third-party dependencies, and decide what to stub rather than run. | |
| NoviceYou can tell that a test is flaky rather than genuinely failing, and collect the run history and logs that show it. You report it instead of re-running until it passes. | BasicYou can find the cause of a common flake — a fixed wait, shared data, test order — and fix it with review. You can say which of two contradictory runs told the truth. | AdvancedYou can chase flakes rooted in the product or the infrastructure rather than the test, including races that only appear under load. You hand teams the pattern behind a class of flakes, not just the single fix. | AdvancedYou can chase flakes rooted in the product or the infrastructure rather than the test, including races that only appear under load. You hand teams the pattern behind a class of flakes, not just the single fix. | ExpertYou can set how the organization measures, quarantines and pays down flakiness, and hold the line when a team wants to retry past it. You make the link between flake rate and how far people trust the pipeline visible to leaders. | |
| NoviceYou can produce the standard test run report showing what passed, failed and was not run, and ask what a number means before including it. | BasicYou can write up a test run for a named audience and pick the few numbers that matter to them. You add the context that stops a raw pass rate being misread. | ProficientYou can decide what to report on a piece of work and defend the metrics you left out. You turn a set of results into a statement about risk that a product owner can act on. | AdvancedYou can design reporting for a program with several teams and competing definitions of done, and keep it honest under pressure to look green. You retire a metric once it starts driving the wrong behavior. | AdvancedYou can design reporting for a program with several teams and competing definitions of done, and keep it honest under pressure to look green. You retire a metric once it starts driving the wrong behavior. | |
| Specialist Testing5 | |||||
| NoviceYou can run an existing load test script against a target environment and read its summary report. | BasicYou can design a simple load test with a stated workload and success criteria, run it against a test environment, and report what you measured. | ProficientYou can plan and run load, soak and stress tests for a service, and identify the limiting resource from the evidence rather than guessing. | AdvancedYou can set the performance test approach for a product, including realistic workload modeling from production traffic, and tell a genuine regression from environment noise. | ExpertYou can set how the organization tests and budgets for performance, and influence architecture decisions before performance has to be retrofitted. | |
| NoviceYou can run an automated accessibility scan on a page and explain what one of its findings means. | BasicYou can check an interface with the keyboard alone and a screen reader for the basics, and file a defect that names the standard it breaks. | ProficientYou can audit a whole feature against a named accessibility standard using assistive technology and manual technique, and judge which automated-scan findings are noise. | AdvancedYou can set the accessibility testing approach for a product, coach others in manual technique beyond automated scanning, and get findings fixed before release rather than logged and left. | AdvancedYou can set the accessibility testing approach for a product, coach others in manual technique beyond automated scanning, and get findings fixed before release rather than logged and left. | |
| NoviceYou can run a provided security checklist against a feature, such as trying an obviously invalid input, and report what happens. | BasicYou can test basic authorization rules yourself, such as whether one user can reach another user's data by changing an identifier, with some support. | ProficientYou can apply common security testing technique, such as input fuzzing and session handling checks, across a feature without being told which checks to run. | ProficientYou can apply common security testing technique, such as input fuzzing and session handling checks, across a feature without being told which checks to run. | AdvancedYou can set the baseline security testing a product runs before every release, and judge which findings need a specialist penetration test rather than routine testing. | |
| NoviceYou can write a contract test against an agreed API schema and run it when the service changes. You ask which fields a consumer actually depends on rather than asserting on the whole payload. | BasicYou can add and maintain contract tests for a service you work on, covering error responses as well as successful ones. You can tell a genuine contract break from a harmless additive change. | ProficientYou can set up contract testing between a service and its consumers so a breaking change fails before it reaches an end-to-end environment. You decide what belongs in the contract and what does not. | AdvancedYou can introduce contract testing across services owned by different teams and settle who publishes and who verifies. You use it to shrink the end-to-end suite rather than to add another layer on top of it. | AdvancedYou can introduce contract testing across services owned by different teams and settle who publishes and who verifies. You use it to shrink the end-to-end suite rather than to add another layer on top of it. | |
| NoviceYou can run a test pass on the browsers and devices you are handed and record what looked or behaved differently. You capture the version and screen size alongside the defect so it can be reproduced. | BasicYou can test a feature across the agreed support matrix and report each difference as a bug or normal platform behavior, with enough detail to reproduce it. | ProficientYou can choose the browser and device coverage a feature needs, weighing real usage against test cost, and run it without direction. You reproduce a device-only defect that a developer could not. | ProficientYou can choose the browser and device coverage a feature needs, weighing real usage against test cost, and run it without direction. You reproduce a device-only defect that a developer could not. | AdvancedYou can get to the bottom of cross-platform failures with no obvious cause, in input handling, viewport behavior or an older engine, and reach a fix rather than a workaround. You keep the support matrix honest against what users actually run. | |
| Quality Leadership4 | |||||
| NoviceYou can follow an existing test plan with support and explain why it exists. | BasicYou can adapt the team's test approach to the risk of a piece of work, with support, and state what the plan does not cover. | ProficientYou can develop a test approach with your team and put in place measures that show whether it is working. | AdvancedYou can manage test strategies across several delivery streams, arguing for quality effort in terms of risk avoided. | ExpertYou can own the organization's test strategy and set the standards, tooling and staffing that test teams follow. | |
| NoviceYou can gather what a release decision needs — test results, open defects, what went untested — and present it without spin. You say plainly which areas you did not have time to cover. | NoviceYou can gather what a release decision needs — test results, open defects, what went untested — and present it without spin. You say plainly which areas you did not have time to cover. | BasicYou can summarize the risk in a release for your own area and recommend a call that someone else makes. You separate the defects that must block from the ones that can ship with a note. | AdvancedYou can judge readiness for a release spanning several teams on incomplete evidence and under pressure, and defend the call afterwards. You state what would change your answer and how fast that could be found out. | ExpertYou can define how releases are judged ready, who owns the call and what evidence counts, and overrule a green dashboard when the risk lies outside what it measures. | |
| NoviceYou can show a colleague how a test or tool you have used works, and say when a question goes beyond your experience. | NoviceYou can show a colleague how a test or tool you have used works, and say when a question goes beyond your experience. | BasicYou can pair with a developer on writing a test and explain why a case is worth covering. You teach the technique as you were taught it rather than improvising your own. | AdvancedYou can lift the quality skill of people who do not report to you and did not ask, and get developers testing their own work instead of handing it back. You can tell coaching that changed behavior from coaching that was merely enjoyed. | ExpertYou can decide how quality capability is built across the organization and where the effort is worth spending. You change how teams beyond your reach think about their own testing, by persuasion and evidence rather than mandate. | |
| NoviceYou can apply the quality gates already defined for a pipeline and say why a build was stopped. You escalate a gate that looks wrong instead of skipping past it. | NoviceYou can apply the quality gates already defined for a pipeline and say why a build was stopped. You escalate a gate that looks wrong instead of skipping past it. | ProficientYou can define the gates for your team's pipeline, choosing what runs at which stage and what the pass criteria are. You keep them strict enough to catch real problems and fast enough that people do not route around them. | AdvancedYou can design gates for a pipeline serving several teams with awkward tradeoffs between speed and confidence, and decide when a gate is retired. You can say what each gate has actually caught since it went in. | ExpertYou can set which quality gates the organization requires and which are a team's own choice, and defend the delivery cost of each one. You remove a popular gate when the evidence says it is stopping nothing. | |
| Certifications3 | |||||
| Not required | Required | Required | Required | Required | |
| Not required | Not required | Required | Required | Required | |
| Not required | Not required | Not required | Required | Required | |
| Delivery4 | |||||
| NoviceYou can keep your own tasks and deadlines in a current to-do list, and tell your manager as soon as work you own will be late. | BasicYou can organize a small piece of work into steps, put them in a sensible order, and finish it by the date you agreed, raising problems before they cause a delay. | ProficientYou can coordinate a small team's work on a shared goal: who does what by when, what has to wait for what, and a revised plan when things change. | AdvancedYou can keep several people's work in step across teams, agree priorities and hand-offs with them, and keep one shared task list that all of them actually use. | ExpertYou can set the everyday habits for how work is organized and followed up across the organization, and teams you do not lead adopt the routines you introduce. | |
| NoviceYou can estimate how long a task will take once the approach is clear, and you say promptly when the estimate turns out to be wrong. | BasicYou can estimate your own work with reasonable accuracy and keep a steady enough pace that other people can plan around you. | ProficientYou can estimate a whole project including its risks and unknowns, split it into stages, and defend the estimate when it is challenged. | AdvancedYou can estimate work that spans several teams, name the assumptions behind each figure, and rework the plan when those assumptions break. | ExpertYou can forecast work and staffing quarters ahead, and set the estimating method other teams use. | |
| BasicYou can stay responsible after you hand work over: you check it did what it was meant to, fix your own mistakes, and give updates before anyone asks. | ProficientYou can pick up a problem that has no obvious owner and make yourself accountable for it, including the parts nobody enjoys. | AdvancedYou can hold accountability for outcomes delivered mostly by other people, taking the blame when it fails and passing on the credit when it works. | AdvancedYou can hold accountability for outcomes delivered mostly by other people, taking the blame when it fails and passing on the credit when it works. | ExpertYou can report the organization's most exposed outcomes to its leaders as they stand, including bad news, and answer for them. | |
| BasicYou can choose checks that suit the task in front of you, catch your own mistakes before anyone else sees them, and confirm the result works once people start using it. | ProficientYou can define what good enough means for a project, put checks in place to show it has been met, and hold work back when it falls short. | AdvancedYou can set how quality is checked on complex work shared by several teams, and you spot the problems that only appear where their pieces meet. | AdvancedYou can set how quality is checked on complex work shared by several teams, and you spot the problems that only appear where their pieces meet. | ExpertYou can raise the quality bar across the organization by building the tools and habits that make the careful way the easy way. | |
| Craft3 | |||||
| BasicYou can work out what is wrong in work you did not create, and you fix the underlying cause instead of working around the symptom. | ProficientYou can break a large, ambiguous problem into pieces and weigh the options for each against the evidence. | AdvancedYou can make the call on a problem outside your expertise and explain its cost, time and risk. | AdvancedYou can make the call on a problem outside your expertise and explain its cost, time and risk. | ExpertYou can crack problems the organization has repeatedly failed to solve, and your approach becomes how others tackle that whole kind of problem. | |
| NoviceYou can apply the basics of your field to the work you are given, and ask an expert when a task goes beyond what you have learned. | BasicYou can work confidently with the tools and methods your team uses daily, and you can explain how your work serves the team's goals. | ProficientYou can advise the team on your area and apply new developments in the field where they pay off. | AdvancedYou can bring in good practice from outside the organization and make it work here, and your judgment clearly improves the work you touch. | ExpertYou can influence how the field is practiced beyond this organization, and your expertise settles questions that have stood open for years. | |
| ProficientYou can pick up an unfamiliar area fast enough to be useful in it, and you turn what you learned into something others can reuse. | ProficientYou can pick up an unfamiliar area fast enough to be useful in it, and you turn what you learned into something others can reuse. | AdvancedYou can judge which new ideas are worth the team's time and which are not, and you make room for the people around you to learn too. | AdvancedYou can judge which new ideas are worth the team's time and which are not, and you make room for the people around you to learn too. | ExpertYou can set what the organization invests its learning time in, and the material and practice you create outlive your involvement. | |
| Communication4 | |||||
| BasicYou can explain your work so your team can act on it, and play a request back in your own words before you act on it. | ProficientYou can explain a complex topic to people with very different backgrounds, adjusting the detail to the audience without talking down to them. | AdvancedYou can bring disagreeing groups to agreement on the facts and the next steps, and help colleagues frame a difficult or sensitive message. | AdvancedYou can bring disagreeing groups to agreement on the facts and the next steps, and help colleagues frame a difficult or sensitive message. | ExpertYou can set how the organization communicates by creating the forums and norms that teams use to share information. | |
| BasicYou can work well with people in other roles, share context and credit, and take criticism of your work without defending territory. | ProficientYou can build working relationships beyond your own team and get things done through people who do not report to you. | AdvancedYou can align teams with competing priorities on a common goal, surfacing the conflict early instead of letting it harden into resentment. | AdvancedYou can align teams with competing priorities on a common goal, surfacing the conflict early instead of letting it harden into resentment. | ExpertYou can remove the barriers that stop teams working together by putting in place routines and forums they use across the organization. | |
| BasicYou can document your own work well enough for a colleague to follow it unaided, such as a how-to guide or a handover, and keep it current as things change. | ProficientYou can write for a defined audience, whether a proposal, a policy, a report, or a decision record, and make the reasoning as clear as the conclusion. | AdvancedYou can own the documents behind a large piece of work, coordinating contributions so that people who were not involved can carry it on. | AdvancedYou can own the documents behind a large piece of work, coordinating contributions so that people who were not involved can carry it on. | ExpertYou can set the writing standard the organization works to, and documents you wrote are still in use long after you have moved on. | |
| NoviceYou can keep your manager and immediate team informed of your progress, and you raise an issue before someone else discovers it. | BasicYou can identify who is affected by your work and keep them updated at a level of detail and a frequency that suits them. | ProficientYou can win support for a proposal, reset expectations when the plan changes, and turn down a request with a reason the other side accepts. | AdvancedYou can hold senior and external relationships, negotiate between competing demands, and deliver unwelcome news without losing trust. | ExpertYou can represent the organization in its most important relationships and set how it engages with everyone who depends on it. | |
| Leadership3 | |||||
| NoviceYou can act on direction well, seek feedback on how you work, and be open about what you need help with. | BasicYou can spot a problem and propose a way forward unprompted, and you take a small leading role such as running a working group. | ProficientYou can lead one piece of work shared by several people, on your own team and beyond, and make calls that they act on. | AdvancedYou can lead across team boundaries, build the credibility that makes people follow you by choice, and create room for others to lead. | ExpertYou can set direction for the whole organization, make hard calls under real uncertainty, and carry the decisions nobody else wants to own. | |
| NoviceYou can share what you have just learned with your peers and help a newer colleague find their way around. | BasicYou can help someone new settle into your team's work, answer their questions patiently, and give feedback specific enough to act on. | ProficientYou can mentor someone over months, tell them the uncomfortable thing they need to hear, and adapt how you teach to how they learn. | AdvancedYou can develop other mentors, coach people through career decisions rather than tasks, and lift the capability of a whole team. | ExpertYou can shape how the organization grows its people, and those you developed are themselves named by others as strong in their field. | |
| NoviceYou can explain why the work you were given matters and who it is for. | BasicYou can connect your team's work to its goals and question a task that does not appear to serve them. | ProficientYou can look a year ahead in your area, name what will matter by then, and turn that into work people can pick up now. | AdvancedYou can set direction for an area, choose deliberately what not to do, and defend that choice when it is challenged. | ExpertYou can shape the organization's strategy, and the bets you argued for are visible in where it ended up. | |
Use this ladder with your own team
For managers and HR teams: create a free account, then add quality engineering from Departments → Add from template in one click: all 38 skills, with the mastery expected at each of your 5 career levels.