Salary expectation questions feel higher-stakes for UX Designers than for many other roles because the pay range is genuinely wide. According to the U.S. Bureau of Labor Statistics, Web and Digital Interface Designers, the closest BLS classification to UX Designer, earned a median of $98,090 in May 2024, with the bottom 10 percent earning under $47,840 and the top 10 percent pulling in more than $192,180. That $144,000 spread between floor and ceiling is not noise; it reflects real differences in seniority, industry vertical, company size, and the depth of research-to-delivery ownership the role requires. Naming a number that ignores those variables can either price you out of a role you wanted or anchor you far below market before the first coffee chat ends.
This guide walks you through a three-part framework built specifically for UX work, the factors that legitimately move your number up or down, eight sample answers at different career stages and contexts, and the mistakes that UX candidates make more often than candidates in other disciplines.
Why This Question Hits Differently in UX
Hiring managers ask about salary expectations partly to filter and partly to calibrate. In UX specifically they are also testing whether you understand the market for your actual scope of work, because “UX Designer” covers everything from a junior who ships Figma screens under close supervision to a senior who runs generative research, synthesizes insights into strategy, and holds a seat at the product roadmap table.
If you quote a number without context, the hiring manager mentally fills in the context for you, and that guess is almost always conservative. If you ask a clarifying question first and then frame your number around the scope of the role, you signal that you understand how UX value is priced, which itself is a form of research skill.
There is also a practical asymmetry: most UX job postings skip the salary range even in states that require disclosure, so you often go in knowing less than you should. Being prepared means doing that research before the screen, not scrambling during it.
The Three-Part Framework
A strong answer to “What are your salary expectations?” has three components: an anchor, a range, and an opening for dialogue.
Anchor: A specific number or tight range grounded in market data and your experience level. Vague answers (“somewhere in the six figures”) make you look unprepared. Precise anchors (“I’m targeting a base of $115,000 to $125,000”) do the opposite.
Justification: One sentence connecting the number to something real, your years of end-to-end ownership, the domain expertise you bring (healthcare, fintech, enterprise SaaS), or the research capabilities you carry. You are not defending yourself; you are giving the hiring manager a logical narrative to use internally when making the offer.
Dialogue opener: A brief invitation to discuss. Something as simple as “Does that land within the band for this role?” accomplishes two things: it gives the recruiter permission to tell you if there’s a mismatch early, and it signals flexibility without volunteering a concession you haven’t negotiated yet.
What Moves Your Number Up or Down
Before you settle on an anchor, work through these factors:
- End-to-end research ownership. Roles where you run user interviews, synthesize findings, and present to stakeholders command more than roles where research is handed to you pre-packaged.
- Industry. Fintech, health tech, and enterprise B2B SaaS consistently pay above the median. Consumer apps and agencies trend lower.
- Company stage. Series B and later startups with design maturity often match big-tech base salaries to compete; early-stage companies usually offset lower base with equity.
- Tool and platform depth. Owning a design system, having shipped accessibility-compliant products under WCAG 2.1, or holding Figma organization-level skills are concrete differentiators recruiters value, cite them when relevant.
- Measurable impact. If you can attach a metric to your past work (conversion rate lift, task-completion improvement, SUS score delta, churn reduction), your asks carry more weight.
- Location and remote policy. Fully remote roles posted by Bay Area or NYC companies increasingly pay geo-adjusted comp, verify before you assume you’ll get SF rates.
Eight Sample Answers for UX Designers
1. Entry-Level, First Full-Time Role
“Based on my research into the market for UX Designers with one to two years of experience in the Pacific Northwest, I’m looking for a base in the range of $72,000 to $80,000. That reflects roles with a mix of product and research work, which I’m excited to continue developing here. Is that in line with what you’ve budgeted for this position?“
2. Mid-Level, Moving from Agency to In-House
“After four years on the agency side, where I led end-to-end UX for clients across retail and healthcare, I’ve done some research into in-house comp for comparable experience, and I’m targeting $105,000 to $115,000 base. A big part of my move is the opportunity to own a product over time rather than in sprints, so I’m also curious how you structure career progression here. Does that range work on your end?“
3. Senior, Bringing Domain Expertise in Fintech
“For a senior UX role at a fintech company, I’m looking at a base between $130,000 and $145,000. I say that because I’ve spent the last three years designing for compliance-heavy financial workflows, KYC onboarding, transaction histories, dispute resolution, and that domain expertise tends to reduce ramp time significantly on a team like yours. Happy to dig into the specifics of how you think about senior UX comp here.”
4. Staff or Lead Level, Design System Ownership
“I’ve been benchmarking at the staff or lead level since I’ve spent the last two years building and governing a design system used across six product teams. For a role with that kind of cross-functional ownership, I’m targeting $155,000 to $170,000 in base salary, with equity as an additional consideration. I know that’s at the higher end of the range for some companies. Is there flexibility in the total comp package if the base is fixed?“
5. Career Pivoting from a Related Field (e.g., Graphic Designer Moving to UX)
“I’m transitioning from a background in visual and brand design, and I want to be realistic about where I sit in the UX market. Based on my research and the bootcamp portfolio projects I’ve shipped, I’m aiming for $65,000 to $72,000, which feels appropriate for someone bringing strong visual fundamentals but still building the user research and information architecture muscles. I’m more focused on getting into the right environment than maximizing the number at this stage, but I did want to have an honest conversation about it.”
6. Negotiating After a Lowball Offer
“I appreciate you sharing that. $90,000 is a meaningful offer and I’m genuinely excited about the role. I was targeting $105,000 based on the BLS median for digital interface designers and the specific research ownership this position involves. I’d love to find a path to close that gap. Is there room to revisit the base, or would a sign-on bonus or accelerated first review timeline be on the table?“
7. Contract-to-Hire or Part-Time Engagement
“For an hourly contract engagement, I typically work at $75 to $90 per hour depending on the scope of research involvement. Discovery-only work sits at the lower end, full end-to-end from problem framing through usability testing and handoff sits at the higher end. If this converts to a full-time role, I’d want to revisit the conversation with total comp in mind, but I want to make sure we’re aligned on the contract terms first.”
8. Remote Role at a Startup with Equity Component
“I’m targeting a base of $115,000 to $125,000, which is where I’d expect to land for a senior IC role at a growth-stage company. I understand equity is a significant part of the package at this stage. I’m interested in understanding the strike price, vesting schedule, and what the last valuation looked like so I can evaluate total compensation properly. Are you able to share those details before we get further along in the process?”
Mistakes UX Designers Make More Often Than Others
Anchoring to a Job Title Rather Than a Scope
“UX Designer” at a 20-person startup and “UX Designer” at a 10,000-person enterprise are different jobs. If you anchor only to the title without acknowledging the scope difference, you’ll either undersell yourself for a complex role or seem out of touch for a simple one. Make scope explicit in your answer.
Citing Portfolio Effort Instead of Impact
It is common in design interviews to describe how hard a project was, the number of iterations, the messy discovery phase, the difficult stakeholder. None of that moves salary. What moves salary is outcome: the checkout redesign that lifted conversion by 11%, the navigation restructure that cut support tickets, the onboarding flow that reduced time-to-value from 14 days to 6. Before the compensation conversation, make sure you have at least one number ready.
Skipping the Equity Question at Startups
UX candidates at early-stage companies sometimes accept lower base salaries in exchange for equity without understanding what they’re agreeing to. Vesting schedules (typically four years with a one-year cliff), the current 409A valuation, the preference stack above common stockholders, and the last round dilution all affect what that equity is actually worth. “I’m flexible on base if the equity is meaningful” is only a reasonable position if you know what meaningful means for that specific cap table.
Confessing Too Soon
A significant number of UX candidates volunteer their current salary when asked about expectations, especially women, who research consistently shows do this at higher rates and to worse outcomes. “What are your salary expectations?” is not the same question as “What do you currently make?” In most US states, employers are legally prohibited from asking the latter. Answer the question that was asked, not the one you’re afraid of.
Refusing to Give Any Number
Some candidates have read advice telling them to let the employer go first, always. That advice is situationally true in early-stage conversations, but in a direct recruiter screen it can come across as evasive and slow down the process. If you have done your research and your range is grounded in data, naming it is a display of confidence, not a concession. Saying “I’d prefer to learn more before naming a number” is reasonable once, not three times in the same call.
Treating the Conversation as One-and-Done
Compensation conversations in UX often span multiple conversations: the recruiter screen, the hiring manager discussion, and the offer call. Your answer in the recruiter screen is an opening position, not a binding commitment. You are allowed to say “that’s my current thinking, and I’d like to revisit once I understand the full scope of the role”, and then do exactly that when you have more information.
Preparing Your Number Before the Interview
Do this research before any compensation conversation, not during:
- Pull the BLS data for Web and Digital Interface Designers (SOC 15-1255) for your region. The national median was $98,090 in May 2024, and the BLS publishes state-level estimates.
- Check two or three current job postings for the same title at similar companies. States like Colorado, New York, and California require pay range disclosure; filter to those if you need benchmarks.
- Know your top three differentiators, the specific research methods you use, the tools you own deeply, the measurable outcomes you can cite, and connect at least one of them to your number.
Your salary expectation answer is itself a UX artifact: it should be clear, grounded in evidence, and designed to move the conversation forward. Put the same rigor into it that you put into your deliverables.
OfferFlow’s resume review tool analyzes your resume against the job description before you go into any salary conversation, so you walk in knowing where you’re strong and where you might want to reframe your experience.