Your software engineer resume after a layoff gap
You were laid off, the search is running long, and the end date on your last role feels like a warning light. It is not. Make the calls one at a time, then keep a short, true answer ready for when a recruiter asks.
You open your resume to send one more application. Your eye goes straight to the top role, to the spot where it used to say "Present." It doesn't say that anymore. It says a month that keeps getting further away.
You stare at it. You wonder whether to blur it, pad it, or explain it in a paragraph. Every option feels like it makes things worse.
Here is the calm version. A layoff is not a mark against you. Recruiters in tech have read a lot of resumes from engineers whose teams got cut, and the end date on your last role is a fact, not a verdict. What they watch for is how you handle it. So handle it like an engineer: one decision at a time, each with a reason.
Decision one: the dates
The call: month and year on every role, including the real end date on the last one. No "Present." No switching to years only.
The reason is simple. Dates get checked. A background check or a reference call will surface your real last day, and a resume that said "Present" turns a neutral fact into a trust problem. A layoff is easy to explain. A fudged date is not.
The years-only trick is the quieter version of the same mistake. Switching every role to bare years hides a few months on paper, but screeners know the move. When every date on the page loses its month at once, the format itself becomes the question.
Keep the date format consistent from top to bottom. Use "to" between dates or a plain separator, the same way on every line. If you're rebuilding the layout anyway, the free editor keeps every role's dates in one format so nothing on the page looks hand-adjusted.
Decision two: a note on the page, or save it for the call
The call: one short, factual line under the last role, when the gap has run past a normal search or the layoff wasn't public news. Everything else waits for the conversation.
A screener reading an end date has one question: did you leave, get fired, or get cut? A single line answers it before they guess. It says "this wasn't about my work" without pleading the case. That's the whole job of the note. It is not a cover letter, and it is not a place for feelings.
Notice what the second version leaves out. No "unfortunately." No account of the search. No promise that you stayed positive. Those words read as apology, and apology tells the reader you think something went wrong. Nothing went wrong. A company made a budget decision.
If the layoff was recent and the gap is short, skip the note. The date speaks for itself, and an unprompted explanation draws the eye to something nobody was worried about.
Decision three: whether anything from the gap goes on the page
The call: list it only if it passes three tests. It happened. Someone could check it. It looks like the work you want next.
The search itself fails the second and third tests. Sending applications is not a role, and a line that says "actively seeking opportunities" fills space without telling anyone what you can do. Leave it off.
Here is how the things that do pass should look.
A few rules hold across all of them. Give the entry an honest title like "Independent Project" or "Career Break," never a made-up company name. Link anything public: the repo, the live app, your contributor page. A course goes under Education or Training with its finish date, and only if you finished it. What you built in the course matters more than the certificate.
Caregiving gets one line and no detail. You owe a screener the fact and the date you came back. You don't owe them the story.
Once those entries are in, read the page against one posting you want. If you'd like a second read on how well your resume lines up with a specific role, the one-time $2.99 Career Analysis Review does that. Your words stay your words. It points at gaps; it doesn't rewrite you.
Decision four: what you refuse to do
The call: no fake contract roles, no hidden dates, no apologizing. Each one trades a small discomfort now for a much bigger problem later.
- Fake contract or consulting roles. "Freelance Software Engineer" with no clients, no shipped work, and no one to call is the first thing a sharp interviewer pokes at. One follow-up question ("who was the client?") and the whole resume loses credibility.
- Hiding dates. Dropping months, moving the last role lower, or leaving dates off entirely. Each one makes the reader hunt, and a reader who has to hunt assumes the worst.
- Apologizing. On the page or on the phone. "Sorry, I know there's a gap" asks the interviewer to treat it as a problem. Say the fact and move on.
The honest version is smaller. It is also the one you can defend through a full hour of interviews, because every word of it is true and you can show the code.
Draft your line, then make it yours
Pick what you did and how long it has been. The builder gives you a resume line and a two-sentence answer for the screen. Treat both as a starting draft. Fill in the brackets with real details, then rewrite the answer until it sounds like you talking to a colleague, not you reading off a card.
Draft your gap line
Pick what you did and roughly how long it has been. You get a resume line and a two-sentence answer for the screen. Then rewrite it in your own words, because a recruiter can hear a pasted answer.
Pick one from each group to see your draft.
The screen call: say it in three sentences, then stop
Sooner or later a recruiter asks, "So what have you been up to since your last role?" This is the moment the whole resume was setting up. Your answer has three beats: what happened, what you did with the time, and what you want next. Then you stop talking.
"I was laid off from Lumen Health in February when they cut most of the platform team. Since then I've been building Tallyline, a budgeting API in Go, which has kept me close to the kind of backend work this role is about. I'm looking for a team where I can own a service end to end, and that's what caught my eye here."
That's the whole answer. No backstory on the reorg. No account of every application. No "I know it's been a while." The recruiter has heard the layoff story many times before. What they're listening for is whether you can say it plainly and turn toward the job.
If they push ("why has it taken this long?"), give one true sentence and pivot: "I've been selective about fit, and this role is the kind I've been holding out for." Then ask them a question about the team.
Write your three sentences tonight. Say them out loud until they sound boring to you. Boring is the goal. Then open your resume in the editor, put the real end date on your last role, and send the next application.