Before you start: Give yourself an hour to breathe
If you just found out today, it's okay to not open your resume immediately. Give yourself a few hours to process, tell people who need to know, and do whatever you need to do to stabilize.
But don't wait too long. The details of your work — the specific metrics, the project names, the outcomes — start fading within days. The best resume bullets come from writing them while everything is still clear.
The complete checklist
Part 1: The basics (30 minutes)
Change the end date on your most recent role to the month of your layoff. Be accurate — don't leave it blank or list "present." Recruiters notice.
Find whatever version of your resume you last used. If you can't find it, start a fresh document — that's fine too. The content matters more than the template.
Before you write anything, decide roughly what kind of role you're targeting next. It doesn't have to be precise — "senior software engineer at a B2B SaaS company" is enough. This shapes every decision about what to include and emphasize.
Part 2: Reconstruct your accomplishments (1–2 hours)
This is the hardest part and the most important. Set aside at least an hour. Close distractions.
Set a 15-minute timer and write down every project, win, contribution, or deliverable you can remember — in any format, no editing. The goal is breadth, not polish. Check your calendar for the past 12 months to jog memory.
Search for: "shipped," "launched," "congrats," "great work," "merged," "deployed." The compliments and announcements are where your evidence lives. Screenshot or copy anything relevant.
Jira, Linear, Asana, Notion — whatever your team used. Look for tickets you closed, epics you owned, PRs you opened and merged. These are your evidence trail.
If you have previous self-reviews, manager feedback, or peer reviews from this role, they're gold. They often contain specific praise that translates directly into resume language.
For each one, ask: how much? How many? What was the before/after? Even rough numbers help. "Reduced churn by approximately 15%" beats "improved customer retention" every time.
Part 3: Write the bullets (30–45 minutes)
Led, Built, Designed, Reduced, Increased, Launched, Owned, Drove, Streamlined. Never start with "Helped," "Assisted," or "Worked on."
The formula: [Action verb] + [what you did] + [quantified result or impact]. "Led redesign of customer portal — reduced support ticket volume by 30% and improved NPS by 12 points."
Older roles (3+ years ago) get 2–3 bullets. Your most recent role gets the most depth. Quality beats quantity — don't pad.
Part 4: The rest of the resume (30 minutes)
Two to three sentences max. Describe what you do, at what level, and what you're targeting. Make it match the jobs you're going for — not just where you've been.
Add tools, languages, frameworks, or methodologies you used in this role. Remove things you haven't touched in 3+ years and wouldn't want to be tested on. For software engineers: keep your tech stack current.
Reduce to 1–2 bullets or remove entirely if not directly relevant to your target role. Recruiters spend most of their time on the top third of your resume — don't bury your best work with irrelevant history.
Part 5: Finishing touches (15 minutes)
Past roles: past tense. Current role (up to layoff date): past tense now. Mixing tenses is a small thing that reads as careless.
Use "FirstName LastName Resume 2026.pdf" as your filename. Not "resume_final_v3_FINAL.pdf." Recruiters file these.
Consistency matters. Update your most recent role with the same end date and your strongest bullets. Update your summary to match your resume. Turn on "Open to work" if you're comfortable with it — the badge increases recruiter outreach significantly.
What to do about the gap
You don't need to hide a layoff. Simply list your end date accurately. If asked in an interview, a brief, matter-of-fact answer is all you need: "The company went through a round of layoffs that affected my team." Then pivot immediately to what you're looking for next.
Hiring managers in 2024 understand that layoffs are common and not a reflection of individual performance. Trying to obscure or over-explain them often creates more scrutiny than the gap itself.
Make sure this never happens again
The most painful part of updating a resume after a layoff isn't the writing — it's the reconstruction. Trying to remember what you did, finding the metrics, rebuilding the context you had at the time but lost over months of not writing it down.
The fix is simple: log your accomplishments continuously, not retrospectively. A 2-minute note the day after something ships is worth more than an hour of reconstruction six months later. And when the next transition happens — voluntary or not — you're ready in hours, not days.
Never start from scratch again
Start logging your wins now. When the next transition comes, your record is ready.
Start for free →