You got the offer. You negotiated the salary. You survived the background check. Now you’re staring at your first Monday, wondering how you went from confidently answering interview questions to feeling like you know absolutely nothing.

Welcome to imposter syndrome on steroids.

Here’s what nobody tells you about starting a new IT job: the interview tested whether you could do the work. The first 90 days determine whether you fit while doing it. Technical skills got you in the door. What happens next decides whether you stay, get promoted, or quietly start updating your resume six months from now.

The stakes are higher than most career advice acknowledges. Research shows 20% of employees quit within the first 45 days. That means a significant chunk of hires don’t survive their probation period. Some quit. Some get let go. Most simply never recover from a rocky start.

You’re not going to be in that group. Here’s the week-by-week playbook.

Week 1: Survival Mode

Your first week isn’t about proving yourself. It’s about not screwing anything up while you figure out where the bathrooms are.

Day 1-2: Absorb, Don’t Perform

Resist the urge to demonstrate your value immediately. The fastest way to alienate your new colleagues is to show up talking about how things were done at your previous company. Nobody cares. Actually, they do care—they care enough to hold it against you.

Your only goals for the first two days:

  • Learn names. Write them down. People notice when you remember.
  • Understand the ticketing system, documentation standards, and escalation procedures.
  • Figure out who actually knows things versus who just talks like they do.
  • Set up your development environment, email, and access without asking the same question twice.

That last point matters more than you think. The ability to ask technical questions effectively separates professionals from burdens. Before asking anyone anything, spend five minutes trying to find the answer yourself. Check the wiki. Search Slack history. Read existing documentation.

When you do ask, frame it properly: “I checked the onboarding doc and the wiki, but I couldn’t find info on X. Where would I find that?” This signals competence, not helplessness.

Day 3-5: Map the Terrain

By mid-week, you should be building a mental map of how work actually flows through the organization. Official org charts rarely tell the full story.

Who makes decisions? Not who has the title, but who actually gets consulted before changes happen. In many IT departments, the senior sysadmin with no management title has more influence than the IT director who’s perpetually in meetings.

What are the unwritten rules? Every team has them. Maybe you never deploy on Fridays. Maybe the shared drive structure is a disaster everyone pretends is fine. Maybe there’s one server nobody touches because the person who configured it left three years ago and no one knows how it works.

Where are the landmines? Ask what previous fires they’ve dealt with. The stories people tell about past incidents reveal what they’re actually worried about. This also helps you avoid accidentally stepping on the same landmines.

Start a private document—call it your “brain dump” or “field notes.” Document everything: passwords, processes, quirks, contacts. You’ll thank yourself in month three when someone asks about something you only touched once.

Common First-Week Mistakes

Over-promising. Your manager asks if you can handle a project. You want to impress them. You say yes without understanding the scope. Now you’re three weeks in, drowning, and afraid to ask for help. Instead: “That sounds interesting. Can I review the requirements and get back to you tomorrow with a realistic timeline?”

Under-communicating. You’re stuck on something but don’t want to look incompetent. You spend four hours on a problem a five-minute conversation would solve. Your manager wonders why you’re so slow. Instead: “I’ve been working on X for about an hour and I’m stuck on Y. Before I spend more time, is there existing documentation or someone who’s worked on this before?”

Criticizing too early. The documentation is a mess. The ticketing workflow makes no sense. The backup system is held together with duct tape and prayers. You’re right about all of it. Shut up anyway. You don’t have the political capital to criticize yet, and you don’t know why things are the way they are. Maybe the person who set it up is still there. Maybe there’s a reason. Find out before you judge.

Weeks 2-4: Building Foundations

You’ve survived week one. People know your name. You can find the coffee. Now the real work begins.

Establish Your Credibility Carefully

This is where many new IT hires go wrong. They’re so eager to prove their technical chops that they take on complex problems before understanding the environment. Then they break something, look foolish, and spend weeks recovering from a preventable mistake.

Instead, look for small wins that build trust incrementally:

  • Fix a low-priority ticket nobody’s gotten to
  • Document a process that exists only in someone’s head
  • Automate a tedious manual task (with permission)
  • Clean up a shared folder or script repository

None of these are glamorous. All of them demonstrate value without risk. They also show you care about the team’s collective sanity, not just your personal highlight reel.

Build Relationships Deliberately

Technical skills got you hired. Relationships determine whether you get promoted, get the interesting projects, or get warned when layoffs are coming.

This doesn’t mean becoming everyone’s best friend. It means being genuinely helpful and curious about others’ work.

Schedule informal one-on-ones. “Hey, I’m still getting up to speed—mind grabbing coffee and telling me about your role?” Most people love talking about themselves. They’ll remember you as someone who listens.

Help without being asked. See someone struggling with something you know? Offer assistance without being condescending. “I ran into something similar last month—want me to show you what worked for me?” Not “Oh, that’s easy, here’s what you do.”

Learn how to explain technical concepts to non-IT colleagues. The ability to translate between technical and business language makes you invaluable. When the marketing director can actually understand your explanation of why the website is slow, you’ve built political capital that lasts.

If you’re working remotely, this relationship-building requires extra effort. You don’t have hallway conversations or lunch tables to fall back on. Be more intentional about reaching out. Turn on your camera. Respond to Slack messages with more than “ok.”

Understand the Real Priorities

What your job description says and what actually matters are often different things.

Ask your manager directly: “What would success look like for me in 90 days?” Listen carefully. If they say “just getting up to speed on the systems,” believe them. If they say “taking over the monitoring stack,” you know where to focus.

Also ask: “What’s the biggest headache the team is dealing with right now?” The answer reveals what’s actually keeping people up at night. If you can help solve that headache—even partially—you’ve demonstrated real value.

Pay attention to what gets attention. When your manager’s manager asks about something, that thing matters regardless of what’s on any official roadmap. When tickets sit for weeks untouched, those aren’t priorities no matter what anyone claims.

The Documentation Discipline

You should already be taking notes. Now formalize it.

Every IT environment has documentation debt—knowledge that exists only in people’s heads, procedures that work but aren’t written down, systems nobody fully understands anymore.

As the new person, you’re in a unique position to fix this. You’re learning things for the first time, which means you notice what’s missing from the docs. When you figure something out, write it down.

This serves multiple purposes:

  • You create value for the team without needing deep technical expertise yet
  • You demonstrate initiative and follow-through
  • You become the expert on the things you document
  • You build a reputation as someone who makes things better

Read our guide on IT documentation best practices for tactical advice on what to document and how to structure it.

Weeks 5-8: Finding Your Groove

By now, the initial terror should have faded. You know where things are. You’ve closed some tickets. People have stopped introducing you as “the new person.”

Time to level up.

Take On Meaningful Work

You’ve proven you won’t break things. Now you can push for more substantial projects.

The key is choosing the right ones. Look for work that:

  • Has clear success criteria (you’ll know when you’re done)
  • Has a reasonable timeline (you can deliver before everyone forgets you started)
  • Involves skills you want to develop
  • Matters enough to get noticed but isn’t so critical that failure is catastrophic

Avoid projects that have been languishing forever. There’s usually a reason nobody’s finished them—political complexity, impossible requirements, or missing budget. You don’t have the context to handle that minefield yet.

Develop a Specialty

Generalists are valuable, but in the first 90 days, being known for something specific accelerates trust.

Maybe you’re the person who really understands DNS. Maybe you’re the one who can actually read error logs. Maybe you’re unusually good at dealing with frustrated users. Whatever it is, let people know.

This doesn’t mean refusing to do anything else. It means having an area where you’re the go-to person. When someone has a question about X, they think of you. That visibility compounds over time.

If you’re early in your career, this is also when you should be thinking about which path you want to pursue. The skills you develop in your first role shape the opportunities you’ll have next.

Get Real Feedback

Don’t wait for your formal review. Schedule a brief check-in with your manager: “I’ve been here about a month—how do you think things are going? Anything I should be doing differently?”

Most managers appreciate this. It shows self-awareness and a desire to improve. It also gives you time to course-correct if something’s off.

Listen to what they say, but also listen to what they don’t say. If they can’t name specific things you’ve done well, that’s a signal you’re not visible enough. If they hesitate before answering, there might be a concern they haven’t addressed directly.

The goal isn’t validation. It’s information. You can’t fix problems you don’t know exist.

Warning Signs to Watch For

Pay attention to how you’re feeling. The honeymoon period is over, and the reality of the job is setting in.

Some friction is normal. New environments are exhausting. Learning curves are steep. But persistent red flags deserve attention:

  • You’re consistently excluded from relevant meetings. This might indicate the team hasn’t integrated you, or doesn’t intend to.
  • Your manager is never available. An absent manager makes it hard to get feedback, grow, or deal with office politics.
  • The culture is worse than it appeared in interviews. That “fast-paced environment” turned out to mean “constant crisis mode.” The “startup mentality” means “no work-life balance.”
  • You dread Mondays. Some adjustment period is normal, but if you’re genuinely unhappy most days, trust that feeling.

Recognizing these signs early gives you options. You might address them directly, adjust your expectations, or quietly start planning an exit. What you shouldn’t do is ignore them and hope they improve on their own. See when to leave an IT job for guidance on making that call.

Weeks 9-12: Cementing Your Position

The home stretch. By now, you should feel like you belong—or at least like you’re successfully faking it.

Demonstrate Clear Impact

Before your 90-day review (formal or informal), document what you’ve accomplished. Be specific:

  • Tickets closed and time saved
  • Documentation created or improved
  • Problems solved before they escalated
  • Skills developed and applied

Don’t be shy about this. Your manager has other things to think about. If you don’t remind them what you’ve done, they might not remember.

Frame your accomplishments in terms of value to the team. “I closed 47 tickets” is less compelling than “I reduced the average resolution time for printer issues by 30%.” Numbers matter, but context matters more.

Plan Your Next Chapter

Ninety days feels like the end, but it’s really just the beginning. Now you have enough context to think strategically about your career trajectory.

Where do you want to be in a year? What skills do you need to get there? What projects should you pursue next? Who should you be learning from?

Consider finding a mentor in your organization. You know enough now to ask intelligent questions and have enough runway to actually implement their advice. If you’re thinking about getting promoted, now’s the time to understand what your organization actually values.

Start conversations about growth. “I’ve really enjoyed working on X—are there opportunities to do more of that?” or “I’m interested in developing skills in Y—what would that path look like here?”

These conversations plant seeds. Even if nothing changes immediately, you’ve signaled ambition and direction. When opportunities arise, you’ll be considered.

Build Sustainable Habits

The frantic learning pace of your first months isn’t sustainable. Neither is the overtime you’ve probably been putting in. Now’s the time to establish routines that work long-term.

That means protecting your time for continuous learning without burning out. Block calendar time for skill development. Set boundaries around after-hours communication. Build processes that reduce firefighting.

It also means developing soft skills alongside technical ones. The people who advance aren’t just the best engineers—they’re the ones who can communicate, collaborate, and handle organizational complexity.

The Mindset That Makes It Work

Beyond tactics, certain mental frameworks help new IT hires thrive.

Be Curious, Not Critical

When you find something that doesn’t make sense, assume there’s a reason before assuming incompetence. “Why did we set it up this way?” instead of “This is stupid.” You might learn something. At minimum, you won’t alienate the person who set it up.

Embrace Imposter Syndrome (Temporarily)

Feeling like you don’t belong is uncomfortable but useful. It keeps you humble, makes you ask questions, and prevents the overconfidence that leads to breaking production at 4 PM on a Friday.

The goal isn’t to eliminate imposter syndrome in 90 days. It’s to build genuine competence until the feeling naturally fades. That takes time. Be patient with yourself.

Invest in Relationships Like They Matter (Because They Do)

Technical skills are table stakes. What separates people who succeed from people who stagnate is often relationships and reputation. The colleague you help today might be the hiring manager at your next job. The mentor who guides you now might become your reference for that promotion.

You’re not networking—you’re being a decent human who cares about the people around you. But it turns out that decent humans who care about others tend to have better careers. Funny how that works.

Document Everything

Not just for the team—for yourself. Someday you’ll need to remember how you fixed that obscure problem. Someday you’ll update your resume and want specific examples. Someday you’ll negotiate a raise and want data.

The time to gather that information is while you’re doing the work, not months later when you’re trying to reconstruct what happened.

When 90 Days Isn’t Enough

Sometimes you do everything right and the job still isn’t working. Maybe the culture is genuinely toxic. Maybe the role was misrepresented. Maybe you’re just not a fit for this particular team.

That’s okay. Not every job works out. The goal isn’t to force yourself to stay in a bad situation—it’s to give the job a fair chance while gathering the information you need to make a good decision.

If you hit 90 days and you’re miserable, that’s valuable information. You now know what you don’t want. You can start thinking about what comes next while you have the stability of employment.

But don’t confuse normal adjustment difficulty with genuine mismatch. New jobs are hard. Learning curves are steep. Feeling overwhelmed at week six doesn’t mean you should quit. If you’re making progress, building relationships, and occasionally enjoying the work, you’re probably fine.

Frequently Asked Questions

How do I handle imposter syndrome in my first IT job?

Imposter syndrome is nearly universal for new IT hires, especially if you’re transitioning from another field or this is your first role after training. The discomfort is normal—what matters is how you respond. Focus on learning aggressively, ask questions without apologizing for not knowing, and track your wins. Each problem you solve provides evidence that you belong. Over time, competence replaces the fear. Most experienced IT pros felt exactly like you do now.

What if I mess something up during my first 90 days?

Everyone makes mistakes. What matters is how you handle them. Acknowledge the error immediately, explain what happened, and propose a solution or prevention plan. Don’t hide problems hoping they’ll resolve themselves—that always makes things worse. Managers generally forgive mistakes from new hires who own them and learn. What they don’t forgive is dishonesty or repeated failures to follow process.

How do I balance learning with getting work done?

This tension never fully resolves, but it’s especially acute in your first months. Build learning into your work by documenting as you go, asking “why” when you solve problems, and choosing tasks that stretch your skills slightly. Use downtime strategically for structured learning like certifications or lab practice. Don’t sacrifice all learning for productivity—you’ll end up with stale skills and a career plateau.

When should I start negotiating for a raise?

Not during your first 90 days. Focus on proving your value first. Once you’ve hit clear milestones—typically after six months to a year—you’ll have standing to discuss compensation. Document your accomplishments along the way so you have evidence when the time comes. Read our guides on salary negotiation strategies to prepare.

What if my manager isn’t giving me enough guidance?

Some managers are hands-off by nature. Others are simply busy. Start by asking directly for what you need: “I’d find it helpful to have weekly check-ins while I’m ramping up—would that work for you?” If that doesn’t work, look for unofficial mentors on the team. When guidance truly isn’t available, use your judgment and document your decisions. The goal is showing you can operate independently while remaining open to feedback.

The Bottom Line

Your first 90 days set the trajectory for everything that follows. Not because it’s impossible to recover from a rocky start—plenty of people have—but because a strong start creates compound returns. The relationships you build, the reputation you establish, and the skills you develop all accelerate when you begin intentionally.

You’ve already done the hard part. You got the job. Now you just have to prove they made the right choice.

Show up curious. Work hard without burning out. Build relationships like they matter. Document what you do. And give yourself permission to be new while actively earning the right not to be.

In 90 days, you won’t be the new person anymore. You’ll be the person who figured it out. That transformation doesn’t happen automatically—but it does happen, if you’re intentional about making it so.