Live data from Hacker News

Ask HN: How to handle a senior hire turning out to be junior?

news.ycombinator.com

1–10 of 231 posts

Ask HN: How to handle a senior hire turning out to be junior?

#1
We hired a developer at the senior level who is lacking basic skills.

Essentially we had deficiencies in our technical interview that allowed for custom-fit preparation, the candidate excelled at selling themselves and negotiating, and there was a breakdown in internal communication where HR was under the impression we wanted to hire at any cost despite us giving the candidate a mediocre rating.

Now we've found they're struggling to do even basic stuff without help and are far from helping others or even taking ownership of minor areas.

They suffer from imposter syndrome (appropriately for once), which further hampers their productivity, communication, and growth as they're reluctant to ask for help with tasks they know should be easy, and equally reluctant to join the efforts of others who might notice their deficiencies.

The result is net-negative productivity. It would probably take another 6-12 months of intense training to get them somewhat productive, and several years to get them closer to the level we hired them at, assuming we can accelerate their learning.

This would require addressing the elephant in the room that they're not at the level we assumed, so that they will understand why we're changing the work mode, accept that learning should be a high priority, and feel permitted to seek more help when they need it. We probably can't reduce the salary, so more productive devs might also be offended if they become aware of it.

Even if we were to successfully address this elephant in the room, they might at some point realize they can't catch up to the level they were hired at without years of dedicated effort and thus quit or "quit internally", making our investment pointless.

I guess in most companies this would be a no-brainer, but we're a small outfit with a focus on personal development, intrinsic motivation, good climate, and low turnover.

Do you think there is any way to rescue this situation? Or should we make this (perhaps justifiably, after their misleading self-presentation) the first time we let someone go for performance reasons?

Re: Ask HN: How to handle a senior hire turning out to be junior?

#2
Have you had a direct conversation with them? If not, have one with a line manager, an out of the line technical expert, and a member of HR. Explain specifics, and how expectations are not being met. Then be silent and see how they respond. Develop an action plan with dates. Mention consequences later, if the action plan is not being followed. Bad things happen to good companies. You must use a process to get out of it.

Re: Ask HN: How to handle a senior hire turning out to be junior?

#5
Only hearing your side of the story, it sounds like they significantly misrepresented themselves and then negotiated something way more than they're worth. It's the kind of developer that makes the rest of us look bad, IMO. Why not let them go? This one's on them.

Re: Ask HN: How to handle a senior hire turning out to be junior?

#7
The same happened with me a while ago, I hired a dev with 8 YoE because he had the best resume and was good on a video call.

Turns out he wrote some of the worst code I've seen, and worse, was unreceptive to feedback.

Ended up firing him by the 3rd day.

Re: Ask HN: How to handle a senior hire turning out to be junior?

#9
As you consider the decision to let them go, consider the impact on other people in your work place too. Other developers notice someone like that underperforming and getting overpaid, and it can hurt the good climate you aim for. It may feel bad to fire them, but it may be worse to keep them.

Re: Ask HN: How to handle a senior hire turning out to be junior?

#10
I’ve been in this situation when I was a junior engineer and found it really frustrating. I’d literally done more work in a week than the “senior” had done in their time at the company. They had shipped one change (a migration) and then nothing for 8 months.

Why should I stay at your company as a junior engineer if the people I’m teaching things to are senior to me?

It devalues seniority and the general appearance of meritocracy in your organization to keep this person at senior. If you really want to be nice, give them the title and compensation that is appropriate for them. If you can’t do that, the right thing to do is to politely say it’s not a great fit for the role and let them go.

Post reply on HN