Product Designer Salary in Minneapolis — 2026 BLS Data
Salary distribution
Percentile breakdown of Product Designer base salaries in Minneapolis.
The $112K median base for a Product Designer in Minneapolis looks reasonable on its face — but it masks one of the widest spreads in any US mid-tier market. That number comes from BLS OEWS May 2024 data for SOC 15-1255 (Web and Digital Interface Designers — the federal classification that captures the core of product design work) applied to the Minneapolis-St. Paul-Bloomington metropolitan area, where wages run approximately 14-17% above the national occupational median of $98,090. The spread from P25 to P90 spans $90K, and the P90 of $175K doesn’t include equity or bonus. If you’re a mid-to-senior designer in the Twin Cities market right now, the question isn’t whether $112K is fair in the abstract — it’s whether your specific role at your specific company maps to P50, P75, or somewhere in between.
The percentile spread: what each band actually represents
Product Designer salaries in Minneapolis don’t form a bell curve. They cluster around a few distinct employer types, and the BLS percentile bands map to those clusters more than they map to years of experience.
P25 — $85,000. Junior-level roles (0-2 years) at regional employers, or mid-level designers at organizations where design is a support function rather than a product investment. Think insurance companies, healthcare systems, government contractors, and traditional retailers that have digital teams but don’t operate as product-led businesses. Designers at this band often hold generalist “UX designer” or “web designer” titles, work on projects handed to them rather than problems they define, and have limited exposure to research or systems thinking at scale.
P50 — $112,000. A mid-level Product Designer (3-5 years) with a portfolio that demonstrates end-to-end ownership — research, wireframes, shipped features, iteration based on data. This is the going rate at a growth-stage Minneapolis startup, a design-forward employer in the retail-tech or healthcare-tech space, or a mid-size enterprise that runs a real product team. If you’re at this career stage and earning below $105K in Minneapolis, you have market data to support a conversation about a raise.
P75 — $145,000. Senior designers who own a problem space from discovery through delivery and can lead junior teammates without a formal management title. This band captures Minneapolis’s highest-paying segment for ICs: Target’s digital product division, Best Buy’s experience design team, UnitedHealth Group’s digital product organization, and the handful of growth-stage B2B SaaS companies in the Twin Cities with real design investment. Designers who specialize in design systems, healthcare UX, or data-heavy B2B interfaces tend to reach this band faster than generalists.
P90 — $175,000. Staff-level designers and above, or senior ICs at the top-paying employers in the metro. This band also captures senior designers employed by remote-first coastal companies but living in Minneapolis and paid at the company’s HQ rate. Realized equity income in a strong vesting year can push some designers into this band even when their base alone wouldn’t.
One structural caveat: BLS OEWS reports base wages paid to employees during the survey reference period. It excludes equity gains, profit-sharing, and performance bonuses that land in a different pay period. The actual spread in the market is wider than the percentile table shows once you include those components.
Hub comparison: how Minneapolis stacks up
Minneapolis is the largest tech market in the Upper Midwest and punches above its weight for design salaries relative to its cost of living — but it does trail the coastal hubs on nominal comp. Knowing where it sits helps you calibrate whether an offer is competitive for the city or just competitive in the abstract.
San Francisco Bay Area. SF product designers run $150K-$165K median base — roughly 35-45% above Minneapolis. That gap shrinks dramatically when you apply cost of living: SF’s COL index of approximately 178-185 versus Minneapolis’s 106 means a $165K SF salary buys roughly the same lifestyle as $95K in Minneapolis. The Bay Area premium is real but it’s mostly consumed by rent.
New York City. NYC median for this role is approximately $130K-$140K, driven by media, finance-adjacent tech, and a dense startup ecosystem. NYC’s COL index runs 185-200 depending on borough. A $130K NYC salary adjusted for cost of living has less purchasing power than a $112K Minneapolis salary.
Chicago. The most direct comparison for Minneapolis designers. Chicago’s product designer median runs around $115K, within $3K of Minneapolis. Chicago’s COL index is approximately 113.5 — about 7 points higher than Minneapolis. On a purchasing-power basis, Minneapolis and Chicago are nearly equivalent, but Minneapolis tends to score better on housing affordability specifically, which is the largest single line item in most budgets.
Seattle. Amazon and Microsoft anchor Seattle’s design market at a $135K-$145K median. Seattle’s COL index runs 140-150, which erodes most of that nominal advantage. A $145K Minneapolis P75 designer has meaningfully more purchasing power than a $140K Seattle designer.
Austin. Austin’s product designer median is approximately $110K-$118K on a COL index of 119.3. Minneapolis and Austin are very close on nominal comp, but Minneapolis’s lower COL gives a slight purchasing-power edge, particularly on housing.
The practical upshot: if you’re a Minneapolis-based designer considering whether to relocate, the only market where the nominal pay difference is large enough to survive the COL adjustment is fully remote work at a SF-paying company. Every other comparison either washes out or favors staying put.
What drives the spread: company tier, level, and specialty
Three variables explain most of the P25-to-P90 range inside the Minneapolis metro.
Company tier
Minneapolis’s design employer market is built around a few dominant sectors: retail (Target, Best Buy, Cargill, General Mills), healthcare and benefits (UnitedHealth Group, Optum, Medtronic, Allscripts), and a growing B2B SaaS layer. The company you work for matters more to your salary than almost any other single variable.
Fortune 500 / large enterprise employers — Target, Best Buy, UnitedHealth Group, Medtronic — pay $120K-$155K at senior levels with structured bands and real benefits. Equity is common in the form of RSUs at the publicly-traded companies, though grant sizes are often more conservative than pure tech companies. These employers offer predictable total comp with less upside ceiling than a high-growth startup.
Growth-stage startups and mid-size tech companies in the Twin Cities startup ecosystem (Salo Partners, Clockwork, Bright Health, Structural) pay $100K-$140K at senior levels, often with equity that ranges from meaningful to speculative depending on the stage and business model. Design leadership roles at these companies can exceed P90 on total comp in good years.
Non-product-led employers — banks, insurance companies, healthcare systems, manufacturers with digital initiatives — typically pay $75K-$110K for roles that carry senior titles but involve less product ownership. These are the employers who populate the P25-P50 bands for experienced designers.
Agencies and consultancies paying Minneapolis-adjusted project billing rates often land at $80K-$115K, without equity, but with broader portfolio variety than in-house roles.
Career level
Minneapolis’s leveling vocabulary varies by company but the economics are consistent:
- Junior (0-2 yrs): $65K-$85K base, usually no equity, nominal bonus
- Mid-level (2-5 yrs): $90K-$120K base, equity at tech-native employers runs $20K-$60K over four years, minimal or no equity at traditional enterprises
- Senior (5-8 yrs): $125K-$155K base, equity grants of $40K-$100K over four years at employers who offer it
- Staff/Lead (8+ yrs): $155K-$190K base at the top employers, equity grants that can approach or exceed annual base at high-growth companies
Each step up represents real additional comp. The P25-to-P90 spread of $90K isn’t random noise — it’s largely the difference between a mid-level role at a non-tech employer and a senior role at a Fortune 500 digital team or funded startup.
Specialty premium
Three specialties command above-median rates in Minneapolis’s design market:
Healthcare UX. With UnitedHealth Group, Optum, Medtronic, and a cluster of health-tech startups, Minneapolis has one of the denser healthcare tech design ecosystems outside Boston and San Francisco. Designers with clinical workflow experience, patient portal work, or EHR system design in their portfolio — especially with HIPAA-sensitive data at scale — earn 10-20% above generalist peers at the same seniority. Regulatory complexity and the cost of design errors in healthcare justify the premium.
Design systems. A senior designer who can build and maintain a design system — tokens, component library, Figma-to-engineer handoff, documentation, and governance — commands $145K-$165K at Minneapolis’s larger product organizations. Supply of designers who can do this well lags demand; if you have shipped design system work, make it prominent in your portfolio.
Data-dense B2B interfaces. General Mills, Cargill, and several supply-chain and logistics companies in the metro need designers who can make complex data readable and actionable. Designers comfortable with dashboard design, data visualization conventions, and working with dense information architectures have a cleaner path to P75 in Minneapolis than generalists do.
Total compensation breakdown
For a mid-level (P50) Product Designer at a typical Minneapolis tech-oriented employer, the full package looks like this:
- Base salary: $112,000. This is the BLS-tracked number and the anchor for all future comp conversations. Most employers structure raises as a percentage of base, so the initial base negotiation compounds over time.
- Annual cash bonus: ~$9,000. Cash bonuses for design roles in Minneapolis run approximately 8-10% of base at companies that offer them — Fortune 500 employers typically hit this range; agencies and smaller companies often pay base-only. When a bonus exists, it’s usually tied to both company financial performance and an individual performance rating, making it discretionary in practice. Budget for 75-80% of target, not 100%.
- Annualized equity: ~$12,000. At the median, this reflects an RSU grant of roughly $45K-$50K over four years at a publicly-traded Minneapolis employer like Target or Best Buy, or nothing at the large volume of non-tech employers that make up part of the Metro average. The equity distribution in Minneapolis skews bimodal: $0 at traditional enterprises, $15K-$80K annualized at tech-native employers. The $12K figure represents the blended average across all employer types and suppresses both tails.
Total at median: approximately $133,000. At P75 ($145K base), assume $12K-$15K bonus and $25K-$50K annualized equity at a tech employer — total comp runs $182K-$210K. At P90, total comp can exceed $230K at the top-paying employers in the metro once equity is included.
Designers evaluating offers should always ask three questions: Is there an equity program, and if so, what is the dollar amount of the initial grant? What is the bonus target and what percentage was actually paid in the last two years? Are there defined level bands, and which band does this role fall into?
Cost-of-living adjusted purchasing power
Minneapolis’s cost-of-living index of approximately 106 (US average = 100) means living expenses run about 6% above the national average. That modest premium is driven mostly by housing — median home prices in the Minneapolis metro were approximately $350,000 in 2024 according to Minnesota Realtors Association data, and median monthly rent for a one-bedroom in Minneapolis proper runs $1,500-$2,000 — combined with Minnesota’s income tax, which ranges from 5.35% to 9.85% for high earners.
On a purchasing-power basis, a $112K Minneapolis salary is equivalent to roughly $106K at the US average COL — meaningfully above the national BLS median for this occupation ($98,090) and miles ahead of what the same nominal salary buys in San Francisco ($63K equivalent purchasing power) or New York ($57K equivalent on a high-COL index).
Where Minneapolis creates a structural advantage for mid-to-senior designers: the P75 band. A $145K Minneapolis salary has approximately $137K of purchasing power at the US average COL. A San Francisco designer at the same purchasing power would need to earn approximately $244K in nominal terms. The SF designer who earns $185K at the local P75 — which is a real number — is still earning $9K less in purchasing-power terms than the $145K Minneapolis designer. For career stages where you’re trying to build equity in a home, pay down debt, or accumulate savings, this math matters in a way it doesn’t for 22-year-olds optimizing for prestige.
Don’t use national or SF-weighted salary averages as your Minneapolis anchor. Use Minneapolis-specific BLS percentile data, cross-referenced with local job postings and Built In Minnesota’s annual survey, and note explicitly in any negotiation that you’re using metro-adjusted figures.
Negotiation playbook: three levers that work in Minneapolis
1. Open at P75, not median
The most common mistake Minneapolis designers make in salary negotiations is anchoring to the number they already earn or to the median they found in a quick search. If you’ve cleared a competitive process and received an offer, the company has already decided you’re their candidate — which means you hold more leverage than a candidate who hasn’t been selected yet.
For a mid-level designer with 4-6 years of solid portfolio work, $138K-$145K is a defensible opening in Minneapolis’s 2026 market. Frame it in market data, not personal need: “Based on BLS OEWS data for the Minneapolis metro and corroborating sources, $138K reflects the 75th percentile for a Product Designer at my experience level in this market. Can you get there?” That framing signals market awareness, not entitlement, which is how the negotiation conversation stays professional.
If the employer is a Fortune 500 with published salary bands, ask which band this role is in and whether there’s room to move within the band before asking to exceed it. Band-to-band moves are harder to approve but within-band flexibility is often available up to 10% without VP-level signoff.
2. Price the equity correctly before you accept or decline
Minneapolis’s equity landscape is more fragmented than SF’s, which makes it genuinely harder to value. RSU grants at Target, Best Buy, or Medtronic are straightforward: they vest in public company stock that you can sell. Equity at a growth-stage Minneapolis startup is a different instrument entirely — it may be worth more long-term or it may be worth nothing.
When evaluating a startup equity package, ask: What is the current preferred share price and the preferred liquidation preference? What is the last 409A valuation? What percentage of the fully-diluted share count does my grant represent? How many rounds of preferred stock are senior to my options? A 0.3% stake sounds meaningful until you learn it represents 200,000 options with a $1.20 strike price in a company where Series B preferred investors hold a 2x liquidation preference on $25M raised. The math matters.
For public-company RSU grants, the negotiation lever is grant size, not base. Companies are often more willing to increase the total grant dollar value than to move base salary, because the grant is a future liability tied to stock price rather than a current cash outflow. If Target offers a $40K RSU grant over four years and a peer at Best Buy has a $65K grant at the same level, that’s a $6K annual difference in expected cash — ask for the grant to be sized comparably.
3. Bring a portfolio case study with a metric to the final round
Minneapolis employers — especially healthcare, retail, and enterprise software companies — respond to evidence more than to years-of-experience claims. Before you enter final-round discussions or respond to an offer, prepare a single focused case study that shows one project outcome in quantitative terms: a reduction in task completion time, a lift in conversion from a checkout redesign, a reduction in engineering rework after implementing a design system, a decrease in user-reported errors after a workflow redesign.
This documentation does two things simultaneously. First, it gives the hiring manager concrete material to present internally when they go to approval for a higher offer. “Candidate achieved 22% reduction in support tickets after redesigning onboarding flow” is a more compelling business case than “candidate has six years of experience.” Second, it opens a natural conversation about role scope — if your case study shows you’ve been operating at staff level, ask explicitly whether the offer reflects that. Companies sometimes hire at a senior title because that’s the approved headcount, but will move the band if the hire makes the case that the role demands a staff designation.
Caveats and data limitations
BLS OEWS is the most methodologically rigorous public salary source available — mandatory employer reporting covering tens of millions of workers — but it has limitations specific to this occupation and this market.
SOC 15-1255 is a broad classification. “Web and Digital Interface Designers” covers UI designers, UX designers, visual designers, and some web production roles that share an occupation code with senior product designers. A junior UI designer at a traditional print-and-digital agency and a staff product designer owning a core surface at a healthcare tech unicorn both show up in the same BLS bucket. The percentile spread is partly this heterogeneity, not just seniority.
Equity is excluded entirely. BLS OEWS captures wages as reported on payroll records — base salary and sometimes cash bonuses. RSU vesting events, stock option exercises, and profit-sharing distributions are outside the methodology. For tech-native employers in Minneapolis, this understates total comp by 15-30% at senior levels. For traditional enterprise and agency roles, the gap is zero.
The Minneapolis-St. Paul-Bloomington MSA is geographically large. The metropolitan statistical area used in BLS metro-level data includes suburban employers in areas with meaningfully lower costs and lower wage expectations than Minneapolis proper. Downtown Minneapolis and the Minnetonka-Eden Prairie tech corridor run 10-15% above the MSA aggregate for design roles. If you’re negotiating for a role in the city core or at a major tech employer’s HQ, you can apply a modest upward adjustment to the metro-wide figures.
May 2024 data reflects wages from early-to-mid 2024. The BLS publishes OEWS data on an approximately 12-18 month lag. By the time you read this in late 2026, the top employers in Minneapolis have likely moved base bands 5-8% higher. Treat these figures as a well-grounded floor, not a static ceiling.
For the most current picture, triangulate BLS percentile data with Salary.com’s Minneapolis UX/product designer salary benchmarks (which showed a P50 of $119K for UX Designer in Minneapolis as of mid-2026), Levels.fyi’s Minneapolis filter for total comp, and Minnesota salary transparency disclosures on job postings, which are increasingly common even without a state-level mandate as remote-first and multi-state employers include ranges by default. The combination of these sources gets you within 8-10% of what any specific Minneapolis offer in 2026 should look like.