How do I get back into software engineering after a long career break?

First, the gap is not the problem you think it is

When people write to me about returning after years away, the fear is almost always the same: that the gap disqualifies them. It does not. Hiring managers see career breaks for family, health, caring and relocation all the time. What they are actually checking is simpler: can this person do the work today, and will they be reliable?

You already have the hardest part. A software engineering degree gave you programming fundamentals, data structures, databases and a sense of how systems fit together. Those change slowly. What changed is the tooling: frameworks, cloud deployment, Git workflows and now AI-assisted coding. Tools can be refreshed in months. Foundations take years, and you have them.

So the job is not to "catch up on everything". It is to prove, in a small number of visible ways, that you can build and ship something now.

What has changed since you graduated

You do not need all of this at once. You need a narrow path through it.

Choose one direction for the return

Returners get stuck by trying to decide between web, mobile, data, AI and cloud before writing a line of code. Choose based on what is hireable and what fits your life, then commit for at least three months.

• Web development (JavaScript/TypeScript, React, Node or Next.js). The widest range of junior and mid roles, lots of remote and hybrid work, and the fastest feedback loop because you see what you build.
• Backend with Python. Good if you enjoyed logic and databases more than interfaces, and it opens the door to data work later.
• Quality engineering and test automation. An underrated re-entry point. It values carefulness and communication, and many engineers move from it into development.

If you are unsure, pick web development. It has the most learning material and the most openings, and the skills carry into almost everything else.

A realistic twenty-week return plan

This assumes roughly eight to ten focused hours a week, which is what most parents can actually protect. Move faster if you have more.

1. Weeks 1 to 4: rebuild the base. Modern JavaScript (or Python), Git and GitHub, the command line, HTTP and how the web works. Finish one structured course rather than sampling four. freeCodeCamp and The Odin Project are free and project based.
2. Weeks 5 to 8: your first real project. Something small that you or someone you know would use: a family meal planner, a school pickup rota, a budget tracker. Get it deployed with a public URL.
3. Weeks 9 to 12: the stack properly. React with TypeScript, a backend API, a real database, authentication. Rebuild your first project on this stack or start a second one.
4. Weeks 13 to 16: make it look like work. Write tests for the important parts, add a README that explains decisions, open pull requests against your own repo, and ask someone to review your code.
5. Weeks 17 to 20: apply while you polish. Update your CV and LinkedIn, start applying and reaching out, and keep one project moving so you always have something new to talk about.

A small amount of data structures practice (two or three problems a week) should run alongside from week 5, because many screening rounds still include it.

What your portfolio should contain

Three pieces of evidence are enough:

• One full-stack application with login, a database and a deployed URL.
• One project that solves a real problem for a real person, ideally something drawn from your own life. It gives you a genuine story in conversations.
• One sign of collaboration: a small open source contribution, a volunteer project for a local organisation, or code reviewed by another engineer.

Each project needs a clear README: what it does, why you built it, the stack, and one hard problem you solved.

How to explain the gap

Put it on your CV as its own honest line, for example "Career break, family (2017 to 2025)", followed by a section listing what you studied and built during your return. In conversation, one sentence is enough: "I took several years out to raise my family, and over the past months I have been rebuilding my skills; here is what I built." Then move on to the work. Do not apologise and do not over-explain.

Where to look for roles

• Returnship and returner programmes. A number of larger employers run paid programmes specifically for people coming back after a break. Search "returnship software engineer" for your country and check each company's careers page for current cycles.
• Companies that advertise flexibility. Look for explicit mentions of part-time, flexible hours or hybrid work in the listing rather than hoping to negotiate it later.
• Your old network. Classmates from your degree are now mid-level and senior engineers. A friendly message asking how their team hires is often the best route in.
• Junior and associate roles, without shame. Coming back at a slightly lower title for the first year is common, and the climb afterwards is usually quick.

Protecting balance from the start

Decide your non-negotiable weekly hours before you begin and schedule them like appointments. Early mornings or the hours after bedtime work for many parents. When you apply, filter for hybrid or remote roles and ask about working hours and on-call expectations in the first conversation, not after an offer.

If you are still stuck

The full version of this plan, with more on confidence and job applications, is in Returning to software engineering after a career break. Browse other answers in the career questions library, and if you want to talk through your own situation, book a free 1:1 session.