Your First 90 Days in a New IT Job After a Career Change: UK Survival Guide 2026

The First 90 Days: Why This Window Matters

You have landed your first IT role. Congratulations. Now comes the part nobody warns you about: the first three months are not a gentle onboarding. They are a high-stakes assessment period where your employer is quietly measuring whether you can actually do the job, and you are measuring whether you have made a terrible mistake leaving your old career.

The statistic is sobering: roughly 40% of career changers in tech roles experience significant confidence collapse in the first eight weeks. Not because they cannot do the work, but because the gap between what they thought they knew and what they actually need to know becomes suddenly, visibly real.

The good news? If you know what to expect and where to focus your energy, you can turn those 90 days into a genuine foundation instead of a survival mission.

Month One: Get Oriented, Not Competent

Your first priority is not to become an expert. It is to understand the landscape.

What to do:

Spend the first week mapping the infrastructure. What systems does your company actually run? Windows or Mac? On-prem or cloud? If you do not know what "on-prem" means yet, ask. Everyone expects you to be asking questions now.

Ask your line manager for the official runbook or knowledge base. Most IT teams have documented processes somewhere. That document is your best friend.

Attend every team meeting, even if half of it makes no sense. You are learning the language and the priorities. Do not worry about contributing yet.

Write down every acronym and term you do not know. Look them up later. Your first week should generate a list of 30 to 50 of these. That is normal.

Pair with a senior colleague for at least one full day. Watch what they do. Ask why, not just how.

What not to do:

Do not try to solve problems independently on day three. If you are stuck after 15 minutes, ask.

Do not assume you need to memorise everything immediately. You will be lost for weeks. That is not failure.

Do not pretend to understand something you do not. Saying "I am not sure what you mean by that" is always safer than nodding and guessing.

Month Two: Start Contributing, Accept Gaps

By week 5, you should have stopped being purely observational. Your confidence will have taken a small hit (this is normal), and you will start noticing the specific technical gaps you need to close.

Where most career changers stumble:

Healthcare workers, for example, are used to processes that prioritise safety and compliance above speed. In IT, you will often encounter a tension between security and usability, or between "technically correct" and "good enough for now". This is not a moral failing in IT. It is just how it works. Adapt.

You will also notice you do not know half of what your peers know. Do not panic. You have not failed. You are learning faster than you think.

What to focus on:

Pick one technical area to go deeper on. Not everything. One thing. If you are in IT Support, maybe that is printer troubleshooting or user access management. Get genuinely competent at that one thing.

Start taking on small tickets or tasks independently. Make mistakes. Report them quickly. This builds trust.

Join an internal Slack channel or Teams channel focused on your area. Lurk if you need to, but you will absorb vocabulary and common problems.

If your company uses a ticketing system (Jira, ServiceNow, etc.), spend an hour learning how to search it for similar issues before asking a colleague. You will find answers faster than expected.

Month Three: Establish Your Rhythm and Spot Your Growth Path

By month three, you should be autonomous on routine tasks and starting to anticipate problems instead of just reacting to them.

Your real goal now:

Understand where you want to go. Not everyone in IT Support stays in IT Support, and not everyone moves to cloud administration. Some people specialise in security, others in infrastructure, others in vendor management.

Ask your manager: where do people typically progress from your role? What skills would move you toward that next role? This is your roadmap for the next 12 months.

What to establish:

A weekly routine that includes time for tickets, time for learning, and time for lunch away from your desk. Burnout in month four is real and it catches career changers hard.

A relationship with one or two more experienced colleagues who have time to mentor you. Not your direct manager necessarily, but someone you can ask "stupid questions" to without affecting your review.

A habit of documenting what you learn. When you solve a problem, write it down. When you learn why something works the way it does, note it. This is your personal knowledge base and it will save you weeks of reworking old problems.

The Invisible Challenges Nobody Mentions

Imposter Syndrome

You will feel like a fraud. Every career changer does. You are not. You were hired because someone believed you could do this role. That belief was not a mistake.

The feeling peaks around week 4 and again around week 8. Expect it. It passes.

Pace and Context Switching

Healthcare teams often work in longer attention cycles. IT teams work in constant interruption cycles: a user calls, you context-switch, you fix it, another user calls. This is exhausting at first. Your brain will adapt, but give yourself permission to be tired for the first month.

The Vocabulary Barrier

You will feel like people are speaking a different language. They are. Learn it actively. Write down phrases you hear and do not understand. Ask what they mean. This is not weakness. This is how you actually close the gap.

The One Resource That Actually Works

Knowing the theory is one thing. Practising it in a real lab environment where you can break things safely is another. If you are finding your first month overwhelming and you did not have formal training before starting your role, consider refreshing your fundamentals with a structured course. The SmoothOps 365 IT Support & Cloud Fundamentals Course covers exactly the practical skills you need for an entry-level IT role, and includes hands-on labs where you can experiment without fear. Many of our students are career changers who want to solidify their foundation while already working, so the course is designed around weekends. Book a free 2-hour live session to see if it fits your learning style and current gaps.

The 90-Day Mark: How to Know You Are Actually On Track

By day 90, you should be able to answer these questions honestly:

Can I resolve 70% of routine tickets without escalation?

Do I understand the major systems and how they connect?

Have I built relationships with at least three colleagues?

Do I know what I do not know?

Have I spotted the next skill I want to develop?

If the answer is yes to all of these, you are doing fine. You might not feel confident yet. But you are on track.

Frequently asked questions

How long does imposter syndrome last in a new IT job?

Most career changers experience peak imposter syndrome around weeks 4 and 8, but it typically settles after month three once you start resolving problems independently. It may resurface when facing a new type of problem or moving to a more senior role, but the intensity decreases once you have evidence that you can actually do the job.

Should I tell my team I am a career changer?

Yes, early and clearly. It resets expectations and makes people more patient with knowledge gaps. Your team will assume you are figuring things out anyway, so being upfront about your background actually builds trust faster than pretending you already know everything.

What is the most common mistake new IT people make in their first month?

Trying to appear competent instead of asking questions. New employees are expected to ask questions. Appearing confident when you are lost creates more problems later because you will have built solutions on shaky ground.

Is it normal to feel completely overwhelmed in week two?

Completely normal. Most people hit a confidence dip between days 7 and 14. The onboarding feels chaotic, nothing makes sense yet, and you are absorbing far more information than usual. This is not a sign you are failing. This is the learning curve.

How do I know if I am progressing at the right pace?

Your manager should give you informal feedback by week four and formal feedback by week eight. If nobody is checking in, ask them directly: am I on track? What would a successful first 90 days look like for this role? This conversation is not just helpful, it is your responsibility as an employee.