Twenty years from helpdesk to architecture. POST is what I wish someone had handed me at year one.

The arc

I started in a call centre. Literally telling people to turn the laptop off and back on again, walking pensioners through ADSL router resets, reading scripts I'd half-learnt to ignore. That company doesn't exist anymore.

From there I moved to a bigger outfit and worked my way up through a tiered support desk. First line, second line, third line. Spent a fair chunk of it on the road doing on-site installs, which is where you actually learn how different places run. Schools, academies, big corporates, a few places that probably shouldn't have been allowed near a network. Every site taught me something the office never would've.

That's also the period where I lost the plot a bit on certs. I was one of those guys who sat every exam I could get funded, convinced the wall of logos on my CV would do the talking for me. It didn't. Looking back I was a mile wide and an inch deep, and I knew it. I kept changing my mind on which direction to go. Networking one month, virtualisation the next. I wasn't sure whether to specialise at all.

The move that actually changed things was a role at a college. They'd advertised it as a senior engineer job. It wasn't. The scope was IT Manager work from day one, just without the title or the pay. I felt a bit catfished if I'm honest. What I didn't know was that this was where I'd really shine. I was on my own, not standing in someone else's shadow the way I had been. Sink or swim, and I had to adapt fast. I did get promoted to IT Manager in the end, the title and the pay eventually caught up with the job I'd already been doing. That's where I started cutting my teeth on security properly. ISO 27001, audit work, the unglamorous side of it. I ran a team of field engineers and was the senior technical escalation point at the same time, which meant doing design and implementation on top of keeping the lights on.

A few years as IT Manager and I moved on again, this time into a security architect role. That's roughly where I am now.

It's not boring, by the way. Sometimes it's fast-paced, sometimes high pressure, sometimes it's banging your head against a wall trying to explain why security should be embedded at the start of a project and not bolted on at the end. Most of my day is the decision-heavy bit of large environments. Identity, segmentation, the long tail of "why is it like this and what do we actually do about it".

That's the bit nobody puts in the LinkedIn version.

What POST refuses to do

• No motivational fluff. No "you can do anything if you believe". You probably can't. The honest version is more useful.
• No gamification. No streaks or points, no "level up your career" language. This is your livelihood. Treat it like one.
• No affiliate pumping. The cert pages don't link out to training providers I get a cut from. There are no providers I get a cut from.
• No 30-day-to-six-figures lies. The actual numbers, which are two to five years to mid and longer for senior, with a hard cap on some specialisations, are written into every Pathway and every role page.
• No AI-generated cornerstone content. Every Perspectives essay and every authored page is written by a person and read back out loud before it ships. The Atlas data is structured. The prose isn't.

What you should do with the site

Start with the Guided Route if you don't know what you don't know. It'll suggest a sensible starting domain and a realistic timeline.

Open the Atlas if you want to see the whole shape of the industry before committing to a direction. It's the map I wish I'd had at twenty-two.

Read the Perspectives essays when you're stuck on a specific decision. Burnout or push for promotion. Stay generalist or specialise. When to leave a job that's stopped teaching you anything.

If something on the site is wrong, please tell me. The disclaimer at the bottom of every page is real. This is one person's opinion, informed by twenty years of being in the room when bad decisions got made. It isn't gospel.