Hacker News new | past | comments | ask | show | jobs | submit login

How do you reconcile this statement:

First of all it sounds like there was some really dishonest communication and there is no excuse for that.

With this one:

People who are unaware of their market value

As an employer it is not my job to assess and pay an employee their market value. I’m not a career counselor. I have positions I need to fill and those have salaries associated with them. Someone who is overqualified might accept a role when I think they could do better, but that’s me projecting a vision onto them. The employee has mobility to reject my offer, or leave and seek a better job.

Also people are complex I don’t necessarily know why the engineer accepted the job for 70% of what I think they could earn elsewhere. It could be an intangible reason.

>As an employer it is not my job to assess and pay an employee their market value

Then how do you do competition market research?

Are you okay with it if it turns out that the offer you make is either 3x or 1/3 The market rate?

>The employee has mobility to reject my offer, or leave and seek a better job.

As long as you never whine about a 'talent shortage' when they reject the offer or leave, that's fine.

You made the offer, they decline or leave because they can get better elsewhere.

You look at that information and decide if you want to raise wages or not. Then put out whatever adverts you wish.

Simple and easy. No need for press,PR,H1B, lobbyists and the like.

If everyone was running like that, these kind of articles wouldn't exist.

An employee’s market value has nothing to do with the job openings I have available. You’re equating the two. When I do salary research I do it based on similar roles that are open. Let me give you a concrete example: A CS Phd applies to be our front desk receptionist. I’m offering them the value of the position they applied for, which has nothing to do with the fact that they could be making $300K+ doing CS research.

I think there's a big difference between floating a number like "2X" to entice someone into an interview, then presenting an offer for "X"... versus just floating "X" in the first place, and maybe someone is too timid or unaware to ask for more.

Honestly, we're not SKU's. Once you get some experience, the main difference between, say, a $100k developer and a $150k developer is that the latter simply decides that's their price and interviews longer until they find it.

I've seen very-underpaid people go through the realization that they've been taken advantage of.

Sometimes it's worked out; the company gives them a big raise, a lump sum in the key of "Sorry!" and the person remains a happy and productive -- and wiser -- member of the team.

Usually they're gone within months, though. And often other people follow ("You got /how/ much at OtherCorp?").

There's nothing dishonest about making someone an offer lower than what you think they could get elsewhere and then accepting it.

There is if the candidate makes their salary a very clear upfront condition of employment and the employer pushes them through a lengthy interview without disclosing zero chance of them being paid that much because the company does not have the money. They are leading a candidate on in bad faith.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact