You’re starting again.
Not from nothing.
You bring something with you: what you've learned, what you've tried, and what you care about. Choose the starting point that feels closest. These are suggestions, not deadlines.
Turn learning into evidence.
You have been learning. Now make it easier for someone to see what you can do.
Choose a direction
Pick one kind of role to explore. Read a few job descriptions and separate recurring fundamentals from the long wish lists.
Finish one useful thing
Choose a small problem you understand. Build a working version, explain your choices, and make it easy for someone else to try.
Practise showing your work
Write a short project story: the problem, your contribution, the trade-offs, and what you would improve. Ask a peer to review it.
Your experience came with you.
Losing a role does not erase the problems you solved or the things you learned.
Take stock of your work
List three problems you helped solve. Describe your contribution and the outcome without sharing confidential information.
Choose a manageable rhythm
Set aside realistic time for applications, conversations, and one small project. Leave room for rest and responsibilities.
Make your experience visible
Refresh one case study or portfolio entry. Reconnect with people who know your work and be specific about the roles you are seeking.
Reconnect at your own pace.
You do not have to relearn everything before taking a first step back.
Start with what is familiar
Revisit a language or project you know. Notice which skills return quickly and where you need a refresher.
Refresh through a small build
Use the current documentation to get one small application running. Keep a note of what has changed rather than chasing every new tool.
Prepare your introduction
Summarise your earlier experience, what you are learning now, and the work you want next. Share only as much about your break as you want.
Make your experience travel.
Years in one company can build deep skills. Translate them for your next chapter.
Translate the internal language
Describe your work without company-specific titles or systems. Show the engineering decisions, collaboration, and outcomes behind it.
Find the actual gaps
Compare a few target roles with what you already know. Choose one recurring gap to explore rather than starting your education over.
Practise outside your familiar setting
Build a small independent project or discuss a design with a peer. Practise explaining decisions to someone without your company context.
You can take the next step with others.
We’re bringing together developers who want to learn, build, and support one another. Explore what that means before deciding whether it is for you.
Explore the community →