Manual Tester Salary in USA (2026)

TL;DR

Salary.com's July 2026 manual-specific benchmark reports USD 68,721 average annual pay, with most reported values from USD 60,960 to USD 74,852. Broader federal Software Quality Assurance Analysts and Testers data has a USD 104,300 median, so match the role definition before choosing a target.

Key Takeaways

• A July 2026 manual-specific source reports USD 68,721 average salary and a USD 60,960 to USD 74,852 central range for Manual QA Tester roles.
• Federal software QA occupation data is much higher because it combines broader analyst, testing, and engineering responsibilities rather than manual-only work.
• Base salary, bonus, equity, health costs, retirement, leave, and on-call expectations must be evaluated as separate compensation layers.
• State, metro, pay zone, sector, clearance, work authorization, and remote-residence rules can materially change comparable offers.
• A contractor hourly rate is not a salary equivalent until unpaid time, benefits, taxes, expenses, and assignment risk are modelled.
• Manual testers improve market scope through API and SQL investigation, accessibility, mobile risk, domain depth, and clear release decisions.

Manual Tester salary USA research in 2026 produces two very different answers. A manual-specific Salary.com page reports USD 68,721 average annual pay, with a central range of USD 60,960 to USD 74,852. Federal 2025 wage data for the much broader Software Quality Assurance Analysts and Testers occupation shows a USD 104,300 median. The gap is a lesson about role classification, not a reason to pick the larger number.

A hands-on manual tester, a quality analyst who validates APIs and data, and an SDET who builds test platforms may appear under neighboring titles. This guide separates those markets and shows how to compare base, total compensation, benefits, location, and employment type with defensible assumptions.

TL;DR

Use the manual-specific range for an execution-focused role. Move toward broader QA analyst or engineering references only when the responsibilities and interview bar support that classification.

1. Manual Tester salary USA benchmarks in 2026

The Salary.com Manual QA Tester page was updated July 1, 2026. It reports USD 68,721 average annual salary, USD 60,960 at the 25th percentile, USD 74,852 at the 75th, USD 53,893 at the 10th, and USD 80,433 at the 90th. It also expresses the average as approximately USD 33 per hour. The page identifies the data as employer-reported.

The O*NET wage page for Software Quality Assurance Analysts and Testers publishes Bureau of Labor Statistics 2025 wage data and was updated in May 2026. It reports USD 104,300 at the median, with USD 80,310 at the 25th percentile and USD 133,180 at the 75th. The Bureau's May 2025 release reports a USD 111,490 mean for the occupation.

Do not average USD 68,721 and USD 104,300. Salary.com's title is Manual QA Tester. The federal occupation covers professionals who develop and execute software tests, analyze causes, prepare modifications, and may have substantial technical scope. It also does not split manual from automation.

Start with the source that matches the job. Then collect current postings with comparable responsibilities, level, location, and employer type. Ask whether advertised ranges are base salary or total compensation.

2. Manual Tester salary USA by level and role scope

Titles such as Manual QA Tester, QA Analyst, Software Tester, Test Engineer, Quality Engineer, User Acceptance Tester, and SDET are inconsistent. A role can be called Manual Tester while expecting API investigation, SQL, logs, accessibility, mobile devices, and release ownership. Another can be called Quality Engineer but focus on scripted business acceptance. Read tasks and interview design.

Years are a weak proxy. An eight-year tester who only runs supplied cases may not match a senior engineering band. A four-year analyst who diagnoses distributed state, designs test strategy, and influences product decisions may belong above a narrow manual-only reference. Neither conclusion is automatic.

Ask for the job family, level code, base band, and expectations. If the interview includes programming and system design, the company may be hiring into an engineering family even when the public title says QA. Use the matching market, but be ready to pass that bar.

3. Base salary, bonus, equity, and total compensation

US offers often include base salary, target bonus, sign-on cash, restricted stock units or options, retirement match, health coverage, paid leave, and other benefits. Salary sources may publish base, starting salary, estimated total pay, or a mix. The definition matters as much as the number.

Create separate categories:

1. Guaranteed recurring cash, usually base salary.
2. Conditional cash, including target bonus, on-call pay, or performance awards.
3. Long-term incentives, including public-company stock, private options, or deferred cash.
4. Employer benefits and employee costs.
5. One-time items such as sign-on or relocation payments.

Suppose an offer includes USD 75,000 base, a target bonus up to 8 percent, and private-company options. The mathematical target cash is USD 81,000, but the bonus is conditional and the options may never become liquid. These figures are illustrative. Compare USD 75,000 with another guaranteed base, then model bonus and equity under conservative scenarios.

For equity, ask about instrument, number of units, vesting, exercise price, current valuation context, dilution, tax events, liquidity, and what happens after departure. For a sign-on bonus, read the repayment condition. Money repayable after a voluntary exit is not equivalent to unconditional base.

4. State, metro, remote zone, and pay-transparency ranges

US compensation varies by state, metro, and employer pay zone. The Bay Area, Seattle, New York City, Boston, Los Angeles, San Diego, Washington DC, Austin, Dallas, Denver, Chicago, Atlanta, Raleigh, Phoenix, Minneapolis, and other markets have different employer concentrations and costs. National data cannot predict one local offer.

Many remote employers assign compensation zones based on residence or an office. A move can change salary. Ask which zone applies, whether the designation is remote or office-based, which states are approved, and how future relocation affects pay. Payroll registration, employment law, customer restrictions, and time-zone needs can limit residence.

Pay-transparency laws and rules vary by jurisdiction and change. When a posting contains a wide range, ask whether it covers multiple levels, locations, or total compensation. Verify current official state or local requirements rather than assuming every employer must publish the same information. This article is not legal advice.

Model housing, state and local taxes, health costs, commute, childcare, insurance, and required travel using current personal inputs. Cost of living determines your decision, but it does not mechanically set the employer's level. A lower salary in a less expensive location can produce greater savings, while a major hub can create career access. Score both.

5. Health insurance, retirement, leave, and working conditions

Benefits are part of US compensation, but their value is household-specific. Request the plan summary before accepting. For medical coverage, compare employee premiums, dependent premiums, deductible, coinsurance, out-of-pocket maximum, provider network, prescriptions, employer account contributions, and coverage start date. Do not value health insurance only from the employer's stated annual cost.

For retirement, record the employer match or contribution, employee contribution requirement, eligible compensation, vesting, waiting period, and investment fees. A 100 percent match up to a stated percentage differs from an automatic contribution. Unvested money is not fully yours if you leave early.

Paid time off can be accrued, fixed, combined, or described as flexible. Ask how much the team actually takes, how sick time works, whether holidays or shutdown days consume PTO, and whether unused time carries or pays out under the applicable policy and law. Flexible PTO is not automatically more generous.

Quality teams may support evening releases, incident response, or weekend validation. Ask about rotation, frequency, response expectation, overtime eligibility, additional pay, and recovery time. Worker classification and wage rights are legal matters. Seek current qualified advice if the facts are unclear. A high base can be less attractive when sustained unpaid on-call work is hidden.

6. W-2 employee, staffing assignment, and independent contractor

The phrase USD 45 per hour does not identify the employment arrangement. You might be a direct hourly employee, a W-2 employee of a staffing company, or an independent contractor responsible for business taxes, insurance, administration, equipment, and unpaid time. The client bill rate may also differ from the worker's rate. Ask who employs and pays you.

Do not multiply an hourly rate by 2,080 automatically. That assumes 40 paid hours for all 52 weeks. Model unpaid holidays, leave, assignment gaps, training, sick time, and early termination. Add the employer benefits you would lose when comparing with permanent salary. Obtain professional advice for taxes, entity structure, and worker classification.

Ask about overtime, pay cycle, benefits eligibility, contract duration, renewal, conversion fee, notice, equipment, background screening, work location, and client shutdowns. Confirm whether the quoted rate is W-2, corp-to-corp, 1099, or another arrangement and what expenses are included.

Contract work can be a useful path into a sector or provide flexibility. It also shifts utilization and benefit risk. A higher hourly rate is compensation for some of that risk, not free additional salary.

7. Industry, domain, clearance, and eligibility

Manual QA in banking, health, manufacturing, defense, retail, media, games, telecom, and SaaS requires different knowledge. Banking rewards understanding of authorization, idempotency, ledgers, reconciliation, audit, and privacy. Health work may add protected information, clinical workflow, interoperability, and formal evidence. Manufacturing can combine software with devices, protocols, firmware, and physical labs.

Government and defense roles may require citizenship, a specific clearance, residence, or on-site work. State your status accurately. A clearance is not a generic credential that can be self-declared. Sponsorship and work authorization also depend on the employer, role, and current rules. Use official sources and qualified advice for immigration decisions.

Domain knowledge improves salary leverage only when it changes what you can safely own. 'Worked in ecommerce' is weak. Explaining how you tested authorization, inventory reservation, partial fulfilment, refund, tax, and reconciliation states is stronger. Protect employer and customer confidentiality while describing the decision.

Regulated and physical-system roles can pay for evidence quality, traceability, and location constraints. They can also offer less remote flexibility. Include lab access, travel, clearance time, and documentation load when evaluating the complete role.

8. Skills that increase a manual tester's market scope

A manual tester creates value by learning what the product does under meaningful conditions, not by clicking every screen. Strong testers model users, states, data, integrations, and failure consequences. They vary conditions deliberately, recognise patterns, and communicate uncertainty in a form the team can act on.

Technical breadth improves that information flow:

• Browser developer tools, HTTP, JSON, authentication, cookies, caching, and network conditions.
• API exploration with positive, negative, authorization, schema, state, and idempotency checks.
• SQL for approved read-only checks of state transitions, duplicates, relationships, and cleanup.
• Accessibility across keyboard, semantics, zoom, contrast, forms, errors, and supported assistive technology.
• Mobile permissions, interruptions, connectivity, storage, notifications, device variation, and upgrades.
• Observability, including logs, traces, correlation identifiers, feature flags, and environment configuration.
• Domain models for payments, claims, subscriptions, logistics, identity, or other high-value workflows.

Use the API testing fundamentals guide to move below the UI and the exploratory testing techniques guide to make human investigation accountable. Learn enough code to read utilities and automated failures, but do not misrepresent a tutorial as production automation experience.

9. Build a runnable total-compensation comparison

This current Node.js script uses the standard Intl.NumberFormat API and no packages. Save it as compare-comp.mjs, replace the illustrative inputs with written offers, and run node compare-comp.mjs. It keeps guaranteed base separate from target bonus and stock.

const usd = new Intl.NumberFormat('en-US', {
  style: 'currency',
  currency: 'USD',
  maximumFractionDigits: 0,
});

const offers = [
  { name: 'Offer A', base: 72000, bonusTarget: 4000, stockAnnual: 0, healthAnnualCost: 3600 },
  { name: 'Offer B', base: 68000, bonusTarget: 2000, stockAnnual: 8000, healthAnnualCost: 1800 },
];

for (const offer of offers) {
  const targetComp = offer.base + offer.bonusTarget + offer.stockAnnual;
  const baseAfterHealthPremium = offer.base - offer.healthAnnualCost;

  console.log(offer.name);
  console.log(`  guaranteed base: ${usd.format(offer.base)}`);
  console.log(`  target comp: ${usd.format(targetComp)}`);
  console.log(`  base less employee health premium: ${usd.format(baseAfterHealthPremium)}`);
}

The model does not calculate tax, deductible exposure, retirement, vesting, stock price changes, leave, or job risk. stockAnnual should be zero for private options unless you deliberately create a separate uncertain scenario. Target bonus is not guaranteed.

A public QA portfolio should show risk work as well as calculators. Include a sanitized test strategy, exploratory notes, defect samples against a practice system, API evidence, or an accessibility review. Never publish employer code, customer data, secrets, internal endpoints, or protected screenshots.

10. Resume and interview evidence for manual QA

A US resume usually benefits from concise outcome-focused bullets. 'Performed manual testing in Jira' makes the tool sound like the achievement. A stronger truthful pattern is: 'Modelled subscription upgrade, downgrade, renewal, and cancellation states across web, billing callback, and account data, finding a duplicate-charge path before release.' It shows what you understood and why it mattered.

Use numbers only when you can reproduce the measurement. If you reduced regression time, state the baseline, new value, test scope, and method. If confidentiality prevents a figure, explain the result qualitatively. Preserve the official job title and make broader responsibilities visible in bullets. Do not rename yourself SDET to access a higher benchmark.

Prepare six stories: ambiguous requirements, a serious defect, a miss, a rejected defect, a compressed release, and a process improvement. Explain your personal action and the tradeoff. The manual testing interview guide for experienced candidates supports practice.

A small original portfolio can include a risk map, session charters, high-value cases, API requests, local SQL, and two strong bug reports. Add setup, assumptions, and explicit limitations. Reviewers value judgement and clarity more than a generated case count.

11. Negotiate a Manual Tester salary USA offer

Build a target from the manual-specific benchmark, matched current vacancies, and the actual responsibility. A useful statement is: 'For a role owning exploratory coverage, API and data investigation, and release risk at this level, I am targeting USD X to USD Y base. Could you share the approved band and how bonus and equity are structured?' Replace the placeholders with evidence that fits the location.

Ask whether a public range covers several levels or zones. Find out the level selected, base range, midpoint, promotion expectations, bonus target, and equity refresh policy. If the employer requests salary history, check current local law and decide with appropriate advice. You can still focus the conversation on the new role's budget and value.

If base cannot move, consider sign-on cash, equity, additional leave, remote designation, schedule, training, title accuracy, or an early written review. Risk-adjust each item. A sign-on with a repayment clause and private options with no liquidity are not base substitutes.

Do not invent a competing offer, work authorization, clearance, title, or metric. Credible evidence is durable leverage. The QA salary negotiation guide provides a complete preparation method.

12. A 90-day plan to improve salary position

Days 1 to 30 are for market definition. Choose target locations or remote zones, employer types, sector, level, and employment arrangement. Collect 25 matching jobs and record title, scope, base range, total-comp language, zone, source, and date. Keep manual QA, broad QA analyst, quality engineering, SDET, and management roles separate.

Days 31 to 60 are for evidence. Identify repeated gaps and build one compact practice project. If roles ask for API testing, document a workflow with authorization, negative, state, and idempotency checks. If SQL is frequent, create a local database and investigate business questions. If accessibility matters, test a critical journey and write user-impact findings.

Days 61 to 90 are for interview calibration. Rehearse scenario answers, run a focused pipeline, and record results by stage. Compare recruiter bands with the public references. If technical rounds consistently target engineering scope, choose whether to build that skill set or narrow the manual QA market. Do not claim it prematurely.

The plan improves the quality of your evidence and decisions. It cannot guarantee a salary or deadline. Hiring demand, location, work authorization, sector, and employer budget remain real constraints.

Interview Questions and Answers

Q: What Manual Tester salary USA range do you expect?

Give a researched base range that matches the location, level, and scope, then ask for the approved band. Keep bonus, stock, and benefits separate so the employer and candidate are discussing the same number.

Q: How would you test a subscription billing change?

Model new purchase, upgrade, downgrade, renewal, cancellation, proration, tax, failed payment, retry, grace period, duplicate notification, refund, and ledger consistency. Verify core rules below the UI and keep focused user journeys for messaging and accessibility.

Q: What do you do with an intermittent bug?

Capture environment, build, account, time, data, request identifiers, logs, and frequency. Compare successful and failing runs and vary one suspected factor at a time. Report the evidence and uncertainty without calling a guess the root cause.

Q: How do you prioritize with one day to test?

Map the change and dependencies, then rank by consequence, likelihood, detectability, and reversibility. Protect critical journeys and integration boundaries first. Report achieved coverage, open defects, and untested risks before the release decision.

Q: When should manual regression become automated?

Automate repeated, valuable, deterministic checks with reliable interfaces and clear oracles when build and maintenance cost is justified. Keep novel exploration and subjective assessment human-led. Reevaluate as the product and testability mature.

Q: How do you test without production data?

Identify the data characteristics that create risk, then generate or provision synthetic records through approved mechanisms. Cover boundaries, relationships, permissions, state history, and privacy constraints. Do not copy sensitive production data into an unsafe environment.

Q: How do you explain release risk to leadership?

Describe affected users, consequence, evidence, uncertainty, workaround, open defects, and untested areas in plain language. Present options and residual risk. Leadership owns the business decision, while QA ensures the information is trustworthy.

Common Mistakes

• Using the broad federal QA median for a narrow execution-only manual role.
• Averaging manual-specific and engineering-oriented salary sources.
• Comparing total compensation with base salary.
• Valuing target bonus or private options as guaranteed cash.
• Ignoring health premiums, deductibles, vesting, leave, and on-call work.
• Multiplying hourly contract pay by 2,080 without modelling unpaid time.
• Applying a national range without matching state, metro, zone, and sector.
• Claiming SDET, security clearance, work authorization, or outcomes inaccurately.
• Negotiating from personal expenses instead of level and role evidence.
• Accepting verbal remote, bonus, or early-review promises.

Conclusion

Manual Tester salary USA evidence supports a clear 2026 starting point. The manual-specific Salary.com model reports USD 68,721 average salary and a USD 60,960 to USD 74,852 central range. The federal USD 104,300 median belongs to a broader software QA occupation and should only inform roles with comparable analyst or engineering scope.

Choose the right population, collect local matched openings, and compare base before bonus, equity, and benefits. Then support your target with credible examples of risk analysis, technical investigation, domain understanding, and release communication. That produces a stronger decision than selecting the largest number on a salary page.

Interview Questions and Answers

Frequently Asked Questions

Related Guides

• Automation Tester Salary in USA (2026)
• Manual Tester Salary in Canada (2026)
• Manual Tester Salary in Germany (2026)
• Manual Tester Salary in India (2026)
• Manual Tester Salary in UK (2026)
• Performance Tester Salary in USA (2026)