4 ms·
As far as I can tell the current job market disagrees with you. It seems like there's two markets for software engineers at the moment: The market for fresh bo
by josephg 7y ago
As far as I can tell the current job market disagrees with you.
It seems like there's two markets for software engineers at the moment: The market for fresh bootcamp & collage grads, which is swamped with job seekers. And the market for mid/senior engineers, which is desperate for talent. If you're a senior engineer its very easy to find well paid work at the moment. But thats really not the experience of most fresh grads. I've spoken to plenty of junior software engineers who send out dozens of resumes for each call back for an interview.[1]
If you could be a decent software engineer with a few years of work, companies would happily hire collage grads. But despite being desperate for talent, most companies don't want to hire average junior developers for any price. The top 15% or so of each graduating class finds work easily enough, but most software companies consistently say no to anyone in the bottom 85% or so of each class.
And thats pretty good evidence that most people can't become decent at programming with only 3-4 years of study. Even amongst the top 15% or so of each graduating class I bet most people started programming long before their freshman year. I know I did.
(And to be clear, I'm not saying that companies filter based on marks in collage classes. As an industry we interview people and assess them as fairly as we can. I'm saying most people are demonstrably not very good at programming after "only" spending 3-4 years studying CS in collage.)
[1] Source: As part of my current role I've chatted with, and technically assessed around 100-200 fresh grads in the last year. Our hiring bar is calibrated off the companies we work with, and we say no to the vast majority of fresh grads from bootcamps and universities.
- saagarjha 7y agoI think the ability to be hired is orthogonal to how good of an engineer you are.
- josephg 7y agoIf that were true, the best paying companies would fill up with charlatans with mediocre engineering skill but who interview well. But at places that think a lot about their interview processes, we don't really see that happening. Most of the engineers I've met who work at Google and Facebook are very capable. (That said, I've certainly worked with entire teams of atrocious engineers at consulting companies and banks and places like that, who are paid well in excess of what they're worth.) And yes, there's also plenty of blog posts from people with solid engineering skills who don't interview well. I've interviewed a few people like that, and I've fought tooth and nail for them. But angry homebrew developers on twitter don't tell you much about the hiring process for the average engineer. And in reality most people who can program effectively at work can also program well enough during a job interview. I'm genuinely sorry if you're not one of those people, but until someone comes up with a better assessment process, we use what we've got. I'm all ears if you have ideas for fairer processes.
- thu2111 7y agoThe problem is that training in programming is very expensive, to the extent that it's easy for just one junior or bootcamp grad to end up consuming all the time of a much more capable and expensive senior developer (e.g. because their code is of such low quality it has to be rewritten). The other issue is that teaching is a vocation. Many people don't want to teach. If they wanted to teach they'd have become a lecturer or some other more obvious career path where they can spend all day teaching programming. If you hire people who are too inexperienced you're basically forcing an unexpected career change on some random team member who won't like it. Programming is really hard. I think we tend to underestimate how hard it is. I've seen people who just came out of a CS programme who can't write basic programs in easy languages like Java, or explain what hexadecimal is. I've seen people who can code but just don't do it right, like an intern my company hired who wrote a Slack/GitHub bot in Java (neat) but the entire program consisted on untyped JsonObjects being passed around a handful of giant methods, all of which were static and many of which were duplicated. He knew the syntax of the language but the reasons why you might want type systems, classes or how to create abstractions were missing. Then he left (it was a short internship) and the tool he had created was abandoned because it wasn't that important to begin with. From a pure financial perspective he was a major net loss to the firm. I don't know what the solution to this is. Training is important, but there doesn't seem to be any way to make it financially sustainable. Ultimately, new developers need to finance more of their education themselves with longer programmes than bootcamps offer, and better bang-for-buck than universities offer.