# Returning to Tech After Travel or a Sabbatical: Telling the Story Source: https://www.techinterview.org/post/3233475374/returning-tech-after-travel-sabbatical-telling-the-story/ Updated: 2026-07-12 · techinterview.org The 9–18-month sabbatical or travel break is a particular kind of career gap. Unlike caregiving or layoff returns, the engineer chose this break and usually had a positive experience. The challenge is telling the story without sounding like a "vacation hire" or, conversely, a burned-out cautionary tale. This guide is for the engineer planning that return. ## What recruiters and hiring managers actually wonder - Are you actually ready to work again, or coasting on savings? - Did you keep up with the field at all? - Will you do it again in two years? - Is this a recovery from burnout that might recur? Framing that addresses each of these without you being asked works in your favor. ## The resume framing - One line: "Personal sabbatical / extended travel (Mar 2024 – Aug 2025)" - Optional: a brief description ("traveled across SE Asia and Europe; learned X") - If you did anything technical or related to the field, list it: courses, OSS contributions, side projects, blog - Do not pad the gap with fake roles or vague "consulting" if it was actual time off ## The interview narrative A clean version of the story: > "I had been at [previous company] for [X] years and we had just shipped [Y]. I had savings and a window before [life change]. I took 14 months to travel through [places], learn [language], and reset. I started picking the technical thread back up around the 9-month mark — built a small project to relearn the stack, contributed to an open-source library I had used. I am back and ready for the next role." This narrative does the work: deliberate decision, calibrated about return, evidence of currency, and a clear forward intent. ## Common framings to avoid - "I needed to find myself": vague, raises burnout flag - "I never wanted to work in tech anyway": said as a joke; received as concerning - "It was just a long vacation": minimizes; reads as not-serious-now - "I was completely off the grid": raises currency concerns ## What to do during the last 3 months of your break - Build one substantive project using current tools (AI-assisted coding, modern framework) - Read 5–10 industry trend articles to recover narrative fluency - Reconnect with 2–3 former colleagues over coffee or a video chat - Update your LinkedIn / GitHub with current activity - Take one paid course or paper-club commitment that ends with a portfolio artifact ## The "did you keep current" probe Hiring managers often ask: "What changed in our field while you were away?" Be ready with: - Two or three concrete shifts (e.g., "AI coding assistants moved from novelty to default", "edge compute matured", "your-domain-specific change") - One specific opinion ("I think the biggest shift was X because Y") - What you did to catch up The candidate who can name shifts beats the candidate who is vague. ## Negotiation considerations - Do not let the gap discount your comp expectations more than 5–10% - Use your previous level as the anchor, not "entry-level + experience" - Be ready for a slightly tighter take-home or screen, since you may have rust - If asked for current salary: there is none; share expectations based on previous + market ## The "will you do it again" question Asked sometimes, often left unspoken. Anticipate it: - "This was a one-time decision, made possible by [savings + life stage]; I am committed to the next 4–5 years of focused work" - "I do plan to take a similar break in 5–10 years; I am happy to be transparent about that with employers I am committing to" - Being upfront wins; do not promise "never again" if it is not true ## What to look for in the next role - A team with a calmer cadence, since you may have lost some "always on" muscle - A manager who values long-term contribution over hero work - A culture that does not punish boundaries - A team that has hired returnees before is a strong signal ## Currency-rebuilding plan in the role - First 30 days: focus on the codebase and team conventions - First 60 days: ship a small visible thing - First 90 days: contribute to a design discussion meaningfully - Resist the urge to over-perform to "earn" the role ## The interview-confidence rebuild Many returnees feel rust in early interviews. Strategies: - Schedule low-stakes interviews first (companies you would not pick) - Mock interview with a former colleague - Pace yourself, keeping to 2–3 active processes max during the first month - Treat early rejection as data, not a verdict ## Frequently Asked Questions ### Should I be open about the burnout if it was burnout? Frame it as "I needed a meaningful break and used the time well." Do not litigate the previous role's pace. Most hiring managers have seen burnout in themselves or peers; being straightforward wins. ### Will companies hold the gap against me? Some will; many no longer do post-COVID. Avoid the few that do; you would not enjoy them anyway. Most senior engineering hiring is friendly to deliberate breaks. ### How long is too long? Under 18 months: rarely an issue. 18–36 months: more questions, manage with currency-evidence. Over 3 years: treat as a returnship-style return; see the broader returnship guide on this site.