IT Quality Assurance Manager Job Description

An IT Quality Assurance Manager is the person accountable for whether an organization's software is fit to release. Engineers write the code and testers exercise it; the QA manager decides how much testing a change needs, who does it, which tools they use, and what evidence leadership sees before a release goes out. On a small team that can mean one manager working beside a handful of testers. In a large IT shop it can mean several test leads, an automation group, and a budget line for device clouds, licenses and contractors.

One public-sector job class spells the job out plainly. Washington State's classification for an IT Quality Assurance - Manager defines quality assurance as "a supporting process that has to provide the independent assurance" that work products, activities and processes comply with predefined plans, and says that can include conformance to standards such as ISO 9000 or a model such as CMMI. The same class lists manager duties that go well past testing: reviewing budget allotments and expenditures, approving specifications and design requirements for applications and systems, and establishing tactical and operational priorities.

Planning the testing

Every release starts with a test approach. The manager works with product owners and engineering leads to rank features by business impact and failure likelihood, then sets the entry and exit criteria a build must meet. Payment flows, login, data migrations and anything touching personal records get deeper coverage; a copy change on a settings page gets a smoke test. Writing that ranking down is what lets the manager explain, in a release meeting, exactly what was and was not tested.

Running the team and the tooling

The people side is constant: hiring testers and automation engineers, assigning them to product squads, reviewing their test code, and deciding when a manual tester should learn Playwright or Cypress instead of running the same regression pass every sprint. The tooling side covers test management platforms such as TestRail, Jira with Xray or Zephyr, CI pipelines in Jenkins or GitHub Actions, and load tools like JMeter or k6. The manager also schedules time to fix flaky tests and prune checks that no longer protect anything, work that never shows up as a new feature.

Owning defects and the release call

The manager writes the defect workflow: severity definitions, triage cadence, who can defer a bug, and what proof closes one. When something escapes to production, the QA manager runs the retrospective that traces it back to a missing test, a skipped environment or an unclear requirement. The final piece is the release recommendation itself. A good QA manager does not simply say yes or no; they put the known risks, the untested areas and the open defects in front of the person who signs off, in terms that person can act on.

Education

A bachelor's degree in information systems, computer science or software engineering is the usual starting point; a degree in another field paired with hands-on testing experience is another route in. For the broader management occupation, Computer and Information Systems Managers, BLS lists a bachelor's degree as the typical entry-level education and 5 years or more of work experience in a related occupation.

Experience

As a rough guide, QA managers arrive after five to eight years in testing or development, including at least a couple of years leading other testers as a lead or senior engineer. Useful experience is broad: manual exploratory testing, building an automation framework, working inside a CI pipeline, running a performance test, and sitting through a production incident from the first alert to the postmortem. A candidate who has done each of those can judge the work of every person on the team.

Certifications

No single credential defines the job, but several map directly to it:

• ISTQB Certified Tester Advanced Level Test Management (CTAL-TM), from the International Software Testing Qualifications Board. ISTQB says it is aimed at anyone involved in the management of software testing. Version 3.0 of the syllabus, dated May 2024, organizes the material into three chapters: Managing the Test Activities, Managing the Product, and Managing the Team. Candidates must first hold the Certified Tester Foundation Level, and accredited courses must provide at least 22.75 hours of instruction.
• ISTQB Certified Tester Testing with Generative AI (CT-GenAI), a specialist-level certificate on applying large language models and generative AI techniques across the testing lifecycle.
• ASQ Certified Software Quality Engineer (CSQE), which covers software quality development and implementation, inspection, testing and verification.
• ASQ Certified Manager of Quality/Organizational Excellence (CMQ/OE), for managers whose remit extends into a wider quality system. ASQ renamed it from the Certified Quality Manager program, and its 2026 Body of Knowledge took effect July 1, 2026.

Skills that separate managers from senior testers

Technical fluency still matters: reading automation code in Python, Java or TypeScript, understanding how a pipeline gates a merge, and knowing what a test environment needs to mirror production. The manager-specific skills are planning and persuasion. That means estimating test effort for a release, writing a budget request for a device lab or a new tool, presenting quality metrics without burying leaders in charts, and holding a release when the evidence says to hold it, even under deadline pressure.

The federal projection

BLS does not project QA managers as a separate group. The closest management occupation, Computer and Information Systems Managers, is projected to grow 15.8% from 2025 to 2035, from 685.8 thousand to 793.9 thousand jobs, with about 53.5 thousand openings a year on average. Those figures cover the whole occupation, which the federal Standard Occupational Classification illustrates with titles such as chief technology officer and information technology systems director, so they describe the management layer of IT broadly rather than testing departments specifically.

Where the pay differs

Industry rows from the May 2025 wage survey show how setting moves pay for the occupation. In computer systems design and related services, which employed 131,930 computer and information systems managers, the median was $179,510. In state government, excluding schools and hospitals, the median was $133,570 and the 90th percentile was $166,460. A QA manager in a state IT agency and one at a consulting firm sit in the same occupation code; these rows describe that whole occupation, not QA managers alone.

Federal software security rules changed in 2026

QA managers on federal software work saw the government-wide policy change in 2026. OMB memorandum M-26-05, "Adopting a Risk-based Approach to Software and Hardware Security," dated January 23, 2026, rescinded memorandum M-22-18, "Enhancing the Security of the Software Supply Chain through Secure Software Development Practices," and its update, M-23-16. The FAR rule meant to carry out that direction, FAR Case 2023-002, Supply Chain Software Security, is listed as closed in the federal acquisition regulatory agenda published August 14, 2026, because the OMB direction it was intended to implement has since been rescinded.

The underlying framework did not go away. NIST's Secure Software Development Framework, SP 800-218 Version 1.1, remains the final publication, dated February 2022. A revision, SP 800-218 Rev. 1 (SSDF Version 1.2), was published as an initial public draft on December 17, 2025; its public comment period closed January 30, 2026, and as of November 10, 2026 NIST still lists it as a draft. For a QA manager, the practical work still centers on test evidence, vulnerability checks in the pipeline, and records that show what was verified before release, along with whatever a given contract asks for.

Paths forward

The QA manager title opens two ladders. One stays in quality: director of quality engineering, head of QA across several product lines, or a quality role spanning software and wider operations, which is where ASQ's management credential fits. The other moves sideways into engineering, release or delivery management, where the habit of asking what could break before it ships transfers directly. Either way, the skill that carries over is turning test results into a decision a non-technical executive can make quickly.

Dear Hiring Manager,

I am applying for the IT Quality Assurance Manager role on your digital services team. For the past four years I have led quality for the claims platform at a regional insurer, with a team of seven testers and automation engineers supporting three product squads.

When I took over, every release ended with a two-day manual regression scramble and nobody could say what had actually been covered. I started with a risk register for the platform, ranked by how much a failure would cost a policyholder or the claims staff, and rebuilt our test plan around it. We moved the highest-risk paths into an automated Playwright suite that runs on every merge, kept skilled manual testers on exploratory work where their judgment matters, and cut the regression window to an afternoon.

The part of the job I value most is the release conversation. I write a one-page risk summary for each release that lists what we tested, what we chose not to test and why, and the open defects with their business impact. Our product director told me it was the first quality report she read all the way through. Twice last year that summary led us to hold a release, and both times the fix went out within a week with no customer impact.

I also manage the budget for our tools and device lab, and I renegotiated our test management licenses when we consolidated two teams. I would bring the same mix of planning, coaching and plain reporting to your team as you modernize your public-facing applications.

I would welcome the chance to talk about your release process and where quality fits in it.

Sincerely, Jordan Ellis