Live data from Hacker News

Ask HN: Why not more hiring of junior devs, then on-the-job-training?

news.ycombinator.com

181–190 of 495 posts

Re: Ask HN: Why not more hiring of junior devs, then on-the-job-training?

#181

Earlier quoted context omitted.

The other replies touch on this, but I'm gonna get straight to the point: Does your friend give them actual, meaningful raises as they grow? Is he actually paying competitively to begin with? Because I think if you have this pattern that consistently, it's really likely that either you're underpaying to begin with or your raises suck or are not even present. I love working at small companies. It's by far my preferenc…

That's the weird thing — they (because there are two cofounders) were actually paying very competitive salaries (for the local market). I was impressed to hear what some of them were making. So it's not the money. I think what's going on is that after a year at any job you start to see the problems with the code base, and it starts to get repetitive. It will be like that both in big-co and small-co, but in a differen…

> That's the weird thing — they (because there are two cofounders) were actually paying very competitive salaries (for the local market). I was impressed to hear what some of them were making. So it's not the money.

This is only half of what I asked. What about the raises? As someone in another thread chain pointed out, the expected raise from job leaping is maybe 15%. How did the raises your friend gave compare to that?

I'm not saying they have to meet it, but if you're sitting there doling out 1-2% raises per year people are gonna leave when they get what they need from you.

Also, small companies (frankly, especially 'web' companies) are not even remotely immune to demanding people just "do their job and not ask questions" or forcing their employees to sit in the same box for 3 years doing the same thing. Often the lack of room for career growth in perpetually small companies almost demands this.

Re: Ask HN: Why not more hiring of junior devs, then on-the-job-training?

#182
Too much risk and effort hiring juniors because it’s a gamble most companies can’t afford, then waste time looking again.

Juniors always leave too early for any investment to pay off.

Juniors are severely disadvantaged because lack of experience just as much as it’s lucky for a junior to find good experience.

Re: Ask HN: Why not more hiring of junior devs, then on-the-job-training?

#183
I'm guessing you're looking for a job in a saturated market (west coast, NY). I'll suggest looking elsewhere at companies that are not primarily tech (but have large IT shops). I mean Fortune 500s, not mom-and-pop. And be willing to shift out of front-end, unless you just love UIs. The pay will be lower, but the cost-of-living will also be muuuuch lower. And you may have the opportunity to be a bigger fish in a smaller pond. It worked for me :).

Show those folks that you learn outside of work. Your silly Raspberry Pi project or learning a new JS framework for the fun of it shows that it's something you care about. But don't ever expect on-the-job training or mention it. Show that you'll pick up anything they need you too as the industry changes.

Nothing pisses me off more than peers complaining about not getting training. This is IT, our job is to keep up. If you're not getting it at work, then you need to work on it outside. It sucks, but it's true. Show that you're the teach yourself person, vs the whine about lack of training person. Unless you're pulling genuine 60 hour weeks. Then you're just getting ripped off.

Look at companies where folks put in 10+ years, vs. hot tech companies where 2-3 is the norm. They're more willing to invest in learners vs people who know everything they ask for. Honestly, I wouldn't trust a company that wants you to know everything you need to do the job, because they don't care about you developing. And any hiring manager who expects to hire experts in the position is a fool. You want people to develop, and you don't want them to come in with 1000 preconceptions about how to do X based on prior (possibly irrelevant) experience.

As someone shopping a position at one of those big companies where we have 1000's of developers with 10+ year anniversaries in a fly-over state, it's impossible to find folks with 2-5 years of on-the-job experience that have not only done contract programming.

We just hired a person with almost no relevant experience because they showed the ability to learn fairly unrelated technology in their previous position in a mom-and-pop setting. Everyone else who applied used "the tech lead/business owner rejected my user story" as the answer to every behavioral question and ended with "I accepted their decision." I hate behavioral interviews, but with a big company our hands are tied in the interview process and an answer like that just shows that you just work tasks.

Contract-to-hire is a rip-off that you should avoid unless you're jobless. No one invests education in a contractor because there's no ROI, and you'll never get any experience making decisions in those type of positions.

Also consider the fact that maybe you are not interviewing well. Make sure to show your flexibility, problem solving, self-motivation, and positive attitude, even if you think it's not necessarily work-related. If you don't have those traits, work to develop them. A lot of times interviews are more about these than technical skill. Senior vs. Junior is more about leadership than out-nerding your peers. At least if the interviewers know what they're doing. If they didn't then you're probably better off for not landing the gig,

Re: Ask HN: Why not more hiring of junior devs, then on-the-job-training?

#184

Earlier quoted context omitted.

One could argue that their "raises" were paid in training

If the only raise you give them is in training, then the only way they can turn that 'raise' into something tangible is by leaving. If this is your attitude and you're still shocked they're leaving you've missed something in your calculus.

Sure, but the baseline of comparison here is vs a situation where the job didn't give you raises nor good training.

And yes, the employer in OP's example should reconsider providing value through training vs straight cash.

Re: Ask HN: Why not more hiring of junior devs, then on-the-job-training?

#185
post #164

Earlier quoted context omitted.

Economies aren't that simple.

Ok then, can you explain why wages for programming jobs are low-ish in Europe even when there is, apparently, a shortage?

These are just my thoughts, take them with a grain of salt:

Success makes more success. If you're a billion dollar company, you can afford to pay more for employees. This lets you hire better developers, which lets you be even more successful. If you're in a poor country and you're trying to start a company... you're still poor. The fact that you need developers doesn't suddenly make you rich enough to afford the same wages a billion dollar company can afford to pay.

These lower wages mean that good developers in such regions are often swayed to move elsewhere to get paid better, leaving that original area even worse off than it was to begin with.

JetBrains has managed to build a globally successful company in the Czech Republic, where engineering wages are usually about a third of what the US pays. Call it luck, elbow grease, whatever. They did it. From a quick google search, JetBrains pays wages that are competitive with Silicon Valley. They can only afford to do that because they have been so successful. This success is making them even more successful, since they can afford to pay competitive wages, and it probably doesn't hurt (now that they're successful) that the cost of living in Prague is super low compared to much of Europe. But it's not like anyone starting a company in Prague can suddenly afford to pay $120k+ per developer.

This cycle of brain drain is very hard to counteract. Banks aren't usually excited about freely giving out large sums of money to try out this whole "paying people more" thing and seeing if that yields better results than the other tech startups they tried to fund, but failed due to a lack of talent, random chance, or mismanagement.

If a company becomes successful, but they're only successful locally, then they're tied to the low economic success of their area. They don't have any more money than other employers, so they can't pay wages competitive with other places.

I'm no professional economist or anything, so I'm sure I'm missing some of the nuances of the situation, but a shortage in one thing (developers) doesn't somehow imply an abundance in another thing (funding), it just means that there aren't enough developers available within the funding that these companies have available.

It takes a certain amount of dish soap to clean dishes, but an absence of dishes doesn't mean your home suddenly has an excess of dish soap... you might not have any dishes or dish soap!

If the companies had a bunch of money, they probably wouldn't have too much trouble getting developers to work for them... but without those developers, how can they get the money?

Banks don't write blank checks, especially not to people who have no track record of success. If someone has a track record of success starting companies, they probably don't need the banks to give them a loan nearly as much.

The whole thing is a catch-22. There are solutions, they're just not obvious or every smaller economy in the world would already be employing those solutions. Stuff like this might help: https://tulsaremote.com/ It's hard to know.

Re: Ask HN: Why not more hiring of junior devs, then on-the-job-training?

#186

Earlier quoted context omitted.

This isn't reflected in the wages which are terrible in Europe compared to the US.

Economies aren't that simple.

Actually market economies are exactly that simple.

Re: Ask HN: Why not more hiring of junior devs, then on-the-job-training?

#187

I think the reason is simple: once the junior dev is trained, they will leave. To be clear, I am not saying that they are obliged to stay in the company that trained them or being ungrateful in any sense, I am simply implying this is a common outcome from such training. In software industry, the first job switch in 2 years seems pretty common and reasonable, and the dev by that time would be able to strike a better j…

A friend of mine runs a web dev shop and I have seen him train at least six people from zero-to-pro (very smart, fast learners with a math background) and what you described is exactly what happens. Once they become medium/advanced-level proficient they often quit and move on to other, bigger companies. If there was some formal, or informal understanding that candidates "trained on the job" would stay for a few years…

Some companies in my home country have a clause in the contract which says approximately this: "The company will provide $FOUR_TIMES_MONTHLY_SALARY worth of training to employee. If employee leaves the company within first 2 years he will have to pay $TWO_TIMES_MONTHLY_SALARY back".

Re: Ask HN: Why not more hiring of junior devs, then on-the-job-training?

#188
post #186

Earlier quoted context omitted.

Economies aren't that simple.

Actually market economies are exactly that simple.

If market economies are that simple, why are wages that bad in parts of Europe? Are the business owners just greedy? Is that really what you think?

see this reply: https://news.ycombinator.com/item?id=18508361

If you think they're that simple, why don't you move somewhere dirt cheap, then call up some developers elsewhere and offer them competitive wages to move to that area?

Show us all how it's done! You have that kind of money, right?

In reality, needing developers doesn't suddenly mean you have lots of money with which to pay those developers.

Re: Ask HN: Why not more hiring of junior devs, then on-the-job-training?

#189

There's either a cost or benefit of everyone on the team. Programmers generally push the code at a constant velocity in one trajectory between the two. They'll be somewhere between fixing things and making it better to breaking things and creating new problems that eventually need to be undone and re-solved, pushing the quality down and deadlines back. People tending towards the second group are a waste of time and m…

I think this is the right answer, though I think there's a mentoring element that has to be considered. Plenty of people will break things if left unsupervised but will learn quickly to contribute if they get the right feedback.

That's fine if you have the cash to burn and people to squander. Larger firms probably do (after all some have daily banquets and onsite gyms), but it is just burning cash and squandering time.

If you're on a tight budget like I usually am, I let someone else do that investment. I simply don't have the resources. Early stage startups are the most enjoyable nightmares I've had.

Re: Ask HN: Why not more hiring of junior devs, then on-the-job-training?

#190
post #144

Earlier quoted context omitted.

Me too. I was a know-nothing kid from off the street with a newly minted economics degree. And I learned SQL as a Junior DBA and now I’m a Senior Python developer at a startup in Germany. Tutoring from senior level coworkers and home study is how I got to where I’m at. I try to give back where I can too!

Curious - are you in Germany on a visa?

I have a residency permit aka a Bleue Karte - which is tied to my employer. I have to maintain a job and it has to pay above 50k euros but it’s good for 5 years.
Post reply on HN