Your First 90 Days in a Tech Job: A Survival and Growth Guide

Why the first 90 days matter

You have worked hard to get the job. The first three months set your reputation, your learning speed and how people see you. You are not expected to know everything; you are expected to learn fast, communicate clearly and be reliable. Treat these 90 days as a structured experiment.

Before day one

• Confirm the joining details, documents and who to contact
• Review the company's products and recent news
• Refresh the main language and tools from the job description (language guides)
• Prepare a short introduction about yourself for colleagues
• Plan travel or your remote setup so the first day is calm

Days 1–30: learn and listen

Goals: understand the company, the team, the product and how work gets done.

• Meet people. Introduce yourself to teammates, ask what they work on, and set up one-to-ones with your manager, buddy or mentor.
• Set up your environment: accounts, repositories, local setup, documentation. Write down every step; you will probably improve the onboarding guide for the next person.
• Learn the process: how tasks are assigned, how code is reviewed and released, how incidents are handled, which meetings matter.
• Read: architecture docs, code in your area, recent pull requests and the issue tracker.
• Clarify expectations with your manager: What does success look like at 30, 60 and 90 days? How do they prefer updates?
• Do a small first task: a bug fix or small feature, to understand the full path from code to production.

Days 31–60: contribute and take ownership

Goals: deliver real work and become dependable.

• Pick up well-defined tasks and finish them completely: code, tests, documentation and follow-up
• Ask good questions. Try for 15–20 minutes first, then ask clearly: what you want, what you tried, what you think the cause is.
• Communicate early when something slips. Surprises are the problem, not delays.
• Learn from code reviews. Read feedback as free teaching, apply it and avoid repeating the same comments.
• Start understanding why decisions were made, not only what the code does
• Write things down: your notes, learnings, runbooks and decisions

Days 61–90: grow your impact

Goals: work more independently and begin to improve things.

• Take on a slightly larger task and own it from design to release
• Suggest one improvement: a script that saves time, better documentation, a missing test or a small refactor
• Help others: answer a question, review a colleague's code, share what you learned
• Have a 90-day check-in with your manager: ask for feedback and set the next goals
• Start thinking about your longer-term growth: which skills to build and what you want to own

Working well with your manager

• Share a short weekly update: what you did, what is next, what is blocking you
• Ask for feedback often, and ask for specifics ("What is one thing I could do better in code reviews?")
• Raise problems with options, not only complaints
• Respect priorities; if you are overloaded, say so early and ask which task matters most

Habits that compound

• Be curious. Understand the product, users and business as well as the code.
• Keep a work log so you can recall impact for appraisals and your future resume (impact-focused resume).
• Test and review your own work before others do.
• Communicate clearly and kindly, especially in writing.
• Look after yourself. Sleep, breaks and boundaries matter; burnout starts early.
• Keep learning, even if work is slow at first. Use the extra time for fundamentals (core CS) and side projects.

Common mistakes

• Staying silent when stuck for hours
• Pretending to know something you do not
• Skipping documentation and tests
• Comparing yourself with senior engineers
• Ignoring relationships; people help those they know and trust
• Sharing company confidential information outside work

If things go wrong

Not every first job is a good fit. If you face unclear expectations, no mentoring or a harmful environment, document the issues, talk to your manager or HR and, if needed, plan a move while you keep learning. A short stint is not a disaster; many people change jobs within the first two years (switch plan).

What next

Keep growing with upskilling guidance for engineers and learn to use AI tools well. If you are still searching for that first role, see our fresher jobs.