Why the first months feel so hard
Every new role combines three learning curves at once: the technology, the codebase and the people. Feeling slow in the first weeks is normal. What matters is a visible upward trend — and asking for help early instead of hiding gaps.
A 30/60/90-day plan
Days 1–30: learn and listen
- Set up your environment and ship one small change in week one.
- Map the system: services, data flows and who owns what.
- Agree on expectations with your manager in writing.
Days 31–60: contribute
- Own a well-scoped feature or bug area end to end.
- Write a short design note before larger changes.
- Learn the stack gaps that keep slowing you down.
Days 61–90: own
- Lead a piece of work and present it to the team.
- Improve something small in the team’s tooling or docs.
- Review progress against the expectations you agreed in month one.
How to get unstuck faster
- Timebox: try for 30–60 minutes, then ask.
- Ask well: what you are trying to do, what you tried and what you expected.
- Pair with a teammate and drive the keyboard yourself.
- Write down what you learned so you never ask twice.
Stay inside the rules
Never share your employer’s confidential code or data where your contract doesn’t allow it, and never let someone else do your work under your name. Besides being a breach of trust, it leaves you unable to do the job when it matters — and it is increasingly detected.
Frequently asked questions
Is it normal to feel behind in a new job?
Yes, especially with an unfamiliar stack. Track your progress weekly and talk about it openly with your manager.
How can a mentor help without seeing my employer’s code?
By working on concepts, sanitized examples, design reasoning and your own explanations — and by screen-sharing only where your employer allows it.
