frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Open in hackernews

How Not to Answer the Salary Question

https://adatosystems.com/2026/02/16/blog-how-not-to-answer-the-salary-question/
35•mooreds•1h ago

Comments

quibono•41m ago
https://archive.is/Xh8E6

Site was hugged to death

mooreds•20m ago
Should have used a CDN :) .

I went through this a few years ago and wrote about it. https://www.mooreds.com/wordpress/archives/2565

gertlex•35m ago
In limited experience, I've been unclear if this strategy changes when dealing with companies that actually list the salary range (generally when required per some recent state laws).
mooreds•21m ago
Yeah, I think if they have published a range and you are comfortable with it, you can say "I reviewed the range on the website and am comfortable with it".

If you are not comfortable, then I'd be clear why, with data, upfront. "I saw the range on the website and it seems low based on X, Y, and Z. Is that range flexible?"

Whether the answer to that is yes or no, you'll be in a better spot whether to decide to move forward.

alistairSH•15m ago
Most of the time, I'd just answer "I'm ok with your published range, we can proceed." or similar.

But, I've also seen ranges that span hundreds of thousands of dollars. Like "Software engineer: $150k-$250" which is a ridiculous range that makes it almost meaningless. I mean, what are they thinking - any candidate worth their time is going to aim for the $250 end...

joezydeco•32m ago
I tell them the number up front. Because I'm not spending a week in their interview loop to find out they're going to offer me 30% less than my current job. Benefits are never a decider, and equity is a lottery ticket.
gertlex•29m ago
I assume the mention of benefits was mostly a polite way to decline giving a number... It might also be more applicable in other industries/roles where benefits are more varied.
joezydeco•24m ago
In either case, it never amounts to more than a $10K swing in comp. Same for vacation time.

Yes, it's a polite way to brush off the question. But the end result is the same. A job offer way lower than what you're making, and now they have $20K in a bucket to go a little higher when you try to negotiate.

djoldman•30m ago
"What's your desired salary?"

"A million an hour, obviously (haha). But in all seriousness, I'd expect to be compensated commensurate with the responsibilities of the role, keeping in mind that the salary number is just one aspect of a compensation package as health insurance and other benefits are important to me."

There are only two reasons HR asks this:

1. possible leverage later in the process.

2. attempting to not waste time if the candidate's expectations are way out of line with the amount the company is willing to pay.

Either way, there is no good reason to name numbers prior to the company making an offer with compensation package details.

mooreds•24m ago
> Either way, there's no reason to name numbers until AFTER the company makes an offer with included compensation package details.

I agree that a candidate shouldn't name numbers until after an offer.

But I think the company should give a range as early as possible. This is because of point #2 above. As an engineering manager I've had at least one heartbreaking experience where we took a candidate through the hiring cycle and then found out we and they were way out of line re: comp. Hiring sucks enough without that curveball.

That's why, for all the warts, I'm a fan of salary disclosure laws (like those in Colorado, USA). Yes, it's hard to have an accurate range, because jobs and skills are squishy. Yes, candidates anchor towards the top. Yes, it's weird for a buyer of a thing (labor) to state a price.

But companies have more power in the hiring process (there are, after all, many employees working for a company, but usually only one company an employee works for). Companies, or the hiring managers, also have a budget.

If you are a hiring manager, I'd encourage you to have your salary range shared with candidates as early as possible in the process.

iso1631•3m ago
> 2. attempting to not waste time if the candidate's expectations are way out of line with the amount the company is willing to pay.

Good reason for them to say what they're willing to pay before I bother reading their job advert

htx80nerd•29m ago
>"Now I recognize that absolutes – especially in the context of job interviews – are a function of privilege. Someone without the societal leverage that gender, age, ancestry confers;"

I can go ahead and ALT+F4 here, thanks

bpt3•27m ago
Terrible advice if you value your time or sanity, especially if you are experienced or not desperate for a job.

Find out the range up front by reading the job posting, making the recruiter tell you, asking a friend who works there, or asking after applying if you have no other connections.

No company is going to refuse to share the information because they are secretly planning to blow a qualified applicant away with a top of market offer.

nobleach•10m ago
I've used this as a chance to turn things back around on the recruiters. "That's a great question and I noticed you didn't mention a salary range on the posting". Allow for an uncomfortable silence as now they're either forced to give a range, or try to say something like, "it's flexible for the right candidate". The latter is my opportunity to agree, "Of course, let's concentrate on that question then, I'd sure like if we could get to the bottom of this 'right candidate' question".
jaggederest•26m ago
The least helpful possible framing for this, I think. Refusing to answer altogether has all of the risks of giving too high/low a salary, and none of the benefits of actual negotiation.

If you're in a position where you can not answer, you're in a position there's no reason not to give them your desired salary up front and let them tell you why they can't do it. Pick a high number of course!

If you're in a position where you can't afford not to answer, you should pick a reasonable number, and take whatever they give you, because you completely lack agency. This is the case where you might screw yourself out of money, but if you need the job that badly, do you really care?

A better way to frame this, and this is always what I do if I have the agency to not answer, is to give them the number I'd like or remain mum, but either way when they make the final offer just ask them a simple question: "Is there any way you can come up a little bit from that?". If they say no, you decide based on that first number. But they'll almost always say yes, and you'll get a small effortless raise.

I've done this about 10 times across my career and about 70-80% of the time I've gotten a bump in the 5-10% range. Which means that, collectively, about 30-40% of my current salary level is a result of that one question, applied consistently over time.

You won't get a raise outside the salary band, but you might move from the median for that band up a notch or two within it, and that absolutely matters in the long run.

nine_k•12m ago
Imho, there is an easy way to turn this around. Ask: "What is your range for the role?" Then it becomes easy to say: "Fine, I'm comfortable with this range", or maybe "Oh, I'm afraid I can't afford this".

Once you're at the offer stage, you can bargain about specifics.

SOLAR_FIELDS•10m ago
Nearly every time I've held out and not given a number I've gotten a much higher salary than the number I would have given.

It is true, of course, that when they give you the number that they leave money on the table for negotiation, that is standard practice. It's even factored into the offer amount at bigcorps, and chances are they have an amount they cannot go over and it's set. So you should always ask for more after they lay the money out.

aspenmartin•2m ago
Yes perfect advice -- negotiate from a position of leverage and always ask for that little bump at the end.

In my experience, not talking about salary early kind of sets everyone up to waste their time. One time it ended up with a full interview process that went very well for a job I thought would be perfect in an industry that _should_ have outstanding pay, and the resulting offer that was lower than my current role, paid hourly without benefits with a vague promise to later be an FTE; not only did we all waste our time, I was pretty upset about it. When I sent an email to the hiring manager they said "well you never told us your expectations" -- now the guy was dumb, he _knew_ I had a good job already, the comp he was offering was well below industry standard, and he knew my background, but nevertheless that is where a lot of hiring folks heads are at and it makes total sense: they want to get a good deal just like you do.

Asking for salary band is good, especially earlier in your career, but to me it's now kind of irrelevant -- for the same reason you will go high, they will try to go low. I have a price I will be happy at, I say a number higher in the beginning but say depending on how everything goes there may end up being flexibility, and that I look at the entire package holistically. This is just to assess: "is it worth us continuing to engage". Not doing this would have wasted a colossal amount of time.

I'm now in a position where I know where salaries generally are in different parts of the industry, and I can set a price based on what I expect and what my current role is, and I explain my reasoning. But yes: it depends so much on the situation. Benefits good? Growth potential at a startup good? Do I believe in the mission and that the founder won't abandon for an acquihire and tank my equity? Etc.

democracy•23m ago
They write as if there is unlimited budget but it is never is. There is a range and you'd better fit into it. Also if you think you are at the top of a market range already and the hiring company thinks it's too early to discuss - run. Unless you don't have a job or want to switch in any case.
Pooge•11m ago
I've used what I consider the golden guide of salary negotiation for a software engineer that has been linked on HackerNews[1].

I've applied these guidelines in my own negotiations and it worked very well for me. I would've undersold myself by at least 15% if I went ahead and answered the salary question first. I declined politely to give a number first—even saying "it's not in my interest to answer that first, as you most likely understand".

Those guidelines work for all jobs that have high added value, I would say.

[1]: https://www.kalzumeus.com/2012/01/23/salary-negotiation/

d4mi3n•8m ago
This guide has aged surprisingly well, but I’d add to this: the above response is about as good as you can get—it is firm, non-combative, and moves the conversation forward.

Don’t antagonize your recruiter. You want them to advocate _for you_ when a prospective employer is drafting an offer. Work with them to give them the ammo they need to make that happen.

klodolph•7m ago
The sheer amount of information asymmetry is the tricky part here. I think that’s the only relevant part of the equation. The company hires N people per year, you get hired by 1 company every N years. Maybe you work for a company that hired 100 people last year, and there’s someone who’s done analysis for salaries day in and day out. That person has a shitload of information about what the salaries are and what people will accept.

So you exploit the flipside of the information symmetry. The company is obviously not telling me all their employee salaries, so I am not telling them mine. I just need enough of a sense of what the range is to figure out if a number I like is in there.

The company is not planning to blow you away with some big salary number, but I’ve gotten some pretty good offers. This happens sometimes because you’re stepping up to a higher role at the other company, or sometimes because you’re going to a company which just has higher compensation bands to begin with. Or maybe you just look really good to that company. I’ve gotten offers which were +50% above the number I had in my head, or well above that.

It feels like a waste of time and such a song and dance to some people, but the time spent is not wasted, it’s turned into salary dollars.

JaumeGreen•2m ago
You can set some reasonably high expectation, not as a target but as an aspiration.

Case in point, once when I was asked it I was "I read in an study that one gets happier with more salary up until 85K€, so my aim is to go towards that range". In the end I ended up halfway between that and my then salary. BTW, the study was then superseded by another that happiness keeps increasing, just not as fast.

Of course your situation might be different, and you could take inspiration for 6 digits, $500K or any other amount that would be perfect for you if accepted because it's higher than what you would have accepted, and you can get something below that that would be a stepping stone.

In Spain, at least, salary needs discussing early, too many divergences between some companies and some people expectations on that. So I disagree leaving it for later.

AI Rot Management

https://jw.hn/ai-code-hygiene
1•jwpapi•59s ago•0 comments

Big tech stocks lose billions as AI spending fears hit valuations

https://www.reuters.com/business/retail-consumer/global-markets-marketcap-2026-02-16/
3•billybuckwheat•2m ago•0 comments

Robert Duvall, a Chameleon of an Actor Onscreen and Onstage, Dies at 95

https://www.nytimes.com/2026/02/16/movies/robert-duvall-dead.html
1•bookofjoe•2m ago•1 comments

Vulkan Easy => Reactor (Like React-App)

https://github.com/AndreeSalazar/REACTOR-Framework-for-Vulkan-
1•QDanteX•2m ago•0 comments

Anthropic got an 11% user boost from its OpenAI-bashing Super Bowl ad

https://www.cnbc.com/2026/02/13/anthropic-open-ai-super-bowl-ads.html
1•general_reveal•2m ago•0 comments

Anthropic Raised $30B. Where Does It Go?

https://fromtheprism.com/anthropic-30-billion
1•heavymemory•3m ago•0 comments

Show HN: VoteShip – Feature request platform built for AI agents

https://voteship.app/
1•madcash•4m ago•0 comments

Porous material uses green and blue light to repeatedly store and release CO₂

https://phys.org/news/2026-02-porous-material-green-blue.html
1•westurner•4m ago•0 comments

Jon Favreau Confirms Lucasfilm Exit Amid 'The Mandalorian and Grogu' Uncertainty

https://insidethemagic.net/2026/02/jon-favreau-lucasfilm-star-wars-mandalorian-grogu-exit-cj1/
2•iancmceachern•5m ago•1 comments

AI Slopageddon and the OSS Maintainers

https://redmonk.com/kholterhoff/2026/02/03/ai-slopageddon-and-the-oss-maintainers/
1•mooreds•5m ago•0 comments

Peon Training feature piggybacks on AI coding session

https://github.com/PeonPing/peon-ping
1•mthwsjc_•6m ago•0 comments

Governor: Extensible CLI for security-auditing AI-generated applications

https://github.com/ulsc/governor
1•ulsc•7m ago•0 comments

Suicide Linux (2009)

https://qntm.org/suicide
2•icwtyjj•8m ago•0 comments

Unreal Tournament 2004 is now available for free thanks to its fan community

https://www.pcgamer.com/games/fps/unreal-tournament-2004-is-now-available-for-free-thanks-to-its-...
1•donutshop•8m ago•0 comments

The Three Juggling Acts (Strategic, Lazy, and Survival)

https://cutlefish.substack.com/p/tbm-407-the-three-juggling-acts-strategic
1•mooreds•9m ago•0 comments

Discovering Domains via NS Correlation

https://interrupt.sh/blog/discovering-domains-via-ns-correlation/
1•arwt•9m ago•0 comments

App builder market trends and statistics

https://getmocha.com/blog/ai-app-builder-statistics/
3•nichochar•10m ago•0 comments

Glimpse – A Clean Architecture Pattern for Django and Coding Agents

https://medium.com/@radoslaw_jan/a-glimpse-of-cleaner-architecture-for-django-projects-c31295529eb5
1•novagalileo•16m ago•0 comments

Show HN: PicoGPT v2 – GPT in <40 lines of vanilla JS running from a QR code

https://github.com/Kuberwastaken/picogpt
2•kuberwastaken•16m ago•1 comments

Programming in Prison: My Redemption Arc

https://www.ck-7vn.dev/blog/Home
4•CK-7vn•17m ago•1 comments

Show HN: RuneScapeCN (open source) – UI kit with authentic OSRS styling

https://github.com/alns0dev/runescapecn
1•alns0•18m ago•0 comments

Testing Postgres race conditions with synchronization barriers

https://www.lirbank.com/harnessing-postgres-race-conditions
2•lirbank•19m ago•0 comments

Let's Practice (Bsd.rd)

https://openbsdjumpstart.org/bsd.rd/
1•todsacerdoti•19m ago•0 comments

Outcome Engineering: The O16g Manifesto

https://o16g.com/
1•mooreds•19m ago•0 comments

The Internet Is Dead

https://joinkith.com/#the-internet-is-dead
1•elliotbnvl•19m ago•1 comments

Zero Knowledge (About) Encryption: Security Analysis of Cloud Password Managers

https://eprint.iacr.org/2026/058
2•gnabgib•20m ago•0 comments

Ask HN: Companies that advertise being a "best place to work", is it a red flag?

3•jrs235•22m ago•2 comments

Simple non-hype agentic coding workflow for well-established codebases

https://alyosha.net/posts/simple-non-hype-agentic-coding-workflow-that-works-for-well-established...
1•nkzd•23m ago•0 comments

Show HN: SafeClaw – Sleep-by-default AI assistant with runtime tool permissions

https://github.com/rawalrahul/safeclaw
1•rawaldelhi•25m ago•0 comments

"King Me": A Defense of King-Making in Board Game Design [video]

https://www.youtube.com/watch?v=UraJElx1ebg
1•euthymiclabs•26m ago•0 comments