Live data from Hacker News

Software engineers hard to find

articles.chicagotribune.com

31–40 of 105 posts

Re: Software engineers hard to find

#31

A related question: What is the current hourly rate that a jr software engineer can expect? I might be starting to work remotely for a company in the Boston area but have no idea what the current salary situation for freelancers in the US is like

All over the map (sorry, bad pun). It depends on where you live, who you work for, what technologies you work in, and (more than any of the above) your skill in marketing yourself to the right clients.

I have personal knowledge of folks who do software development at a range of price points between $25 and $200.

Re: Software engineers hard to find

#32
post #7

Supply and demand. If you're having trouble finding people with what you're offering, raise your offer.

But that raises the false positive rate of unqualified applicants that are only in it for the money. Given that such a programmer may have net negative productivity, underpaying qualified developers migth even be beneficial for the employers, as they can be sure that the remaining pool of applicants will only contain persons with a qualification level commensurate with the offered wages (which can easily be filtered out) and people passionate about programming. They may loose some of the best that way, but they loose all of the duds, too.

Re: Software engineers hard to find

#33
post #21

I'm an older developer. I was eating lunch at a restaurant near my new workplace. Sitting at the table next to mine, a college senior (at Colorado School of Mines - which is a pretty decent engineering school) was talking with her father about her boyfriend interviewing for a job as a software developer. The BF had a 4 hour long programming test as part of the interview. Something is very wrong with our industry. Mos…

This is a problem that has been recurring for a long time in many technical/scientific professions, and there's really no-one "official" telling the truth. When I went to college in the 90s were were told - by even the IMechE, the body meant to represent engineers - that there was a desperate shortage. Truth is if it were desperate, that would be reflected in salaries, and despite the UK's heritage engineering is not…

Some years ago people joked SAP was an acronym for "Sammlung arbeitsloser Physiker" (Some Unemployed Physicists).

Re: Software engineers hard to find

#34

"JumpForward interviews three to five engineers a week as it tries to fill four to six technology jobs, but most candidates don't have current skills or they lack the passion to stay on the cutting edge" In other words, there's no shortage of software engineers, there's a shortage of perfect candidates. If these companies were actually willing to train people, they'd have a lot fewer problems. The trend seems to be t…

Unfortunately, it's also very easy for an engineer to jump ship after their training - meaning a very expensive loss of time and effort. Personally, I think the "shortage" has something to do with increases in job-hopping. If there were some guarantee that an engineer were going to stick around for a few years after training, perhaps training new recruits wouldn't seem so unreasonable.

Re: Software engineers hard to find

#35
So the article says the shortage is of "highly trained" workers only.

And a big problem is you can't lure them away since their current employer might give them a counter offer, and there's apparently no way to deal with that, it's the end of the world.

And the solution to all this is "a six-month retraining program for displaced workers. Participants, who must be unemployed, will come away with skills in one of eight tech-training areas" which trains people with no programming skills how to become "highly skilled" in only six months. So highly skilled that they will kick the butts of the guy with the 15 years useless C, C++, Perl and PHP experience because what we really need is Ruby on Rails.

Re: Software engineers hard to find

#36
If your pay is not high enough, or your standards are not low enough, you will find yourself lacking "software engineers". There is no shortage, however, just an unwillingness to pay the right price (either in money or lack of skill).

Re: Software engineers hard to find

#37
post #11

"One good developer can do the work of three or four guys," Annerino said. "Once a company finds them, they don't let them go." We might get paid double what they do, but not 3x or 4x. Or maybe I'm not that good ;)

I am gradually coming to the opinion that many 10X developers really do end up being compensated fairly, but it rarely happens while they are still in the "developer" box. It doesn't necessarily just happen from taking on extra risk, either, though starting your own company is one way to do it. Personal anecdote (I'm not a 10X developer but I know a few things about a few things): I previously built CRUD apps and mad…

That was one of the things that really surprised me about the real world: that big advancement only comes from big lateral jumps. Different companies, different projects, different markets, or different customers.

There's this model of the world we're taught as schoolkids - at least where I grew up - where you work hard at something, do as your told, and slowly but surely you rise up. And maybe at one level it's true, but it's very slow, and you'll never become the sort of success you read about in the paper that way.

Instead, I've found that what usually happens is that you join an organization because you meet some minimum skill baseline that they're looking for. And then as you practice and learn from the people around you, you end up picking up a bunch of other skills and getting better at your job. But the people around you generally won't notice. First impressions usually pigeonhole you into a general category, and then people are blind to gradual changes.

So to reap the rewards of everything you've learned, you have to expose yourself to new people. Jump ship, and suddenly you seem really valuable to them, because all those skills you've picked up which your current organization takes for granted are new and useful.

There's a leverage effect as well: people try to work with others of roughly the same level. If you're diligent about practicing, you'll go from being (hopefully) near the bottom of your team to the top of it. If you then repeat the process, your new teammates better be higher skilled still, and so your team as a whole can tackle more ambitious problems.

Re: Software engineers hard to find

#38
post #29
post #23

Earlier quoted context omitted.

The problem there will be that the competent engineers - if they have any - will have been burned by too many dud candidates wasting their time, and have gotten HR to pre-screen the CVs...

The job of a good HR department is to at least be able to screen the really dumb ones and pass the rest up the technical chain for evaluation. The good engineers might be burned out but if they know that not spending time interviewing and reviewing resumes will result in having to deal with a dud that gets hired, having to babysit them, teach them the basics of programming and watch them slowly destroy the code base,…

If anyone in HR had the capabilities to tell the difference between a qualified candidate and one who is lying, then that HR person is also qualified to transfer to engineering and start coding.

Re: Software engineers hard to find

#39

"JumpForward interviews three to five engineers a week as it tries to fill four to six technology jobs, but most candidates don't have current skills or they lack the passion to stay on the cutting edge" In other words, there's no shortage of software engineers, there's a shortage of perfect candidates. If these companies were actually willing to train people, they'd have a lot fewer problems. The trend seems to be t…

You generally can't train attitude. Many of those candidates who don't have the skills or passion lack it because there are other things in their life that they value more, like family.

Re: Software engineers hard to find

#40

I'm an older developer. I was eating lunch at a restaurant near my new workplace. Sitting at the table next to mine, a college senior (at Colorado School of Mines - which is a pretty decent engineering school) was talking with her father about her boyfriend interviewing for a job as a software developer. The BF had a 4 hour long programming test as part of the interview. Something is very wrong with our industry. Mos…

I'm not sure what point you're trying to make with the 4-hour test anecdote. But I think most people here would agree a warm body has more potential for harm than a cold seat when it comes to software developers. However you want to ensure you don't get a problem employee, whether it's with 4-hour tests or whatever, it is definitely a good practice regardless of how badly you need to hire someone. Also, I completely…

The point he was making with a 4 hr programming test is that it is a complete waste of time. It doesn't take a 4 hr test to separate the wheat from the chaff unless the interviewer knows nothing at all.
Post reply on HN