Your resume shows a gap between roles — walk me through what you were doing during it.
answer
- name the gap plainly, no flinch
- one sentence on the reason
- what the months were spent on
- one concrete artifact from the period
- close forward: what you chose next
basics
~10 sProbes honesty and whether the time off left you rusty. Name the gap plainly in one sentence, say what the months were actually spent on, and close on why you are ready now.
how to answer
5 beats- state the dates and the reason in one sentenceGive the length and the cause in a single unhurried sentence, using the same words you would use to state any other fact. This should take ten to fifteen percent of your airtime, no more — a long preamble signals that you think it is a problem.
- say what the months were actually spent onThis is the bulk of the answer, roughly sixty percent. Describe the shape you gave the time: contract work, study, caregiving alongside a side project, a deliberate reset. Concrete and ordinary beats impressive and vague.
- point at one artifact with edgesName one thing that exists — something you shipped, a client you billed, a course you finished, a measurable improvement you made for someone. One artifact told with a number lands harder than four listed technologies.
- name what you screened for when you came backSay what you deliberately did or did not accept during the search. This converts the gap from lost time into a filter that produced a choice, and it sets up the motivation close.
- close on why this role, nowEnd forward-facing: connect the criteria you just named to something concrete about this team or product. Keep the last twenty percent of your airtime for this rather than trailing off after the explanation.
your answer
5 story prompts- Draft the one-sentence version of your gap, dates included, that you can say in under ten seconds.
- Pick the two most job-relevant things you did during the gap and cut the rest from the answer.
- Find one artifact from that period — a contract, a course, a repo — you can name concretely.
- Write down what you screened for when you started searching again; that becomes your close.
- This can reuse material from your why-you-left answer, re-angled onto the months in between.
draft and rehearse your own answer in a learn session
go deeper
A gap is a cheap probe of honesty and risk, not a judgement on your life. The interviewer wants to see whether you volunteer inconvenient facts under mild pressure, whether the time away cost you currency in the craft, and whether your return was deliberate. A strong answer treats the gap as one plain fact inside a coherent motivation story.
There is a five-month gap between my last two roles, and the reason is simple: the agency I worked at lost its largest retainer and cut the backend pod I was on, nine of us in one afternoon. The first three weeks I applied to everything and got scattered, so I gave the time a shape. Mornings went to interview prep and one algorithms course I actually finished. Afternoons went to a small contract for a two-person studio rebuilding their booking API, and that is where I first had to care about cold-start time. Their first request after an idle period took about 2.4 seconds, and people were dropping off the confirmation screen. I pulled the client setup out of the request handler and warmed the connection pool at boot, and the first call came down to roughly 680 milliseconds. That contract ran eleven weeks part-time, which is why the dates read as a gap rather than a job. The second half of the gap I was picky on purpose. The first agency I interviewed with was almost a copy of the one that had just cut us, and I turned it down because I wanted to own something past handover instead of cycling through retainers. That is the same thing I am looking for here, and it is why the platform role caught my attention rather than the delivery one.
The signal is in the shape given to the time and the one artifact with a number, not in the layoff. Naming the reason in a single sentence and closing on a criterion he applied during the search does the work. It would downlevel if the contract were described vaguely, with no before-and-after and no reason for the choice that followed.
I have a ten-month gap two roles back, and I put the reason on the resume line so nobody has to guess: a parent was in treatment and I was the one who could be there. I gave notice properly. I was running the platform side of an agency account at the time, and I spent my last six weeks writing the runbooks and splitting the pager between two engineers rather than one, because the account had been routing through me and I did not want to leave that behind. During the break I kept one day a week advising a former client on their queue setup — it was not employment and I do not list it as such. Coming back I was deliberate about the kind of place. I had spent four years optimising for billable hours and I wanted to own a system past launch, so I filtered for in-house platform work. The first thing I picked up in my current role was the cold-start problem nobody had time for: the internal reporting API sat around 3.1 seconds on a cold hit and was timing out on Monday-morning traffic. Lazy-loading the report templates and holding one warm instance took it to about 480 milliseconds, and the Monday alerts stopped. The gap is a fact about one year. The pattern on either side of it is eight years of the same platform work.
Mid-level weight comes from the handover — pager split, runbooks written — and from naming a filter that produced the next role. The personal reason stays at one sentence; share only the detail you are comfortable with, since expectations vary by country and employer. Vagueness about the exit, or no work shown after the return, would downlevel it.
Early on, this is mostly honesty and momentum. Name the gap, point at one thing you built, studied or shipped, and stop — nobody expects a portfolio out of a few months off.
By mid-level the worry is whether the gap broke your trajectory. Show that the work either side is continuous in kind, and that you left cleanly rather than mid-commitment.
Senior candidates are judged on what they left behind: handover, on-call coverage, who took ownership. The break itself is fine; a team left exposed is the part that reads badly.
At principal scope the question touches organisational continuity — what kept running without you, who you grew to cover it, and whether your return is a deliberate choice about the kind of org you now join.
saying these in an interview costs you the question
- Hedging the dates so the gap sounds longer and murkier than it was
- Spending two minutes on a personal reason that needed one sentence
- Inventing consulting work to paper over the months
- Blaming the market, a layoff, or a former manager for the whole period
- Offering no evidence of staying current beyond 'I was applying'
- Apologising, as if the gap disqualifies you before they said it did
- How did you keep your skills current during that time?Name one or two concrete things with edges — a paid contract, a course you finished, a system you rebuilt — and say what it changed in how you work. Avoid listing passive consumption. If you genuinely did little technical work, say so briefly and pivot to how fast you ramped once you returned, with evidence.
- Were you interviewing that whole period, or did you start later?Answer with the real shape of it. A deliberate pause followed by a focused search is a stronger story than a vague claim of constant searching. If the search was slow, own one reason without self-pity, and show what you tightened in your criteria as it went on.
- Would you take a break like that again under the same circumstances?Say yes if the reason was outside your control or genuinely worth it, and mean it — hedging here reads as shame. Then add what you would do differently in the mechanics: earlier notice, a cleaner handover, keeping one professional thread alive. Do not promise never to have a life event again.
## The prompt family This one arrives in several wordings and they all want the same thing: - *What were you doing between these two roles?* - *Are you working at the moment?* - *I notice a break here, can you fill that in for me?* - *Is there anything on your resume you would like to explain before we start?* The last is the friendliest version and the most commonly fumbled, because candidates hear an invitation to confess. It is not. It is an invitation to **state a fact and move on**. ## What is actually being priced Interviewers are not moral auditors of your calendar. They are pricing two risks. 1. First, **skill decay**: if you have been out of the codebase for a while, does your first quarter cost more than a candidate who never stopped? 2. Second, **honesty under mild pressure** — the gap question is a cheap probe of whether you volunteer inconvenient facts or make the interviewer dig for them. A candidate who names the dates before being asked has already answered the second risk. That is why **proactive framing** works so well: mentioning the break yourself, in one clause, during your opening narrative removes it as a discovery. ## Structure, and the airtime split - The **reason** deserves one sentence, roughly ten to fifteen percent of your airtime. - **What you did with the time** is the bulk. - The **close** — what you screened for when you started looking again, and why this role fits it — carries the motivation signal and should not be tacked on as an afterthought. The failure mode is inverted: ninety seconds of explanation, five seconds of substance. ## Evidence types, strongest to weakest - Paid work of any size beats unpaid; - unpaid but shipped beats unpaid and unfinished; - finished study beats started study; - and anything with a number, a user, or a person who can vouch for it beats a list of technologies you read about. One well-told artifact outperforms four vague ones. If the period genuinely held no technical work — caregiving, illness, immigration limbo, a move — do not fabricate one. Say what the period was for, then show currency from the work on either side of it, and let the ramp-up speed you demonstrated on returning carry the weight. ## Personal reasons and how much to say You generally owe an interviewer **the shape of a gap, not its contents**. Health, family and legal matters can be given at the altitude you are comfortable with — a family member needed care, I dealt with a health matter that is resolved — and in many places questions that push past that are outside what an interviewer should be asking. Norms differ by country and by employer, so decide your own line before the interview rather than in the room, and rehearse the one-sentence version so a probe does not knock you into over-sharing. ## How the bar shifts - **Early career**, a gap is background noise and the whole game is showing momentum. - **Mid-career**, the question becomes continuity of craft. - At **senior level**, the interviewer quietly checks whether you left a team covered — handover and succession are the substance, not the dates. - And at the **top of the ladder**, the gap is read as a strategic choice: what you stepped away from and what that says about what you will attach yourself to next.