Hire QA Automation developers in San Francisco
What the published figures say about hiring this skill into the San Francisco-Oakland-Fremont, CA market, what a seat here actually costs, and how to run the search so it closes.
The local market for this occupation
QA Automation developers are counted by the Bureau of Labor Statistics under Software QA Analysts and Testers. In the San Francisco-Oakland-Fremont, CA area the Bureau puts employment in that occupation at 5,880, with a median annual wage of $134,630. The national median for the same occupation is $104,300, so San Francisco sits about 29% above the country as a whole.
Ranked against every US metropolitan area where this occupation is separately published, San Francisco is 4 of 214 by median wage. Of the 28 markets covered on this site it is 2. Those two numbers together are a better guide to what an offer needs to look like than any single national figure, because they say where the market sits rather than what it averages.
The middle half of the local market runs from $97,320 to $168,050. That band, not the midpoint, is the number to carry into a budget conversation about a QA automation engineer here. Where in the band a particular hire lands depends far more on what the person can be left to own than on how many years the CV shows, which is why the level definitions matter more than the title.
One qualification applies to all of this and it is worth stating plainly. The Bureau classifies by occupation, not by technology. Nobody publishes an official wage figure for QA Automation specifically, and any site that quotes one has either modelled it or made it up. The occupation figures are the honest available baseline: they describe the market a QA automation engineer is hired into, and the technology adjusts where inside that band a given person sits.
What each level looks like against local pay
Percentiles describe a market; they do not describe a person. The useful step is to read the published Software QA Analysts and Testers band for San Francisco against what someone at each level can actually be left to own. The mapping below is a working guide rather than a rule, and the overlap between adjacent levels is genuine: a strong mid-level engineer can be worth more than a weak senior one and frequently is.
| Level | Indicative local band | What they can be left to own |
|---|---|---|
| Junior | $75,100 to $97,320 | Writes tests within an established framework. Needs review on level selection and on flakiness. |
| Mid-level | $97,320 to $134,630 | Owns test coverage for a feature area, builds reliable tests, and keeps them fast and isolated. |
| Senior | $134,630 to $168,050 | Owns test strategy, the infrastructure, the pipeline integration, and the judgement about what is not worth automating. |
| Staff | $168,050 to $205,990 | Owns quality practice across teams, the relationship between automated and exploratory testing, and the standards that make results trusted. |
Bands are percentiles of the published local occupation wage, not FuturByte rates, and not a guarantee that any individual sits where the band suggests.
Two things go wrong when this mapping is used carelessly. The first is budgeting a senior seat at the local median and then interviewing people who can genuinely own an area of the system; in San Francisco that band starts around $134,630 and an offer below it will not close against a counter. The second is the reverse: paying at the top of the band for someone who still needs their work scoped by somebody else. The level definitions are there so the conversation is about what the person will own rather than about how many years the CV shows.
It is also worth being explicit that years and level are only loosely related in QA Automation work. Somebody who has spent six years maintaining one application carries less transferable judgement than somebody who has spent three across three very different ones. When a CV and a band disagree, the interview should settle it, not the CV.
The titles you are bidding against locally
A QA automation engineer in San Francisco is not only being recruited by other teams hiring the same title. The same person is a credible candidate for several adjacent occupations, and what those pay locally is part of what any offer has to clear. These are the published local figures for the titles that compete for this pool.
| Occupation | Employed | 25th percentile | Median | 75th percentile | 90th percentile |
|---|---|---|---|---|---|
| Software QA Analysts and Testers | 5,880 | $97,320 | $134,630 | $168,050 | $205,990 |
| Software Developers | 69,030 | $163,500 | $186,640 | $219,670 | $273,400 |
| Web Developers | 1,420 | $115,170 | $152,450 | $179,950 | $216,060 |
| Data Scientists | 10,460 | $130,430 | $170,110 | $212,970 | $272,430 |
| Information Security Analysts | 3,730 | $115,000 | $162,310 | $201,690 | $246,070 |
| Computer and Information Systems Managers | 23,830 | $203,840 | $232,890 | $313,220 | $335,770 |
Where a row is missing, the Bureau does not publish a separate estimate for this metro, usually because the local sample is too small to release.
The spread across these titles in San Francisco runs from $232,890 for computer and information systems managers down to $134,630 for software qa analysts and testers. That gap is the practical reason technical people move sideways between titles rather than up within one: in this market the fastest available pay rise for a competent engineer is often a change of job title rather than a change of employer. If you are hiring at the lower end of that range, expect to lose some candidates to the upper end of it, and expect that to happen after they have accepted.
This also affects how a role should be written. A specification that describes the work in terms of one narrow title competes only for people who already hold it. One that describes the system and the ownership on offer reaches people currently sitting under a different title who would be entirely capable of the work, and that is usually where the available capacity in a tight market actually is.
Which direction this market is moving
A single year tells you the price. Three tell you whether it is going up. These are the published figures for software qa analysts and testers in the San Francisco-Oakland-Fremont, CA area across the last three releases.
| Reference period | Employed | Median wage |
|---|---|---|
| May 2023 | 8,260 | $134,830 |
| May 2024 | 7,910 | $139,580 |
| May 2025 | 5,880 | $134,630 |
Source: BLS Occupational Employment and Wage Statistics, metropolitan area files. The Bureau does not design these releases to be read as a time series; treat the movement as a direction rather than as a growth rate.
Across those two years the local median moved by less than a percent. Employment moved down 29% over the same period. For someone planning a QA automation engineer hire in San Francisco, the practical reading is that a salary band set from figures more than a year old is probably still close enough to work from.
Markets a candidate here would also consider
Candidates do not compare your offer against a national average. They compare it against what they could get nearby, and for a QA automation engineer in San Francisco that means a handful of specific metros. These are the closest comparisons on the published figures.
| Metro area | Employed | Median wage | vs San Francisco | Location quotient |
|---|---|---|---|---|
| San Francisco-Oakland-Fremont, CA | 5,880 | $134,630 | — | 2.06 |
| San Jose-Sunnyvale-Santa Clara, CA | 6,480 | $166,530 | +24% | 4.76 |
| San Diego-Chula Vista-Carlsbad, CA | 2,280 | $120,210 | -11% | 1.24 |
| Seattle-Tacoma-Bellevue, WA | 6,650 | $129,690 | -4% | 2.65 |
Percentages compare each metro against San Francisco rather than against the national median.
San Jose-Sunnyvale-Santa Clara pays meaningfully more for this occupation than San Francisco does. For remote-capable work that is a real competitor for the same people, and it is worth knowing before you set a band rather than after a candidate declines.
The same table read the other way is a sourcing map. If the local pool is thin and a neighbouring metro pays less for the same occupation, that metro is where a remote or relocating candidate is most likely to come from, and the conversation is easier because the move is upward for them.
Where QA Automation work actually sits in this economy
The San Francisco economy is anchored by venture-backed SaaS, fintech, AI and machine learning and marketplaces. QA Automation is not used identically across those, and the version of the skill that is abundant locally is shaped by whichever of them employs the most engineers. That is the part a national salary table cannot tell you and it is usually what decides whether a shortlist converts.
Venture-backed SaaS
Where QA Automation appears in venture-backed SaaS, it most often looks like the api and integration testing pattern: Service estates where contract testing between components prevents a large class of failure. Developers coming out of this part of the San Francisco market therefore tend to arrive strong on the constraints that sector imposes and lighter on the ones it never had to deal with. If your product shares those constraints, that is experience you would otherwise spend a year building. If it does not, the gap is real, and it is a fair thing to ask about directly rather than to discover in month two.
Fintech
Where QA Automation appears in fintech, it most often looks like the api and integration testing pattern: Service estates where contract testing between components prevents a large class of failure. Developers coming out of this part of the San Francisco market therefore tend to arrive strong on the constraints that sector imposes and lighter on the ones it never had to deal with. If your product shares those constraints, that is experience you would otherwise spend a year building. If it does not, the gap is real, and it is a fair thing to ask about directly rather than to discover in month two.
AI and machine learning
Where QA Automation appears in AI and machine learning, it most often looks like the complex web applications pattern: Products where manual regression testing has become impractical. Developers coming out of this part of the San Francisco market therefore tend to arrive strong on the constraints that sector imposes and lighter on the ones it never had to deal with. If your product shares those constraints, that is experience you would otherwise spend a year building. If it does not, the gap is real, and it is a fair thing to ask about directly rather than to discover in month two.
Marketplaces
Where QA Automation appears in marketplaces, it most often looks like the mobile applications pattern: Device and version fragmentation making manual coverage impossible. Developers coming out of this part of the San Francisco market therefore tend to arrive strong on the constraints that sector imposes and lighter on the ones it never had to deal with. If your product shares those constraints, that is experience you would otherwise spend a year building. If it does not, the gap is real, and it is a fair thing to ask about directly rather than to discover in month two.
The practical use of this is in reading CVs rather than in sourcing. Two candidates in San Francisco with the same number of years of QA Automation can have been solving quite different problems, and the interview should be aimed at the difference rather than at the technology they have in common.
What a local QA automation engineer seat costs to keep open
Salary is the quoted number and it is not the budget. Below is the employer-side payroll cost of one person in this occupation in San Francisco, using published local wages and the statutory 2026 employer rates.
| Wage point | Annual wage | Employer OASDI and Medicare | Wage plus these taxes |
|---|---|---|---|
| 25th percentile | $97,320 | $7,445 | $104,765 |
| Median | $134,630 | $10,299 | $144,929 |
| 75th percentile | $168,050 | $12,856 | $180,906 |
Employer OASDI at 6.2% to a wage base of $184,500, Medicare at 1.45% uncapped. Source: Social Security Administration, Contribution and Benefit Base, retrieved 2026-09-25. Unemployment insurance, benefits, equipment and recruitment cost are additional.
Then there is the cost nobody puts in the model. Every month the role is open, the work it was meant to do is not happening. That cost is the same whichever way you eventually fill the seat, and in a specialist search it routinely exceeds the difference between the options being compared. It is the single most common reason a cost comparison that looked careful turns out to have been wrong.
What to test when the pool is this one
The full interview guide for this technology is on the QA Automation developers page. What changes in San Francisco is emphasis rather than substance: given what the local market has been building, these are the areas where candidates here differ most from each other, and therefore where an interview earns its keep.
Test data and isolation
The most common source of unreliable suites.
- Strong answer: Tests create their own data and clean up, and do not depend on shared environment state.
- Warning sign: Relies on a seeded shared environment that somebody maintains by hand.
Suite speed
A slow suite is a suite people route around.
- Strong answer: Knows how long the suite takes, parallelises, and treats duration as a metric to defend.
- Warning sign: Has no idea how long it takes, or accepts an hour without concern.
Working with developers
Automation that sits outside the team does not get maintained.
- Strong answer: Tests live with the application code, developers contribute, and failures are the team's responsibility.
- Warning sign: Describes a separate suite owned solely by QA, which is the arrangement that reliably decays.
Two patterns worth asking about directly, because they show up in inherited codebases far more often than candidates volunteer them:
Coverage as the target
- What you see: A percentage treated as a goal in its own right.
- What it costs: Tests written to touch lines rather than to verify behaviour, which provides confidence without substance.
- The fix: Measure whether tests catch real regressions. Coverage is a diagnostic, not an objective.
A separate QA-owned suite
- What you see: Tests in their own repository, maintained only by QA, run after development finishes.
- What it costs: It drifts from the application, breaks constantly, and becomes a bottleneck rather than a safety net.
- The fix: Tests live with the code and the whole team owns failures. This single change fixes more than any tooling decision.
The options, and what actually decides between them
Once the local figures are on the table, most teams are choosing between three ways of getting QA Automation capacity into San Francisco. They are not ranked. Which one is right depends on how long the work lasts, how much of it there is, and how much of the surrounding context the person needs to hold.
Hiring locally onto your own payroll
The right answer when the work is permanent, when the person needs to accumulate context that has no value anywhere else, or when presence in San Francisco is a genuine requirement rather than a preference. The costs are the ones in the table above plus benefits and recruitment, and the risk is time: in a market this concentrated the search itself is usually quick and the closing is where offers are lost.
Adding a vetted developer to your existing team
Staff augmentation suits work that is real but not permanent, and teams that already have the review capacity and the architectural direction in place. The person joins your standups, your repository and your process. What you are buying is capacity and specific QA Automation experience, not decision-making, and the constraint is almost always how much code your existing team can review rather than how many developers you add.
A dedicated team that owns an area
The right shape when there is a whole area of work to own rather than a queue of tickets, and when you would otherwise be hiring three or four people at once into a market where that takes a year. It asks more of you at the start, because an area cannot be owned without a clear definition of what it includes and who decides, and it asks less of you afterwards.
The comparison people get wrong is between a local salary and an hourly rate. Those are not the same quantity. A fair comparison puts the fully loaded employer cost of a local seat, including the months it stands empty and the recruitment spend that filled it, against the total cost of the alternative including the coordination overhead it adds. Run honestly, that comparison sometimes favours hiring locally, and when it does we will say so.
A realistic plan for this search
Compress the process before you start
With QA Automation work this concentrated in San Francisco, the candidates worth hiring are in several conversations at once. Fix the panel, the decision-maker and the offer range before the first call. Processes that add a stage midway lose the people they were trying to be careful about.
Plan for the counter-offer
Expect the current employer to respond, and decide in advance whether you will match, improve or walk. Improvising that decision under a deadline is how teams end up overpaying for a hire who leaves in a year anyway.
Give the hire something to land on
A running environment on day one, a named reviewer and access to the real system rather than a mock. The difference between a first merged change in week one and in week four is almost entirely on your side of the table, not the candidate's.
Write the brief around the system, not the stack
State what the system does, what it runs on, what is already decided and what the new person would own. A list of technologies with no context filters for keyword matches, and keyword matches are exactly who gets rejected in the technical round.
What changes when the developer is not in the building
Most of what makes a distributed QA automation engineer productive is decided in their first two weeks, and almost all of it is on the client side. These are the things that reliably separate a first merged change in week one from a first merged change in week four.
A running environment on day one
Not documentation describing how to build one. An environment that starts, with seed data, on the machine the developer actually has. Every day spent on environment setup is a day billed at full rate for no output, and it is the single most common avoidable cost in an engagement.
A named reviewer with real capacity
Someone whose job explicitly includes reviewing this work, not someone who will get to it. A developer who waits two days for review does a quarter of the work they otherwise would, and the cost of that lands on you.
Access to the real system, not a mock
Staging with representative data, the actual API, the actual error messages. Work built against a simplified mock has to be rebuilt when it meets production, and that rework is invisible until it is expensive.
A first task that is small and real
Something that ships in the first few days. It proves the environment, the review path and the deployment path all work, and it surfaces the broken one while it is still cheap to fix.
None of this is specific to working with us. It is what any developer joining any team needs, and it is worth stating plainly because the failures above get attributed to the developer far more often than to the setup that produced them.
The same role in other US markets
Ranked by how many people are employed in this occupation locally, which is the figure that most affects how long a search takes.
- QA Automation developers in New York $130,540
- QA Automation developers in Dallas-Fort Worth $103,210
- QA Automation developers in Washington, D.C. $126,350
- QA Automation developers in Los Angeles $122,210
- QA Automation developers in Seattle $129,690
- QA Automation developers in San Jose $166,530
- QA Automation developers in Boston $122,210
- QA Automation developers in Atlanta $105,800
- QA Automation developers in Chicago $105,580
- QA Automation developers in Charlotte $81,990
- QA Automation developers in Denver $123,690
- QA Automation developers in Austin $103,070
- QA Automation developers in Phoenix $100,740
- QA Automation developers in Baltimore $129,880
- QA Automation developers in Philadelphia $102,740
Other technologies in San Francisco
Skills that appear alongside QA Automation on most job specifications.
- Python developers in San Francisco
- Java developers in San Francisco
- JavaScript developers in San Francisco
- TypeScript developers in San Francisco
- DevOps developers in San Francisco
For the technology itself, including the full interview guide, migration paths and what each level can own, see hiring QA Automation developers. For the wider San Francisco technical market across every occupation, see hiring developers in San Francisco.
Frequently asked questions
What does a QA automation engineer cost in San Francisco?
There is no official wage figure for QA Automation specifically, because the Bureau of Labor Statistics classifies by occupation rather than by technology. The honest baseline is Software QA Analysts and Testers in the San Francisco-Oakland-Fremont, CA area, where the median annual wage is $134,630 and the middle half of the market runs from $97,320 to $168,050. Those are employer wages, before payroll taxes, benefits and recruitment cost.
How many QA automation engineers are there in San Francisco?
Nobody counts developers by technology, so any specific number you see quoted is an estimate. What is published is the occupation: 5,880 people in software qa analysts and testers in the San Francisco-Oakland-Fremont, CA area. QA Automation is one technology inside that population, and the share using it is a matter of inference rather than record.
Is it faster to hire a QA automation engineer locally in San Francisco or remotely?
With the occupation this concentrated in San Francisco, local sourcing is usually quick and closing is the slow part, because good candidates have options and current employers counter. Remote widens the pool but does not remove the closing problem.
Do we need someone in the San Francisco time zone?
Usually less than teams assume. What genuinely needs the local clock is live incident response, work with people who are only available in local hours, and anything tied to a physical site. Everything else needs a committed overlap window of a few hours rather than a matching working day. San Francisco runs on Pacific time.
Which local industries will a QA automation engineer here have come from?
The anchors of this economy are venture-backed SaaS, fintech, AI and machine learning and marketplaces. Most experienced candidates in this market will have spent time in at least one of them, and that background shapes both what they are good at and what they have never had to handle. It is worth asking about explicitly rather than inferring from the CV.
Can you supply a QA automation engineer who overlaps with San Francisco hours?
Yes. Overlap is the thing we schedule around rather than a side effect of where someone happens to live, and it is agreed before an engagement starts rather than negotiated afterwards. Tell us which hours genuinely need to be covered and why, and we will tell you whether we can meet it.
How do you assess a QA automation engineer before we see them?
Working code and a conversation about decisions, not a quiz. We look at what someone has built, ask what they would now do differently and why, and probe the areas where this technology most reliably separates people. You see our reasoning alongside the shortlist, including the reservations.
What if the shortlist is wrong?
Tell us why and we will recalibrate. A rejected shortlist normally means the brief and the need had drifted apart, and that is worth finding out in week one rather than month three. We would rather say we are not the right fit for a role than keep sending candidates against a brief that is not working.