For students and early-career professionals

Cybersecurity Engineer

Designs security into systems by hardening infrastructure and building protections.

15 chapters · About 6 months · 15–30 min a day

Start this plan free →

Chapter 1 is free.

Skills

14 skills, and what you'll learn in each

Each skill is a few short lessons, then practice. You rate yourself at the start and again at the end.

Core to the job

Chapter 4

Security fundamentals

Spot phishing emails and fix a system's weak security settings

What you'll learn

  • CIA triad
  • Least privilege
  • Defense in depth
  • Attack surface

Practice

  • Triage 5 vulnerability scan findings25 min
  • Spot 5 signals in a phishing email15 min
  • Check your own laptop against a basic hardening checklist25 min

Chapter 4

Vulnerability management

Rank scan findings and list fixes with owners and dates

What you'll learn

  • Asset inventory
  • Scan types
  • CVSS score
  • Exposure and exploitability
  • Remediation SLA

Practice

  • Choose the scan that can actually see it15 min

Chapter 5

Log analysis

Trace an alert back to the log lines behind it

What you'll learn

  • Log sources
  • Query refinement
  • Alert to evidence
  • Event timeline
  • Escalation threshold

Practice

  • Trace one alert back to the log lines that made it fire15 min
  • List the log sources that would prove the claim, and the ones you do not have20 min
  • Build one timeline from three log extracts across two hosts25 min

Chapter 5

Threat hunting

Map attacker behaviour to logs, search for what alerts missed

What you'll learn

  • MITRE ATT&CK
  • Hunting hypothesis
  • Detection coverage
  • False positive

Practice

  • Write one detection as code and review it like a change30 min

Chapter 6

Linux

Manage files and who can open them using short commands

What you'll learn

  • Filesystem map
  • File permissions
  • Pipes and filters
  • Process signals

Practice

  • Solve 5 Linux command-line puzzles25 min

Chapter 6

Networking fundamentals

Trace a web request and write rules for app connections

What you'll learn

  • Request path
  • Subnet range
  • Network layers
  • Network access controls
  • Cloud network placement
  • Joining networks

Practice

  • Capture and read your own network traffic for 5 minutes25 min
  • Review a firewall rule set and find the rules that should not be there20 min

8 more in the plan

Problem solvingTest each possible cause of a problem instead of guessingCh 2

What you'll learn

  • Problem vs symptom
  • Clean problem splits
  • Root cause
  • Deciding under uncertainty

Practice

  • Break an Ambiguous Problem into Actionable Parts20 min
Critical thinkingSpot a weak assumption and ask where numbers come fromCh 2

What you'll learn

  • The hidden assumption
  • Argue the other side
  • The base rate
  • Fact vs inference
  • Wanting it to be true

Practice

  • Spot the Weak Link in an Argument10 min
Access managementChoose the least access that works and flag broad permissionsCh 7

What you'll learn

  • Identity and access
  • Least privilege
  • Role-based access
  • Multi-factor authentication
  • Federation trust
  • Access audit

Practice

  • Evaluate an Urgent Access Request Using Least Privilege15 min
  • Audit a sample IAM permissions set20 min
ScriptingWrite a script that checks disk space and warns youCh 9

What you'll learn

  • Script arguments
  • Error handling
  • Input checks
  • Readable scripts

Practice

  • Write a Script That Checks Disk Space and Warns You20 min
GitSave clear changes to a project's history and request reviewCh 9

What you'll learn

  • Change states
  • Short-lived branches
  • Merge conflict
  • Useful commit message
  • Pull request review

Practice

  • Practise a small Git branching workflow30 min
Incident responseBuild an incident timeline from logs and write plain updatesCh 10

What you'll learn

  • User impact first
  • Mitigate before root cause
  • Blameless post-mortem
  • Incident command roles

Practice

  • Analyze How a Company Communicates During an Outage15 min
  • Write an on-call handoff note15 min
CommunicationRewrite an update for two different readers, cutting extra linesCh 11

What you'll learn

  • Lead with the point
  • Match detail to the reader
  • Said versus heard
  • Specific feedback

Practice

  • Write a Six-Line Delay Message10 min
Working with othersContribute to group work, ask for help and credit teammatesCh 11

What you'll learn

  • Early team friction
  • Clear ownership
  • Challenge ideas, not people
  • Lead or follow

Your plan

Chapter by chapter.

15 chapters, in this order. Chapter 1 is free.

1~2 wks

See the work of a Cybersecurity Engineer

StartFree
2~2 wks

Find the cause before you fix it

Skills
3~2 wks

Scan for weaknesses and fix the worst

Project
4~2 wks

Find and close known weaknesses

Skills
5~2 wks

Hunt threats and trace alerts to evidence

Skills
6~2 wks

Find your way around Linux and networks

Skills
7~2 wks

Control who gets access to what

Skills
81–2 wks

Talk to two working security engineers

People
9~2 wks

Automate repeat tasks with versioned scripts

Skills
10~2 wks

Handle production incidents when on call

Skills
11~2 wks

Make yourself understood across a team

Skills
12~2 wks

Capstone: build a detection lab with five rules

Project
131–2 wks

Answer the questions interviewers ask

Interview
141–2 wks

Decide how you will get in

Decide
15on your timeline

Send your first applications

Apply

The job

What a Cybersecurity Engineer does

Builds and improves security controls for an organization so its systems and data stay safe and available.

The work

  • Design security controls for networks, cloud, endpoints, and applications
  • Harden systems by setting secure configs, patching, and reducing attack surface
  • Build detection and response playbooks with logging, alerts, and automation
  • Review architectures and changes to spot risks before release
  • Test defenses using vulnerability scanning and controlled penetration testing
  • Investigate incidents, contain threats, and support recovery with clear updates
  • Write security standards and help teams follow them in daily work

A typical day

  1. Check alerts and logs, then triage anything suspicious with the response team
  2. Meet engineers to review a new feature and agree on security requirements
  3. Fix or coordinate fixes for top vulnerabilities and verify patches worked
  4. Tune detections, update playbooks, and document what changed and why

Tools

Operating systems: Linux, WindowsScripting: Python, Bash, PowerShellVulnerability scanning: Nessus, OpenVASNetwork analysis: Wireshark, tcpdumpSIEM and logging: Splunk, Elastic StackCloud security: AWS IAM, Azure ADVersion control: Git

Ways in

There is more than one route.

Ways to study

  • Bachelor degree in cybersecurity, computer science, or information systems
  • Diploma or vocational program in IT networking and system administration
  • Cybersecurity bootcamp with hands-on labs and a portfolio
  • Self-study path using online courses plus home lab practice

How people get their first job

  • IT support or system admin role to learn real systems and troubleshooting
  • Cybersecurity internship in security operations, engineering, or cloud security
  • Build a home lab and publish write-ups of hardening and detection work
  • Earn entry certifications like Security+ or Network+
  • Contribute to open-source security tooling or documentation

How the work is changing

What AI is doing to this role

How AI is changing this role · one of 6 tasks we track

Harden systems and cut attack surface

Sped up a lot

What AI does

Terraform and policy-as-code checks catch bad configs before they ship.

Still yours

You decide what to break to close a hole.

Reviewed September 2026

In the app · Premium

The rest is in the app

  • How AI affects the other 5 tasks
  • Whether this job is growing or shrinking
  • How hard the first job is to get
  • Similar roles that are easier to get into
  • Updated every month, with sources
See it in the app →

How we rate a job →

Already working

Already a Cybersecurity Engineer?

Plan your move to Senior Security Engineer: 13 chapters that end with a strong case for your next review.

Grow in the role →

Other roles in IT & Cloud Infrastructure

Questions

Questions about this plan

How long does it take to become a cybersecurity engineer with Welica?

The plan is 15 chapters, 6 months at 15 to 30 minutes a day. You can go faster or slower; the plan moves with you.

Do I need a degree?

Not always. Common routes are bachelor degree in cybersecurity, computer science, or information systems, diploma or vocational program in IT networking and system administration, cybersecurity bootcamp with hands-on labs and a portfolio, or self-study path using online courses plus home lab practice.

What is free?

Chapter 1, See the work of a Cybersecurity Engineer, is free for good. Premium unlocks the rest of the plan.

Start the Cybersecurity Engineer plan.

Chapter 1 free. About 15 to 30 minutes a day.

Start on web Continue your session Download for MacMac Get the iPhone appiPhone Get it on Google PlayAndroid