How I Used TryHackMe to Learn Cybersecurity

By Emmanuel Rodriguez • Published November 11, 2025

TL;DR: TryHackMe is the single best place I found to turn curiosity into hands-on cybersecurity skills. This guide shows a beginner-friendly path, how to get the most from rooms, an example walkthrough pattern you can copy, and how to turn your TryHackMe work into a portfolio that actually helps land interviews.

Why TryHackMe? (Short and practical)

When you’re starting out, concepts are easy to read about but hard to internalize. TryHackMe bridges that gap with guided, bite-sized labs (“rooms”) that teach a concept, give you a controlled environment to practice, and usually finish with a small assessment or challenge. That mix of explain, show and practice is why TryHackMe accelerates learning faster than videos or pure theory alone.

Who this article is for

My recommended TryHackMe learning path (first 8 weeks)

Follow this suggested progression, spending ~5–10 hours per week depending on your schedule. The idea is to alternate theory + short labs with progressively harder challenges.

  1. Weeks 1–2 (Foundations): Start with the “Complete Beginner” / “Pre-Security” learning paths. Focus on Linux basics, SSH, and simple networking concepts.
  2. Weeks 3–4 (Web basics & OWASP intro): Do web fundamentals rooms, then a few OWASP-style labs that demonstrate SQLi and XSS conceptually.
  3. Weeks 5–6 (Offense fundamentals): Work through “Web Exploitation” and “Active Directory” introductory rooms, plus 1–2 easy HTB/THM machines if you feel ready.
  4. Weeks 7–8 (Defensive awareness): Try SOC or Blue Team beginner rooms to understand detection and logging (this makes you a well-rounded candidate).

A reusable 5-step lab workflow (copy this for every room)

Every time you open a TryHackMe room, follow this pattern. It trains your methodology and gives you consistent notes for write-ups.

  1. Read the room intro & objectives. Note expected skills and tools (nmap, curl, burp, etc.).
  2. Attempt the tasks hands-on. Type commands; don’t copy/paste blindly. If you get stuck, read one hint at a time.
  3. Record commands + short outputs. Keep a notes file with the exact commands that worked and a one-sentence explanation of why they worked.
  4. Write a mini write-up (200–400 words). Include your approach, key commands, and the lesson learned.

This helps you go back to your notes often when you get stuck as you progress through more rooms. Writing also helps reinforce your learning.

Example: Walkthrough template

Title: [Room Name] - Quick Walkthrough
Objective: [What the room teaches]

Environment:
- VM IP:
- Tools used: nmap, gobuster, curl, browser, Burp Suite (as applicable)

Steps:
1) Recon: nmap -sC -sV -oN nmap.txt <target-ip>
2) Enumeration: found X service on port Y; discovered /admin via gobuster
3) Exploitation: submitted payload "..." and received...
4) Root/Privilege Escalation: used "..." (if applicable)
5) Cleanup and lessons learned

TL;DR: [1–2 sentence summary of the vulnerability and how you exploited it]

Include any code you used in the write-up as well as explanations of why you used it. Explain where you found it (hints, docs, forums, etc.). Code you use is code you should eventually be able to write. Try to memorize common commands and their flags.

Common tools you’ll actually use on TryHackMe

How to handle hitting a wall (when a room feels too hard)

Final notes: what I wish I’d done earlier

Start writing early. Even short, messy write-ups after each room build writing stamina and technical communication skills. Recruiters don’t expect perfection; what matters is consistency, curiosity, and evidence that you can learn by doing. TryHackMe gives you the environment to prove that; your job is to record and present the evidence.


Also read: What is DVWA and why you should do it