Exit Strategy Guide

How to Leave Your Job Strategically (Before You Need To)

Target Audience: Tech professionals (engineers, SREs, infrastructure specialists)
Reading Time: 30-35 minutes

What This Guide Is

A proactive framework for preparing to leave your job before you're forced to, burned out, or desperate. An "exit strategy" is not about disloyalty — it's about maintaining career agency and reducing risk. Think of it like insurance: you hope you never need it, but you'll be grateful it exists if you do.

Core premise: The best time to prepare an exit strategy is when you don't need one. Waiting until crisis (layoff, burnout, toxic manager) means you negotiate from weakness, make poor decisions, and damage your career trajectory.

What This Guide Is Not

❌ Encouragement to quit your job (stability has value)
❌ Permission to be a bad employee (exit strategy ≠ checked-out employee)
❌ Financial advice (consult professional for personal finance decisions)
❌ Legal guidance (consult employment lawyer for contract/severance issues)

Why Exit Strategies Matter

The Cost of Unpreparedness

Scenario 1: Sudden Layoff (No Runway) - Company announces layoffs → you're included → 2 weeks notice - If unprepared: - Resume outdated (last updated 3 years ago) - No emergency fund (1 month expenses saved) - Network cold (haven't talked to former colleagues in years) - Interview skills rusty (haven't interviewed in 5 years) - Result: 3-6 month desperate job search, accept suboptimal offer

If prepared:
Resume current (updated quarterly)
6-month emergency fund (financial runway)
Warm network (maintained relationships)
Interview-ready (practiced annually)
Result: 1-2 month strategic search, accept strong offer

Pattern (observed in tech layoffs 2022-2023): Engineers with updated portfolios, active networks, and financial buffers found roles 2-4x faster than unprepared colleagues.

Source type: Anecdotal observation from tech layoff waves (Twitter, Reddit r/cscareerquestions), recruiter informal surveys.

Uncertainty: "2-4x faster" is rough estimate from self-reported data, not controlled research.

Scenario 2: Burnout-Driven Exit (Reactive Quitting) - You're burned out → impulsively quit → no plan - If unprepared: - No savings (immediate financial pressure) - No job search strategy (panic apply to 100 companies) - Explain resume gap in interviews ("Why 6-month gap?" → "I was burned out" = red flag) - Result: Accept first offer to stop bleeding money, often lateral or downward move

If prepared:
Emergency fund covers gap (can afford to be selective)
Job search plan ready (target companies, recruiter contacts)
Narrative prepared ("I took time to recharge and upskill" = positive framing)
Result: Strategic sabbatical, return with better offer

Source: Burnout research (Maslach & Leiter), career transition case studies.

Uncertainty: Not everyone can afford to quit without another job (privilege assumption addressed below).

The Strategic Advantage of Preparation

Negotiating leverage = options.

If you have: - 6-month financial runway (savings) - Updated portfolio (resume, GitHub, LinkedIn) - Warm network (former colleagues, recruiters) - Interview skills (practiced recently)

Then you can: - Negotiate aggressively (you can walk away) - Be selective (turn down bad fits) - Time exit strategically (leave on your terms, not theirs)

Source: Negotiation theory (BATNA - Best Alternative To Negotiated Agreement, Fisher & Ury "Getting to Yes").

The Four Pillars of Exit Readiness

Pillar 1: Financial Preparedness (Runway)

Goal: Build financial buffer to survive unemployment without panic.

Minimum viable runway: 3 months of living expenses
Recommended runway: 6 months of living expenses
Ideal runway: 12 months of living expenses

Why 6 months? - Average tech job search: 2-4 months (LinkedIn data, self-reported) - Buffer for selectivity (don't accept first offer out of desperation) - Accounts for unexpected delays (interview loops slow, offer rescinded, market downturn)

Source: Personal finance literature (Ramit Sethi "I Will Teach You to Be Rich", Dave Ramsey emergency fund recommendations), unemployment duration statistics.

Uncertainty: "6 months" is heuristic, not rule. Depends on: - Job market (bull market = 1-2 months, bear market = 4-6 months) - Specialization (niche skills harder to place quickly) - Geographic flexibility (limited to one city = longer search)

How to build emergency fund:

Step 1: Calculate monthly burn rate - Rent/mortgage + utilities + food + insurance + debt payments + minimum discretionary - Example: $3,000/month → 6 months = $18,000 target

Step 2: Automate savings - Direct deposit split: 10-20% to savings account (high-yield savings, not checking) - Treat it like mandatory bill (not "save what's left")

Step 3: Separate from other goals - Emergency fund ≠ vacation fund, house down payment, retirement - Dedicated account, label it "DO NOT TOUCH (job loss only)"

Step 4: Adjust for life stage - Single, no dependents: 3 months acceptable (lower risk) - Family, mortgage, dependents: 9-12 months safer (higher risk)

Privilege check: - Building 6-month runway assumes disposable income (after rent, food, debt) - Not everyone can save (low income, high cost of living, medical debt, caregiving) - If financially constrained: Start with 1 month, build incrementally

Source: Personal finance frameworks (emergency fund strategies), financial planning research.

What counts as "emergency":

Valid reasons to tap emergency fund: - Layoff / job loss - Medical emergency (can't work) - Quit toxic job (health > money) - Relocation (family, caregiving)

Invalid reasons (don't drain fund for): - ❌ Vacation, new car, gadget - ❌ "This investment opportunity is too good to pass up" - ❌ Impulse purchase

Why discipline matters: If you drain fund for non-emergencies, it won't be there when you actually lose your job.

Pillar 2: Professional Preparedness (Portfolio)

Goal: Always be "interview-ready" — portfolio current, skills sharp, network warm.

Components of professional readiness:

2.1 Resume Maintenance (Quarterly Updates)

Problem: Most people update resume when job hunting → stale, missing accomplishments, rushed.

Better approach: Update quarterly (even if happily employed).

Quarterly resume ritual (30 minutes every 3 months):

Step 1: Document recent accomplishments - Projects shipped (scope, impact, technologies) - Metrics improved (uptime, latency, cost reduction, incident reduction) - Skills acquired (certifications, new tech stack)

Step 2: Refresh format - Remove outdated skills (deprecated tech you no longer use) - Add recent skills (Kubernetes, Terraform, whatever you're using now) - Update job title if promoted

Step 3: Store versions - Save dated version (resume_2026_Q2.pdf) - Keep master document (easy to customize for specific applications)

Why quarterly? - Fresh memory (you forget details after 6 months) - No gaps (continuous record of growth) - Low effort (30 min/quarter << 8 hours cramming before job search)

Source: Resume best practices (recruiter guides), career coaching literature.

2.2 Portfolio Artifacts (Ongoing Visibility)

Principle: Your portfolio is your proof. Resumes claim skills; portfolios demonstrate them.

Minimum viable portfolio: - [ ] GitHub: 2-3 pinned repos (real projects, not tutorials) - [ ] LinkedIn: Current headline, summary, skills (updated quarterly) - [ ] Blog/Writing: 1 post per quarter (technical tutorials, case studies, reflections)

Advanced portfolio (higher visibility): - [ ] Conference talks: 1-2 talks/year (local meetups → regional conferences) - [ ] Open-source contributions: Regular PRs to projects you use - [ ] Certifications: Cloud (AWS, Azure, GCP), Kubernetes (CKA, CKAD), platform-specific

Why portfolio matters for exit: - Faster job search: Recruiters find you (inbound > outbound) - Interview leverage: "Here's code I wrote" > "I claim I can code" - Negotiation power: Strong portfolio = multiple offers = better terms

Maintenance schedule:

Monthly: - [ ] Post 1 technical update (LinkedIn, Twitter/X, blog)

Quarterly: - [ ] Write 1 blog post (300-1000 words, tutorial or case study) - [ ] Review GitHub pinned repos (are they still representative?)

Yearly: - [ ] Major portfolio refresh (update READMEs, archive old projects) - [ ] Conference talk or major contribution (if feasible)

Source: Developer marketing research (GitHub portfolio impact), recruiter surveys on what gets callbacks.

Privilege check: Portfolio building requires time outside work (assumes no caregiving, health constraints, multiple jobs).

2.3 Network Maintenance (Warm Connections)

Principle: Your network is your early warning system and job discovery engine.

Pattern (Granovetter "Strength of Weak Ties"): Job offers come more from acquaintances than close friends.

Source: Granovetter, M. (1973). "The Strength of Weak Ties". American Journal of Sociology.

Why weak ties matter: - Close friends = same information bubble (you know same jobs they know) - Weak ties = diverse networks (they know opportunities you don't)

Network maintenance strategy:

Monthly (low effort): - [ ] LinkedIn engagement (comment on 3-5 posts from connections) - [ ] Respond to recruiter messages (even if not interested — maintain relationship)

Quarterly (medium effort): - [ ] Reach out to 2-3 former colleagues ("How are you? What are you working on?") - [ ] Attend 1 meetup or virtual event (expand network)

Yearly (high effort): - [ ] Attend 1-2 conferences (in-person networking, deep connections) - [ ] Give talk or workshop (visibility boost, attract connections)

Red flags (network has gone cold): - You don't remember last conversation with former coworkers (> 1 year ago) - Recruiters stopped messaging you (invisible on LinkedIn) - You have no one to ask for job referrals (network = 0)

How to revive cold network: - Genuine outreach (not "I need a job, can you help?" → "Saw your post on X, curious about your thoughts") - Offer value first (share article, make intro, congratulate on achievement) - Rebuild gradually (1-2 reconnections/week for 3 months)

Source: Networking research (Keith Ferrazzi "Never Eat Alone"), social capital theory.

Cultural variance: - US networking: Transactional, fast (coffee after 1 conversation) - European networking: Slower trust-building (multiple interactions before asking favors) - Asian networking: Hierarchical (referrals flow through seniority)

2.4 Interview Skills (Annual Practice)

Problem: Interview skills atrophy. If you haven't interviewed in 5 years, you'll bomb first few loops.

Better approach: Practice annually (even if happily employed).

Annual interview ritual:

Step 1: Refresh fundamentals (1-2 weeks prep) - [ ] Coding practice (LeetCode, HackerRank — not because it's realistic, but because it's what companies test) - [ ] System design review (read "Designing Data-Intensive Applications", practice whiteboarding) - [ ] Behavioral prep (STAR method — Situation, Task, Action, Result)

Step 2: Real interview loop (1-2 companies) - [ ] Pick companies you'd genuinely consider (don't waste their time) - [ ] Go through full loop (phone screen → technical → onsite) - [ ] Get feedback (even if you don't accept, learn what worked/didn't)

Step 3: Calibrate market value - [ ] If you get offers, you know real market rate (not just Levels.fyi estimates) - [ ] If you don't, you know skill gaps (address them before next year)

Why annual practice matters: - Interview anxiety decreases (familiarity breeds confidence) - You discover market perception (are you still competitive?) - Maintains optionality (you could leave if needed)

Source: Interview preparation guides (Gayle Laakmann McDowell "Cracking the Coding Interview"), career coaching best practices.

Uncertainty: "Annual" is arbitrary. Some argue every 6 months, others every 2 years. Depends on market volatility.

Pillar 3: Psychological Preparedness (Mental Readiness)

Goal: Be emotionally/psychologically ready to leave when signals align.

Why psychological prep matters: - Exit decisions are often emotional (anger, fear, loyalty, guilt) - Unprepared minds make poor decisions (impulsive quit, or stay too long in toxicity) - Mental models help you recognize signals without panic

3.1 Pre-Commitment (Decide Criteria in Advance)

Principle: Decide when you'll leave BEFORE you're emotional about it.

Pre-commitment contract (write this down):

"I will activate job search if: 1. [ ] Compensation: I'm 20%+ below market for 6+ months after negotiation attempt 2. [ ] Growth: I haven't learned new skill or technology in 12 months 3. [ ] Culture: Toxic behavior (harassment, unethical practices, chronic overwork) persists after escalation 4. [ ] Burnout: I experience 3+ burnout symptoms for 3+ months 5. [ ] Organizational: Company shows 3+ distress signals (layoffs, exec turnover, revenue decline) 6. [ ] Promotion: I'm blocked from promotion for 2+ years despite strong performance

If 2+ triggers activate → start passive job search
If 3+ triggers activate → start active job search

Why pre-commitment works: - Removes emotion from decision (you're not deciding in crisis) - Creates objectivity (clear thresholds, not vague "I'm unhappy") - Prevents both extremes (impulsive quit OR staying in misery)

Source: Decision science (pre-commitment strategies), behavioral economics (Thaler & Sunstein "Nudge").

3.2 Exit Narrative (Story You'll Tell)

Problem: "Why are you leaving?" is most common interview question. Unprepared answer = red flag.

Bad answers (avoid): - ❌ "My manager is toxic" (badmouthing = unprofessional) - ❌ "I'm burned out" (raises concern about your resilience) - ❌ "I hate my job" (negativity = culture fit risk) - ❌ "I was laid off" + defensiveness (signals insecurity)

Good answers (professional framing): - "Seeking growth opportunities in [specific skill/domain]" (positive, forward-looking) - "Company direction shifted, I'm looking for [mission alignment]" (neutral, values-driven) - "Excited about [new company's] approach to [technical problem]" (enthusiasm, not escape) - "Layoff gave me opportunity to be strategic about next role" (reframing, agency)

How to craft your narrative:

Step 1: Identify true reason (private) - Be honest with yourself: toxic culture, boredom, low pay, burnout - Write it down (for your eyes only)

Step 2: Reframe professionally (public) - Find the growth-oriented angle (what are you moving TOWARD, not running FROM) - Test with trusted friend/mentor (does it sound believable?)

Step 3: Practice delivery - Say it out loud 10 times (until smooth, natural) - Record yourself (check for defensiveness, negativity in tone)

Example reframes:

Private truth	Public narrative
"Toxic manager micromanages me"	"Seeking role with more autonomy to lead technical decisions"
"Bored, no challenge"	"Looking for opportunity to work on [specific tech] at scale"
"Underpaid by 30%"	"Excited to join company that values [skill I have] at market rate"
"Company is failing"	"Company pivoted away from infrastructure; I'm passionate about that domain"

Source: Interview coaching guides, recruiter feedback on what works.

Privilege check: Some people can't afford "positive framing" (e.g., discrimination, harassment). If you left due to illegal behavior, consult employment lawyer before interviews.

3.3 Emotional Resilience (Handling Rejection)

Reality check: Job search involves rejection. Lots of it.

Typical rejection rates (observed patterns): - Cold applications: 95-98% rejection (no response or auto-reject) - Recruiter reach-out: 30-50% rejection (after initial screen) - Full interview loop: 50-70% rejection (make it to final round, don't get offer)

Source type: Job search statistics (self-reported, aggregated from Reddit r/cscareerquestions, Hacker News), recruiter informal surveys.

Uncertainty: Rates vary widely by seniority, market conditions, role competitiveness.

Why rejection happens (often not about you): - Hiring freeze (budget cut after you interviewed) - Internal candidate (they were legally required to post externally, but had someone in mind) - Competing offer (someone else accepted faster) - Skill mismatch (not a fit, but doesn't mean you're bad)

How to handle rejection psychologically:

1. Expect rejection (normalize it) - "I will apply to 20 companies, expect 15 rejections, 5 interviews, 1-2 offers" (math, not emotion)

2. Depersonalize rejection - "They said no to my skills for this specific role" ≠ "I am worthless"

3. Learn from patterns - If rejected after 5 phone screens → polish your pitch - If rejected after 5 onsites → practice technical/system design - If rejected after 20 applications with no interviews → resume needs work

4. Build rejection resilience - Each rejection = data point (what to improve) - Reframe: "This wasn't the right fit" (not "I failed")

Source: Resilience research (Carol Dweck "Mindset"), job search psychology (career coaching literature).

Mental health note: If rejection triggers severe anxiety/depression, seek therapist support (this is common, not weakness).

Pillar 4: Tactical Execution (How to Leave)

Goal: Execute exit cleanly — preserve relationships, secure references, avoid burning bridges.

4.1 Notice Period (How Much Warning)

Standard: 2 weeks notice (US norm)
Senior roles: 3-4 weeks (courtesy, transition planning)
Critical roles: 1-2 months (if you're sole expert on system, ethical to give more time)

Source: Employment norms (vary by country — US 2 weeks, EU 1-3 months contractual), professional courtesy guidelines.

Why notice period matters: - Too short: Burn bridges (company scrambles, colleagues resent you) - Too long: New employer impatient (they want you to start), you're awkward lame-duck - Balance: Enough time to transition, not so long you're useless

When to give LESS notice (1 week or immediate): - Toxic environment (harassment, retaliation risk) - Offer has tight start date (new company needs you ASAP) - You're being pushed out anyway (PIP, hostile manager)

When to give MORE notice (4+ weeks): - Senior leadership role (C-suite, VP — succession planning) - Sole expert on critical system (ethical to document/train replacement) - Strong relationship with company (you want future collaboration, references)

Cultural variance: - US: 2 weeks standard, at-will employment (can leave anytime) - EU: 1-3 months contractual (must honor contract or risk legal action) - Japan: 1-2 months norm (longer notice culturally expected)

Privilege check: Some people can't afford notice period (need paycheck immediately, toxic environment unsafe). Survival > courtesy.

4.2 Resignation Conversation (How to Tell Manager)

Best practice: In-person (or video call if remote), private 1-on-1, prepared script.

Bad approaches (avoid): - ❌ Email resignation (impersonal, manager blindsided) - ❌ Announce in team meeting (humiliates manager publicly) - ❌ Tell colleagues before manager (manager hears through grapevine = disrespect)

Good approach (professional protocol):

Step 1: Schedule 1-on-1 with manager - "Can we chat privately for 15 minutes today?" (don't say why over Slack/email)

Step 2: Deliver news directly - "I wanted to let you know first: I've accepted another offer. My last day will be [date]." - Keep it brief, factual, unemotional

Step 3: Offer transition support - "I want to make this transition smooth. I can document X, train Y, wrap up Z."

Step 4: Express gratitude (if genuine) - "I've learned a lot here, especially [specific thing]. Thank you for [specific support]."

Step 5: Avoid burning bridges - Don't badmouth company, colleagues, or manager (even if they deserve it) - Don't gloat about new offer (classless)

If manager asks why you're leaving: - Use prepared narrative (growth-oriented, positive) - Don't lie, but don't overshare ("toxic culture" → "seeking different team dynamic")

If manager makes counter-offer: - Politely decline (accepting counter-offer rarely works — see below) - "I appreciate it, but I've made my decision" (firm, respectful)

Source: Professional resignation guides (Ask a Manager blog, HR best practices), etiquette research.

4.3 Counter-Offer (Should You Accept?)

Pattern: You resign → Manager panics → Company makes counter-offer (raise, promotion, bonus).

Statistics (informal surveys): 50-80% of people who accept counter-offers leave within 12 months anyway.

Source type: Recruiter anecdotes, HR informal data (not rigorous research).

Why counter-offers rarely work:

1. Trust is broken - You threatened to leave → company knows you're flight risk - They may start planning your replacement (quietly)

2. Root issues unchanged - If you left for culture/growth/mission → money doesn't fix that - If you left for toxic manager → raise doesn't make them less toxic

3. Resentment - Colleagues learn you got raise by threatening to quit (morale damage) - You resent that it took resignation to get market rate

4. New job offer burned - You renege on accepted offer → reputation damage (recruiter, new company) - Hard to go back to job market soon (you're now "unreliable")

When counter-offer might be acceptable (rare): - Leaving ONLY for money, no other issues (and counter matches new offer) - Company immediately addresses root cause (promotes you, removes toxic manager) - You have written commitment (not verbal promise — get it in writing)

Best practice: Politely decline counter-offer, proceed with resignation.

Script: "I appreciate the offer, but my decision isn't just about compensation. I'm excited about [new opportunity] and I've made my choice."

Source: Career transition research (counter-offer dynamics), recruiter guidance.

4.4 Reference Management (Securing Strong References)

Principle: You need 2-3 strong references for future job searches. Secure them BEFORE you leave.

Who makes a good reference: - Direct manager (if relationship is good) - Skip-level manager or director (if they know your work) - Peer who can speak to technical skills (senior colleague, tech lead) - Cross-functional partner (PM, engineering manager from adjacent team)

Who makes a bad reference: - ❌ Toxic manager (will sabotage you) - ❌ Colleague who barely worked with you (can't speak to specifics) - ❌ Former boss from 10 years ago (too outdated)

How to secure references:

Step 1: Identify 2-3 people (before you resign) - Pick people who will say positive things (strong performance, good working relationship)

Step 2: Ask permission - "I'm exploring new opportunities. Would you be comfortable being a reference?" - Give them out (they can decline if uncomfortable)

Step 3: Provide context - "Here's my resume and projects we worked on together. If asked, it'd be great if you could mention [specific accomplishment]."

Step 4: Maintain relationship - Update them when you land new job (courtesy + future reference potential) - Stay connected (LinkedIn, occasional check-in)

If leaving toxic environment: - Find references outside toxic leadership (peers, skip-level if safe) - If no good internal references, use external (open-source collaborators, conference contacts)

Source: Reference check best practices (HR guides), professional networking research.

Legal note: In some jurisdictions, companies can only confirm employment dates (not performance). Check local laws.

4.5 Exit Interview (What to Say/Not Say)

Purpose (from company's perspective): Gather feedback to improve retention.
Reality: Exit interviews rarely change anything (data goes to HR, forgotten).

Should you be honest?

Safe topics (constructive feedback): - Process improvements (hiring, onboarding, tooling) - Compensation benchmarking (if you're leaving for market rate gap) - Growth opportunities (if lack of promotion path was factor)

Risky topics (don't burn bridges): - ❌ Toxic manager by name (HR may share feedback, retaliation risk) - ❌ Specific colleague complaints (petty, unprofessional) - ❌ Ranting about culture (comes across as bitter)

When to skip exit interview entirely: - Toxic environment (they won't listen, may use against you) - Layoff (you didn't choose to leave, no feedback needed) - Burnt out (you're not in headspace to be constructive)

Safe script (if you do exit interview): - "I learned a lot here. I'm leaving for [growth/opportunity/mission] that aligns with my career goals. I hope the team continues to [positive thing about work]." - Keep it brief, professional, forward-looking

Source: Exit interview research (HR literature), professional departure etiquette.

Special Scenarios (Non-Standard Exits)

Scenario 1: Layoff (Involuntary Exit)

If you're laid off:

Immediate actions (first 48 hours): - [ ] Review severance agreement (don't sign immediately — consult employment lawyer if unsure) - [ ] Negotiate severance (companies often offer baseline, but will increase if you ask) - [ ] File for unemployment (if eligible — this is insurance you paid into, not charity) - [ ] COBRA health insurance (US: you can continue employer health insurance, but expensive)

Week 1-2 (stabilize): - [ ] Update LinkedIn (headline: "Open to opportunities in [domain]", not "LAID OFF HELP") - [ ] Notify network (former colleagues, recruiters — "I'm available as of [date]") - [ ] Process emotions (grief, anger, fear are normal — don't suppress, but don't spiral)

Week 3+ (job search): - [ ] Activate exit strategy (resume, portfolio, network, interview prep — this is why you prepared)

Narrative for interviews: - "Company had layoffs affecting [department/X% of workforce]. I'm now looking for [growth opportunity]." - Don't apologize, don't overshare, don't badmouth company

Source: Layoff survival guides (career coaching literature), unemployment navigation resources.

Privilege check: Severance, unemployment, COBRA assume US employment law. Other countries have different protections.

Scenario 2: Quitting Without Another Job (Gap Year, Burnout Recovery)

When this is viable: - 6-12 month financial runway (savings) - Severe burnout (health requires break) - Strategic sabbatical (upskill, pivot careers, personal project)

When this is risky: - ❌ No savings (immediate financial crisis) - ❌ Weak job market (hard to re-enter) - ❌ Resume gap hard to explain (aimless gap = red flag)

How to make intentional gap:

Before you quit: - [ ] Build narrative (what will you do during gap?) - "I'm taking 3 months to learn [new skill], build [side project], recover from burnout" - ❌ "I'll figure it out" (aimless = resume red flag)

During gap: - [ ] Document progress (blog posts, GitHub commits, certifications) - [ ] Stay visible (LinkedIn activity, conference attendance) - [ ] Set timeline (3-6 months ideal, 12 months max before resume gap hurts)

Returning to market: - [ ] Frame gap positively ("I took strategic sabbatical to [accomplish X]. Now I'm energized and ready for [opportunity].")

Source: Sabbatical research (career break strategies), resume gap navigation guides.

Privilege check: Quitting without job requires financial privilege (savings, safety net, no dependents).

Scenario 3: Toxic Environment (Emergency Exit)

When immediate exit is justified: - Harassment, discrimination, abuse (physical/psychological safety at risk) - Illegal activity (company asks you to break laws) - Severe burnout (doctor/therapist recommends immediate leave)

Emergency exit protocol:

Step 1: Document everything - Emails, Slack messages, incidents (dates, witnesses) - Medical records if health impact (therapist notes, doctor visits)

Step 2: Consult lawyer (if severe) - Employment lawyer can advise on wrongful termination, hostile work environment claims - Don't resign until you understand legal options

Step 3: Resign or take medical leave - Medical leave (FMLA if US, sick leave if EU) preserves job while you recover - Immediate resignation (if unsafe to stay)

Step 4: Protect references - Find references outside toxic chain (peers, former managers, external collaborators)

Narrative for interviews: - "Company culture wasn't aligned with my values. I'm seeking [positive attribute]." - Don't badmouth (even if justified — interviewers hear "difficult person")

Source: Toxic workplace survival guides (Ask a Manager blog), employment law resources.

Lehetséges Torzítások és Bizonytalanságok

Forrásoldali Torzítások

Author background: - This guide reflects Western tech culture (primarily US/EU software/infrastructure) - Assumptions: Individual contributor roles, competitive job market, ability to save money - May not apply to: Government, academia, non-tech industries, non-Western cultures

Survivorship bias: - Strategies reflect "what worked" for people who successfully exited - People who left jobs and regretted it are under-represented - Success stories over-represented; failures invisible

Privilege assumptions: - Guide assumes: Financial ability to save, job market access, visa freedom - Reality: Not everyone can build 6-month runway (low income, dependents, debt) - Emergency exits assume safety net (family support, savings) not universal

Tech industry bias: - Examples from software, SRE, cloud infrastructure - May differ in: Embedded, hardware, corporate IT, non-tech roles - Startup vs. enterprise dynamics vary significantly

Értelmezési Bizonytalanságok

"6-month runway" is arbitrary: - Some argue 3 months sufficient (fast job market) - Others argue 12 months safer (slow market, niche skills) - Context variance: Bull market = shorter runway OK, bear market = longer needed

"Update resume quarterly" is heuristic: - Some people update monthly (aggressive job search) - Others update yearly (stable, not looking) - Quarterly is balance (fresh memory, not overwhelming)

"Notice period" norms vary: - US: 2 weeks standard (at-will employment) - EU: 1-3 months contractual (must honor or risk legal action) - Japan: 1-2 months cultural expectation - Toxic environment: Immediate exit may be justified (survival > etiquette)

Kontextuális Korlátok

Career stage: - Early career (0-3 years): Build runway quickly (aggressive saving, fast job search) - Mid-career (3-10 years): Balance runway + family obligations - Late career (10+ years): Higher savings, but also higher burn rate (lifestyle inflation)

Economic cycle: - Bull market: Shorter runway acceptable (jobs plentiful, fast placement) - Bear market: Longer runway critical (job search 4-6 months, not 2)

Geographic/visa constraints: - H1B/L1 visa (US): Job loss = 60 days to find new sponsor or leave country (no runway option) - EU Blue Card: More stable, but sponsorship still matters - Remote work: Expands options but time zones, legal complexity

Life stage: - Single, no dependents: Higher risk tolerance (can relocate, take pay cut, quit without job) - Family, mortgage, dependents: Lower risk tolerance (stability > growth)

Saját Feltevések (Author's Assumptions)

Assumption 1: "6-month runway = safety" - Belief: If you have 6 months savings, you can job search without panic - Reality: Some job searches take 9-12 months (specialized roles, weak market) - Counter-case: 6 months runs out → desperation hiring → bad fit - Uncertainty: Optimal runway depends on specialization, market, seniority

Assumption 2: "Counter-offers rarely work" - Belief: 50-80% who accept counter-offers leave within 12 months - Source: Recruiter anecdotes, not rigorous research - Counter-evidence: Some counter-offers DO work (company immediately fixes root issue) - Caveat: If leaving ONLY for money, counter-offer may be acceptable

Assumption 3: "Exit interview is useless" - Belief: HR collects feedback, nothing changes - Counter-evidence: Some companies genuinely act on exit feedback (rare, but exists) - Nuance: Exit interview CAN be useful if you trust leadership + company culture supports change

Assumption 4: "Layoff narrative is neutral" - Belief: "I was laid off" is acceptable explanation (external factor, not performance) - Reality: Some hiring managers still stigmatize layoffs ("Why were YOU chosen for layoff?") - Mitigation: Frame as company-wide event, not individual performance ("20% workforce reduction")

Kutatási Hiányosságok

No longitudinal exit strategy research: - Zero controlled studies on "exit preparedness → job search duration" - Confounding variables: People who prepare also network more, learn more, perform better

Self-reported data: - Job search duration data is self-reported (LinkedIn, Reddit — selection bias, memory errors) - "3-6 month runway" is pattern recognition, not rigorous research

No cross-cultural validation: - Strategies tested primarily in US/Western EU tech - Unknown effectiveness in: Asia, Middle East, Africa, Latin America, Eastern Europe

Missing privilege analysis: - Guide assumes: Financial ability to save, job market access, visa freedom - Reality: Not everyone can build runway (medical debt, caregiving, low income)

Ethical Tensions

Individual preparedness vs. Collective action: - Guide focuses on individual exit strategies - Missing: When is organizing (union, collective bargaining) more effective than leaving? - Trade-off: Prepare personal exit vs. fight to improve system for everyone

Exit vs. Voice: - Guide encourages exit when dissatisfied - Alternative: Use "voice" (speak up, push for change) before exiting - Hirschman's framework: Exit, Voice, Loyalty (all valid responses to org problems)

Transparency vs. Self-protection: - Guide recommends discretion (don't tell manager you're job searching) - Reality: Some managers retaliate when they sense intent to leave - Dilemma: Honesty vs. survival

Next Steps (Using This Guide)

Month 1-3: Build financial runway - [ ] Calculate 6-month burn rate (monthly expenses × 6) - [ ] Set up dedicated savings account (high-yield, separate from checking) - [ ] Automate savings (10-20% direct deposit)

Month 4-6: Establish professional presence - [ ] Update resume (current format, recent accomplishments) - [ ] Refresh LinkedIn (headline, summary, skills) - [ ] Write 1 blog post or make 1 open-source contribution

Month 7-9: Activate network - [ ] Reconnect with 5-10 former colleagues (genuine outreach) - [ ] Respond to 2-3 recruiter messages (build relationships) - [ ] Attend 1 conference or 3 meetups (expand weak ties)

Month 10-12: Practice interviews - [ ] Prep fundamentals (coding, system design, behavioral) - [ ] Do 1-2 real interview loops (calibrate market value) - [ ] Document feedback (what worked, what to improve)

Ongoing: Maintain readiness - [ ] Quarterly resume updates (30 min every 3 months) - [ ] Quarterly portfolio updates (1 blog post, 1 contribution) - [ ] Annual interview practice (1-2 companies)