Picture this: It’s Monday morning. You badge into your new office (or log into your new company’s VPN) for the first time. Your laptop is fresh. Your Slack channels are empty. Everyone seems to know each other, and you’re the outsider trying to figure out where the documentation lives—assuming it exists.

The first 90 days at a new IT job are a strange mix of excitement and anxiety. You want to prove you were the right hire. You want to contribute immediately. And you desperately don’t want to be the person who breaks production in week two.

Here’s the reality: what you do in these first three months matters more than you think. It shapes how your team perceives you, how much trust you earn, and whether you set yourself up for growth or stagnation.

This isn’t about impressing people with flashy wins. It’s about laying a foundation that pays dividends for years.

Why the First 90 Days Matter So Much

New hires operate in a unique window. During this period, asking questions is expected. Admitting confusion is acceptable. Requesting explanations for “obvious” things doesn’t make you look incompetent—it makes you look thorough.

That window closes.

After roughly three months, you’re expected to know the basics. You’re expected to navigate systems independently. The tolerance for confusion drops sharply.

This means the first 90 days are your chance to learn everything you can while the social permission to ask “dumb questions” still exists.

Use it wisely.

Phase 1: Absorb (Days 1-30)

Your first month has one primary goal: understand the environment. Resist the urge to fix things immediately. You don’t know enough yet, and premature action creates problems.

Week 1: Survive and Orient

Focus: Basic survival

Your first week is about getting functional. Where’s the bathroom? How does the coffee machine work? What’s the WiFi password? These mundane details matter because you can’t focus on real work if you’re still figuring out logistics.

For IT specifically:

  • Get all your accounts and access provisioned
  • Set up your development environment or admin tools (if you’re new to IT, our help desk getting started guide covers the basics)
  • Learn the ticketing system—even if you’re not handling tickets yet, understand how work flows
  • Identify where documentation lives (Confluence, SharePoint, wiki, README files scattered across repos)
  • Map out who owns what systems

Don’t try to memorize everything. You’re building a mental map of where to find information, not the information itself.

Common mistake: Immediately diving into code or systems without understanding how they connect. Context matters more than details in week one.

Weeks 2-3: Learn the Landscape

Focus: Understanding systems and relationships

Now you start going deeper. But not too deep—broad understanding first.

Technical priorities:

  • Walk through the architecture. Ask someone to whiteboard the major systems and how they interact
  • Understand the monitoring and alerting setup—what gets monitored, who gets paged, what the response expectations are
  • Review recent incidents. Post-mortems tell you more about real system behavior than any documentation
  • Learn the deployment process. How does code go from development to production? If you’re in a DevOps role, our DevOps interview guide covers what you should already know

People priorities:

  • Identify the subject matter experts. Who’s the person everyone asks about networking? About the legacy billing system? About that ancient Perl script nobody dares touch?
  • Learn how to communicate with your specific team—Slack? Email? Formal tickets for everything?
  • Understand your manager’s expectations. What does “doing well” look like in their eyes?

Documentation priorities: Start building your own notes. The official documentation is probably incomplete or outdated. Your personal notes, written while everything is fresh, become invaluable later. Note:

  • How things actually work (vs how they’re supposed to)
  • Who to ask about what
  • Gotchas and workarounds nobody wrote down

Week 4: Start Contributing (Carefully)

Focus: Small wins with low risk

By week four, you should start doing actual work. But choose your battles carefully.

Good first contributions:

  • Fix a small, well-understood bug
  • Improve documentation you found lacking during onboarding
  • Automate a manual task you observed
  • Handle a straightforward ticket or request

Bad first contributions:

  • Refactoring that “terrible” code you found (you probably don’t understand why it’s written that way)
  • Proposing major architectural changes
  • Pointing out everything you think is wrong

The unspoken rule: Your first month is about building trust through reliability, not brilliance. Show up consistently. Follow through on small things. Be someone people can count on.

Phase 2: Engage (Days 31-60)

Month two is when you shift from observation to participation. You have enough context now to contribute meaningfully—but not enough to be overconfident.

Expand Your Scope

Start handling more complex work, but stay within guardrails.

Technical expansion:

  • Take on tickets or projects with more ambiguity
  • Participate in code reviews or change approvals
  • Shadow on-call rotations if your team has them (don’t take primary yet)
  • Learn the systems adjacent to your primary focus

Relationship expansion:

  • Build connections beyond your immediate team
  • Attend cross-functional meetings if appropriate
  • Start having 1:1s with teammates you work with regularly

Identify Patterns

You’ve seen enough now to notice patterns. What keeps coming up?

  • Are the same issues causing incidents repeatedly?
  • Is there documentation everyone ignores because it’s wrong?
  • Are there manual processes that could be automated?
  • Where does communication break down?

Write these observations down. Don’t act on them all immediately—but start building a list of improvement opportunities.

Find Your Niche

Every IT environment has gaps. Systems nobody wants to own. Tasks everyone avoids. Knowledge that only exists in one person’s head.

These gaps are opportunities.

Becoming the person who understands the unloved-but-critical system makes you valuable. It’s not glamorous work, but it’s the kind of work that builds job security and influence.

Look for:

  • Legacy systems that need ongoing maintenance
  • Integration points between teams
  • Areas that touch multiple teams, like security, compliance, or documentation
  • Processes that span multiple systems

Get Feedback Early

Don’t wait for your 90-day review to find out how you’re doing. Ask directly:

  • “What’s one thing I should do more of?”
  • “What’s one thing I should do less of?”
  • “Is there anything I’m missing that you expected me to know by now?”

Most managers appreciate proactive feedback-seeking. It shows self-awareness and a desire to improve.

If the feedback surprises you, that’s valuable information. Better to course-correct at day 45 than discover a problem at day 90. Consider finding an IT mentor who can provide ongoing guidance beyond what your manager offers.

Phase 3: Deliver (Days 61-90)

The final phase is about demonstrating value. You’ve learned the environment. You’ve built relationships. Now show that you can deliver results.

Own Something Meaningful

By month three, you should have ownership of something. This doesn’t mean running a major system solo—but you should have an area where you’re the go-to person.

This might be:

  • A specific application or service
  • A type of ticket or request
  • A recurring process or maintenance task
  • A documentation domain

Ownership means you’re responsible for outcomes, not just tasks. You notice problems before others do. You improve things without being asked. You think about the future, not just the present.

Complete a Visible Win

Before your 90 days end, aim for at least one contribution that others notice. Not to show off—but because visibility matters for your career trajectory.

A visible win could be:

  • Fixing a long-standing problem that annoyed the team
  • Shipping a feature or improvement users actually wanted
  • Building a tool that saves significant time
  • Creating documentation that becomes a team resource
  • Resolving a tricky incident effectively

The key word is “visible.” Great work that nobody knows about doesn’t build your reputation. Make sure the right people see what you’ve accomplished—through standups, retrospectives, or direct communication.

Solidify Relationships

Your first 90 days end, but your career continues. The relationships you built during this period are assets.

Before the honeymoon period ends:

  • Thank people who helped you onboard
  • Offer to help new hires who join after you
  • Set up regular 1:1s with colleagues you want to stay connected with
  • Give feedback to your manager about the onboarding experience (they’ll appreciate insights for the next hire)

Plan Your Next 90 Days

Don’t let momentum die at day 90. Before the official onboarding period ends, think about:

  • What skills do you want to develop?
  • What systems do you want to learn more deeply?
  • What certifications might be valuable?
  • What project would you like to take on?

Write these down. Share them with your manager. Having explicit growth goals shows initiative and gives your manager something to support.

The Mistakes That Sink New Hires

Look, none of this is rocket science. But it’s easy to mess up when you’re nervous about a new job and trying to prove yourself. These are the patterns that trip people up most often:

Mistake 1: Going Too Fast

The urge to prove yourself is strong. But rushing creates problems.

What it looks like:

  • Pushing changes without understanding the testing process
  • Proposing redesigns before understanding why things exist
  • Taking on too much and missing deadlines
  • Skipping documentation review to “just figure it out”

Why it hurts: Breaking something in your first month is recoverable. Building a reputation as someone who moves too fast and breaks things is harder to undo. This is one of the common IT interview mistakes that also applies once you’re hired.

Mistake 2: Going Too Slow

The opposite problem. Some new hires are so afraid of making mistakes that they barely contribute.

What it looks like:

  • Asking permission for everything, including trivial decisions
  • Refusing to commit to opinions or recommendations
  • Treating every task as requiring extensive review
  • Waiting to be assigned work instead of finding it

Why it hurts: You were hired to contribute. If you’re not contributing, people question whether the hire was right.

Mistake 3: Not Asking Questions

Staying silent when confused is common but costly.

What it looks like:

  • Spending hours stuck on something that a 5-minute conversation would solve
  • Making assumptions about how things work instead of confirming
  • Nodding along in meetings when you don’t understand
  • Delivering work that misses requirements because you didn’t ask

Why it hurts: The first months are when questions are expected. Later, your silence creates bigger problems when foundational misunderstandings compound.

Mistake 4: Being Negative

New environments often have obvious problems. The temptation to point them out is strong.

What it looks like:

  • Frequently saying “At my old job, we did it better”
  • Criticizing decisions made before you arrived
  • Dismissing current practices as stupid or inefficient
  • Focusing on what’s wrong rather than understanding why it’s that way

Why it hurts: Nobody likes a critic without context. And every environment has history you don’t know yet. That “stupid” decision might have solid reasoning behind it.

Mistake 5: Not Building Relationships

Some IT folks focus purely on technical contribution and neglect the human side.

What it looks like:

  • Eating lunch alone every day
  • Skipping optional team events
  • Only communicating through tickets and documentation
  • Not learning teammates’ names or backgrounds

Why it hurts: IT is a team sport. Technical skills get you hired; relationships determine your ceiling. The isolated contributor eventually hits walls that only human connections can break through. If networking feels awkward, check out our guide on building IT career connections.

Special Situations

Starting Remote

Remote onboarding adds friction. You miss the casual conversations, the overheard context, the organic relationship-building that happens in offices.

Compensate by:

  • Being more explicit about your status and progress
  • Over-communicating rather than under-communicating
  • Scheduling video calls instead of defaulting to async
  • Creating reasons to interact beyond strict work necessity
  • Finding virtual coffee chats or casual conversation opportunities

Remote work requires more intentional relationship-building. It won’t happen naturally. For more on navigating remote IT roles, see our remote work tips for IT professionals.

Starting at a Startup vs. Enterprise

The 90-day playbook varies by company size.

At startups:

  • Expect to contribute faster (there’s no time for extended learning)
  • Be ready for ambiguity and undefined processes
  • Your scope might expand rapidly based on company needs
  • Documentation is probably minimal—create it as you go

At enterprises:

  • Expect more structure and slower ramp-up
  • Navigating bureaucracy is part of the job
  • Understanding the organizational chart matters
  • Process matters more; following it correctly builds credibility
  • LinkedIn optimization matters more at larger companies where recruiters and hiring managers review profiles

Starting After a Career Change

If you’re transitioning from another field—say, coming from help desk to sysadmin or switching into IT from another industry—your first 90 days require extra attention.

Focus on:

  • Transferable skills. Your industry experience gives you perspective most IT folks lack
  • Gaps to fill quickly. Identify the technical basics you need to be functional
  • Learning from peers without being defensive about what you don’t know
  • Demonstrating your strengths from day one—problem-solving, communication, domain expertise

Don’t hide your background. Use it as an advantage while actively filling technical gaps.

Building for the Long Term

Here’s the honest truth: the first 90 days are a sprint within a marathon. Do them well and you’ve built a foundation. Do them poorly and you’ll spend months rebuilding trust.

What Success Looks Like at Day 90

At the end of your first quarter, you should:

  • Understand the major systems and how they interact
  • Know who to ask about what
  • Have delivered several meaningful contributions
  • Be handling work with decreasing supervision
  • Have relationships across your team (and ideally beyond)
  • Know what you want to focus on next

What Success Sets Up

Getting the first 90 days right creates compound benefits:

  • Trust: You’ve earned credibility that makes future work easier
  • Context: You understand not just what exists but why
  • Relationships: You have people who will help you and vouch for you
  • Reputation: You’re known as someone who ramps up well
  • Clarity: You know where you fit and where you want to go

These advantages grow over time. The person who onboards well gets better projects, more autonomy, and faster promotions than the person who stumbles early and never quite recovers. For guidance on career growth after onboarding, see our help desk to sysadmin progression guide.

Your 90-Day Checklist

Here’s a condensed reference you can actually use:

Days 1-30: Absorb

  • All accounts and access working
  • Development/admin environment set up
  • Understand ticketing/workflow systems
  • Know where documentation lives
  • Have mental map of major systems
  • Identified subject matter experts
  • Taking personal notes
  • Completed first small contribution

Days 31-60: Engage

  • Handling more complex work
  • Building relationships beyond immediate team
  • Documented patterns and improvement opportunities
  • Found potential niche or ownership area
  • Received and incorporated early feedback
  • Shadowed on-call or incident response

Days 61-90: Deliver

  • Own at least one area or system
  • Completed visible win recognized by others
  • Solid relationships across relevant teams
  • Plan for next 90 days and beyond
  • Shared onboarding feedback with manager
  • Set up ongoing learning or certification goals

The Mindset That Wins

Beyond tactics, the right mindset shapes everything.

Be curious, not judgmental. When you see something that seems wrong, ask why before concluding it’s stupid. There’s usually context.

Assume good intent. Weird processes and frustrating decisions usually weren’t malicious. People did their best with the information they had.

Play long games. The person you dismiss today might be your manager next year. The boring legacy system you master might become critical. Short-term thinking creates long-term problems.

Add value before extracting it. Before asking for promotions, raises, or opportunities, demonstrate that you’re worth the investment. When the time comes to discuss compensation, our IT salary negotiation guide can help.

Document what you learn. Your notes help future you and future teammates. Creating documentation is a contribution even when it doesn’t feel like one.

The first 90 days set the trajectory for everything that follows. Invest in them wisely.

Frequently Asked Questions

How quickly should I start making suggestions for improvements?

Wait until you understand why things are the way they are—usually 30-60 days. Present suggestions as questions first: “I noticed we do X manually. Has the team considered automating it?” This acknowledges that there might be context you’re missing while still contributing ideas.

What if my manager doesn’t provide clear expectations?

Some managers are hands-off by default. If expectations aren’t clear, create them yourself. Write down what you think success looks like for your first 30/60/90 days and ask your manager to review. This shows initiative and creates alignment.

How do I balance learning with contributing?

Early on, tilt toward learning. By day 30, you should be contributing meaningfully. By day 60, contribution should dominate. If you’re still mostly learning at day 90, something went wrong. The ratio shifts gradually, not suddenly.

What if the onboarding experience is terrible?

Many companies have poor onboarding. Document what’s missing, find your own answers, and share feedback at the end of your 90 days. Improving the process for future hires is itself a valuable contribution—and shows leadership potential.

How do I know if I’m doing well?

Ask directly. Don’t wait for formal reviews. A simple “How am I tracking so far?” to your manager clears up uncertainty. If you’re afraid to ask, that itself might indicate a problem worth addressing.