Getting hired after a career break is the harder problem. Once the offer letter is signed, your next job is to ramp up effectively and rebuild credibility. Strong returnees use the first 90 days to build relationships, identify wins, and pace themselves. Weak returnees burn out trying to prove they belong.
The first 30 days: orient and observe
Goals:
- Understand the team’s mission, structure, and current priorities
- Learn the codebase well enough to read a PR fluently
- Build relationships with your immediate team
- Understand the company’s rituals (standups, sprint planning, retros)
Concrete actions:
- 1:1 with every direct teammate in week 1
- 1:1 with PM, designer, adjacent engineers in week 2
- Pair-program with 2–3 different teammates to learn the codebase
- Read the past 90 days of design docs and post-mortems
- Identify the team’s most-cited internal tools, libraries, and conventions
The 30-day question: am I ramping at the right pace?
Ask your manager directly at week 4: “How am I tracking compared to your expectations? Anything you would like me to do differently?”
Their answer calibrates the next 60 days. Most managers will say “you are doing great, take your time.” Take that at face value but verify by asking again at week 8.
The first 60 days: small contributions
By week 5–6, start shipping:
- Tackle small bugs to learn the codebase
- Write the documentation no one else wants to write
- Improve onboarding docs for the next person
- Pick up an unowned but important task
Avoid: large projects in the first 60 days. The risk of getting stuck without enough context is high.
The 90-day milestone
By day 90, you should have:
- Shipped at least 2–3 visible features or fixes
- Written at least one design doc or technical writeup
- Built relationships with key collaborators
- Internalized the team’s code review and shipping rhythm
Things to ask early — even if it feels embarrassing
- “Why do we do X this way?” — context matters
- “Who should I ask about Y?” — builds your map of the org
- “What is the long-term direction of this codebase?” — strategy matters
- “What are the best resources for learning Z?” — accelerates ramp-up
Things to be wary of
- Promising too much in your first month — credibility costs more to repair than to build
- Pretending to know something you do not — almost always discovered
- Becoming the person who only fixes bugs — get on actual feature work
- Working long hours to prove yourself — bad signal, bad pattern
Building credibility deliberately
Credibility comes from a chain of small wins, not from one big project. Each PR you ship, each comment you write, each meeting you contribute to, accrues.
Specific levers:
- Code review: high-quality reviews that catch real issues — visible early.
- Documentation: writeups that help others — visible across the team.
- Technical clarity: in design discussions, summarize tradeoffs cleanly.
- Reliability: show up to commitments, deliver on promises.
The 90-day check-in conversation
At day 90, request a 1:1 with your manager:
- “How am I tracking against the original expectations for this role?”
- “What should I focus on for the next 90 days?”
- “Is there feedback I have not received that I should know?”
Mid-cycle calibration is much better than waiting for review season.
Pacing for the long term
Returnees often over-work in the first 90 days from anxiety. Then crash at month 4. Avoid:
- Take real weekends
- Take vacation in months 4–6
- Establish working hours and stick to them
- Ask for more responsibility only after you have absorbed the current load
Frequently Asked Questions
What if my team thinks I am too slow at ramp-up?
Address it directly with your manager. Most will give you appropriate runway. If not, the bar may be unreasonable — talk to peers who returned to gauge.
How do I network internally as a returnee?
Same as anyone new — coffee chats, joining ERGs (especially returnee or parent-focused ones), and contributing visibly in cross-team initiatives.
When can I start interviewing for promotion?
Most returnees focus on fit and stability for the first year. Promotion conversations naturally start at the 12–18-month mark.