Plot a route

Pick where you are now and where you want to get to. Atlas draws a realistic route, lets you optimise it for time, cost or coding, and explains what each step actually asks of you.

Most realistic

From

Optimise for

Your next step

IT Support → Sysadmin

Prepare evidence for this move first.

A recurring problem you removed rather than reprocessed
Documentation you wrote that someone else used

A lab can show learning, not production ownership. Label examples honestly and keep confidential information out.

Build my Route Brief

Free, no account. Continue with these roles already selected.

TechWaymark verdict

IT Support to Cloud Engineer is a load-bearing route. The plotted line is roughly what real careers in this lane look like.

Reachability: Common
Timeline: ~3–7 years · +£33k · 2 hops

What usually happens

The route holds together. TechWaymark flags IT Support to Sysadmin as the transition to examine most closely; build evidence for that move.

Biggest risk

You inherit the change window. Outages are yours now, not someone else's escalation.

Would we recommend it?

Yes

Load-bearing transitions, realistic pacing, grounded endpoint. This is what the route looks like when it works.

Where this route is most likely to break

IT Support → Sysadmin

Of the hops on this route, TechWaymark rates this one weakest (documented). That makes it the likeliest place for a plan to stall, and it is a judgement about the transition, not a measured failure rate. The cost is named as Biggest risk above.

Your route

IT Support → Cloud Engineer

~3–7y · +£33k · 2 hops

Salary and time figures are TechWaymark practitioner estimates, not survey data.

IT Support
↓ Sysadmin
Bottleneck
Commonly paired
Most sysadmins pass through support; the leap is autonomy, not skills.
~1–2y on step·+£13k·documented
Sysadmin
↓ Cloud Engineer
Common hop
Adjacent pivot
Systems experience can transfer into cloud operations, but the remaining automation and platform gaps vary by role.
TradeoffOn-prem muscle memory stops paying. You're back to being the junior in the room on IAM, networking primitives and IaC.
~2–5y on step·+£20k·common

What the labels on this route mean

Commonly paired: These two roles regularly appear in the same career histories. Not a promotion, more an autonomy/accountability step.
Pacing: documented: TechWaymark rates this real but not the default: it turns up in career histories without being the obvious next move.
Adjacent pivot: Cross-domain move documented in real careers. Senior in your old lane, mid-level in the new one for a year or so.
Pacing: common: TechWaymark rates this a load-bearing transition: the move the rest of the route is built around. A judgement about the transition, not a measured rate.

Longest step

Sysadmin ~2–5y

Most of the calendar time on this route sits here. If you're impatient, this is the step to question.

The full interactive map is easier to explore on a larger screen.

From

2steps·most realistic

Optimise for

Focused route

IT Support → Cloud Engineer

2 stages·~3–7 years · +£33k · 2 hops·IT Support to Cloud Engineer is a load-bearing route. The plotted line is roughly what real careers in this lane look like.

Build my Route Brief

Your next step

IT Support → Sysadmin

Focus on evidence for this move before planning every later step.

Evidence to prepare

A recurring problem you removed rather than reprocessed
Documentation you wrote that someone else used

Use work you can discuss without sharing confidential information. A lab or study project can show learning; label it honestly, because it does not prove production ownership.

Why this route, and what could make it difficult

Most sysadmins pass through support; the leap is autonomy, not skills.

What could make this route difficult

You inherit the change window. Outages are yours now, not someone else's escalation.

Time and salary figures are TechWaymark practitioner estimates, not survey data. A salary difference compares role estimates; it is not a predicted pay rise for you.

Free, no account. The brief stays in your browser.

Weighing up a certification for this route? Check whether it is relevant yet.

Where this route is most likely to break

IT Support → Sysadmin

Route narrativeCommon route2 authored · 0 inferred

Most realistic

Load-bearing transitions people actually make. Pacing is realistic, not aspirational.

Authored steps carry TechWaymark's own written rationale. Inferred steps are derived from the shape of the graph alone and deserve stronger scrutiny before you plan around them. Salary and time figures are TechWaymark practitioner estimates, not survey data.

1
IT SupportSysadmin
Commonly paired
Most sysadmins pass through support; the leap is autonomy, not skills.
~1–2y on step·+£13k·documented
2
SysadminCloud Engineer
Adjacent pivot
Systems experience can transfer into cloud operations, but the remaining automation and platform gaps vary by role.
TradeoffOn-prem muscle memory stops paying. You're back to being the junior in the room on IAM, networking primitives and IaC.
~2–5y on step·+£20k·common

What the labels on this route mean

Common route: How trustworthy this route is, not just whether it exists. Common means load-bearing. Stretch means possible but slow or org-dependent. Compressed means Fewest steps mode has skipped realistic dwell. Rare means an uncommon hop plus an aspirational endpoint.
Commonly paired: These two roles regularly appear in the same career histories. Not a promotion, more an autonomy/accountability step.
Pacing: documented: TechWaymark rates this real but not the default: it turns up in career histories without being the obvious next move.
Adjacent pivot: Cross-domain move documented in real careers. Senior in your old lane, mid-level in the new one for a year or so.
Pacing: common: TechWaymark rates this a load-bearing transition: the move the rest of the route is built around. A judgement about the transition, not a measured rate.

Total journey

~3–7 years · +£33k · 2 hops

Rough total. Many people take longer. Salary and time figures are TechWaymark practitioner estimates, not survey data.

Longest step

Sysadmin ~2–5y

Most of the calendar time on this route sits here. If you're impatient, this is the step to question.

The next step

You have the route. Now judge whether it holds up for you.

The free route shows what tends to happen. The Career Verdict tests that route against your experience, time and constraints.

A route shows what is possible. A Career Verdict makes the call.

TechWaymarkVerdict no. PA-2026-0512

Career analysis report

Career Verdict

Helpdesk → Security Architect

“Realistic, but not by adding another certification.”

01
The callA clear judgement on whether your route is realistic, and under what conditions.
02
Where the route breaksThe most likely point to stall, and why it happens in practice.
03
What to do nextSpecific priorities for the next 6–24 months, and what to drop.

Career Verdict

£39One-off payment. No subscription.

The callA single written judgement on whether the route is realistic for you.
Plateaus and failure modesThe flat years and the specific ways this route tends to stall.
Where you standThe strongest and weakest parts of your current position, named.
Salary realityWhat this route actually pays, set against what you've been told it pays.

See the Career Verdict

Usually within minutes of payment. Kept 24 months, then deleted. Deletion on request at any time.

Built on TechWaymark's practitioner-authored assessment framework, informed by two decades across helpdesk, infrastructure and security. The verdict applies that framework to your inputs.