The email comes in at 4:47 PM. Five rounds of interviews, a skills assessment, a 90-minute panel with three people who would be your direct reports. You open the offer letter and read the number.
It's $19,000 below what you need.
Now what?
Most career advice at this point splits into two camps: push back, or walk away. What almost nobody tells you is that how you walk away — if that's what you choose — is one of the most underrated moves you can make. Declining a job offer is a communication act. Done badly, it confirms what they suspected. Done well, it can actually raise your standing with the company — sometimes more than accepting would have.
Here's how to do it right.
First: Make Sure the Number Is Actually a Lowball
Before you decline anything, run the actual math. Not gut-feel math. Not what your last job paid. Real market data for this role, this city, this level of experience.
A lot of people refuse offers based on a number that disappoints them, without knowing whether it's genuinely below market or just below their expectations. Those are different problems with very different solutions.
The senior marketing manager who expects $130,000 because that's what she made at her last company — but the market in her new city caps out at $108,000 for that title — has a location problem, not a lowball problem. The software engineer offered $95,000 for a role that benchmarks at $115,000–$130,000 in every comp database has an actual lowball problem. Knowing which situation you're in changes everything.
Before deciding, pull real market data. SalaryAsk benchmarks job offers against current compensation data so you can see exactly where an offer falls — whether it's the bottom quartile of market, mid-range, or actually competitive in disguise. Once you have that number, you're deciding with information instead of instinct.
If the offer is genuinely below market, you have two options: counter before you decline, or decline outright. We'll cover both.
Why Declining Is Sometimes the Better Counter-Offer
Here's the counterintuitive part: in a lot of hiring situations, a polite, grounded decline signals more confidence than a negotiation does.
When you push back on a number, the subtext is: I want this job, but I want it at a different price. When you decline because the offer doesn't meet your market rate, the subtext is: I know what I'm worth, I'm not negotiating down from that, and I take myself seriously. That's a different signal. And the best hiring managers respond to it.
Most people assume that declining kills the relationship. The data from actual hiring managers tells a different story.
Three things happen more often than people expect when you decline a lowball offer professionally:
They come back. A company that couldn't meet your number on Tuesday sometimes calls back a month later because budget was revised, the hiring manager went to bat for a re-leveled role, or a different position opened. The candidates who get those calls are the ones who left cleanly. The ones who accepted and quietly stewed — or declined in a way that felt pointed — don't get called.
They refer you. Recruiters talk to other recruiters. A hiring manager who thinks well of you because you were direct, gracious, and clear will sometimes pass your name to a colleague at a company that can actually pay what you're worth.
You preserve your comp baseline. This one gets underestimated. Accepting at $19,000 below your market rate doesn't just cost you this year. It costs you the raise that's calculated as a percentage of that number, the bonus tied to base, and the anchor point every future employer uses when they ask what you currently make. Sometimes declining is the negotiation — just one you're running against your own future.
For more on why pushing back rarely carries the social cost people expect, read our piece on whether negotiating salary is actually rude. The research is more reassuring than most people's fear would predict.
Try a Counter Before You Decline
A decline is final. A counter keeps both doors open, and it costs you almost nothing to try.
If the offer is within $10,000–$15,000 of your target, send a counter first. Something like:
"Thank you so much for the offer — I'm genuinely excited about the role and the team. The base is lower than I was hoping for; based on my research into the market rate for this position, I'm looking for something closer to $X. Is there flexibility there?"
That's it. One direct sentence. Then stop. (See our full breakdown of exactly what to say when negotiating salary — including what to do with the silence after you name your number.)
You might be surprised. Budget adjustments happen. Managers who like you go back to their director. And sometimes the initial number is genuinely a starting point — not a deliberate test, just the natural result of making an offer just under the ceiling to see what happens.
If they come back with something real, great. If they come back with a token $1,500 adjustment that still leaves you $16,000 below where you need to be — or with nothing at all — then you decline. And you do it with the script below, knowing you already did the asking.
The Script: Exactly What to Say When You Decline
The goal of a good decline is to do four things at once: close this offer, explain your reasoning briefly, leave the door genuinely open, and make them feel good about how you conducted yourself.
Most people only manage the first one. They write something apologetic and vague — "I've decided to go in a different direction" — which raises more questions than it answers and leaves everyone with a slightly flat feeling.
Here's a version that does all four:
Subject: Re: [Job Title] Offer — [Your Name]
Hi [Name],
Thank you for putting this offer together — I genuinely enjoyed learning about the team and remain impressed by [one specific, honest thing: the product roadmap, the team's approach to X, the mission].
After carefully reviewing the package, I'm not able to accept at the current compensation level. Based on my research into the market rate for this role, the salary is below what I'm targeting.
I wanted to give you a clear answer quickly so you can move forward with other candidates without delay.
If the compensation picture changes on your end, I'd genuinely welcome that conversation. Until then, I hope our paths cross again — thank you for your time and for the thoughtful process.
[Your name]
A few notes on why this works:
You don't have to give a counter-number. If you've already tried a counter and it didn't go anywhere, you don't owe them a second bite at the apple. "Below what I'm targeting" is sufficient. No spreadsheet needed.
You explain without over-explaining. One sentence on the reason. Not three paragraphs of justification. Over-explaining reads as insecurity — it suggests you need them to agree that you're right, which undermines the whole signal you're trying to send.
You're fast. The phrase "so you can move forward without delay" is there deliberately. It reframes your decline as a consideration for them. It's true — sitting on an offer you won't accept while they hold other candidates in queue is genuinely inconsiderate — and naming it lands well.
Keep the warmth honest. If you'd actually go back to this company for the right offer, say so and mean it. If you wouldn't, don't. Hollow courtesy is easy to read, and it sours a clean exit.
What Actually Happens After You Decline
Reality: usually nothing dramatic.
The recruiter thanks you for letting them know. The role gets re-posted or offered to the second candidate. Life moves on. There's no blacklist. No industry memo. No grudge filed under your name.
The fear of burning bridges stops thousands of candidates from making the move that's actually right for them. But bridges get burned by different things: rudeness, ghosting, accepting an offer and then backing out two days before your start date, lying about having another offer. A clear, timely, professional "no" doesn't burn anything. It's the kind of communication that most hiring managers — who spend large parts of their lives chasing ambiguous responses from candidates — find genuinely refreshing.
The thing that actually burns the bridge? Accepting an offer you resent. Taking a job at a number that felt like defeat, spending six months making that resentment obvious to your colleagues and your manager, and leaving after a year. That's the burn. The clean decline is the opposite of that.
For a full walkthrough of what to do from the moment an offer lands — including when and how to counter before deciding whether to decline — see our guide on how to negotiate salary after receiving a job offer.
FAQ
Will declining a lowball offer hurt my chances of working at that company later?
Almost never. Companies hire people they respect, and a professional decline is a respectable act. Hiring managers have hired candidates who previously declined their offers — it happens more than most people realize. The key is leaving them with a clear answer, not a vague brush-off. Direct and gracious closes the loop; ambiguous leaves them wondering.
Should I always try to negotiate before declining?
If the offer is in the neighborhood — within $10,000–$15,000 of your target and otherwise a role you actually want — yes, try a counter first. The ask costs you almost nothing and occasionally produces real movement. If the gap is $30,000 and the role was already a stretch in other ways, a clean decline makes more sense than a negotiation that can't solve the actual problem.
How quickly should I decline?
Fast. Don't sit on an offer you're not going to take. Companies are holding other candidates in queue, and the longer you wait, the less goodwill you have when you finally respond. Making your decision and communicating it within 24–48 hours is professional. After a week, it starts to feel inconsiderate regardless of how gracious your message is.
What if I change my mind after I've already declined?
You can reach out and say so. Most companies would rather reopen the conversation than restart a search. Email the recruiter directly, acknowledge that you previously declined, and explain what's changed — briefly, without drama. There's no guarantee they haven't moved on, but a clear, unpretentious message gives you the best shot. What you don't want to do is disappear for three weeks and then resurface asking if the role is still open — that reads as confusion about your own priorities, which is its own kind of bridge-burner.