Skip to main content
How TechWaymark is built

Why this exists, and who's behind it.

Most career advice for technology gets written by people selling courses, ranking affiliates, or chasing search traffic. TechWaymark isn't that. It's written by one person who's spent twenty years inside the work, from the helpdesk phone through to security architecture, and who got tired of watching newcomers burn two years on certifications that lead nowhere.

Last reviewed September 2026·Check each record’s source date and review scope·No paid placement or sponsored ordering. Commercial relationships must be disclosed.
About the author · James

Twenty years from helpdesk to security architect.

I started in technology by telling someone over the phone to turn their laptop off and back on. From there I moved through tiered support (L1, L2, L3), did onsite installs and field engineering, ended up as a senior engineer, ran an IT department as a manager, and now work as a security architect. Along the way I sat (and passed) a decent stack of certifications across multiple vendors. I currently hold CISSP.

TechWaymark is the guide I wish I'd had at every one of those stages. It's also the guide I now wish existed when I'm on the hiring side of the table reading another CV built out of YouTube playlists.

  1. Phone support
  2. Tiered desk
  3. Field / onsite
  4. Senior engineer
  5. IT manager
  6. Security architect

Why TechWaymark exists

The single most damaging pattern I see, on both sides of the hiring table, is people stacking certifications and tutorials with no operational time wedged in between. Credentials alone do not show how someone handles an operational problem. In interviews, I look for examples of decisions, checks and outcomes alongside the study.

The opposite extreme is just as bad. Pure self-study with no structure leaves people busy for two years with nothing a recruiter can decode. Both routes waste real money and real time. Both get pushed hard by content optimised for engagement rather than outcomes.

TechWaymark sequences the route the way it actually plays out: foundations first, then a real role, then specialisation grounded in the work you're already doing. It says no to promises that study alone guarantees a role. Adjacent experience, employer support and the opportunity to practise can change the route.

To be fair, there are edge cases. Someone with adjacent experience, a sharp referral and decent timing can compress a couple of years. It happens. It's just not a plan you can hand to a stranger and expect to work.

How the pathways are built

Pathways combine the following kinds of information. Coverage varies: inspect the evidence panel on the page rather than assuming every route has an external employer study.

  • 01
    Hiring reality

    Published vacancy requirements can help explain the work, but TechWaymark does not maintain a representative live vacancy survey for every role. Where employer or research evidence is used, its source and scope should be stated. UK and US coverage are separate.

  • 02
    Operational truth

    What the work feels like once you're in the chair. The distance between a job description and what's expected of you on day one is wider than most resources admit, and that gap is where people quietly quit in year one.

  • 03
    Cert sequence that holds up

    Which credential opens the conversation, which one's worth the money once you're already in role, and which one is a long-term bet that only starts paying back after three to five years of relevant work. Not what the vendor recommends. What hiring managers actually weight when they're shortlisting at 11pm.

  • 04
    Realistic timelines

    Planning bands make the scale of a route visible. They are practitioner estimates, not a representative study of time to hire. Prior experience, available practice, local vacancies and employer selection can shorten or extend the journey.

Where the Atlas figures come from

TechWaymark estimates UK mid-career base salary and typical time on a step for every role on the Atlas. The figures are judgement calibrated against job adverts and practitioner experience, not a salary survey, and they carry no employer, region or sector breakdown. They are precise enough to rank routes and to flag a hop that is a large step; they are not precise enough to plan a negotiation around.

The route planner also distinguishes two kinds of reasoning. An authored step carries TechWaymark's own written rationale for that exact transition. An inferred step is derived from the shape of the graph alone: the two points are genuinely connected, but nobody has written the judgement yet, so it is labelled on screen and deserves stronger scrutiny before you plan around it. Where the planner calls a hop load-bearing, documented or uncommon, that is TechWaymark's rating of the transition, not a measured rate of how often people make it.

Estimates last reviewed end to end on 2026-09-17. Basis: TechWaymark practitioner judgement, calibrated against UK job adverts.

What TechWaymark will not claim

  • That a certification stack on its own makes you hireable. It doesn't.
  • That you can skip the boring operational years and walk into a senior role.
  • That AI is about to delete IT. It isn't, and the loudest voices on this aren't doing the work.
  • That any one vendor's path is universally correct. Most of them aren't.
  • That getting into security, cloud or DevOps is fast. Occasionally it is. Usually it's a slog, and pretending otherwise just sets people up to feel like they've failed when they're actually on track.

If a section of TechWaymark starts drifting toward any of these claims, that's a bug. Tell me.

What TechWaymark is not

Not a course platform.
TechWaymark points you at where the real learning lives (vendor labs, one good instructor, the docs) and then gets out of the way.
Not an affiliate funnel.
Training provider links can earn a commission. When they do, they're labelled, and the judgement around them doesn't change. Recommendations aren't for sale.
Not a recruiter.
TechWaymark won't promise you a job. It'll tell you which roles are realistically reachable from where you're sitting today.
Not motivational.
No "you've got this." Just the sequence, the timelines and the actual work.

Sources, AI assistance and simulations

Essays, role guides and pathway judgements are written by James. Certification facts are checked against the awarding body's own pages, and labour-market figures link to the published report they come from, with its date.

Paid reports and some drafting use AI assistance inside a framework James wrote. AI output is never treated as evidence, and product pages say where it is used.

Classroom and interview scenarios are simulations. The organisations, tickets and people in them are fictional, and they have not yet been evaluated in classroom trials.

TechWaymark is independent. It is not endorsed by any government department, employer or certification body.

Update cadence

Our aim is to revisit pathways regularly and re-check certifications when vendors change their assessments. The recorded dates on individual facts, prices and editorial assessments show what has actually been checked. A recent vendor check does not mean hiring outcomes have been validated. Corrections can be sent through the contact page.