Handling an average-performing employee who wants a promotion
6 December, 2017
A few years ago, I hired somebody who wanted to be hired at a higher level. However, I felt he was not quite ready for that level. He was hired at the lower level with the perception that he could advance but I tried to work with him to ramp him up quite fast. I gave him room for initiative, while also giving him tasks that were linked with the expectations of a leadership position. He was underperforming and constantly finding excuses, such as "Nobody's helping me", yet he was not reaching out to anyone.
A few months went by. By the time he asked about a possible promotion we had formalized our engineer ladder and salary grid. With that document, it was quite easy for me to tell him "This is where you are, this is what you do well, and this is where you could improve". By doing this I could clearly show him that he was paid fairly for his position and could show him how he needed to improve to be promoted. He didn't like the concreteness of the grid but I couldn't promote him at the time so we agreed on coaching to get him there. Unfortunately, it didn't help and he ended up leaving.
The key message here is that when not promoting someone (or not agreeing to a salary raise), having concrete explanations of the reasons behind it helps a lot. When both parties know the expectations and have agreed on them early on, it's much easier to discuss why they will not be promoted. Our grid and ladder was published for everyone and the majority of engineers appreciated the transparency. It actually triggered a lot of advancement, as people knew what was expected of them to advance. I strongly believe you should not inflate somebody's title or salary, because:
- It gives your employees an incentive to work harder.
- As an employee, an inflated position salary or position tends to limit your options for moving forward, as people tend not to want to downgrade.
- As an employee, it reduces your legitimacy if you are not at your proper position.
Good blog post on Enginering Structure: http://dresscode.renttherunway.com/blog/ladder Link to sample ladder: https://docs.google.com/spreadsheets/d/1k4sO6pyCl*YYnf0PAXSBcX776rNcTjSOqDxZ5SDty-4/edit
Jeff Foster, Head of Product Engineering, shares how he managed to break down silos in his organization by encouraging their employees to choose their own team.
Head of Product Engineering at Redgate
Elizabeth Daggert, VP of Engineering at GuideSpark, taps into her experience of overcoming Imposter Syndrome to become an inspiring, impact-making leader.
VP Engineering at GuideSpark
Krzysztof Zmudzinski, Director of Engineering at Egnyte, recalls how he handled -- with much difficulties and frustration -- a perfectionist on his team.
Director of Engineering at Egnyte, Inc.
Julien Plee, CTO at Synthesio, reveals how he built a career ladder guided by three goals: (1) providing engineers with a vision for their future, (2) justifying salary increases, and (3) providing engineers with a clear sense of understanding of what their mission is.
Chief Technical Officer at Synthesio
Stephanie Tan, CISO of Marcus at Goldman Sachs, shares her self-tailored rules on successful networking and explains how they helped her not to be nervous when networking.
CISO of Marcus by Goldman Sachs at Goldman Sachs
You're a great engineer.
Become a great engineering leader.
Plato (platohq.com) is the world's biggest mentorship platform for engineering managers & product managers. We've curated a community of mentors who are the tech industry's best engineering & product leaders from companies like Facebook, Lyft, Slack, Airbnb, Gusto, and more.