30-Day IT Career Starter Plan

Days 1–5: choose and baseline

Choose one target role. Review 15–20 relevant job descriptions and create a list of repeated skills. Assess what you already know.

Days 6–10: systems fundamentals

Practice Windows/Linux basics, users, files, services, processes, logs, command line, and hardware concepts.

Days 11–15: networking

Learn IP addressing, subnetting basics, DNS, DHCP, gateways, ports, TCP/UDP, and connectivity troubleshooting.

Days 16–20: role-specific labs

Data center: hardware/cabling. Support: accounts/M365-style scenarios. Networking: switching/routing labs. SOC: logs/alerts. Cloud: deploy a small environment.

Days 21–24: document proof

Turn three labs into portfolio write-ups with objective, diagram, steps, troubleshooting, result, and lessons.

Days 25–27: resume

Write a targeted resume around genuine skills and projects. Remove irrelevant filler and quantify real outcomes where possible.

Days 28–30: interview and apply

Practice scenario answers, improve LinkedIn/profile materials, apply to realistic roles, and track applications and skill gaps.

What to put in your first IT portfolio

Use the month to produce three small, repeatable demonstrations. A completed lab is more useful when another person can understand the goal, reproduce the steps and see how you checked the result. Use a personal lab or authorized simulation and remove personal details, credentials and employer information from screenshots.

Project 1: document a connectivity problem

Draw a client, gateway and DNS resolver. Record the IP configuration, test the local connection and compare a name lookup with an address-based test. Explain what each observation rules out. Your deliverable is a network diagram plus a short incident note separating symptoms, evidence and conclusions.

Project 2: practice an account-support ticket

Write a fictional request for access to a shared folder. Record the identity checks, approval needed, intended permission and validation steps. Explain when you would escalate rather than grant access. A paper exercise is enough to demonstrate the process; label it clearly as a simulation.

Project 3: choose a role-specific task

For a data center role, label a rack-to-switch path and document a link-down investigation. For IT support, record how you would investigate a slow workstation using available logs and resource measurements. For a SOC path, create a timeline from a fictional alert and list the evidence you would preserve. Focus on one role rather than attempting every specialty.

A simple lab write-up template

1. Goal: the problem you intended to solve.
2. Environment: equipment or simulation used, with a small diagram.
3. Evidence: the observations and checks performed.
4. Decision: why you chose the next step.
5. Validation: how you established the outcome.
6. Limitations: what you could not test and would escalate.

How do you know you are ready to apply?

Choose a real vacancy and map each essential requirement to an honest example, a completed exercise or a specific gap. Practice explaining one incident in two minutes. Thirty days can establish a study habit and a starting portfolio; it does not guarantee job readiness or employment. Continue the plan where your evidence is weakest.

Data center technician skills roadmap · Practice with TechLoomix Academy · Find practice worksheets