undefined | Better HN

0 pointsnine_k6y ago0 comments

Not hiring junior developers makes sense when you are still unfolding, and have a really small engineering team (< 5-7 people).

As you grow, you will see that not all work is equally important, and you want your more senior guys work on harder problems. And you will also note a number of good, smart developers applying to you who do not yet have the experience of a senior engineer, but could quickly grow.

Then you can start hiring junior engineers, and nurture them.

[Edit: grammar]

0 comments

1 comments · 1 top-level

nicoburns6y ago

I'm currently working for a company whose first 4 technical hires (other than the CTO, who wasn't always involved in day-to-day development) were juniors. This was a terrible idea, as there are basic architectural mistakes baked into the codebase all over the place, and lots of issues with data integrity and things that only work most of the time. They'd have been better off with a single senior.

Agree that it makes sense to hire juniors once you've grown though.

j / k navigate · click thread line to collapse