How to Start a Career in IT: A Practical 90-Day Roadmap

Amalia Stan, O365 L1 Engineer

Starting a career in IT can feel overwhelming. There are many possible directions, including IT support, system administration, networking, cloud platforms, Microsoft 365, automation and cybersecurity.

The good news is that you do not need to learn all of them before applying for your first job.

A more effective approach is to build a strong foundation, choose one realistic entry-level path and demonstrate what you can do through practical projects. Employers do not expect a beginner to know everything. They are more likely to look for structured thinking, curiosity, communication skills and evidence that you can learn.

This guide explains what to study, which projects to complete and how to prepare for an entry-level IT position over 90 days.

It also explains how IT work operates inside real business environments, where technical knowledge must be combined with documentation, security awareness, prioritisation and communication.

How do you start a career in IT?

To start a career in IT:

1. Learn the fundamentals of operating systems, hardware, networking and security. 
2. Choose an entry-level direction, such as IT support or Microsoft 365 support. 
3. Build practical experience through small labs and troubleshooting exercises. 
4. Document your projects in a simple portfolio. 
5. Learn how real IT teams manage tickets, users, devices and business systems. 
6. Prepare a skills-based CV and practise explaining your troubleshooting process. 
7. Apply for realistic junior roles before you feel that you know everything. 

For many beginners, IT support or service desk work is a practical starting point. It exposes you to users, devices, accounts, connectivity, permissions and workplace applications while helping you discover which technical area you may want to specialise in later.

Can you start an IT career without experience or a degree?

You can begin developing IT skills without professional experience or a technology degree. However, individual employers may have different education and experience requirements.

When you do not have previous IT employment, you need another way to demonstrate your ability. That evidence can include:

• Documented home labs 
• Troubleshooting exercises 
• Small automation scripts 
• Relevant certifications 
• Volunteer or internship experience 
• Customer service experience 
• A clear explanation of how you approach unfamiliar problems 

A degree may be helpful for some roles and career paths, but it is not a replacement for practical ability. In the same way, a certification may demonstrate foundational knowledge, but it does not prove that you can diagnose a real problem on its own.

Your objective should be to combine learning with visible evidence of practice.

Choose your first IT career path

You do not need to choose your entire career before you begin. You only need to select a suitable first direction.

Use the following comparison to identify a path that matches the type of work you enjoy.

Career path	It may suit you if…	Beginner project	Possible first role	Possible next step
IT support and service desk	You enjoy helping users and investigating everyday problems	Document five common Windows support scenarios	Helpdesk analyst or IT support technician	System administrator or Microsoft 365 administrator
System administration	You enjoy managing systems, users and configurations	Build a Windows or Linux virtual machine and configure accounts	Junior system administrator	Infrastructure or cloud administrator
Networking	You want to understand how devices and services communicate	Create and troubleshoot a small virtual network	NOC technician or network support technician	Network administrator or engineer
Microsoft 365 and cloud support	You enjoy working with identity, email, collaboration and access	Design a user onboarding and access-management workflow	Microsoft 365 support technician	Microsoft 365 or cloud administrator
Automation and scripting	You look for ways to reduce repetitive work	Create a PowerShell system-information report	Junior IT administrator or automation support technician	Automation or platform engineer
Cybersecurity	You enjoy investigation, risk reduction and access control	Build a basic security-hardening and incident checklist	Junior security support or SOC analyst	Security analyst or engineer

IT support and service desk

IT support involves helping users solve problems with accounts, devices, applications, connectivity and workplace services.

Typical requests may involve:

• Password and account-access problems 
• Email and collaboration applications 
• Laptop configuration 
• Printers and peripherals 
• Software installation 
• VPN or Wi-Fi connectivity 
• Shared folders and permissions 
• Multi-factor authentication 
• Device updates 

Support work is not simply about knowing an answer immediately. It requires you to gather information, test possible causes, communicate with the user and document the result.

That makes it a strong foundation for many other IT careers.

System administration

System administration focuses on keeping business systems available, secure and correctly configured.

A system administrator may work with:

• Windows or Linux systems 
• User accounts and groups 
• Access permissions 
• Servers and virtual machines 
• Software updates 
• Monitoring 
• Backups 
• Basic automation 

This direction may suit you if you prefer structured technical work and want to understand how systems operate behind the scenes.

Networking

Networking is the study and management of how devices, applications and services communicate.

Useful beginner topics include:

• IP addresses 
• DNS 
• DHCP 
• Ports and protocols 
• Wi-Fi 
• VPNs 
• Firewalls 
• Routing fundamentals 

Networking knowledge is useful even when you do not plan to become a network engineer. Many support and cloud problems are ultimately related to connectivity, name resolution or access.

Microsoft 365 and cloud support

Microsoft 365 brings together services used for email, communication, file sharing, collaboration, identity and access management.

A beginner should focus first on concepts such as:

• Users and groups 
• Licences 
• Outlook and Exchange concepts 
• Teams 
• SharePoint 
• OneDrive 
• Permissions 
• Multi-factor authentication 
• Administrative roles 

You do not need to begin with advanced cloud architecture. Understanding how users receive access to business services is a more practical starting point for entry-level support.

Automation and scripting

Automation reduces repetitive manual work.

A beginner can start with small PowerShell tasks, such as:

• Displaying system information 
• Checking running services 
• Exporting data to a file 
• Listing users or folders 
• Testing network connectivity 
• Generating a simple report 

The objective is not to build a complex application. It is to understand how a repeatable process can be expressed as a sequence of commands.

Cybersecurity

Security is part of every IT role.

Before learning advanced security tools, beginners should understand:

• Strong authentication 
• Multi-factor authentication 
• Phishing 
• Software updates 
• Least-privilege access 
• Endpoint protection 
• Secure file sharing 
• Backups 
• Basic incident reporting 

Cybersecurity becomes easier to understand when you already know how operating systems, networks, identities and permissions work.

The core skills entry-level IT candidates need

The tools used by different employers will vary. The underlying skills are more transferable.

Area	What to learn	What you should be able to demonstrate
Operating systems	Windows settings, updates, applications, services and file systems	Configure a system and investigate a common issue
Hardware	Storage, memory, peripherals, displays and common laptop components	Identify likely hardware symptoms and basic checks
Networking	IP addresses, DNS, DHCP, Wi-Fi, VPNs and ports	Diagnose a basic connectivity problem
Identity and access	Users, groups, passwords, roles and permissions	Create accounts and test access rights
Microsoft 365	Outlook, Teams, SharePoint, OneDrive and admin concepts	Explain how users receive services and access
Security	MFA, phishing, patching, least privilege and safe sharing	Recognise basic risks and recommend safe actions
Backup and recovery	Backup purpose, retention and restoration	Explain why a backup must be tested through recovery
Scripting	Basic PowerShell commands, variables and output	Automate or document a simple repetitive task
Documentation	Symptoms, tests, changes, results and next steps	Produce a clear troubleshooting record
Communication	Questions, updates and non-technical explanations	Explain a technical problem in simple language

Learn a repeatable troubleshooting process

Good troubleshooting is not random experimentation.

Use a process such as:

1. Clarify the problem. What is the user trying to do? 
2. Identify the scope. Is one user affected or several? 
3. Collect evidence. What error messages or symptoms are visible? 
4. Check what changed. Did the issue begin after an update, password change or configuration change? 
5. Test simple causes first. Check connectivity, credentials, permissions and service status. 
6. Change one thing at a time. Avoid making several changes without knowing which one resolved the problem. 
7. Confirm the result. Ask the user to repeat the original action. 
8. Document the solution. Record what happened, what you tested and what fixed it. 
9. Escalate when necessary. Explain what has already been checked. 

A simple problem can still require disciplined investigation. An expired password, missing permission, interrupted connection or incorrect setting may produce symptoms that initially appear more complicated.

Seven hands-on IT projects for your portfolio

Watching tutorials can introduce a topic, but practice is what turns information into usable skill.

Your projects do not need to be advanced. They need to show that you can plan a task, complete it safely, investigate problems and explain the result.

Only use devices, accounts and environments that you own or are authorised to access.

1. Install and configure a Windows virtual machine

Objective: Learn operating-system installation and basic configuration.

Complete tasks such as:

• Install Windows in a virtual machine. 
• Apply updates. 
• Create a standard user and an administrative user. 
• Install an application. 
• Review startup applications and system information. 
• Create a restore point or snapshot where supported. 

Portfolio evidence: Include a short configuration summary, screenshots and a list of lessons learned.

2. Install Linux and practise basic commands

Objective: Become comfortable with a second operating system.

Practise:

• Navigating directories 
• Creating and editing files 
• Viewing permissions 
• Installing an application 
• Checking disk usage 
• Reviewing running processes 
• Using command help and documentation 

Portfolio evidence: Create a one-page command reference and document one problem you encountered.

3. Create users, groups and file permissions

Objective: Understand identity and access management.

Create several test users and groups. Configure a shared folder with different levels of access, then test which users can read, modify or delete its contents.

Portfolio evidence: Add a simple access matrix showing each user, group and permission.

4. Troubleshoot a connectivity or DNS problem

Objective: Practise structured network troubleshooting.

Create a controlled problem in your lab, such as an incorrect DNS setting. Record:

• The original symptom 
• The commands or tools used 
• The results of each test 
• The cause 
• The correction 
• The final verification 

Portfolio evidence: Present the work as a support ticket or incident report.

5. Write a basic PowerShell report

Objective: Automate a small administrative task.

Create a script that collects information such as:

• Computer name 
• Operating-system version 
• Available disk space 
• Network configuration 
• Running services 
• Installed applications 

Export the result to a text or CSV file.

Portfolio evidence: Include the script, sample output and an explanation of each section.

6. Document a user onboarding workflow

Objective: Understand how business access should be organised.

Design a hypothetical process covering:

• Account creation 
• Group membership 
• Licence assignment 
• Email and collaboration access 
• Device preparation 
• Multi-factor authentication 
• Manager approval 
• Completion checks 

Use a lab or trial environment only when its terms permit it.

Portfolio evidence: Produce a workflow diagram and checklist.

7. Test a backup and restore process

Objective: Understand that recovery matters more than the existence of a backup file.

Create test files, back them up to a separate authorised location, delete or modify one file and perform a restoration.

Record:

• What was backed up 
• Where it was stored 
• When the backup ran 
• How the restore was tested 
• Whether the restored file was usable 

Portfolio evidence: Write a short recovery report.

A practical 90-day IT learning plan

A 90-day roadmap can give your learning structure. It is not a guarantee of employment or a deadline for becoming an expert.

The goal is to build a useful foundation and produce evidence that you can apply it.

Days 1-30: Build the foundations

Focus on operating systems, hardware, networking and troubleshooting.

Weeks 1-2

Study:

• Computer components 
• Windows settings and administration 
• Applications and updates 
• Users and file systems 
• Basic command-line tools 

Complete:

• A Windows virtual machine 
• A system-configuration document 
• Two simple troubleshooting exercises 

Weeks 3-4

Study:

• IP addresses 
• DNS 
• DHCP 
• Wi-Fi 
• VPN concepts 
• Ports 
• Basic Linux navigation 

Complete:

• A Linux virtual machine 
• A connectivity troubleshooting report 
• A personal troubleshooting checklist 

End-of-month outcome: You should be able to configure a basic system, explain common network concepts and document how you investigated a problem.

Days 31-60: Learn workplace tools

Focus on identity, collaboration, permissions, security and scripting.

Weeks 5-6

Study:

• Users and groups 
• Roles and permissions 
• Outlook and email concepts 
• Teams 
• SharePoint 
• OneDrive 
• Microsoft 365 administration concepts 

Complete:

• A user-onboarding workflow 
• A group and permission matrix 
• A file-access troubleshooting exercise 

Weeks 7-8

Study:

• Multi-factor authentication 
• Phishing 
• Software updates 
• Least privilege 
• Endpoint protection 
• Backup and recovery 
• Basic PowerShell

Complete:

• A security checklist 
• A backup and restore exercise 
• A PowerShell information report 

End-of-month outcome: You should be able to explain how business users receive access to services and how basic security controls protect those services.

Days 61-90: Build evidence and apply

Focus on your portfolio, CV, interviews and job applications.

Weeks 9-10

Complete:

• Three polished portfolio projects 
• A one-page technical CV 
• A professional online profile 
• A list of entry-level roles matching your skills 

Weeks 11-12

Practise:

• Describing each project in two minutes 
• Explaining your troubleshooting process 
• Answering basic technical scenarios 
• Communicating with a non-technical user 
• Explaining when you would escalate an issue 

Begin applying for suitable positions and keep a record of:

• Roles applied for 
• Skills requested repeatedly 
• Interview questions 
• Gaps you need to address 
• Feedback received 

End-of-plan outcome: You should have a basic technical foundation, several documented projects and a repeatable process for improving your applications.

Which beginner IT certifications are worth considering?

Certifications can help organise your learning and demonstrate that you have studied a defined body of knowledge.

They are most useful when:

• You need a structured syllabus. 
• Employers in your target market request a specific credential. 
• You are changing careers and need additional evidence of commitment. 
• You combine the certification with relevant practical projects. 

They are less useful when you collect several credentials without practising the underlying skills.

As of June 2026, examples of active entry-level options include:

Cisco Certified Support Technician IT Support

Cisco describes CCST IT Support as an entry-level certification covering support tasks such as troubleshooting, documentation, assisting users, computer components and identifying security threats. 

It may be relevant when your target roles include helpdesk, service desk or end-user support.

Cisco CCST Networking or Cybersecurity

Cisco also provides CCST paths covering entry-level networking and cybersecurity concepts. The networking path addresses how network devices, media and protocols support communication, while the cybersecurity path covers introductory security, endpoint and incident-response topics. 

Choose the path that matches the roles you plan to pursue rather than attempting all of them at once.

Microsoft Certified: Azure Fundamentals

Microsoft positions Azure Fundamentals as a beginner credential covering cloud concepts, Azure services, management and governance. 

It can provide useful cloud context, but it should be combined with practical understanding of users, networking, access and administration.

Certification catalogues and exams change. Always verify the current syllabus, language, cost and retirement status on the vendor’s official website before enrolling.

How to build an entry-level IT portfolio

A beginner portfolio should not attempt to make you look like a senior engineer.

Its purpose is to demonstrate that you can:

• Complete a technical task 
• Work methodically 
• Document your process 
• Recognise security boundaries 
• Explain what you learned 
• Improve after encountering a problem 

For each project, use a consistent structure:

Project title

Use a specific title such as:

Windows Virtual Machine and User-Permission Lab

Scenario

Explain the problem or objective.

The objective was to configure separate administrator and standard-user accounts and test access to a shared folder.

Environment

List the technologies used.

Windows virtual machine, local users and groups, NTFS permissions.

Actions

Explain what you configured or tested.

Problem encountered

Describe at least one issue. A project in which everything works immediately often reveals less about your troubleshooting ability.

Resolution

Explain how you identified and corrected the problem.

Result

State how you verified that the intended outcome was achieved.

Lessons learned

Explain what you would do differently next time.

Do not publish passwords, licence keys, personal information, internal business details or screenshots from systems you are not authorised to share.

How to write a CV for your first IT role

Your CV should make it easy for the reader to understand what you have practised.

Avoid long lists of advanced tools that you cannot discuss confidently. Use specific evidence instead.

Weak CV statement

Knowledge of Windows, networking, cloud, cybersecurity and PowerShell.

Stronger CV statement

Built and documented a Windows virtual lab with separate user accounts, group-based folder permissions and a tested backup-and-restore process.

Other examples include:

Diagnosed a controlled DNS configuration issue using network tests, documented the root cause and verified connectivity after correcting the configuration.

Created a PowerShell script that collected operating-system, disk and network information and exported the results to a structured report.

Designed a user-onboarding checklist covering account creation, group membership, service access, MFA and completion verification.

Transferable experience also matters. Customer service, administration, retail, logistics and hospitality roles may demonstrate communication, prioritisation, reliability and the ability to stay calm when someone needs help.

What entry-level IT interviews usually assess

A technical interview is not always a test of whether you remember the correct command.

The interviewer may also be evaluating:

• How you gather information 
• Whether you test assumptions 
• How you communicate with users 
• Whether you understand security boundaries 
• How you document your work 
• Whether you know when to escalate 
• How you respond when you do not know something 

Consider the following scenario:

A user says that email is not working.

A weak response is to guess one solution immediately.

A stronger response begins with questions:

1. What exactly happens when the user attempts to open or send email? 
2. Is there an error message? 
3. Is the problem affecting one user or several? 
4. Does it occur in one application or through the web interface as well? 
5. Is the device connected to the internet? 
6. Has the user recently changed a password? 
7. Are other Microsoft 365 services available? 
8. Is the account active and correctly authorised? 
9. What has already been tried? 

You are not expected to know the final cause before beginning the investigation. You are expected to demonstrate a logical process.

When you do not know the answer, say what you would do next:

“I have not encountered that exact error before. I would capture the error details, check the relevant documentation, confirm the account and service status, and escalate with a record of the tests I completed.”

That is more credible than pretending to know.

How managed IT teams work in practice

IT work inside a business is not a sequence of unrelated technical fixes.

Each action can affect users, security, productivity and business continuity. That is why organised IT teams use defined processes.

Tickets and priorities

Requests and incidents are recorded so that teams can track ownership, urgency, communication and resolution.

A password reset, a single-user application issue and a company-wide service interruption should not be handled with the same priority.

User onboarding and offboarding

New employees need appropriate accounts, services, devices and permissions. Departing employees must have access removed in a controlled and timely way.

These processes connect IT support with identity management, security, licensing and business operations.

Monitoring and maintenance

IT teams monitor systems, review alerts, apply updates and address issues before they become larger disruptions.

Change management

A technically correct change can still cause problems if it is made without testing, approval, communication or a rollback plan.

Escalation

Junior engineers are not expected to solve every issue independently. They are expected to recognise when a problem exceeds their access, authority or expertise.

A useful escalation should include:

• The user or service affected 
• The original symptoms 
• Relevant error messages 
• Checks already completed 
• Changes made 
• Results observed 
• The current business impact 

Documentation

Good documentation allows another person to understand what happened without repeating the entire investigation.

It also helps teams:

• Resolve recurring incidents faster 
• Transfer knowledge 
• Maintain consistency 
• Review changes 
• Improve onboarding 
• Reduce avoidable errors 

Security and business continuity

Security is not limited to a specialist team. Support and administration decisions can affect account security, data access, endpoint protection and recovery.

A managed IT environment therefore connects multiple disciplines: user support, Microsoft 365, cloud services, automation, cybersecurity, backup and disaster recovery.

At Optimizor, these areas form part of the broader work required to keep business technology secure, available and manageable. For a beginner, the important lesson is that individual tools should always be understood in the context of the people and business processes they support.

Common mistakes beginners make

Trying to learn everything at once

IT is too broad to study effectively without priorities.

Start with operating systems, networking, identity, troubleshooting and security. Add specialist knowledge after you understand the foundation.

Watching courses without practising

Passive learning can create familiarity without practical ability.

After each topic, complete a small task that forces you to configure, test or explain what you learned.

Skipping networking basics

Networking appears in support, cloud, security and system administration.

You do not need advanced routing knowledge at the beginning, but you should understand how a device obtains an address, finds a service and communicates over a network.

Collecting certifications without building projects

A certification can support your application. It should not be the only evidence of your skills.

Pair every major topic with a practical task.

Making undocumented changes

If you change several settings and the problem disappears, you may not know which change resolved it.

Record what you changed and test one likely cause at a time.

Ignoring communication

A technically accurate solution is less useful when the user cannot understand it or does not know what to do next.

Clear questions and updates are part of the technical service.

Pretending to know

IT professionals regularly consult documentation and colleagues.

Honesty, combined with a sensible investigation plan, is more valuable than an unsupported answer.

Frequently asked questions about starting an IT career

What should I learn first for an IT career?

Start with Windows, basic hardware, networking, users and permissions, troubleshooting, documentation and basic security. Add Microsoft 365 or another workplace platform once those foundations are understandable.

What is the best first IT job?

IT support, helpdesk and service desk roles are common starting options because they develop practical troubleshooting and communication skills. The best role for you depends on your existing experience, interests and the opportunities available in your market.

Do I need to learn programming?

Most entry-level support roles do not require advanced programming. Basic scripting can still be valuable because it teaches logical thinking and helps automate repetitive tasks.

PowerShell is particularly relevant for Windows and Microsoft-focused administration.

Should I learn Windows or Linux first?

For many workplace-support roles, Windows is a practical first choice. Linux is still valuable and should be introduced early, especially if you are interested in cloud infrastructure, servers, cybersecurity or automation.

Should I learn Microsoft 365 or Azure first?

Learn Microsoft 365 concepts first when your target role involves end-user support, accounts, email, collaboration and permissions.

Begin with Azure fundamentals when your target path is more focused on cloud infrastructure, administration or architecture. The two areas increasingly overlap, but they serve different immediate learning objectives.

Are IT certifications required?

Not always. Requirements vary between employers and roles.

A certification can provide structure and improve the credibility of a beginner application, but it works best when supported by labs, projects and clear explanations.

How can I get IT experience without an IT job?

Build virtual labs, document projects, create simple scripts, practise troubleshooting scenarios and contribute to authorised volunteer or community projects when available.

Treat your projects as professional work: define the objective, record your process and verify the result.

How long does it take to become job-ready?

There is no universal timeline. Your starting knowledge, available study time, target role and consistency all matter.

A focused 90-day plan can create a useful foundation and portfolio, but learning continues after you begin applying and throughout your career.

When should I start applying?

Begin applying once you can demonstrate basic troubleshooting, explain several projects and discuss the fundamentals required by the job description.

Do not wait until you meet every listed requirement. Apply selectively, remain honest about your current level and use the responses you receive to guide further learning

Start building your IT career

A career in IT does not begin when you know every answer. It begins when you learn how to investigate a problem responsibly.

Focus on the fundamentals:

• Operating systems 
• Networking 
• Users and permissions 
• Microsoft 365 
• Basic security 
• Backup and recovery 
• Troubleshooting 
• Documentation 
• Communication 

Then turn your learning into evidence. Build a lab, create a user, configure a permission, break something safely, diagnose it and write down what happened.

Your first projects may look simple. That is not a problem. Simple projects can demonstrate the habits that matter throughout an IT career: structured thinking, attention to security, clear communication and a willingness to keep learning.

At Optimizor, our work connects managed IT services, Microsoft technologies, cloud infrastructure, cybersecurity, automation, backup and disaster recovery. 

Explore the Optimizor blog for practical guidance from business IT environments, or visit our Careers page to learn about opportunities to develop your skills within a professional IT team.