- Your first goal is to learn the codebase, the team and how work gets shipped.
- Ask good questions early — after trying for a reasonable time on your own.
- Small, reliable contributions build trust faster than one big heroic change.
Days 1–30: learn and set up
Nobody expects you to be productive immediately. Focus on understanding.
- Get your development environment running and document any steps that were missing
- Read the main parts of the codebase and draw a simple diagram of how it fits together
- Learn the team's workflow: tickets, branches, code review, testing and releases
- Ship one small fix or improvement, even a documentation change
How to ask good questions in your first software developer job
Seniors are happy to help juniors who have tried first. A useful pattern: what you are trying to do, what you have tried, what you expected and what happened. Time-box your struggle — 30 to 60 minutes is often a good guide before asking — so you neither give up too fast nor stay stuck for days.
Days 31–60: contribute reliably
- Take on small tickets end to end, including tests
- Respond to code review feedback quickly and without defensiveness
- Keep notes of what you learn — they become your personal documentation
- Start understanding the business: who the users are and what matters to them
Days 61–90: grow ownership
- Own a small feature or area of the code
- Improve something nobody asked for but everyone benefits from: a test, a script, documentation
- Ask your manager for feedback and agree goals for the next quarter
- Help the next new joiner with what you learned
Habits that build trust
- Communicate early when something will be late
- Write clear pull request descriptions
- Test your own work before asking for review
- Admit mistakes quickly and explain the fix
Common first-job mistakes
- Staying silent when stuck for days
- Rewriting large parts of the system to match your preferences
- Ignoring tests and code review comments
- Comparing yourself to seniors instead of to who you were last month
Frequently asked questions
What if I feel I know nothing?
That feeling is normal. Every developer feels it in a new codebase. Focus on steady progress and keep notes.
Should I work extra hours to prove myself?
Occasional extra effort is fine, but sustainable habits and clear communication matter more than long hours.
How do I get good feedback?
Ask specific questions, such as what one thing would make your pull requests easier to review, and act on the answers.
Written by Mubashar Hussain · Founder, TechCareerWay
Engineering leader with 20 years building banking and fintech software across 7 countries. Spotted an error or outdated advice? Tell us.