Hacker News new | ask | show | jobs
by ruh-roh 1566 days ago
Early in my career I just did the standard '2 weeks' thing, but as I progressed I extended to 4 (and in one case I gave 6). In my mind, I thought it was respectful to the company, helped soften the blow on finding a replacement, gave loads of time to recruit/promote and transfer knowledge, etc.

But after reflection, that was a mistake. 4-6 weeks is an eternity in product & engineering time. Too much time to sit around and work-but-not-really-work, and was ultimately disrespectful to my staff, peers, and myself.

My current place has an unwritten rule to not allow notice periods of longer than 2 weeks. When someone resigns, just cut it off and move on. We suffered in knowledge transfer in a few cases, but that's been rare. If it takes longer than that to transition, we probably have other problems.

2 comments

If someone is leaving on good terms, you can always have a contract where you can contact them later for some set contractor rate.
Yep I agree. For me I'm mid-level so it's not like I'm super specialized although my team is smaller than needed because labor market is hot.

Maybeeee if you're like high up two weeks might be too quick and you need an actual transition plan of some kind.

I'd rather take those extra weeks and put them into a real vacation to combat burnout.