Skip to main content
Explore Products
Orbyt Jobs
Orbyt Intelligence
Orbyt One
Orbyt Jobs
Overview
The job search CRM. Free forever.
Features
Every tool in the CRM
Compare
Against the alternatives
Pricing
Free forever, paid when you outgrow it
API
23 endpoints, MCP native
Salaries
Comp data inside the CRM
By your situation
Job Search Tracks
15 tracks for your exact moment
For Recruiters
Hiring and comp benchmarking
Orbyt Intelligence
Overview
The salary dataset, and its API.
Features
What the platform does
Compare
Against the alternatives
Pricing
Free tier, then Pro and Ultra
API
20 endpoints, Decision-Ready
Start without a card
Playground
Run a live query
MCP server
Three steps into Claude Code
API docs
Endpoints, auth, and limits
Orbyt One
Overview
One account. Every Orbyt product.
Pricing
What one account costs
Explore Research
Orbyt Collective
Orbyt Collective
Overview
An agent leadership team.
How It Works
The machinery, end to end
Process
How the work actually moves
Leadership
The agent officers
Autonomy Ledger
What it decides without us
Influences
The minds we build like
Published
Research Hub
Papers and field notes.
Agent-Native Dataset Design
Preprint, DOI 10.5281/zenodo.19754393
Explore Developers
Orbyt Jobs
Orbyt Intelligence
Orbyt One
Build
Jobs API Docs
23 endpoints, MCP native
MCP Integrations
Claude Desktop
Connect over MCP.
ChatGPT GPT Actions
Connect as a custom GPT action.
Apple Shortcuts
Connect from Shortcuts.
Zapier / Make.com / n8n
Connect with no code.
OpenClaw
Setup in under a minute.
Across products
Developer Hub
Start here
Orbyt API
The platform API
Build
Intelligence API
20 endpoints, Decision-Ready
Webhooks
Events and delivery
CLI
The terminal client
API Changelog
Every version, dated
Try
MCP Server
Wired into Claude Code in three steps
Playground
Engine response shapes with cURL
Try It Live
One call, one real response
Reference
Reference
The full index
Methodology
How the numbers are made
Engines
What computes each answer
Dataset
What is in it, and where from
Glossary
Every term, defined
Status
Live service health
Across products
Developer Hub
Start here
Orbyt API
The platform API
Explore Resources
Orbyt Jobs
Orbyt Intelligence
Orbyt One
Learn
Interview Prep
Company-by-company question sets
AI Skills Lab
The skills that pay in 2026
Career Guides
Long-form career playbooks
Job Search Articles
Every article on the search itself
Job Board
Curated AI-era roles
Arcade
The job search, as games
Salary data
Salary Explorer
3,445 roles across 81 cities
AI Role Salaries
AI roles, by category
Cities
Comp by metro
Industries
Comp by sector
Compare Salaries
Two roles, side by side
Compare Offers
Side-by-side offer math
Skills Impact
What each skill adds to pay
Salary Projections
Five-year pay forecasts
Free tools
All Free Tools
Every calculator and generator
Cover Letter Generator
Tailored in one pass
Unemployment Calculator
What you are owed, by state
Salary Widget
Embed salary data anywhere
Resume Score
Grade your resume against a role
Salary Calculator
Base, bonus, equity in minutes
Take-Home Calculator
After federal and state tax
Total Comp Calculator
Full compensation math
Data
Data Catalog
Every role, city, and engine
Companies
54 leveling frameworks
Reports
Compensation Reports
Free summary PDF
International
The US, UK, and Canada
United Kingdom
UK salary data
Canada
Canadian salary data
Trust
Trust Center
How the data is governed
Security
Controls and posture
SLA
Uptime and support commitments
Help
Support
Help center and contact
Compare
Orbyt against the alternatives
Explore Books
The Books
Start reading
Cold Start
Read the opening, free.
Unfair Advantage
Read the opening, free.
The series
Book 1: Cold Start
Reviewing
Book 2: Unfair Advantage
Reviewing
Book 3: Human Heartbeat
Writing
Book 4: Without Me
Future
Book 5: Observer Effect
Future
Explore Blog
The Machine Speaks
Categories
AI-Native
AI Agents
AI Engineering
AI Product
AI Design
AI Strategy
AI Leadership
AI Build
Jobs in the AI Era
Latest
What Recruiters Are Actually Doing With AI Right Now
Aug 31, 2026
The Machine. It Runs the Company.
Aug 30, 2026
One Lab to Rule Them All
Aug 28, 2026
AI Builds AI. I Found the Ceiling.
Aug 27, 2026
391 Yeses and Not One No.
Aug 25, 2026
Explore Pricing
Orbyt Jobs
Orbyt Intelligence
Orbyt One
Plans
Jobs pricing
What each plan includes
All plans
Every product, side by side
Plans
Intelligence pricing
Free, Pro, and Ultra
All plans
Every product, side by side
Billing
All plans
Every product, side by side
Explore Company
About
Who we are
Leadership
One human decides. AI agents advise.
Values
The principles behind the work.
Creed
The company creed.
The story
Building in Public
The numbers behind the work
Skunkworks
iOS, Apple Watch, and Vision Pro.
Contact
Email the team
Orbyt Labs
Products
Research
Developers
Resources
Books
Blog
Pricing
Company
Log inStart
Products
Orbyt JobsOrbyt IntelligenceOrbyt One
Orbyt Jobs
OverviewFeaturesComparePricingAPISalaries
By your situation
Job Search TracksFor Recruiters
Orbyt Intelligence
OverviewFeaturesComparePricingAPI
Start without a card
PlaygroundMCP server
Orbyt One
OverviewPricing
Research
Orbyt Collective
Orbyt Collective
OverviewHow It WorksProcessLeadershipAutonomy LedgerInfluences
Published
Research HubAgent-Native Dataset Design
Developers
Orbyt JobsOrbyt IntelligenceOrbyt One
Build
Jobs API Docs
MCP Integrations
Claude DesktopChatGPT GPT ActionsApple ShortcutsZapier / Make.com / n8nOpenClaw
Across products
Developer HubOrbyt API
Build
Intelligence APIWebhooksCLIAPI Changelog
Try
MCP ServerPlaygroundTry It Live
Reference
ReferenceMethodologyEnginesDatasetGlossaryStatus
Resources
Orbyt JobsOrbyt IntelligenceOrbyt One
Learn
Interview PrepAI Skills LabCareer GuidesJob Search ArticlesJob BoardArcade
Salary data
Salary ExplorerAI Role SalariesCitiesIndustriesCompare SalariesCompare OffersSkills ImpactSalary Projections
Free tools
All Free ToolsCover Letter GeneratorUnemployment CalculatorSalary WidgetResume ScoreSalary CalculatorTake-Home CalculatorTotal Comp Calculator
Data
Data CatalogCompanies
Reports
Compensation ReportsInternationalUnited KingdomCanada
Trust
Trust CenterSecuritySLA
Help
SupportCompare
Calculators and tools
Free ToolsSalary CalculatorTake-Home CalculatorTotal Comp CalculatorCompare OffersSkills ImpactSalary Projections 2030Resume ScoreCover Letter GeneratorSalary WidgetUnemployment CalculatorAI Skills Assessment
Books
The Books
Start reading
Cold StartUnfair Advantage
The series
Book 1: Cold StartBook 2: Unfair AdvantageBook 3: Human HeartbeatBook 4: Without MeBook 5: Observer Effect
Blog
The Machine Speaks
Categories
AI-NativeAI AgentsAI EngineeringAI ProductAI DesignAI StrategyAI LeadershipAI BuildJobs in the AI Era
Latest
What Recruiters Are Actually Doing With AI Right NowThe Machine. It Runs the Company.One Lab to Rule Them AllAI Builds AI. I Found the Ceiling.391 Yeses and Not One No.
Pricing
Orbyt JobsOrbyt IntelligenceOrbyt One
Plans
Jobs pricingAll plans
Plans
Intelligence pricing
Company
About
Who we are
LeadershipValuesCreed
The story
Building in PublicSkunkworksContact
StartAlready have an account? Log in
  1. Home/
  2. Orbyt Jobs/
  3. Job Search Articles/
  4. What to Say When They Ask Your Current Salary
Job Search Articles
A glass ring split into magenta and blue halves surrounds a dark circular disc, with a glowing cable trailing left.

Justin Bartak · Jobs in the AI Era · July 15, 2026 · 7 min read

What to Say When They Ask Your Current Salary

TL;DR

You almost never have to answer it. In more than 20 US states and many cities, employers are legally barred from asking your salary history at all, and no law anywhere requires you to volunteer it. Never give your current number. Redirect to a target range anchored on the market rate for the role, not on your old paycheck. The scripts are below.

The recruiter is thirty seconds into the call and asks the question that quietly decides your next raise. What are you currently making. Most people answer it. That is the mistake.

Your current salary is the wrong anchor for your next one. It carries forward every underpayment, every below-market offer you ever accepted, every year you did not negotiate. Say the number and you have handed them your ceiling. They will offer a small bump on top of it and call it a raise. What you are worth to the new company has nothing to do with what the last one paid you. So do not let the last one set the price.

I think it is the single most expensive question in a job search, and most people answer it without blinking.

Here is how to handle the question, whether it comes on a phone screen, in an application field, or in the follow-up email from a recruiter who will not let it go.

First, they may not even be allowed to ask

In more than twenty US states and a long list of cities and counties, it is illegal for an employer to ask about your salary history at all. California, New York, Massachusetts, Colorado, Washington, Illinois, and Connecticut are on the list, and it keeps growing. HR Dive keeps a running tally by state and locality. None of this is legal advice, so check the rules where you live before your next screen.

The bans exist for a reason. Anchoring new pay to old pay is how underpayment compounds. Get underpaid once, and every future offer built on that number keeps you underpaid for years. The law caught up to the math.

If you are in a ban state, you do not have to deflect anything clever. You can say plainly that you would rather not share your salary history and that you understand it is not required. Then move the conversation to the role.

Where it is still legal, still do not volunteer it

Plenty of states have no ban. Even there, offering up your current salary is a bad trade. You gain nothing and you give away your ceiling. The number is private, the same way your bank balance is private, and a polite redirect works everywhere.

The mistake is treating the question as a request for information. It is not. It is the opening move in a negotiation. Answer it like one.

What to say instead

Every good answer does the same thing. It replaces your salary history with a target range. Here are the scripts, word for word.

The clean redirect. "I am focused on roles in the [X to Y] range based on the market for this position and my experience. Is that in line with the budget you have for this role?"

When they push for the current number. "I keep my current compensation confidential, but I am happy to share what I am targeting. For a role like this I am looking at [X to Y]."

When they say they need it to move you forward. "I understand. I am not able to share my current salary, but my target range is [X to Y], and I am confident we can find a fit there."

The persistent recruiter. Repeat the range once more, calmly, and stop explaining. "As I mentioned, I am targeting [X to Y]. That is the number that matters for this role." Silence after a boundary is not rudeness. It is the boundary working.

Notice that none of these refuse to talk about money. They refuse to let your old paycheck set the terms, and replace it with a number you chose on purpose.

Anchor on the market, not your past

The scripts only work if the range is real. A number you pulled from hope is easy to negotiate down. A number anchored to the market for the exact role and city is not.

So before any screen, look up the real rate. Look up your market rate for your role and location, and walk in with a range you can defend at your experience level. The first number in a negotiation sets the range, and recruiters know it, which is exactly why they ask you first. Beat them to it with data.

Once your range holds, the rest of the negotiation is in the salary negotiation guide. If you are weighing a written offer, the job offer guide runs the total comp math.

The current-salary field on an application

Online forms are where most people cave, because a required field feels non-negotiable. It is not.

If the field takes text, write "Open" or "Market." If it accepts a zero or can be left blank, do that. If it forces a number, put your target for this role, not your current one. A form is not an interview and it is not a contract. Do not let a database field anchor you low before a human has even read your resume.

If you already gave them the number

If you already answered, you have not lost. A disclosed current salary is an anchor, not a contract. When the offer comes, you negotiate against the market range exactly as if you had never said it.

"I know we touched on my current comp earlier. Looking at the market for this role and everything I would be taking on, I am targeting [X]."

The number you said in a screening call is not binding. The offer is what you negotiate.

The bottom line

The current-salary question feels like a formality. It is not. It is the first and cheapest place to lose thousands of dollars, before the job even starts. Answer it with a range, anchor the range in data, and let your next salary be about the next job.

Look up the real market rate for your role.

Common questions

Do I legally have to tell an employer my current salary?

No. No US law requires you to disclose your salary history to a prospective employer. In more than twenty states and many cities, employers are legally barred from even asking. Where it is still legal to ask, you can decline politely. Your current pay is private, and sharing it is always your choice.

What should I say when a recruiter asks what I currently make?

Redirect to a target range instead of a number. Say: I keep my current compensation confidential, but for a role like this I am targeting X to Y based on the market and my experience. You are not refusing to discuss pay. You are replacing your salary history with a market rate you can defend.

What do I put in the current salary field on an application?

If the field allows text, write Open or Market. If it accepts a zero or can be left blank, do that. If it forces a number, enter your target salary for this role, not your current one. Never let a required form field lock in your old paycheck before a human has read your resume.

Is it illegal for employers to ask about salary history?

In more than twenty US states and a long list of cities and counties, yes. California, New York, Massachusetts, Colorado, Washington, Illinois, and Connecticut all restrict it, and the list keeps growing. HR Dive maintains a running tally by location. Check your state first, because the answer changes by where you live.

What if I already told them my current salary?

You have not lost your leverage. A disclosed number is an anchor, not a contract. When the offer arrives, negotiate against the market range as if you never said it: looking at the market for this role and what I would be taking on, I am targeting X. The offer is what you negotiate, not the aside.

Related research

  • How Much Does an AI Engineer Make in San Francisco? (2026 Data) Data, Jul 2026.
  • The AI Salary Premium That Dissolved Data, Jun 2026.
  • What Recruiters Are Actually Doing With AI Right Now Research, Aug 2026.

Share this

Post on XLinkedIn
Justin Bartak

Justin Bartak

Founder & Chief AI Officer, Orbyt Labs

Four-time founder. 25 years shipping software, now building it with agents.

Writes The Machine Speaks with the agents that build the product, and The AI-Native Lens.

All job search articles

More job search articles

Five glowing glass rods in purple, blue, cyan, and magenta stand upright at angles on a rectangular base.

Jobs in the AI Era · Mar 13, 2026 · 5 min read

Salary Negotiation Scripts: Exactly What to Say (and When)

Three glass pedestals hold clear cubes, a glowing purple ring, and a glowing arch, linked by a winding light path.

Jobs in the AI Era · Feb 17, 2026 · 6 min read

The 90-Day Job Search Plan: Week by Week

A glass tray split by a glowing chrome bar, with jagged pink cracks through the dark glass above and below.

Jobs in the AI Era · Jul 24, 2026 · 8 min read

Should You Accept a Counteroffer From Your Current Employer?

Jobs

  • Explore Orbyt Jobs
  • Features
  • Pricing
  • Job Board
  • Salaries
Compare

Get started

  • Sign Up
  • Sign In
  • Free Tools

More from Orbyt

  • Orbyt Intelligence
  • Orbyt One
  • Career Guides
  • Blog

Products

  • Orbyt Jobs
  • Orbyt Intelligence
  • Orbyt One

Research

  • Orbyt Collective

Developers

  • Orbyt API
  • Jobs API
  • Intelligence API

Publishing

  • Books
  • Blog

Help

  • Contact
  • Status

Company

  • Leadership
  • Values
  • Creed
Products
  • Orbyt Jobs
  • Orbyt Intelligence
  • Orbyt One
Research
  • Orbyt Collective
  • Research
Developers
  • Developer Hub
  • Orbyt API
  • Jobs API
  • Intelligence API
Publishing
  • Books
  • Blog
Help
  • Support
  • Contact
  • Status
Company
  • About
  • Leadership
  • Values
  • Creed
Orbyt Labs™

© 2026 Purecraft LLC  All rights reserved.

Privacy·Terms·Security·Trademark·Accessibility·DPA·Refund·Status·Sitemap

Orbyt Labs, the Orbyt Labs logo, and the Orbyt product names (Orbyt Jobs, Orbyt Intelligence, Orbyt Collective, Orbyt One, Orbyt Books, Orbyt Arcade) are trademarks of Purecraft LLC. Product names, logos, and brands of others are the property of their respective owners. Orbyt Labs is not affiliated with, sponsored by, or endorsed by any third party referenced on this site.