What the interviewer is worried about
Not the gap. The interviewer's concern is forward-looking and narrow: is there a pattern here that will repeat on my team, and is there something you are not telling me. A single gap or one short role answers both concerns as soon as it is explained, which is why the explanation is short work. Three short roles in a row is a different conversation, because now there is a pattern and you have to say what you have changed.
It helps to know that the recruiter has read a lot of CVs and that gaps are ordinary. Redundancies happen in waves, visas lapse, parents get ill, children arrive, people burn out, start-ups run out of money, and some people take a deliberate break because they could afford one. None of that is remarkable to someone who screens for a living. What is remarkable, and what gets remembered, is a candidate who becomes visibly uncomfortable, because discomfort suggests there is more.
The shape of the answer
Three beats, and then silence. Beat one is the fact, with the dates matching what is written on the page. Beat two is what you did with the period, or in the case of a short tenure, what you understood by the end of it. Beat three, only if it is true, is a forward statement about what you are looking for now. Twenty to forty seconds in total.
For a gap the second beat matters more than people expect, and it does not have to be impressive. Studying, contract work, caring for someone, recovering, or simply looking for the right role in a bad market are all complete answers. "I did nothing for four months, deliberately, and came back to it in January" is fine if said evenly. What reads badly is inflation — describing three weeks of a tutorial series as a period of intensive upskilling — because the follow-up question about what you built has an obvious answer and it is not the one you implied.
For a short tenure, the second beat is a diagnosis rather than an activity. Something was different from what was described, or the fit was wrong, and you concluded that early rather than sitting there for three years. The distinction the interviewer is listening for is whether you can name your own part in it. "The role turned out to be maintenance on a system being retired, which was not what the job description said, and I should have asked harder questions about the roadmap before accepting" is a strong answer precisely because of the second clause. It shows you learned something transferable and it makes you a better candidate for this role, since you are now the person who asks about the roadmap.
Sample phrasings
GAP (redundancy):
"My team was cut in March last year - the whole product line went.
I spent about five months looking, took a short contract in
September to keep working, and I have been focused on backend
roles since."
GAP (personal):
"I took eight months out for a family health situation that needed
me. That ,
."
:
" , .
'
. ,
,
."
:
" ,
.
. ;
."
Each of these is deliberately unadorned. Read them out loud and notice how quickly they end — that ending is the technique.
Apologising and over-explaining
Two failure modes sit either side of the right answer, and they are the same mistake in different directions.
Apologising sounds like "unfortunately", "I know it looks bad", "I am sorry to say". It offers the interviewer a judgement they had not yet made and invites them to accept it. Nobody had decided the gap was a problem until you framed it as one. The same content delivered as a plain fact is simply information, and information gets ticked off.
Over-explaining is the more common failure and it is worse. The instinct after answering is to add support, so a twenty-second answer becomes ninety seconds of context about the reorganisation, the new VP, the two colleagues who also left, the project that was cancelled. Every added sentence signals that you do not think the previous one was believed, and the interviewer's read shifts from fine, next question to why is this still going. Length is the tell. There is a good reason it happens — silence after a difficult answer feels like disapproval, and the reflex is to fill it — but the person opposite you is usually just writing a note.
There is a related trap in blaming, particularly on short tenures. Some short tenures genuinely are the employer's fault: the role was misrepresented, the funding vanished, the manager was impossible. You are still not helped by saying so at length, because a story in which you had no part gives the interviewer nothing to be reassured by. If the mismatch was entirely external, you can still own the detection: what you would ask before accepting next time.
The career change is not a gap
Candidates changing field often present it apologetically, as though the years before the change were lost. Panels do not read it that way. Someone who has worked in insurance, logistics, teaching or accounting and then moved into engineering brings domain knowledge that teams routinely lack and pay consultants for, plus the ordinary professional competence of having held a job with real consequences. The framing that works is continuity: name the thing from the old field you still use, and the thing that genuinely changed. What fails is presenting yourself as a beginner, because the interviewer then has to argue you back up to your own level, and they will not bother.
One practical note on dates. Whatever you say must match the CV exactly, because a recruiter with your CV open will notice a year that has moved, and a discrepancy discovered at the background-check stage is far more damaging than any gap. If your CV shows months, keep months; if it shows years only, expect to be asked for the months.
The gap is not the risk. An answer that runs three times longer than the question needed is the risk, because length is what tells the interviewer there is something to find.
© 2026 Preptima. Originally published at preptima.com (opens in a new tab).