Job search
Salary History vs. Salary Expectations: Responding to a California Job Application
Read a California salary question by time period and compensation component, then answer expectations truthfully or clarify a blocked history field.
Salary history asks what you earned before; salary expectations ask what you want for the new role. In California, employers generally may ask about expectations but may not seek an outside applicant's salary history. Read the exact field before answering. If an application requires a numeric history answer, document the field and ask recruiting how to proceed rather than inventing a number or placing your desired salary in the wrong field.
This guide addresses an outside applicant seeking a California position, using official guidance checked October 12, 2026. It does not establish the law for every state, remote arrangement or internal transfer. LandOffer publishes it; you can use recent roles on LandOffer.ai to find a relevant opening, then inspect the employer's own form. All candidates, amounts and exchanges below are fictional teaching examples, not legal advice for a dispute.

Read the time period and compensation component
Read a salary question for its time period, compensation component and unit. Identify all three before choosing an answer. “Current compensation” and “desired annual base salary” can appear near each other while asking for different information.
History can concern a current job or a previous one. Expectations concern the position you are applying for. A field asking for the most you have earned remains a history question even if its label avoids the word salary.
Next, distinguish annual base pay, hourly wages and total compensation. A desired package that includes bonus or equity cannot automatically be copied into a base-pay box. Recording the component and currency keeps an annual base-pay answer from being mistaken for an hourly rate or a full package.
If the prompt says only “salary,” look for adjacent instructions, a currency selector or an hourly/annual choice. If the intended meaning remains unclear, ask a bounded question. The aim is to determine what the employer is requesting, not to negotiate with an unidentified field.
Do this before relying on an answer bank or autofill. A previously saved expectation is not a verified answer to a new question about current earnings. The question's words decide the response; proximity on the page does not make the fields interchangeable.
Understand the California distinction without expanding it nationwide
The California Labor Commissioner's FAQ says employers generally cannot seek applicants' salary history, including benefits, or rely on it in deciding employment or pay. It permits questions about expectations. It identifies exceptions for publicly disclosable history and voluntarily disclosed, unprompted history; prior salary still cannot justify prohibited unequal pay.
The FAQ defines an applicant here as someone seeking employment who is not already employed by that employer. It also describes pay-scale access on reasonable request and posting requirements for employers with at least 15 employees, with additional counting and California-location interpretations. Those qualifications matter; a small employer's posting and an internal transfer should not be analyzed with an oversimplified slogan.
Use that official explanation to frame your question. It does not mean every pay-related field is prohibited, and it does not determine which jurisdiction governs a complicated cross-state situation. If the role's California connection is uncertain, establish the intended working location and ask for appropriate guidance before asserting a legal conclusion.
A form can also be outdated or configured for multiple locations. The form alone does not establish why the employer included the field. Describe what the application asks and let recruiting address the specific issue.
Map the field to the response it needs
Use this completed classification example before discussing an amount. The responses show a practical approach, not words every employer must accept.
| Application wording | What it asks | A response approach for the California scenario |
|---|---|---|
| Current annual salary | Existing earnings | Ask how to proceed without supplying salary history |
| Base salary at your last employer | Earlier earnings | Treat as history even though the employment has ended |
| Desired annual base salary, USD | New-role expectation | Give a genuinely acceptable expectation in the requested component |
| Expected total compensation | New-role package | Clarify included components; do not silently substitute base pay |
| Minimum acceptable hourly rate | New-role threshold | State a real hourly threshold if ready to commit to one |
| Salary, numeric answer required | Ambiguous | Ask whether this means expectations or history before entering a number |
The last row remains unresolved because its wording does not identify history or expectations. Classifying an ambiguous question honestly is better than turning a convenient interpretation into an unsupported answer.
For a history text box, one possible response is: “I prefer to discuss the compensation for this position rather than prior pay. Please advise how to complete this salary-history field for a California application.” Adapt the wording to your situation and the actual instructions.
If the field is optional, consider leaving it blank. If it offers an accurately described decline option, that may be usable. Do not assume a blank is accepted until the form's validation and review page permit it.
Build an expectation from the role you would accept
A useful expectation reflects the new role's work, level, location and compensation structure. Start by reading any published range and identifying what it covers. The separate guide to salary ranges in tech postings explains how to compare ranges and unresolved components.
Write a private minimum you would actually consider, then decide the expectation you want to communicate. These need not be the same number, but neither should be a random entry chosen only to pass validation. A submitted amount may become the starting point for later discussion.
For an annual base-pay question, keep bonus, equity and one-time payments in separate notes. If the employer's range includes several levels or locations, ask which range applies to this vacancy. A broad published band does not tell you where your specific offer would fall.
For hourly work, use the requested hourly unit. Do not convert to annual pay without accounting for working hours and paid weeks, and do not present an assumed annualization as a guaranteed income. If the question asks for a minimum, make sure the answer represents a minimum you could accept under the stated conditions.
A text field can carry a range and a qualification about scope. A numeric field cannot express the same detail. Before choosing one number, decide whether you are comfortable standing behind it and how you will communicate any unresolved terms.
A completed example: two salary fields, two different actions
Consider Dana, a fictional backend engineer applying to a California position. The fictional posting lists an annual base range of $130,000–$170,000. After reviewing the responsibilities and her requirements, she would target $145,000–$160,000 in annual base pay, with other components discussed separately. These amounts are invented, not a market benchmark.
The form contains “Current annual salary” and “Expected annual base salary, USD.” Dana does not copy one number into both. She treats the first as a history question and the second as an expectations question.
If both allow text, her completed draft could read:
Current annual salary: Please advise how to complete this salary-history field for a California application without supplying prior compensation.
Expected annual base salary: $145,000–$160,000 USD, depending on the confirmed level and responsibilities. Bonus and equity would be discussed separately.
The result is a draft with one explicit clarification and one defined expectation. It does not establish that the employer accepted either entry or that Dana will receive an offer in that range.
If the expectation field accepts a single number, Dana might enter 150000 only if that is an expectation she genuinely wants to communicate. That example is not a rule to choose a range's midpoint. She records that the entry means annual base salary in USD, and keeps the fuller wording for the recruiting discussion.

When the salary-history field will not let you continue
A required number field creates a form problem. Entering zero, one or a desired amount can create an inaccurate record unless the employer has explicitly instructed applicants to use that value for a defined purpose. A system accepting a number does not make the number truthful.
First, save your draft if the application supports it. Record the job reference, exact field label, required marker, numeric-only restriction and validation message. Keep a screenshot that shows the question while avoiding unrelated sensitive details.
Then use the employer's stated recruiting or application-support channel. A concise message for Dana could be:
I am applying for backend role CA-214. The application requires a numeric “Current annual salary” entry and does not offer a decline option. For this California position, how can I continue without providing salary history? I can provide my expected annual base compensation in the separate expectations field.
This question gives the recipient enough information to reproduce the obstacle. It does not accuse an individual recruiter of misconduct or require you to disclose the history while asking how to withhold it.
If support provides a placeholder instruction, save the response with the application record and confirm what the value will represent. Do not generalize that employer-specific workaround to another company's form. If the instruction remains unclear, seek clarification before submitting an entry you cannot explain accurately.
A deadline may arrive before a reply. You must then decide whether to pause, use another officially offered application route or stop pursuing the vacancy. This guide cannot promise that a support request preserves a deadline or guarantees review.
Keep evidence and escalation proportionate
Preserve the relevant question, date, job identifier and response. Those records help distinguish what the form asked from what you remember it asking. They also make a later correction more specific than “the salary section was confusing.”
The state's pay-transparency complaint instructions distinguish salary-history issues from missing-range issues and other complaint routes. The accompanying complaint form includes a category for employers seeking or relying on applicants' salary history. Consult the current official materials or qualified advice if you want to evaluate a complaint.
A recruiting clarification and a formal complaint serve different purposes. The first asks how to complete an application accurately. The second invokes an official process with its own information requirements. You do not have to treat every technical obstacle as a proven violation to preserve evidence or ask for help.
If you already entered an inaccurate amount, identify the exact field and seek a correction through the employer's channel. Explain whether it was a mistaken history entry or an expectation entered with the wrong unit. Do not create a new account or duplicate application simply to erase the first version.
Review the answer before reuse
Keep expectations attached to the role and date that justified them. A range suitable for one level, location or employment arrangement may not fit another. Reusing the wording should begin with a new reading of the question.
Before submitting, check that history, expectations, base pay and total compensation have not been merged. Verify currency and period, retain a copy of your final entry, and note any unresolved instruction. This creates a clear record for the next conversation rather than a misleading number that happens to pass validation.
For your next California application, select a relevant opening from recent roles on LandOffer.ai, classify each compensation field and prepare one truthful expectation for that specific role. If a history field blocks the form, ask the employer for a way to continue without inventing an entry; save any reply with the application.
Sources and Further Reading
- California Labor Commissioner: Equal Pay Act and pay-transparency FAQ — salary history, expectations, applicant scope and pay-scale distinctions.
- California DIR: pay-transparency complaint instructions — issue categories and filing context.
- California DIR: pay-transparency complaint form — current official reporting categories.


