How to explain a gap in your resume (and what to do during one)

You're 6 months out of work. Maybe 12. Maybe more. The gap on your resume keeps growing and you can feel the dread every time you open a job application.

Here's the thing nobody tells you: the gap itself is rarely the problem. The story you tell about the gap is the problem, and the difference between a candidate who lands offers and one who doesn't is usually just whether they have a clean answer ready or fumble through it.

This piece covers both halves of the question: how to talk about the gap (in the resume, in the application, in the interview), and what to actually do during the gap to make the answer easier in 6 months.

The data: gaps are less stigmatized than you think

For about a decade, conventional wisdom said any gap longer than 3 months was a death sentence. That isn't true anymore.

According to BLS data for April 2026, roughly 1.8 million Americans had been unemployed for 27 weeks or more (the BLS definition of "long-term unemployed"), accounting for 25.3% of all unemployed people. A quarter of the unemployed population has a gap longer than 6 months. That's not a fringe condition; it's a substantial slice of the labor market that hiring managers see every week.

A 2022 LinkedIn survey of nearly 23,000 workers and more than 7,000 hiring managers (published when LinkedIn launched its Career Break feature, and widely cited since) found:

• 62% of workers have taken a career break at some point.
• 35% of workers, mostly women, would like to take one in the future.
• 64% of women globally and 69% of US women have taken a career break.
• About 1 in 5 hiring managers said they'd outright reject candidates with a career break, but nearly half said they view candidates with breaks as an untapped talent pool.

Translated into plain terms: if you're worried that every hiring manager will discard your resume on sight, you're wrong about most of them. About one in five really will. The other four either don't care, or they specifically value the experience and perspective that comes with time away from a desk.

So: the gap is more common than you think, the stigma is shrinking, and the interview question is no longer "is this person fundamentally damaged" but "do they have a coherent story." Your job is to give them the story.

The one-sentence framework

Almost every gap-related question (in the interview, in the cover letter, on a phone screen) deserves the same shape of answer:

1. One sentence on what happened. Honest, specific, no melodrama.
2. One sentence on what you did with the time. Concrete and forward-pointing.
3. One sentence on why this role is the right next step. Pivot back to the conversation they want to be having.

That's it. 30-45 seconds total. The interviewer asked one question; don't answer five.

Here's the same shape applied to common situations.

Layoff: "I was part of a 15% reduction at my previous company in March. I used the months since to take a full-stack React course and ship two open-source contributions. I'm specifically looking for a frontend role at a product-led company, which is why this opening caught my attention."

Caregiving: "I stepped back to care for a parent through a health crisis. I freelanced part-time for two former clients to keep my skills sharp, and I'm now ready to return to a full-time role. The thing that drew me to this job is [specific reason]."

Burnout / mental health: "I burned out at the end of a particularly intense project and took six months to reset. During that time I did contract work, built a side project, and got clear on what I want next. That clarity is why I'm specifically interested in this role and not just any open role."

Failed startup: "I cofounded a company that didn't reach product-market fit. We wound it down at the end of last year. I've spent the months since consulting with two early-stage clients and codifying what I learned. I'm looking to bring that operating experience to a more established team, which is why this role appealed to me."

Travel / sabbatical: "I took a planned six-month break to travel after eight years of continuous work. I came back at the start of the year, did some freelance work to ramp back in, and I'm now looking for a full-time role with the kind of scope this one has."

The pattern: own it, point to something specific you did, pivot to why this role.

What to put on the resume

Your resume has to address the gap because dates make it visible. Trying to hide it with vague formatting reads worse than naming it.

If the gap is short (under 6 months): No special handling needed. Just leave the dates as they are. Most recruiters won't ask.

If the gap is 6-18 months: Add a one-line entry in your work history that names what you did during the gap. Examples:

Independent Consultant   |   Mar 2025 to Sep 2025
Project work for two former clients in marketing analytics. Built a dashboard
adopted as the team's primary reporting tool.

Career Break (Caregiving)   |   Jan 2025 to Aug 2025
Full-time caregiving for a family member through a medical recovery. Maintained
contributions to two open-source projects during this period.

LinkedIn's Career Break feature (introduced in 2022, now standard) lets you formally mark a break with a reason: caregiving, health, layoff, travel, full-time parenting, professional development, relocation, voluntary work, or career transition. Use it. The category itself signals you're not hiding anything.

If the gap is 18+ months: You need more than a one-liner. The gap entry should include 2-3 bullet points about what you did, what you learned, and what you produced. Even modest output (a course completed, a portfolio site shipped, a community group you led) reads better than blank space.

What not to do:

• Don't change your job dates to overlap or extend to "hide" the gap. Background checks catch this and it's a fireable offense if discovered post-hire.
• Don't use year-only date ranges (2024 - 2026) to obscure month-level gaps. Recruiters know that trick and it raises a flag.
• Don't list a fake "consulting" entry where you weren't actually consulting. If a hiring manager asks for client names and you can't produce any, you've torpedoed your own credibility.

Honest, specific, brief. That's the standard.

How to handle it in cover letters

Most cover letters don't need to address the gap at all. The hiring manager is reading the cover letter to learn whether you're motivated for this role; the gap question is for the interview.

The exception: if the gap is recent and a reasonable person would wonder about it (a 9-month gap visible at the top of your resume, for example), one short sentence in the cover letter pre-empts the awkward thought. Something like:

"After being laid off from [company] in March, I spent the past several months [doing X]. I'm now ready to return full-time, and this role caught my attention because [specific reason]."

That's it. One sentence, then move on.

What to do during the gap

This is the half of the question most candidates ignore until it's too late. The single biggest determinant of how easy your gap is to explain in an interview is what you actually did during it.

The framing for everything below: in 6-12 months, when an interviewer asks "what have you been doing during this time," you want a concrete answer that shows you're the kind of person who does things rather than waits for something to happen. The specific activity matters less than the fact that there's an answer.

Tier 1: Things that produce measurable output

These are the most powerful. Anything that produces an artifact (code, a writeup, a number, a working thing) gives you something to point to.

Freelance or contract work. Even one or two clients. The income matters less than the line on your resume and the answer to "have you been working." Platforms like Upwork, Toptal, and Contra are obvious starting points; reaching out to former colleagues for project work is often more productive.

Portfolio projects with measurable results. Not "I built a clone of Twitter," which everyone has. Something that addresses a real problem and produced a real outcome. "I built a tool that analyzes my city's open transit data, and the local transit authority adopted two of my findings" is a different conversation than "I made a personal website."

Open-source contributions. A handful of merged PRs to a real project beats a hundred personal repos with no users. For technical roles, this is high-signal practice and the activity itself maps to interview questions you'll actually be asked.

Writing or teaching. A blog with 10 substantive posts, a YouTube channel with a real audience, a course you taught at a community college. Something that demonstrates you can communicate and that other people found useful.

Tier 2: Credentials and structured learning

Useful, but only if the credential is actually used in your field.

Real certifications. AWS Solutions Architect, GCP Professional Data Engineer, CFA Levels (for finance), PMP (for project management), Google Project Management, Meta's professional certificates. Anything that hiring managers in your field actually recognize. Verify that the credential is a real signal in your industry before spending months on it.

University extension courses. Stanford's online courses, Berkeley extension programs, MIT's xPRO, Wharton Online, Imperial College's executive courses. Higher signal than free MOOCs, lower cost than a full degree.

Free MOOCs with completion credentials. Coursera and edX certifications are easy to mock if they're the only thing on your resume. They're useful in support of other concrete output, weaker as the headline of your gap year.

The trap: spending 6 months on certifications that aren't recognized in your target field. A "Cloud Computing Foundations" certificate from a low-credibility issuer is worse than nothing because it suggests you don't know what good signal looks like. Ask people in your target role which credentials they actually look at.

Tier 3: Activities that aren't on the resume but matter in interviews

These don't show up as line items. They still help.

Maintaining your network. Coffee chats, alumni group involvement, regular reach-outs to former colleagues. The mechanical reason: most jobs come through warm intros, and a warm intro shortcuts the gap question entirely.

Volunteer work with measurable impact. Not generic "volunteered at a nonprofit." Specific, quantifiable. "Built the Google Ads campaigns for [nonprofit] that generated 40% of their annual donor inflow."

Caregiving or other non-work commitments. These are valid and increasingly normal to name. The thing to avoid is treating them as a black box. "I was the primary caregiver for my mother through her cancer treatment, which involved managing her care team across four specialists and coordinating insurance escalations" is a real story with real skill content. Treat it that way.

Therapy, recovery, or rest. Real things, and named appropriately, they're not disqualifying. Most candidates don't volunteer this in interviews and they don't need to. A simple "I took time to reset" is enough; you don't owe the interviewer a clinical breakdown.

What not to do during a gap

A few patterns that make the gap harder to explain, not easier:

• Applying constantly without any other activity. "I've been job searching for 14 months" is the worst possible answer to "what have you been doing." Job search isn't an activity; it's the absence of one.
• Starting and abandoning many things. Three half-built portfolio projects with no users is worse than one completed project with results. Pick something, finish it, point to it.
• Studying without producing. "I took 8 courses on machine learning" with no project to demonstrate it lands as ungrounded learning. Pair every course with output.
• Going silent on LinkedIn. Recruiters look at activity. A profile that hasn't been touched in 18 months reads as stalled. Even occasional posts about what you're learning or building are useful signal.

Practicing the answer

Once you've got the story, practice it out loud. Most candidates have a great answer in their head and a meandering 90-second answer in their mouth. The gap isn't where you want to find that out.

A few mechanics:

• Read your answer aloud at conversational pace. Time it. Aim for 30-45 seconds.
• Record yourself answering "tell me about the gap." Watch the recording. Notice where you trail off, hedge, or over-explain.
• Practice with someone who'll push back. The follow-up question (the one after your prepared answer) is where most gap conversations actually go sideways.
• If you don't have someone to practice with, an AI mock interview tool that does voice-based practice can simulate the back-and-forth and give you feedback on pace and structure. The first time you say the gap answer out loud should not be in the real interview.

If you want a structured warm-up before any interview, our solo practice guide walks through a 30-minute session you can use to rehearse this kind of answer alongside the rest of your prep.

A note on tone

The single biggest factor in how a gap conversation lands is your own posture. If you treat the gap like a stain you have to apologize for, the interviewer will treat it the same way. If you treat it like a normal chapter of a normal career, with a clear reason and a clear thing you did during it, the conversation moves on within a minute.

The gap is fact. The story is yours. Both can be true.

Related reading

• How to navigate a layoff in 2026 covers the broader playbook if your gap started with a layoff and you're still in the early weeks.
• Career change interview tips is useful if your gap is also a pivot point into a new field.
• STAR method interview guide gives you the structure for answering follow-up questions about what you actually did during the gap.
• How to prepare for behavioral interviews walks through the story-banking process for the rest of the behavioral round.

Statistics in this post are sourced from BLS Employment Situation data for April 2026 and a 2022 LinkedIn global survey of approximately 23,000 workers and 7,000+ hiring managers (published in connection with LinkedIn's Career Break feature launch). Verify current figures on the original sources before citing.