Hacker News new | ask | show | jobs
by JamesBarney 4023 days ago
This is how I see the problem.

Here are some assumptions.

1. You're ideal ios dev is working. The unemeployment rate among good ios devs is 0%.

2. He is probably getting paid above market wage.

3. He doesn't have a lot of time to research positions.

4. Most job openings are shitty because shitty job openings take longer to fill than good ones(or never get filled).

5. Your ideal ios dev doesn't have time to look up glass door salaries on every job that comes along on indeed. So they probably won't look up yours.

So how do you differentiate yourself to your would-be dev? Well you could tell them that you have an AMAZING-COOL workplace with GREAT people. Problem is even terrible companies say they have an AMAZING-COOL workplace, sometimes even more vocally then legitimately great workplaces. So whats an employer to do? Put your money where your mouth is. Tell your prospective employees that you offer above average compensation[0]. This signalsthat your workplace takes their devs seriously. It will tell them your employer hires professionals who take software seriously. And a a workplace that respects their devs, and hires great people, that IS an AMAZING-COOL workplace where I and many other devs want to work.

[0] - Use actual numbers because many employers are in denial about what the actual market rate is.

TL;DR - The only honest signal a company can give me in a job ad is compensation and from that signal I extrapolate working conditions, culture, and caliber of workers.

2 comments

Exactly. The clearest signal that a company can send that it is truly a good place to work, is to pay a good salary. A strong commitment there implies strong commitments elsewhere. It's not always the case, of course, but you can trust numbers a lot more than you can trust rhetoric and promises. (Not to mention, it's easier to measure, as well.)
it's interesting that you state in point 2 that the dev is "probably getting paid above market wage" - because normally, if someone is PROBABLY getting paid X then X is not above market rate: x is market rate. (Another way to state 'market rate' is 'is probably getting paid x').

It would be like saying that listing a used iPhone on eBay will probably fetch more than its market price on eBay. It kind of doesn't make any sense at all.

However, it certainly can make sense if you define "market rate" more broadly than the amount that ideal devs are themselves earning. If you define market rate as the rate for all devs, then the ideal dev may be making more. So what this really means is that ideal candidates have a much higher market rate than the general market rate.

If this is the case, then advertising that much-higher market rate will very possibly flood the advertiser with applications from average devs (the broader market).

But if this segmentation isn't what you mean, then it's very hard to interpret your point 2, and I would like you to expand on it.