Ask HN: Taking Time Off?

I took about three years off to travel after ~12 months of working. It was very difficult to get back into the work force. Partially that was the economic environment. But probably the biggest issue was that I didn't really have the experience to be comfortably above entry level and for entry level roles companies preferred new grads.

That was a non-programming career though. For programmers that can pass a leet code style it's different. You probably could take a dump on a recruiter's desk and still get a job.

But, IMHO, it's wise to get 2-3 years of experience before taking significant time off. At that point you're solidly out of junior/entry level roles and into experienced hires.

I think under 25 you would be fine. But if you have significant work history, hard fact is some employers will ask, so long as you can explain I have never heard of a tech job where this was a deal-breaker but don't take mu word for it. It really depends on the hiring manager. I have been told I would be a bad fit because I didn't stay more than 3 years at a job by one employer, another told me I should be making a lot more money at my experience level, even though I continually progressed upwards. Their personality and work culture matters a lot.

If you have decent skills and apply at the typical YC company, I would be extremely surprised if they cared about you taking time off. But apply for a gov clearance requiring job or non-tech well established company, it's hit and miss.

An important question, now more than ever.

> This would probably involve separating with my current employer, and finding a new position at the end of the sabbatical.

Why do you assume that? You may find that your manager is entirely sympathetic to your burnout concern. An extended unpaid absence may also let some much-needed air out of the budget for the rest of the team.

Why not just tell your manager you're taking a sabbatical for psychological reasons? It's the truth, and everyone is going through it. They may be willing to save your spot for you.

> I would also keep my skills sharp, programming & collaborating with friends.

Depending on how long you've been coding, your skills won't go dull after 3-6 months. You'll be able to jump right in without issues. If you're going to take a sabbatical, actually take one.

I’m currently sitting on a plane to Madrid after quitting my job last week. I was in a similar boat as you.

Personally I’ve never believed in putting off your dreams until you’re least able to enjoy them - retirement. If you’re good at what you do, I highly recommend taking mini retirements every few years. There’s no better way to explore what’s important to you.

But let’s imagine the worst happens and the world plunges into a deep recessions while you’re on your sabbatical. Maybe someone steals your car too. You have a year of expenses saved up. This is huge. Could you take a job waiting tables for a time too? Enjoyable. No. End of the world. Absolutely not. Eventually you will find a tech job again.

This calculus completely changes if you have a family to look after but you sound like you’re young and single. I highly recommend the below thread asking a similar question.

https://news.ycombinator.com/item?id=27743368

I took two separate 1-yr breaks in my 20s, and I can't say it has had any negative impact career-wise (some might view fewer years of work experience as a negative, but strictly speaking it hasn't made getting other jobs more difficult for me). If you have a solid skill set / body of work to share and speak about, and great recommendations from previous co-workers then I would say do what feels right to you.