Every week someone asks us the same thing: “How do I get my first job in cybersecurity?” Instead of writing another generic roadmap, we went back through two months of posts from people in our own LinkedIn network: final-year students, SOC analyst trainees, people switching from sales into security, trainers and hiring managers. What they describe is more honest, and more useful, than most career guides.
We’ve kept the people anonymous, because several were sharing personal job-hunt struggles. But every situation below comes from a real post.
The job hunt right now: “selected” is not the same as “hired”
One final-year cybersecurity student, already ISC2 CC certified and aiming for GRC and SOC roles, summed up his month in four outcomes. He was selected for an unpaid internship. A paid role turned him down for lacking experience. He was one of two people picked for a GRC role with two openings, until the company cut it to one at the last minute. And he turned down a trainer role because it wasn’t the path he wanted.
His takeaway is worth repeating to every fresher: an offer can disappear in a minute, so put your energy into the things no company can take back. Your skills, your proof of work, and your network.
He’s not an isolated case. In the same weeks, we saw SOC analysts with SIEM and incident-response training posting that they were open to work, including people who had moved into security from sales and edtech jobs. Experienced recruiters in our network described the wider market the same way: more rounds, more assignments, and more candidates being ghosted after the final interview. If you’re struggling, it’s not just you.
The biggest mistake: trying to learn all of cybersecurity at once
A regional director at a cybersecurity training company posted a roadmap for freshers that cuts through a lot of the confusion. His main point: cybersecurity is not one job. Pick one track and go deep. Here’s our summary of the tracks he laid out:
| Track | What to get really good at | Typical first roles |
|---|---|---|
| SOC / security operations | SIEM and log analysis, incident response, EDR/XDR | SOC Analyst L1, junior security analyst |
| Network security | TCP/IP, routing, firewall policies, VPN, segmentation | Junior network security engineer, firewall support |
| Identity and access | MFA, SSO, role-based access, PAM, Zero Trust | IAM analyst, PAM support engineer |
| Cloud security | Cloud IAM, cloud security controls, SASE | Cloud security analyst |
| Vulnerability management | Scanning, CVE and CVSS, patching, risk prioritisation | Vulnerability analyst |
| GRC | ISO 27001, NIST CSF, SOC 2, risk assessments | GRC analyst, compliance associate |
The order he recommends is simple: IT fundamentals, networking, Windows and Linux, security basics, then one track, then hands-on labs, then a certification, then projects. Only then start applying.
We’d add one thing from our own side. Networking is the part freshers most often skip, and it’s the part that shows up in almost every interview, whatever the track. If you can’t explain what happens when you type a URL into a browser, fix that before buying any course.
Certificates help, but “I did it” beats “I studied it”
The same roadmap ended with a test we like a lot. Before an interview, you should be able to say: I configured it, I investigated it, I troubleshot it, and I practised it in a lab. Collecting certificates isn’t the goal.
You can see the gap in how freshers present themselves on LinkedIn. Plenty of posts in our network announce course completions, such as a Splunk e-learning module or a vendor badge. Those are good, but they rarely get an interview on their own. A short write-up of an investigation you ran in a home SOC lab tells a hiring manager far more. Include what alert fired, what logs you checked and what you concluded.
Some proof-of-work ideas that cost nothing:
- SOC: set up a free SIEM on a spare laptop or free cloud tier, generate failed logins and suspicious PowerShell activity, and document how you detected it.
- Network security: build a small lab in a network simulator with a firewall, write rules, and show what gets blocked and why.
- GRC: pick a small fictional company and write a one-page risk register and an access-control policy mapped to ISO 27001 controls.
- Vulnerability management: scan your own lab machines, rank the findings by CVSS and real risk, and explain what you’d patch first.
Which first certification, then?
For many freshers in our network, the ISC2 Certified in Cybersecurity (CC) was the starting point. That’s largely because ISC2 offered the training and exam free for years. That’s changing. In April 2026, ISC2 announced it would conclude its free One Million Certified in Cybersecurity programme, and the CC page now sells the exam with a 365-day window to sit it. Check the current price before you plan around it.
Our honest view: one entry-level certification is enough to get past HR filters. After that, spend your money and time on labs, not a second beginner certificate. For a full comparison of CC, Security+ and others, see our guide to entry-level cybersecurity certifications. If you’re weighing Security+, our piece on taking SY0-701 now or waiting for V8 covers the timing. For later, see CEH vs OSCP and CISSP vs CISM.
The unpaid internship question
The student we mentioned ended his post by asking seniors: in a layoff-heavy market, is an unpaid internship in Chennai, Bengaluru or Pune smart, or should you hold out for a paid one? It’s the most common dilemma we see, so here’s how we’d think about it.
An unpaid internship can be worth it if three things are true. You’ll touch real tools, such as a live SIEM, real tickets or a real audit. Someone senior will actually supervise you. And it’s short, ideally two to three months, with a clear end date. It’s not worth it if you’ll mostly be making slides or doing sales calls, if there’s no named mentor, or if you have to relocate and pay rent in a metro to do it.
Ask before you accept: “What tools will I use in the first month, and who will review my work?” A vague answer is your answer. And keep applying for paid roles while you’re there. An internship should add to your proof of work, not pause your search.
Why your network matters more than your resume
One thing stood out in almost every post we read. The people making progress weren’t the ones with the longest certificate lists. They were the ones sharing what they learned. One cybersecurity engineering student wrote about running a career-guidance session for his juniors, including his own mistakes, and his point was that real mentorship means sharing those lessons, not just pointing people to resources.
That habit works for you too. Post your lab write-ups. Comment thoughtfully on posts by security leaders, for example on a breach in the news and what controls would have helped. Recruiters do read these. A hiring manager who has seen three of your posts is far more likely to open your resume than one who hasn’t.
A realistic 90-day plan
- Days 1–30: networking and Linux basics, every day, until you can explain DNS, TCP handshakes and common ports without notes.
- Days 31–60: pick one track from the table above. Build one lab and write it up properly.
- Days 61–75: sit one entry-level certification, if the cost works for you.
- Days 76–90: post your two best write-ups on LinkedIn, update your profile with your track and the tools you’ve used, and apply to 5–10 roles a week that match that track, not every security job you see.
The market is tough right now, and the posts in our network don’t hide that. But the pattern is clear: focus beats breadth, proof beats certificates, and people who share their work get found.
Are you breaking into cybersecurity, or hiring for it? Tell us what you’re seeing through our contact page or on LinkedIn. We may feature your experience in a future article.

Leave a Reply