|
|
|
|
|
by julianh95
1724 days ago
|
|
I enjoyed reading this. _As an engineer_, I have always had trouble with determining how to go about putting in my notice. I know that it’s “just business”, however I still get consumed by how my manager at the time will take it. Reading this gives me a sense of relief and I hope it helps when that time rolls around again. |
|
It's also one of the biggest challenges to me, replacing those people, who are often top performers on my teams. But that's my job. It's what I do for this organisation. "As an engineer" I hope you never consider holding your own career progress back just to make that part of my job easier. If that's a serious problem for me, then that's because I failed at _my_ job. I need to have contingency plans and succession plans and we both need you to not be irreplaceable. When I've got my ducks in a row, my reaction is "Right, time to accelerate $otherDev's seniority, temporarily move those @responsibilies to @colleagues with a handover, and call up HR/recruiting to hire in someone with @skillset. Let's plan some celebratory drinks."
When you're ready, and when a great opportunity presents itself, do not spend a second worrying about how I'll need to deal with you leaving. While you've probably just made a whole bunch more work for me as I scrabble to fill the gap you're leaving, I will genuinely be happy for you and proud of you for getting there.
(And I will try my hardest to communicate that pride and happiness much better than I show my frustration and stress as I do the hard parts of my job.)