Skip to main content

About the project

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

TechWaymark is a single-author project. No editorial team and no anonymous panel of "experts". One person who's spent the last two decades inside UK tech, writing down what's actually true about getting in and getting past mid without burning out on the way to senior. I'm James, a security architect. The judgement here is mine. Where a tool assembles prose inside my framework, the product page says so.

Experience
20 years in UK IT
Now
Security architect
Written by
One author

The route

The arc

  1. Call centre

    I started in a call centre. Literally telling people to turn the laptop off and back on again, helping people get their internet working again, reading scripts I'd half-learnt to ignore. That company doesn't exist anymore.

  2. Support desk and field work

    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.

  3. College IT Manager

    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.

  4. Security architect

    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.

Standards

What TechWaymark refuses to do

  • Honest limits

    Practical encouragement with clear limits. Your starting point, access to learning and available opportunities all affect the next step.

  • No gamification

    No streaks or points, no "level up your career" language. This is your livelihood. Treat it like one.

  • No affiliate pumping

    Cert pages aren't a funnel into training providers. Some links may earn a commission; where they do, they're labelled as such, and the judgement around them doesn't change.

  • No guarantees

    No guaranteed job, salary or timeline. Published ranges are planning estimates; the relevant experience and responsibilities matter more than a fixed number of years.

  • Accountable judgement

    Editorial accountability stays with TechWaymark. AI assistance does not make a claim evidence. Automated products explain how they are produced; factual records should link to their sources and state their limits.

Where to start

What you should do with the site

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.

Get in touch

There's no Discord and no sales call. The Atlas, route planning and synthetic report samples cost nothing; personalised CV reviews and written products are paid, and they're all listed on the pricing page. If you're stuck on a specific decision, or something on the site got it wrong, the contact form is the way through.

Contact