I have thankfully worked in mostly rational companies and been able to be honest with managers about what is or isn't working. At my last job though I spent more than a year saying repeatedly that I wasn't happy with my project work and that I wanted more pay. Annual review rolls around and they didn't fix it. I had a new job offer in a month and when I put in my notice my manager was shocked. He's a good guy but he was also my boss which means he's only going to pay me enough to stay. Just accept that fact and move on.
Match your notice period to the handover period - I'm sorry but everything about this section is wrong. Nothing you are working on is so important that you can't put it in a good state for someone else to pick up in your absence in two weeks. You stayed for 10 months? I can't tell if you or your employer was the one being strung along.
"Your new role, if you have one arranged, should respect your decision to be professional about your handover period. They’ll wait, don’t worry."
No - The hiring market for developers is red hot right now, no doubt about it, but potential employers are not going to sit around with a position open for months. Potential employers are not going to be impressed at your loyalty to a previous employer. They will think you are wasting their time and will probably be working to put someone else in that position while you dawdle.
The two weeks notice period is the conventional standard and everyone knows what it means. Stick to that and you'll be fine.
And they will keep information asymmetrical in their favor. No. Matter. What. In the long run they will be dishonest with you, they will lie to your face, and they will keep you in the dark. You won't know plans until they want you to know plans. They have to. It's the only way it works.
You, as the employee, need to play the same game in the same way. Defensively. Know that you can keep information from them. Know you should only give information that is beneficial to you. Never self- sabotage. Never be weak. Business is a ruthless competitive game, and that includes employee to manager. You have no obligation to be honest in an exit interview. If it sucked horribly, leave with a smile and say it was great. Make it so they'll give you a great recommendation for your next gig. Lie to them like they lie to you. Bluff. Play chess, play poker.
You don't have to care one whit about leaving your teammates with more work. Does the company give one shit about laying you off a week before Christmas with zero notice? No. They don't give a care at all about the disarray this causes for your life. Ultimately you are a cog, and disposable. You are not "the most valuable resource". You must be as ruthless with them as they are with you. It's the only way it works.
Sure, this sounds super cyncial, you can absolutely do this and not be a dick. You don't have to be a dick at all, just think strategically, and know that you are the only one looking out for you, and you don't owe anyone anything.
But it is true.
In a big company, the VP of whatever department may feel bad about a layoff before Christmas, but they don't know you personally, and whatever numbers or major investors are motivating this don't lie.
In a small company, the same is true. They might wait until things are hopeless instead of trending to hopeless, but either way, they'll lay you off when it makes sense for them.
You might like your boss, but informing them well in advance of a departure is generally not a good move. Nice as they may be, they can't unknow that knowledge, and it will affect all their decisions going forward. And you, who are so sure you are leaving, may find that your outside offer is rescinded the week before Christmas (see above).
2 weeks is a reasonable courtesy and an acceptable risk. If your company needs you beyond that, contract billing should start at 5x your salaried rate, 20 hour minimum.
I am a manager in a large tech company and we care about our employees. We will not fire/lay them off/relieve them of their duty for any reason or not reason. We treat them as we expect to be treated. We will support them if they have some unusual circumstances. We do this because it is the right thing to do, and because it makes business sense. These are not mutually exclusive.
Is that the same as saying there's no situation where people will be laid off or let go? No. But it would happen for a good reason.
In a previous large company a decision was made collectively to take a wage cut and not lay people off. Employees got stock options to make up for the cut. In the end that all worked out.
Being ruthless to your employees doesn't make business sense. Who wants to work at a place like that? Does everyone do that? Absolutely not.
It's true a company isn't a person, but a company is made of people, and decisions are made by people, and you want to work somewhere that has good people that give a damn. At least I do.
All that said ;) if you are leaving, I agree there's no reason to stretch it out. That doesn't help anyone. In any properly managed project any employee leaving isn't the end of the world. There should always be more than one person that know what's going on. Having someone sit around, like a Schrodinger's Cat, that is both there and not there, doesn't really help anyone. It just feels weird. The rules of the game are set (in your contract), you need to give a notice, you give this notice, you're done. We'll take you out for lunch. No hard feelings. People move on for all sorts of reasons.
Also, you have no obligation to give former employers free insights and advice that they'd otherwise have to pay consultants thousands of dollars to figure out for them. That's what your feedback in an exit interview can be: free insights they'd otherwise have to pay for. There's no reason to give it to them for free.
Like that quote from Peaky Blinders “Big fucks small. Always, actually.”
It’s a business arrangement, not a family or a friendship. Hold them to the contract. If they ask for more, tell them you’ll need compensation for it.
If they ask you to stick around, have an excuse ready. Don’t lie, because you don’t need to. “I can’t stay another 2 weeks I have a preexisting obligation.” “No, i can’t say what is it’s personal.”
I’ve been through 6 reorgs and been laid off several times. You take it personally at first, but then gain some clarity. The “family” stuff, the promises are all worth nothing. But once you know that it’s ok. You go in with eyes wide open.
However, I can't help but feel you're painting with an overly broad brush. There absolutely are CEO's out there who would lie awake at night after laying people off a week before Christmas. Does that mean they wouldn't do it? No. They, like all of us, will ultimately make the decisions they need to make to succeed.
It may be comforting for you to imagine that everyone in a position of power over you is some evil super-villain devoid of empathy or emotion, but that isn't always the case. Things aren't that black and white.
Again I agree with your general sentiment. Be greedy and ruthless in your career. Don't make decisions that benefit your employer to your own detriment. Look out for yourself. 100%. I'm just not a fan of absolute statements like yours and wanted to add that businesses are ran by people too, and while some may be complete sociopaths, not all of them are.
If companies were actually struggling they would fund education and find people to hire. Overwhelmingly tech refuses to fund education and is heavily competed over for job positions and internships. Just like every company says they make the best products, they say they're always hiring.
What you did at your last job sounds exactly right to me – you were giving good feedback about what you needed, and when it wasn't heeded you left. Your manager didn't (or wasn't able to) hold up their side of that conversation and you moved to the "you should have left anyway" box. Doesn't sound fun, but we're in agreement on the steps there.
The 10 months thing seems to have tripped a few people up… I might try to rephrase that? Note that the section is titled "Avoid giving too much notice" and lists the reasons that 10 months was way too long. The advice is to match the notice period to the handover period, along with giving your manager ongoing feedback (as you did) if you're heading in this direction. Interestingly, one other commenter did a 12 (!) month notice period and it seemed to work in that situation.
Maybe that is where we've crossed wires on your last point too? I'm specifically not advocating for super-long notice periods, but as a hiring manager I would always respect a candidate who wanted to do e.g. 6 weeks instead of 2 if there was a good reason. For more senior roles, two weeks is not standard, nor is it internationally.
Because the previous employer will also have to wait for a new hire, he will not want to let you out much sooner. It works the other way round as well. The employer can't fire you with a shorter notice period, unless there was some criminal behavior.
it's also got a very silly title. the way a boss quits is they sell the company.
How often do you fellow HNers disagree with management? Is it that common? I think it's probably the worst part of "working for a living".
Every time I hear people worried about disagreeing with management, it's because management are assholes. The managers I work with are good people. They're not perfect, but I do (mostly) trust their competency.
I'm also senior enough people can't push me around.
"How Your Boss Would Like You to Quit"
I've always found the sociology of work fascinating, and how it can vary so much from industry to industry. When I read statements like:
> Your team trusted you and depended on you. It’s unethical to screw them over because they’re not paying you any more.
I wonder what their world view is, and why they think you're screwing them over and not the manager/company screwing them over. I see this often in society where there is a large imbalance of power: The weak turn on the weak rather than turn on those in power.
> Again, it’s unethical!
Leaving the team at short notice is unethical? You may want to look into how such a notion came into place, and who it benefits more.
Similarly, I often call out people at work who start throwing the words "professionalism" or "unprofessional" around. What do they think it means and why do they think that? It is fascinating.
There is some good stuff in the article. While I do believe one should treat the management and company well if they treat you well, I also tell people that they should never forget that if they can drop you at no notice, you don't owe them any more than that. Staying 2 weeks or longer is a courtesy, and not a sign of professionalism.
Just today got an email from a coworker who moved to another company some years ago. Her manager who she got along with very well recently jumped ship to another company, and her life is miserable under the new manager. Even if you have a great manager, always remember that they can (and probably will) leave. Plan your career accordingly.
This is especially true for hard conversations (like firing someone, or leaving a company, etc etc). Note that understanding and getting into their shoes does not mean bending over backwards to do it their way; you can still do things your way (or find a compromise between the two), but you have to convey that you understand their perspective and (ideally) how what you are doing can be beneficial / neutral for them from that perspective.
Another good source is Coyote Talk vs Giraffe talk (it sounds silly, but I promise it isn't). That one is more focused on personal relationships, but I think much of it can be applied to work interactions too.
Most fighting and animosity in the world is caused by people talking past each other, not engaging in actual constructive dialogue.
In the case of quitting your job, I'm not sure it applies since what you really want to do is to leave. If you have a good relationship with your team and company, by all means be generous with your time. Otherwise, I don't think you'll get much value out of being overly considerate of your old company.
> Put yourself in their shoes, and think about what they care about, what they value, and then whatever you want to do, express it to them with reference to their perspective.
Agreed, but applies equally to managers as it does to employees.
> Most fighting and animosity in the world is caused by people talking past each other, not engaging in actual constructive dialogue.
The challenge in doing this is that there is often a great deal of information asymmetry between employees and management. It's quite common for managers not to be completely transparent (and at times, they're not allowed to when it comes to things like compensation). This automatically (and in my opinion, fairly) results in employees withholding information (personal motives, etc) as well. When there is either a power or information asymmetry, you'll find that usually the one who has the more power/information has to put in more effort to win the trust of the other.
Touché, yes there's some truth to this. Many of the points in the post were reflections on people leaving my team as I have an order of magnitude more examples of that than me leaving a team. If you're implying there's some kind of zero-sum thing going on here though, I disagree: it can be good for both you and your boss.
> I wonder what their world view is…
I don't quite follow this paragraph, could you rephrase?
> Leaving the team at short notice is unethical?
Ah, no – this is in the "Don’t sabotage, it’s a dick move" section: it's sabotage which is unethical.
I guess the source of the confusion is that you didn't specify what the sabotage actually is. I mean, deleting all your code before leaving is sabotage. Leaving without notice isn't. What did you have in mind when you wrote that?
> I don't quite follow this paragraph, could you rephrase?
I was highlighting a bunch of beliefs some people have:
- The notion that you should have loyalty to the team beyond your last paycheck.
- The notion that it is you being disloyal to the team, as opposed to management being disloyal to the team.
- The general framing that by lumping people into a team, that there is a single shared goal. A lot of people come to work to get paid, and they do it by providing value. Two people in the same team are allowed to have very different goals. One may care much more deeply about the mission than the other, etc.
- That much of the article places the burden on the employee leaving compared to on the management.
Thinking the employee is sabotaging by leaving the company is a sign you don't understand what the role of an employee is. You are not 5 friends hacking together a game and if someone quits because they get a girlfriend you call them a dick. You are a resource that has been purchased and assigned to work on a specific task. The company hopes to leverage something you do into a profit or as support for a business unit.
But as a rule I wouldn't tell my boss I'm actively interviewing until I have an offer in hand. Just like, and for a lot of the same reasons, the company as a rule isn't going to inform under-performing employees that they're actively looking to hire someone to replace them before firing them.
It can sure seem that way -- and no doubt is that way, in certain situations.
More often I find they're simply ... scared. Of how they'll be evaluated, or what will happen if they make a mistake (or heavens, let someone below them make a mistake). Or of simply being "found out" (that they're not nearly as experienced or as sage in their advice as others have made them out to be).
These managers definitely do exist - I have had them, I have seen them, and I have tried to be one.
Perhaps I should have included "rational conversation is possible" as a decision point in the flowchart, with a negative answer leading to "you should leave anyway"!
I could work for a boss that I couldn't trust with that data, but I much prefer working for one that I can and I try to be the one that my directs can trust with it.
Leaving gracefully has never backfired on me. Actually, the opposite happened. Leaving gracefully has left me with some good friends and has led me to opportunities from people I worked with in the past and have became successful in the meantime.
Additionally, at almost every company I happen to work with somebody that I have known before. Answer yourself, do you really want your ungraceful exit to become a problem at your new company now or in the future? What does it cost you to leave gracefully?
Would a company share they are posting a job to replace you and then ask you to train that person before they actually do?
Graceful is 2/3 weeks notice of handing off projects.
The part about giving ten months notice is terrible. He even says that it was bad for both sides! He was mentally checked out for months and not coming up with long term solutions because he knew he was out of there. Not my supposition - he literally says that.
My past three jobs have all lasted at least a decade. I just don’t agree with much if any of the advice here other than the blatantly obvious things like “don’t sabotage them” lol.
The section you're referring to is titled "Avoid giving too much notice " and basically gives five reasons for why 10 months was a harmfully-long notice period.
The advice is to give much less notice than that.
> Quitting should never be a surprise for your boss
> What’s the worst that can happen?
Not a total surprise, but in many environments even hinting that you're looking to leave will... greatly increase the urgency of your search. They might not terminate you outright (or they may), but it's gonna make the rest of your time there a lot less fun. The worst that can happen is that you admit you're thinking about leaving and get escorted out by security. Obviously it depends exactly what we mean by not being a surprise; problems should generally be communicated... perhaps it would be better to say "Your boss should be able to say why you left"?
> Match your notice period to the handover period
I personally think the handover part is a symptom; at least for the kind of work I do, if there was truly that much to hand over something already failed. Process goes in wiki, tasks go in Jira, code goes in version control... sure, there will always be a few things that only you really understood and some in-flight work that's not fully written down in a ticket, but IMO if it takes you even 2 full weeks to exit gracefully then either you messed up or the company messed up (ex. there was no other person to hand off to and they couldn't hire that fast).
Just to provide a single anecdote of this, my friend worked as a recruiter at a well known company. If higher ups got proof that you had applied to another job, you would be terminated day of and whisked out of the office by security.
The stories from him and his coworkers of the subterfuge involved in job applications were impressive.
I just tightened up the intro explaining whom this post is meant for, and assumed that high-demand industries would be pretty immune to this kind of insanity
Much later, after the startup failed I learned that those months of knowing that I'd likely be leaving and there was little they could do about it was a very terrible time for the higher up dev vp/cto/whatever. My team lead was all fine with it. So the lesson I learned is that it's not the thought that counts.
[It was ironic/unfortunate when I came back for a short term contract and got hired-away before completion on accident by a thinly-veiled coding contest.]
Not just say why, but this has been an ongoing discussion between you with attempts to resolve it (assuming everything is working as it should).
In my experience at such companies, people certainly aren't walked if they express dissatisfaction in their role – but you're right that this doesn't necessarily transfer onto roles which are less competitive. I will think about how to tighten that piece up: thanks for the feedback.
On the second point, I can only congratulate you if you manage to keep everything so organised and compartmentalised! It's something I've aspired to but always fallen short of.
If your boss/company values it, you'll do it. If they don't, I don't feel obligated to wrap this up before I leave. Typically, they tend to reward folks who prefer not to write good documentation and rather code features. It shouldn't be up to these folks to fix the problem their manager/company culture has by suddenly writing docs when they have to leave.
I think training someone on work you've done in the last few weeks makes sense. But beyond that - no. If my manager wants me to work solo on a project for months and doesn't want me to train someone until I announce I'm leaving, then it's the manager's headache - not mine.
Been there 2 years and haven't gotten a raise/promotion? 2 weeks.
Been there 10 years and are bored/didn't get what you want? 2 weeks.
Don't fall over yourself helping the company. Chances are they are going to forget you in 3 months anyway.
That doesn't justify being a jerk and quitting without making an effort to ensure that the transition is smooth for your colleagues.
I hate generalities.
Last time I left a firm, there was 12 months notice (and the decision was mutual). That was the right choice for both sides.
The organization I'm working at right now, it's not uncommon to give years of notice, mostly heading for retirement.
Most tech companies are definitely two weeks, but that's far from the universe.
Unless there’s a contract or an extreme circumstance that demands otherwise, 2 weeks is a courtesy and an employer should be ready for 0 days notice.
However, this is the worst advice I have ever read. Good experiences should not be translated into advice. Your employer is not your friend. You may be lucky enough to have friends who share the same employer, but at the end of the day you are employed by a business, treat it accordingly.
Here's how I handle quitting in a remote world (as a cold hearted jerk/machine, aka a business). I give my two weeks notice, and start my new job the same day I give notice. I effectively have no real work to do the last two weeks at my current job, and have a nice relaxed onboarding at my new job. At the end of the two weeks I collect two paychecks. Rinse and repeat every 1-2 years to collect a 30-40% raise.
This is bad advice. Most contracts in US explicitly prohibit this, so you could land in legal troubles if either company ever found out.
I've never had a contract that explicitly stated I couldn't work multiple jobs. (I work multiple full time jobs now)
Where else would advice come from?
If you work for nice people and things just don't align, yeah, sure, this approach may be fine, but it's by no means universal.
The most risk-averse strategy should still use some of the advice posted here, but concerns like minimizing other people's problems and your own guilt are not worth the dangers.
That's correct – although I definitely take on board some of the other commenters' feedback about things like visas tied to roles. I'm going to add some clarification to make it clear this really relates to employees in good standing in tech companies (obviously a tiny minority of the populace and one of the few groups who have the guarantee you mention).
Any personal effects that I'm not using regularly have already snuck home with me during the previous week or two. Documentation I've been meaning to write has at least been attempted to be cleaned up.
And while that may be better in the long term, it's not so good if you want to keep earning while you find your next move.
FWIW I gave 5 weeks notice at a job a decade ago and immediately regretted it - the last few weeks were beyond awkward as I'd already wrapped up all my projects, spoken to all my colleagues and clients, etc. I was waiting for the job to end but kept getting roped into last minute projects that I could not in good faith contribute to because I was, admittedly, just sitting around waiting for it to be over. Everyone lost.
2 weeks max is optimal and expected for everyone. If you're feeling pressured to give more time to the company after resigning, say no and stick firm to 2 weeks. If they've got actionable work and you're able (i.e. not exclusively employed immediately thereafter), give them the option to hire you as a contractor. If the work is actually valuable, they should have no problem cutting you a check to complete it as a consultant. If not, well they're lying to you and stringing you along to extract any value they can - and you should leave in two weeks if not sooner.
I gave that much of a heads-up of my leaving (not a formal resignation, as it happens) for a few reasons including:
1. It's a C-level replacement, which takes _months_
2. I cared deeply (and still do) about my team and the company mission, and wanted them to succeed: "the more notice the better" seemed right to me (it wasn't)
3. My career plans were to move into a new field which would require various courses, lots of reading, conferences, etc. – although I knew I was leaving, I hadn't even started speaking to potential next employers or investors when I told my CEO I was leaving
Putting all of that together is how I ended up with the 10 month blunder, but the post is less against 10 month notice periods, and more for matching the notice period to your handover, whatever that would be.
I feel your pain on working out those 5 weeks you mention! Awkward for everyone involved.
The game in California is "at will employment". I don't know about other industries, but most tech firms will lay you off with 0 days of notice if they no longer need your services, for example, to save money.
On the other hand, loyalty to people may or may not be worthwhile - this very much depends on the people and your experience may be drastically different from everyone else'.
I had a non-standard 1 month notice period in my contract(normal is 2 weeks). I let them know I'm leaving in two weeks. They mentioned the notice period but I held my ground. They folded and 2 weeks was plenty to handover my work.
I get the spirit of this. But someone whos in tech on a visa, this is absolutely the worse advice. The fear or retaliation is real, especially in bigger firms where your manager has a lot of say. The moment higher ups have the slightest inkling that you're looking for other jobs, you'll soon get pushed out.
> I let my boss know I was leaving in February, so my commitment to see things through to the end of the year was effectively a 10-month notice period.
This, ironically, was the first sentence in a section entitled "Avoid giving too much notice"
If you can't handoff your work in less than 2 weeks, either you as an employee have failed to properly document and communicate status of what you are doing, or the company culture has failed because it created an environment where someone could not pick up what you were doing and continue it. Why? Replace "quitting" with "suddenly died." Companies that can't recover from stuff like this are poorly run and with bad frontline managers.
Short of being a founder and CEO of a startup who has to leave, and needs to gently hand it over so the company doesn't die, there is no valid reason for 10 months of notice. Hell, that is probably not a good reason.
It sounds like it may be more of a north american phenomenon to walk out of jobs at your own discretion(?). In my experience, people in the UK are observant of contractual notice periods and 3 months is not unusual for someone in a senior position.
It's become a bit of a nonsensical arms race to tie people down to longer and longer notice periods to make it easier to bring someone in who hopefully has a shorter notice period for a convenient handover.
Luckily for them I am a contractor not an employee but there are definitely grey areas.
I can't remember which company it was, but some startup CEO posted on Hacker News a few months ago that they have a proper procedure for "long notices" where they help employees, even if they decide to stay at the end of it. That should be the goal in my opinion.
P.S.: Yes, it can be more tricky in large corporations where the manager isn't independent and their manager is vindictive.
As many commenters have pointed out: When there are no professional relationships you want to preserve for the years (decades!) to come the matter is easily handled with a two week notice and a swift departure before the morning light.
However, when you have been fortunate enough to have worked with great colleagues it is a lot harder to exit the building without damaging your relationship with them.
I've worked with great people a lot. When I make a move they understand that it's best for me. I understand it's best for them. One of the reasons they're great is that they document their work and share knowledge, so if someone leaves the rest of the team can pick up where they left off.
Yes, the company then has the hassle of hiring, but companies need to factor that in and get to it.
It seems almost childish that anyone would take such a move personally.
A few other commenters have pointed out good reasons (e.g. visas) where you need to keep your cards closer to your chest, but the vast majority of people reading Hacker News can find a role where it's not so transactional. Where you're valued as a person and teammate, and where you can have a grown-up conversation about your career plans.
Those open conversations are harder to have if you truly believe your second sentence, however!
In exchange, I usually get shafted by the employer. In one case they tried to claw back a signing bonus (despite the employment agreement etc not giving them the right to do it - nice) and in another case the abusive studio head walked over and told me to take my shit and leave immediately despite the fact that I was a producer in charge of an entire team and hadn't done any handoff (shocking no one, the latter studio ended up shipping their product 4+ years behind schedule)
So I guess my takeaway is that it's still valuable to be nice if you care about the impact on your teammates, but I don't think your boss deserves it. Especially now when many companies have a policy of not providing references beyond 'yes i can confirm that so-and-so worked here' - the concept of 'burning your bridges' by not being sufficiently deferential to your awful boss doesn't exist.
Perhaps I should add that this advice best (only?) applies if you're leaving a company in a sort of "natural parting of ways" kind of situation? Thanks for the feedback.
Regardless of the cause, an employer almost-always will require a separation agreement be signed as a requisite action for any amount of severance pay. This is entirely to the benefit of the employer.
I just left a role. I wasn't really unhappy, I just hit a tenure that was long enough that it was time to go. 4-5 years if you're senior++ level is about right. I read the employee handbook, which asked for 2 weeks, and that's what I gave. I worked hard to transition and document everything I could. Never said anything bad about the company (I really didn't have anything to say), and I complemented and thanked my bosses.
Keep it classy, respectful, and professional - that's how a true boss quits.
This hasn't been my approach, nor has it been for many people I've worked with – or perhaps we're tripping over language?
Let's say that someone is super motivated by a high salary. They would be helping their manager (and, in most situations, themselves) if they were open about that. Up to and including conversations like "I hear that Company X is paying 20% more for a comparable role – here's some data to show I'm underpaid".
It's those kinds of conversations which would mean that your manager won't be surprised if in 6 months you leave for a better-paying role. Or, perhaps you get a nice pay rise. Or, if you can't have such conversations, see the red "you should leave anyway" box in the post!
In the work life, one needs to be strategic; it appears to me that most people on here who are commenting somewhat negatively about people giving 2-week notice and nothing else have never been laid off or fired or somewhat "mistreated" by a company.
The way to be an excellent employee is to always deliver work to the best of one's capabilities and give 2-week notice before leaving. In one company I worked for, somebody gave a 2-week notice and was let go immediately. It is not unheard of, and most legacy companies could not care less about a possible PR problem. Those legacy companies live in a galaxy that is far away from the one inhabited by start-ups and similar good PR-dependent companies, they are populated mostly by old dinosaurs that recruit heavily among the not-too-brilliant technical people.
Your quitting should not be a surprise to your manager.
Just like year-end review (for those companies that have it) should not be a surprise to the employee - feedback should be continuous. Similarly, if your (rational, to another posters point) manager's reaction is one of complete shock and surprise, it may be a sign you two weren't communicating sufficiently and planned/discussed your goals/expectations/challenges/direction/etc.
For any employee, including managers, directors and up—there is only one thing to remember: when the company intends to let you go, they don't ask for your opinion. Two-week notice is professional and more than enough.
American culture is so bizarre.
Here in the UK notice (in both directions) is usually contractually 1 month after 6 months, sometimes up to 3 months. If they really want to get rid of you they can pay you to job seek full-time for a few months, which is great. In practice, you get several months of relaxed handover.
After 2 years you get statutory protection and can't be fired, only made redundant, which comes with 1 week notice per year worked.
As nice as your manager is, even if they have your best interests in mind, they ultimately answer to someone else. And that means that even if they don't want to, they can f*k you over with minimal notice anyways. There's a power imbalance there.
Certainly don't be a dick about leaving and burn a ton of bridges... but the standard 2 weeks with professional and minimal responses is the way to go.
An employment relation is a business relation ship with some contractual obligations and rights. It's all spelled out in the employment contract. Anything on top of that is the personal integrity of the employee and the reputation of the company. It's a mutual interest to do the right thing on both sides and behave in a way that is consistent with maintaining a good reputation.
For employees: your actions at company A might cause you problems at company B. People talk. I've seen people torpedo their careers by basically getting a well deserved reputation for not being entirely reliable/trustworthy. Anger issues in particular can be a problem. If you have them, learn to deal with them. I've actually advised friends to not hire certain people based on my negative experience with them. I've also done the opposite and helped people out by introducing them to their future employer. My own career changes each involved people in my network recommending me or introducing me. So, don't burn any bridges even if your employer treats you badly. Keep it friendly and professional.
For employers: people talk about their employers both inside and outside the company. If your reputation suffers because of how you treat your own employees, it becomes a problem for recruiting. The more disgruntled ex-employees you have, the harder it becomes to recover from that. You can offer more money to compensate but your actions will cost you. Worse, your own employees might start voting with their feet if they see you treat people badly. It's usually your best people that leave first when that happens. Because they have options and good reputations. If the A's leave, you end up with a lot of B's hiring C's.
"Your manager hears you out" NO -> "You should leave anyway"
That's exactly the reason why you don't share your exit plan prematurely. Your exit plan is still in progress, it may need more time, it may fail altogether. You're risking all of that by telling about your exit too early.
Don't say anything until you have a signed contract at the next employer. Do leave cleanly and gracefully.
Do lie about reasons. Just say the place was great, and you were just looking for a change. This keeps your network spotless and you might get a reference letter. Should times go dark, you may have a place to run back to.
The employee has no duty to their co-workers/team above good manners/civility and faithfully working towards a handoff.
Two weeks is not enough to hand off your work and allow a company/team to prepare.
If your managers are asshole, then maybe you cannot change your environment by voicing concerns, and risk being fired. But if you made up your mind and know you're leaving, by giving 2 months notice you can make sure not to leave your team in a bad state
If arguments based on core-values do not sway you, doing the right thing is also the way to get good recommendations and opportunities in the future.
Why should I serve my employers interests over my own?
I will behave as an employee in the way that is most beneficial to me personally. How much I care about my employers success is 100% dependent on how much I personally benefit from their success. If my employer wants a better transition than 2 weeks, they need to start thinking about how to incentivize that behavior.
In one job, I gave a months notice to leave for a startup. Just before I left, some extra urgent work came in and I was retained for a couple of months as a contractor to avoid leaving a key client and my former employer in a lurch. It actually benefitted the startup that I was able to incrementally transition.
My advice: do the bare minimum, so you're not considered a complete trash bag. Anything more might backfire on you in horrible ways.
Disclaimer: I worked in trading, which can be a fairly hostile environment at the best of times.
Two jobs ago, I resigned three months after having won one of the three top technical slots in the company. My SVP (a talented and smart climber) told me that she intended to plagiarize my resignation letter without even a perfunctory attempt at retention (not the first sneer to pass over my face as I confront the false cognate blessé -- begging pardon from our francophones).
CapitalistCartr has commented that the advice is good given the environment be rational. I endorse this, as far as it goes, but the rationality here, really, is only of the etiquette of gentlemanly advancement. Advancement -- to what, exactly? Meaning? Remuneration? Prestige? As if the absence of a particular individual really creates any adversity for the so-called subordinates.
Every organism is predicated upon a survival strategy, be it tooth or claw or (in our case) cooperation. When you are about to leave, lend aid to those who aided you.
