Can we make this more concrete? What sacrifices do you think is being asked of competent developers? What pay do you think they are offered?
How do you know, objectively? Have you tried paying twice (or more) the current market rate, for instance, and binary search for a point where you have enough happy hires and failed? Perhaps the market rate is artificially lowered.
Edit: Didn't realize you weren't the person I originally replied to. Let's reverse your question. What is the objective basis for the claim that engineers are asked to sacrifice to much for too little pay?
I have one possible answer for this issue: Well, no one in the Valley (to best of my knowledge) really advertises that they are going to pay a meaningful multiple of what's considered the market rate to potential employees. So from the potential employee side, it is reasonable to assume that they are going to get paid around the "market rate".
The Valley seems to be at a point where "starting/not starting a startup" is becoming an IQ test (compared to "market rate") financially if you think you are reasonably good at doing stuff, so it is natural that good engineers wouldn't go and apply for a job, because the expectation for compensation is unlikely to be satisfactory anyway (or at least that's what they believe and prevents them from trying).
>And you dodged my questions.
Oh, I am not the OP and I'm not pretending to have the answers. I was genuinely interested in knowing how you measured that you are paying very well, except for the fact that they were competitive with what's considered the "market rate" which is the questionable piece of data here.
Another interesting wrinkle to this is the fact that hiring someone at a high salary is a big gamble. How confident can you really be after interviewing someone?
I'd love to see one of your job postings. I'd bet at least one of the following is happening:
1) unreasonable academic requirements
2) unreasonably broad list of required previous experience
3) unqualified HR people pre-screening and discarding resumes
You need to be willing to "kiss a lot of frogs", i.e. do phone screens and onsite interviews, of people who might generally be suitable. Then be willing to hire not-quite-perfect candidates who are willing to learn and are willing to work hard.
> How confident can you really be after interviewing someone?
I've seen an increase in contract employment postings. That might be a way to go. Start someone on a six-month contract. You might find some takers. Not everyone is ready to "get married" after a single days worth of job interviews.
I see salary ranges advertised all the time in the New England area so its not impossible.
Like some else mentioned; when I don't see a salary range I assume it isn't great or maybe they don't want to piss off the current employees that are working for below market rate.
Of course, some bootstrapped company, or some company which had minimal angel funding or the like is taking more of a gamble, but everything is a gamble when you have no product/market fit and only 18 months or less worth of cash in the bank.
What do you think is more likely, that no one is doing it because it's highly effective or that no one is doing it because it causes problems?
I've found that most practices that make for visionary, distinctive companies are both highly effective and cause large problems. For example, Google has a massive shared codebase, does promotion & performance reviews via peer feedback, and shares information very widely inside the company at the expense of being a black box externally. Fog Creek makes all salary data public within the company. Palantir, I've heard, pays all engineers the same (relatively low) salary but doubles down on perks and work environment. Apple under Steve Jobs let the CEO berate any employee over the slightest product detail. Facebook releases new software via IRC chatroom.
All of these practices cause major problems, but they also fix major problems. Moreover, they're distinctive. They draw a certain type of employee, one who's willing to give up convenience in some dimension to gain autonomy, or excellence, or collaboration. It's often better to be differentiated than good.
2. glassdoor.com
3. my network of people who work at various companies and will tell me what they make.
I'm assuming that you are a small company that doesn't actually show up in either of 2 or 3.
If your methods don't work - try going to a local programmer meetup. Chat up some of the programmers. Encourage them to apply. I go to programmer meetups as a programmer, and all the time I meet other programmers who are out of work, or who are unhappy at their job and looking to work elsewhere. Most are employed, but there's always a few who are looking.
What is happening is this - in 2008/2009 the economy was tighter, and employers could get by with a CL posting, or talking to a headhunter or two. Now that unemployment rate is less than 10%, you don't have dozens of good programmers checking CL for jobs every day. You have to do a little more work to find people. Just like THEY had to do a little more work when unemployment was double digit.
"we pay well" What is the salary range for this position? If you have already hired into this role, what are you paying them? I'd say a specific number is important here, rather than "market rate" (if you say market rate, It's important to define it with a number).
"we don't expect anyone to work crazy overtime" How many hours, on average, does someone in this role work a week? If you offer vacation, how much time off do you offer? How many paid days off per year? If you don't do those things (many companies don't do vacation time anymore), what are the average number of days take off per week.
"good engineers", "competent developers" How do you define this? This is probably hardest of all, but if you already have someone in this role... what degrees do these workers typically hold? How many years of experience is typical? Could you share specific examples of interview questions, and what kind of response is required for an offer to be made? Could you share an example of a problem solved on the job that represents the kind of work someone like this does?
I haven't seen any evidence here in the Boston area that contract rates have risen since I was a contractor 4 years ago. (I still get calls and invariably the rate is always <= what I got before.) One can surmise that there isn't a shortage in economic terms or that companies are unwilling or unable to pay true market rates. It may be true that there is a shortage of engineers a company can afford but that doesn't mean that there is a shortage of engineers. I.e. just because I can't buy gold at $100oz doesn't mean there is a shortage of gold.