1 Application Tracker & Your Professional Story
Create a spreadsheet to track applications — company, role, date applied, stage, salary, contact, notes:
| Company | Role | Date Applied | Stage | Notes |
|---|---|---|---|---|
| Company A | SOC Analyst | 1 Sep | Recruiter | Awaiting response |
| Company B | IT Support | 3 Sep | Technical | Interview Friday |
| Company C | IAM Analyst | 5 Sep | Applied | Entra / SSO role |
This prevents applications from becoming chaotic once you're juggling several at once. Alongside it, prepare your own professional story — the coherent version of everything you've just spent this course building: "I started by learning computer fundamentals and networking, then built Windows Server and Active Directory environments. From there I moved into Microsoft 365, Linux and cloud infrastructure. I became particularly interested in identity and cybersecurity, so I studied MFA, SAML, OAuth, OpenID Connect, SIEM, incident response, APIs, logs and PowerShell. I then built a home lab where I could combine those technologies and practise troubleshooting real-world scenarios." That's a compelling story because it demonstrates deliberate learning, not a random collection of facts.
2 Your Home Lab Is Experience & Career Paths
Never falsely describe home-lab work as commercial experience — but don't dismiss it either. Instead of "I have no experience," say: "I haven't managed Active Directory professionally yet, but I've built my own Windows Server domain where I configured users, groups, DNS, Group Policy and Windows clients and practised troubleshooting authentication issues." That's significantly stronger, and it's entirely true if you completed Module 19.
Your first job is not your final job. Common paths: Service Desk → Desktop Support → System Administrator → Cloud/Security Engineer; or Technical Support → Senior Support → IAM Engineer → Security Architect; or SOC Analyst → Senior SOC Analyst → Incident Response → Security Engineer. There are many valid paths — your first role primarily needs to create momentum, not define the rest of your career on day one.
Keep learning after you're hired. Technology evolves constantly — cloud platforms, authentication standards, AI systems, Zero Trust, endpoint security, containerisation, DevSecOps, identity security, SaaS, Infrastructure as Code. At the same time, engineers still need to understand older technologies, because companies can't replace everything overnight. Someone who understands both Kerberos and OIDC, both Active Directory and Entra ID, both VMware and containers, both on-premises and cloud, both NTLM and passkeys, can be extremely valuable — and that dual fluency is exactly what this entire course has been built around, module after module.
Lab Practice: CV, LinkedIn, GitHub & Portfolio
Lab 1 — Build Your CV
Create a technical CV with professional summary, technical skills, projects, home lab, education, certifications, GitHub and LinkedIn. Remove every vague phrase and replace it with technical evidence — per Lesson 1.
Lab 2 — Build LinkedIn
Write a professional headline, an About section, add technical skills, projects, certifications and GitHub, follow relevant companies, and connect with technology professionals — per Lesson 2.
Lab 3 — Build GitHub
Create repositories for a PowerShell project, a network troubleshooting project, an Active Directory project, a security investigation, and an API project — each with real documentation, not just code.
Lab 4 — Create a Portfolio
Publish at least three projects (e.g. Active Directory Lab, SOC Investigation, REST API/Authentication Lab), each explaining architecture, setup, technology, testing, problems, troubleshooting, results, and lessons learned — per Lesson 3.
Lab Practice: Technical & Troubleshooting Interviews
Lab 5 — Technical Interview
Answer, out loud, without notes: What is DNS? Explain DHCP and NAT. What happens when you type a URL into a browser? What is the TCP handshake, and how does TCP differ from UDP? What is Active Directory, Group Policy, Kerberos, an OU? What causes an account lockout? How do you check running processes or view logs on Linux, and what does chmod do? What is a virtual machine, a security group, IAM, the shared responsibility model? What is phishing, ransomware, SIEM, EDR, least privilege? What is MFA, SAML, OAuth, OpenID Connect, and the difference between authentication and authorisation?
If you struggled with any of those, which module in this course covers it? (This is worth actually answering — it tells you exactly where to go back and review before a real interview.)
Reveal the map
DNS/DHCP/NAT/TCP-UDP → Module 3 (Networking). Active Directory/Group Policy/Kerberos/OUs/lockouts → Module 4 and Module 9. Linux commands → Module 6. Virtual machines/security groups/IAM/shared responsibility → Module 7. Phishing/ransomware/SIEM/EDR/least privilege → Module 8 and Module 11. MFA/SAML/OAuth/OIDC/authN vs authZ → Module 9 and Module 10. If a gap shows up here, it's cheaper to close it now than in front of an interviewer.
Lab 6 — Troubleshooting Interview
Work through five scenarios using the troubleshooting framework: a user cannot access a website; VPN connects but internal applications don't work; a user account repeatedly locks; an API returns HTTP 401; an application suddenly becomes slow. For each, state your investigation steps out loud before reaching a conclusion — the process is what's being scored, per Lesson 4.
Lab Practice: Behavioural Interview & Salary Negotiation
Lab 7 — Behavioural Interview
Prepare STAR answers covering: a difficult problem, a mistake, a conflict, a customer issue, learning something quickly, working under pressure, and managing competing priorities. Don't memorise scripts word-for-word — understand your own stories well enough to tell them naturally and adapt them to whatever's actually asked.
Lab 8 — Mock Salary Negotiation
Practise responding out loud to: "What salary are you looking for?" / "The maximum we can offer is X." / "Are you interviewing elsewhere?" / "Would you accept the offer today?" The goal is becoming comfortable discussing compensation professionally — per Lesson 5, this is a normal business conversation, not an awkward one.
3 The Final Job-Ready Checklist
Before applying, you should be able to answer yes to most of the following:
- CV: Is it technically relevant, concise, honest, keyword-appropriate, and does it include projects?
- LinkedIn: Does the headline describe your career direction? Does the About section explain your skills? Is the profile professional?
- GitHub: Do you have several documented projects, with secrets and credentials removed?
- Portfolio: Can you demonstrate practical work, explain what you learned, and describe problems you encountered?
- Technical skills: Can you explain DNS, DHCP, TCP/IP, Active Directory, Linux, cloud, authentication, MFA, APIs, logs, SIEM, and basic scripting?
- Interview skills: Can you introduce yourself clearly, explain technical concepts simply, troubleshoot logically, admit when you don't know something, ask intelligent questions, and give STAR examples?
If so, you're ready to start interviewing. Your complete professional package by this point should include: a polished CV, a completed LinkedIn profile, at least three documented GitHub projects, a working home lab, portfolio documentation, a bank of technical interview questions and troubleshooting scenarios you've practised, at least five STAR stories, and a job application tracker.
The Most Important Lesson — and the End of the Course
Technology companies do not expect junior engineers to know everything. The strongest junior candidates demonstrate four things together: technical fundamentals, troubleshooting ability, communication, and willingness to learn.
Across this course you've learned how computers work, how networks communicate, how organisations manage identity, how authentication works, how cloud platforms operate, how cybersecurity teams detect threats, how incidents are investigated, how APIs communicate, how logs reveal what happened, how scripting automates work, how engineers troubleshoot problems, how professional teams communicate, how tickets and incidents are managed, and how to build your own technical lab. The final skill — the one this module has been about — is communicating all of that to an employer.
Your goal was never to convince an interviewer you know everything. It was to demonstrate: "I understand the fundamentals, I can investigate problems methodically, I communicate clearly, and I can learn the technology your organisation uses." That is what makes someone employable in IT and cybersecurity — and it's the whole reason this course exists. Good luck out there.