Hired two junior devs to save money. They broke production 3 times and cost us $10k in fixes.
Six months ago, we needed to speed up our development. We couldn't afford a senior engineer at $150k/year, so we decided to hire two junior developers at $60k each. We thought it was a smart financial move—two heads are better than one, right?
It was a disaster.
Because neither of them had experience working in a production environment, they made critical mistakes:
One of them pushed directly to the main branch without code review, which took down our servers for 4 hours.
They built features that didn't match our architectural patterns, forcing us to rebuild them from scratch.
They wrote no tests, so every deployment introduced new bugs.
My co-founder and I spent 60% of our time reviewing their code, writing documentation they didn't read, and fixing their mistakes instead of building new features. When I added up their salaries plus the cost of my time fixing their work, we were actually spending more than if we had hired one senior engineer.
We had to let them go last month, and we still have months of technical debt to clean up. I realized I was optimizing for the wrong metric. I looked at salary, not total cost of ownership. A senior engineer who ships clean, tested code alone is worth more than three juniors who need constant supervision.
For founders who have made this hiring mistake: How do you decide when to hire a junior vs. a senior engineer?
Do you always hire senior first, even if it's expensive? Do you pair juniors with seniors? I need to figure out the right hiring ratio before we hire again.
p/runevr
p/producthunt
p/google-cloud-platform
p/any-video-to-text
p/seldon
p/tabstack
p/jot-2-0
p/gatrends
p/rithub
p/okapi-2
p/flamigo
p/dino-kids
p/ski
p/replay-11
p/dex-by-exmergo
p/appxiom
p/verse-engine-by-ctruh
p/codedesign
Replies
Be the first to reply
Have a question or a thought to share? Add a comment above to start the conversation.