How to Answer the Desired Salary Question on Workday and Other ATS Forms (2026)

How to Answer the Desired Salary Question on Workday and Other ATS Forms (2026)
TL;DR β The desired salary field is a screening tool, not an offer. When the field is free text, answer with a researched range or say "negotiable"; when the employer posts a salary band, stay inside it. Anchor low and the ATS filter can reject you before a recruiter ever sees your resume. Jobzmatic saves your answer in the Knowledge Bank and holds every application for your review before submission, so the number stays consistent across applications and stays yours to adjust per role.
What recruiters actually use that number for
Answer first: the desired salary field exists to filter candidates cheaply. It is one of the only questions on an application that produces a single comparable value, so recruiting teams build rules around it. Three uses, in order of consequence:
- Knockout filter. Large employers configure their ATS with an approved band per requisition, and Workday lets recruiters set a maximum expectation that triggers automatic rejection with no human review. Above the band's ceiling, the process can end there.
- Budget screening. Even without a hard knockout, your answer tells the recruiter whether the requisition is fundable at your expectation. Far below the band raises its own question; far above it ends the conversation.
- Range anchoring. Whatever you type becomes the baseline for the eventual offer conversation. Recruiters negotiate from your stated number, so a low anchor drags the offer down before it starts.
The range-field variant. Workday and several other platforms split the question into two numeric fields, "Desired Salary Minimum" and "Desired Salary Maximum," usually with a frequency dropdown (annual, monthly, hourly). Fill both: a minimum with no maximum looks evasive, and some configurations treat an empty maximum as zero when filter logic runs. Match the posted frequency too, since an annual figure typed into an hourly field multiplies your number by roughly 2,000 and lands you straight in the knockout pile.
How the desired salary field flows:
ATS input (single number, or a min/max pair)
|
v
Recruiter filter stack
|-- Hard knockout: expectation above approved max -> auto-reject
|-- Budget screen: expectation vs. posted band
`-- Anchor: your number becomes the negotiation baseline
|
v
Shortlist and interviews
|
v
Offer stage (real negotiation happens here, not in the form)
The three defensible strategies
Exactly three answers hold up under scrutiny. Everything else (a joke, a dash, "1") fails validation or signals you did not think about the question.
1. Give a researched range. When the field is free text and no salary is posted, state a range built from posted ranges of comparable roles at your level. Keep the spread tight enough to look informed and wide enough to leave negotiating room. A range is also more honest than a single number, because it admits what a single number hides: your expectation depends on level, equity, and total compensation.
2. Say "negotiable" or "open" when it is free text. Legitimate when you genuinely do not know the market for that role and city, and it moves the salary conversation to the offer stage where you have more leverage. Caveats: it only works in text fields, and a recruiter screening hard on salary may treat it as a non-answer and screen on your work history instead.
3. Match the posted range when it is posted. In US states with pay transparency rules (California, Colorado, New York, Washington, among others), the band is printed on the posting. The safest answer sits inside the posted band, at or slightly above the midpoint if you meet most of the qualifications. Quoting the absolute maximum reads as zero flexibility; quoting below the minimum invites a lowball.
How to research the number before you type it
You need three inputs, and none of them require guessing:
- Posted salary ranges where disclosed. The strongest signal is the band on the posting itself, then the bands on similar postings from the same company. Same company, same level, adjacent titles tell you how that employer grades roles.
- Level benchmarks. Look up the title at your level across comparable employers and triangulate across several sources rather than trusting one. A seniority mismatch (senior title, mid-level band) explains most "why is this range so low" moments.
- Geographic adjustment. The same role pays differently by metro. For remote roles, anchor to the location the employer uses for pay purposes, which is usually stated in the posting or its fine print. If it is not stated, anchor to the role's listed location, not your own address.
Then sanity-check the format before typing: annual versus hourly, base versus total compensation, currency. The field does not care about your reasoning. It cares that the number fits the band.
Common mistakes that cost interviews
- Anchoring low with a single low number. Done to seem flexible or to clear the filter, it then becomes the ceiling for the offer. You cannot un-anchor a number; you can only negotiate away from it.
- Inconsistent answers across applications. Large employers keep your answers in one candidate record, so the number you typed last quarter sits next to today's. Contradictions read as bad faith or as not knowing your own market value.
- Putting text into numeric-only fields. Salary fields on Workday and most ATS platforms are numeric inputs with separate currency and frequency selectors. Typing "$120,000 (negotiable)" or "open" into a numeric field triggers a validation error or blocks the submit button with no useful message. If the field is numeric, type digits only.
- Leaving a required field blank. A blank required field prevents submission. If you have no research yet, use the posted range if one exists; otherwise use a range you can defend out loud.
How Jobzmatic answers it for you
The answer to this question belongs in a saved profile, not in your working memory across fifty tabs. The Jobzmatic browser extension for Chrome and Firefox stores your desired salary answer in the Knowledge Bank, and when a form asks the question it resolves the field through a five-layer engine:
- Layer 0: resume-data heuristics. Direct matches against your structured candidate profile (expectations, location, work authorization).
- Layer 1: past approved answers cache. Fast lookup of answers you already approved on earlier applications.
- Layer 2: Knowledge Bank lookup. Your saved canonical answers, matched by keyword and semantics.
- Layer 3: statistical offline rules. Category heuristics that resolve common field types with no network call.
- Layer 4: AI fallback. Queued only when Layers 0 through 3 cannot resolve the field.
Because the answer comes from your saved entry rather than a fresh guess, it stays consistent across every application, which is exactly what the filter stack rewards. The extension runs client-side inside your own logged-in browser session and never asks for your LinkedIn or ATS passwords. Every application is held for your review before submission, so you can adjust the number for a specific role before it goes out, and you receive a confirmation screenshot afterwards. It covers 40+ ATS platforms, including Workday, Greenhouse, Lever, and Ashby. The full pipeline is on the auto-apply feature page; platform mechanics are in our guide to auto-apply on Workday, Greenhouse, and Lever. Daily caps (5 per day free, 15 Pro, 50 ProMax) keep volume at a level a human can actually review. The free tier includes 1,000 credits with no credit card required; Pro is $9 per month.
What happens after you pass the filter
The field is not the offer. It is an input to the recruiter's sorting decision. The real negotiation starts after the offer, when you have information the form never had: the level you were slotted at, the band the requisition was approved for, and the equity and bonus components. Recruiters expect movement between the form answer and the signed offer; nobody treats a screening field as a binding number.
What the form answer does control is your starting point. Negotiate total compensation at offer stage, cite the posted band if there was one, and keep the gap between your form answer and your final ask reasonable so the conversation starts from credibility rather than contradiction. If you want to know what Workday screens on beyond salary, our guide to beating the Workday ATS walks through the full question stack. If the bottleneck is volume rather than any single question, our breakdown of how many jobs to apply for per day covers a pace that survives both ATS filters and your schedule.
Frequently Asked Questions
Is it better to leave the desired salary field blank?
If the field is optional, blank moves the salary conversation to the offer stage, where you have more leverage and better information. If the field is required, a blank blocks submission, so give a researched range instead. Treat blank as a deliberate choice, not a default.
Does answering high get you filtered out?
Yes. The most common mechanical use of the field is a knockout rule that auto-rejects candidates whose expectation exceeds the approved maximum for the requisition, often before a human sees the application. Answering above the posted band risks silence; answering far below it invites a lowball offer.
Should you match the posted range exactly?
Match the band, not the ceiling. A number at or slightly above the posted midpoint signals you meet the requirements while leaving room to negotiate. Quoting the absolute maximum reads as no flexibility; quoting the minimum wastes the pay transparency rules that printed the band in the first place.
Can you change your answer later in the process?
Yes. The screening answer is an input to filtering, not a contract, and salary is renegotiated at the offer stage when level and band are known. What you should avoid is contradicting yourself between applications at the same employer, since the ATS profile often carries your earlier answers forward and inconsistency costs credibility.