Starting a new developer job is terrifying. You feel like everyone knows more than you. Impostor syndrome hits hard. Here's how to not just survive but thrive in your first 90 days.
Days 1-30: Learn and Listen
Week 1: Setup and Observe
- Set up your development environment
- Read the team's documentation (all of it)
- Understand the deployment process
- Meet everyone on your team (coffee chats)
Week 2-3: Small Wins
- Pick up small bugs or tasks
- Ask questions (seriously, ask everything)
- Start a personal notes document
- Learn the codebase by reading, not just coding
Week 4: First Contribution
- Ship your first meaningful PR
- Present it briefly in standup
- Ask for feedback proactively
Key mindset: You're not expected to be productive yet. You're expected to learn.
Days 31-60: Build Momentum
Start Contributing Regularly
- Take on medium-sized tasks
- Pair program with senior developers
- Start understanding the architecture
- Contribute to code reviews (even as a learner)
Build Relationships
- Find a mentor (formal or informal)
- Help other new joiners if any
- Participate actively in team discussions
- Share interesting articles or tools you find
Document Everything
- Write down processes that aren't documented
- Create guides for things you struggled with
- This helps you AND future team members
Key mindset: Focus on consistency, not heroics.
Days 61-90: Own Your Space
Take Ownership
- Volunteer for a feature or project area
- Start proposing small improvements
- Write your first technical design doc
- Present a learning to the team
Set Goals
- Discuss expectations with your manager
- Set 3-month goals together
- Identify skill gaps to work on
- Plan your growth trajectory
Avoid Common Traps
- Don't try to refactor everything on day one
- Don't work 12-hour days to prove yourself
- Don't stay silent when you're stuck
- Don't compare yourself to people with 5+ years experience
The Questions You Should Be Asking
Week 1: "How does X work?" (understanding the system)
Month 1: "Why was X built this way?" (understanding decisions)
Month 2: "What if we tried X instead?" (contributing ideas)
Month 3: "I'd like to own X" (taking initiative)
Signs You're Doing Well
- Team members come to you for help on areas you know
- Your PRs need fewer revision rounds
- You can explain the system to newer people
- You feel less anxious and more curious
Signs You Need Help
- You're stuck for more than 2 hours without asking anyone
- You feel overwhelmed every single day after month 2
- You don't understand what success looks like in your role
- You're working nights/weekends regularly
If any of these apply, talk to your manager. That's what they're there for.
The Secret
Nobody expects perfection from a new developer. They expect:
- Curiosity
- Effort
- Communication
- Growth over time
Do these four things and you'll be fine.
I created a First 90 Days Survival Guide with day-by-day checklists, conversation scripts, and goal-setting templates. Daily developer tips on Telegram.
Top comments (0)