Ian Klosowicz
Data analyst salaries in major cities like San Francisco, New York, and Seattle run 20% to 40% above the national median, but fully remote roles have closed a meaningful portion of that gap over the last few years. Whether a city or remote role pays more for you personally depends on cost of living, company location-banding policy, and what you're actually comparing. This post breaks down the real numbers by city, how remote pay actually works, and how to evaluate competing offers honestly.
The remote side of this only matters if the jobs exist, and whether analyst roles can be fully remote covers how available they actually are.
Before comparing cities and remote, you need a baseline. Across the US, the median data analyst salary sits in the range of $70,000 to $85,000. Entry-level roles cluster around $55,000 to $75,000. Mid-level analysts with 3 to 5 years of experience typically earn $80,000 to $105,000. Senior analysts push past $110,000 in most markets.
These numbers shift significantly based on industry, company size, and the specific role. A "data analyst" at a mid-size insurance company in Ohio earns a very different number than a "data analyst" at a Series C fintech in San Francisco, even if the job posting titles are identical. Industry is the bigger lever than city, but city still matters, especially for in-person roles where the cost of living is directly tied to where the company operates.
Here's how the major markets stack up against the national median. These are base salary ranges for full-time, in-person or hybrid data analyst roles at mid-size to large companies.
San Francisco / Bay Area
Entry-level: $85,000 to $110,000. Mid-level: $110,000 to $145,000. Senior: $145,000 to $185,000+. The Bay Area pays the highest base salaries in the country for analytics roles, driven by tech company concentration and cost of living. Total comp at larger tech companies often adds another $30,000 to $80,000 in equity on top of base.
New York City
Entry-level: $75,000 to $100,000. Mid-level: $100,000 to $135,000. Senior: $135,000 to $175,000+. New York is close behind the Bay Area, driven by finance and media. Financial services analyst roles in NYC often include meaningful bonuses that push total comp well above base salary.
Seattle
Entry-level: $80,000 to $105,000. Mid-level: $105,000 to $140,000. Senior: $140,000 to $180,000+. Seattle's market is anchored by Amazon and Microsoft. No state income tax in Washington makes the net take-home meaningfully higher than comparable California roles.
Boston
Entry-level: $70,000 to $90,000. Mid-level: $90,000 to $120,000. Senior: $120,000 to $155,000+. Strong healthcare and biotech concentration drives demand. Pharma and clinical analytics roles are particularly common here.
Austin
Entry-level: $65,000 to $85,000. Mid-level: $85,000 to $115,000. Senior: $115,000 to $145,000+. Austin has grown fast as a tech hub. No state income tax, lower cost of living than SF or NYC, and a growing roster of tech company offices make this an increasingly attractive market.
Chicago
Entry-level: $65,000 to $85,000. Mid-level: $85,000 to $110,000. Senior: $110,000 to $140,000+. Chicago has a strong finance and consulting presence. Salaries are competitive but cost of living is lower than coastal cities, making real purchasing power relatively strong.
Denver / Boulder
Entry-level: $60,000 to $80,000. Mid-level: $80,000 to $105,000. Senior: $105,000 to $135,000+. A growing tech and startup market. Cost of living has increased significantly over the last 5 years, which has pulled salaries up but the ratio remains favorable compared to SF or NYC.
Atlanta
Entry-level: $58,000 to $78,000. Mid-level: $78,000 to $100,000. Senior: $100,000 to $130,000+. Atlanta is underrated as an analytics market, with strong healthcare, media, and logistics company presence. Lower cost of living means the effective purchasing power of these salaries is strong.
Fully remote roles don't have a single salary standard. What a company pays a remote analyst depends almost entirely on where that company is headquartered and what policy they've adopted for remote compensation. There are 3 basic models.
Pay by company location. Some companies pay every employee the same rate regardless of where they live, anchored to the company's headquarters market. A company headquartered in San Francisco that pays $110,000 to a local analyst will pay that same $110,000 to a remote analyst living in Columbus, Ohio. This model is increasingly rare among large companies but still exists at smaller or earlier-stage startups.
Pay by employee location (location banding). The most common model among larger employers. The company defines salary tiers by city or cost-of-living zone. A remote analyst in San Francisco gets one number. The same role in Denver gets a lower number. Austin gets another. This model means remote doesn't automatically mean "SF salary from anywhere."
National rate. Some companies establish a single "remote rate" that sits between their highest and lowest market rates. It's usually benchmarked against a median cost-of-living city. The remote rate is often around what you'd get in Chicago or Austin, regardless of where you actually live.
The model matters enormously when you're evaluating offers. Always ask: "How does the company determine compensation for remote employees?" before you negotiate.
Location banding is the single biggest thing most aspiring analysts don't understand before they start comparing remote offers to city offers.
Here's how it plays out in practice. A company offers you a remote data analyst role at $95,000. You're living in a mid-cost city. Sounds great. Then you move to Austin for other reasons, and your salary stays at $95,000 because Austin is already in that tier. Fine. But if you then move to San Francisco, the company adjusts your pay down to match the SF band, which might be $115,000, or they leave it at $95,000 because you're now underpaid relative to market but still technically within band.
The reverse is also true. If you're currently in San Francisco and take a remote role at the SF rate, then move to a lower cost-of-living city, many companies will reduce your salary to match the new location's band at the next review cycle. Some do it immediately.
Before accepting a remote role, ask explicitly:
Most companies are willing to answer these questions directly during the offer stage. If they aren't, that's a signal worth paying attention to.
The honest comparison isn't just base salary. It's total compensation minus cost of living, adjusted for taxes. Here's how to think through it.
A San Francisco in-office role at $120,000 sounds significantly better than a fully remote role at $95,000. Run the actual numbers and the picture changes. California has a top marginal income tax rate of 13.3%. Housing in San Francisco averages significantly more than most of the country. When you adjust for state income tax, rent differential, and commuting costs, the $95,000 remote role in a no-income-tax state can net out to the same or better real purchasing power.
The math works differently depending on your specific situation. But the variables to factor in are:
I've seen this play out repeatedly across people I talk to through Analyst Hive. The analyst who took a fully remote role at $88,000 in a mid-cost city is often in a materially better financial position than the one who took a $105,000 in-person role in a high-cost market, once you account for taxes and rent. The headline number lies. The take-home number is what matters.
Target in-person or hybrid roles in a major city if:
Target fully remote roles if:
Neither path is universally better. The decision that looks obvious from the outside often doesn't hold up once you run the actual numbers for your specific situation.
If you're at the stage of building the skills and portfolio that get you to either type of offer, Analyst Hive is built specifically for that path, whether you're targeting a local market or remote-first companies.
Remote candidates are in a structurally different negotiating position than in-person candidates, and most people don't use that difference effectively.
If a company uses location banding, you can use competing offers from different bands as a reference point. An offer from a company anchored to SF rates gives you a legitimate reason to push back on a company using mid-market remote rates. "I have a competing offer at $X from a company that anchors to their headquarters in San Francisco" is a real negotiating position even if you're in Austin.
For companies with national rates, the negotiation is more like a standard negotiation: competing offers, demonstrated expertise, and specific value you bring to the role. The remote factor doesn't hurt or help much here.
A few tactics that work specifically for remote roles:
The worst thing you can do is accept the first number without asking at least one question. Even a simple "Is there flexibility on the base salary?" costs you nothing and has a real chance of adding $5,000 to $10,000 to a remote offer.
If you're working through offer evaluation and negotiation for the first time, that's covered in the job search section of Analyst Hive, including scripts for how to ask these questions without sounding inexperienced.
Do fully remote data analyst jobs pay the same as in-person jobs?
It depends on the company's remote compensation policy. Companies that pay by HQ location tend to pay remote employees the same as local employees. Companies with location banding pay based on where you live. The range is wide, so always ask how compensation is determined before you evaluate the offer number.
Is it possible to get a San Francisco salary while living somewhere else?
Yes, but it's becoming less common as more companies have shifted to location-based pay. It still happens at startups and companies that haven't implemented formal location banding, and some companies grandfathered existing employees under old pay structures. Going forward, the trend is toward location-adjusted pay for remote roles.
Which city has the best real purchasing power for data analysts?
Austin and Seattle consistently score well when you combine salary levels, tax environment (no state income tax in either), and cost of living. Chicago and Atlanta offer strong purchasing power too. San Francisco and New York have the highest base salaries but the cost of living significantly erodes the advantage for most salary levels below $150,000.
Does being remote hurt your chances of promotion or raises?
Potentially, depending on the company. In companies where the majority of leadership is still in-office, remote employees sometimes report slower promotion timelines and less visibility. This is less of an issue at companies that were remote-first or have fully distributed leadership. It's worth asking how many current senior analysts or managers are remote before accepting a role if this matters to you.
How do you compare a remote offer with a city offer fairly?
Run the after-tax, after-housing-cost comparison. Calculate your expected state income tax for each scenario, estimate the realistic rent difference, and add any commuting costs for the in-person role. Compare the resulting monthly take-home. Then factor in things like career trajectory, team quality, and growth opportunity, which don't show up in the math but often matter more over a 3 to 5 year horizon.
Are there data analyst jobs that are truly location-agnostic in pay?
Yes, but they're more common at smaller companies and startups that haven't built out a formal HR infrastructure around location banding. Some mission-driven tech companies and certain consultancies also maintain flat national rates. They're worth targeting if you're in a lower cost-of-living area and want the salary ceiling that comes with HQ-anchored pay.
Base salary is the starting point. What you actually take home after taxes, rent, and commuting costs is the number that changes your life. A remote role at $90,000 in a no-income-tax state with low rent can net out better than a $115,000 in-person role in San Francisco or New York. Run the math for your specific situation before you decide which type of role to chase.
The skills that get you to either type of offer are the same: strong SQL, a real portfolio, and the ability to communicate your analysis clearly. Those are what move the salary number regardless of the city on the offer letter.
If you're building toward your first data analyst offer, in a major city or fully remote, join Analyst Hive. The 90-day program covers the technical skills, portfolio builds, and job search strategy that gets you to the offer stage.
