Career Verdict
Understand what supports your plan, where it could stall and what to prioritise next.
£39 · One-off report
Personalised automated assessment using a practitioner-authored framework and AI-written prose. Individual consultation or human review of every report is not included.TechWaymark
Alex · Fictional editorial case
IT support → supervised cloud support
A supervised cloud-support move is worth investigating; independent cloud engineering is not yet supported by the evidence described.
A lab should remain labelled as a lab.
Inspect the full reasoning →How realistic is the move, given your current position and constraints?
See what strengthens the route and where it is most likely to stall.
Know what to prioritise, what to question and what would change the call.
Sample report excerpt · Alex · Fictional editorial case
If the chosen team uses Azure, use its administration syllabus to identify learning gaps. If it uses AWS, use the relevant AWS syllabus instead. Neither is a universal prerequisite. Before paying, check the current vendor requirements, full cost and whether the vacancy actually asks for the credential. Do not buy both simply to cover uncertainty.
Explore the annotated sample →A decision you can inspect
Your Guided Route provides the context. The report examines your responsibilities, constraints and evidence.
Keep an example of the investigation and the guidance you improved.
Supervision is a condition to investigate, not an assumption.
Record an expected result, a failure case and what changed.
Your route: Your current position → your target role
See what is inside the report →Career Verdict · Fictional editorial case · Alex
Two years in support. Four hours a week. No production cloud ownership.
1 / 7 · The call
Alex has two years in IT support, investigates access issues and writes team guidance. The proposed move is a cloud-support role with mentoring. This invented case assumes four study hours a week and no production cloud ownership. The call would change if the vacancy required independent incident or platform ownership.
Alex can explain a difficult ticket and a guide improved after feedback. That supports investigation and communication. It does not establish experience controlling cloud permissions, reviewing infrastructure changes or recovering a service. A lab should remain labelled as a lab.
How it works
Complete your Guided Route.
Review the purchase details.
Inspect the reasoning and assumptions.
Act on the priorities and revisit the call when things change.
Avoid if
Why a Verdict exists when the route is free
The Guided Route is free and stays free. It already provides planning constraints, likely bottlenecks and an evidence checklist. The paid Verdict adds a written decision report based on your submitted situation; it is not a charge for access to the route or its PDF.
Free Guided Route
Career Verdict, £39
Neither is better. They answer different questions. Most people only need the route. Some need the call.
Explore the report structure
Explore the annotated samplePrepared for Alex (fictional example) · 13 October 2026
IT support → supervised cloud support
A supervised cloud-support move is worth investigating; independent cloud engineering is not yet supported by the evidence described.
Invented case · four study hours a week · no production cloud ownership · Reference TW-EXAMPLE-ALEX
The call · Where you stand · The route · Certification rulings · Failure modes · Salary reality · Progression conditions
Section 01
A supervised cloud-support move is worth investigating; independent cloud engineering is not yet supported by the evidence described.
Alex has two years in IT support, investigates access issues and writes team guidance. The proposed move is a cloud-support role with mentoring. This invented case assumes four study hours a week and no production cloud ownership. The call would change if the vacancy required independent incident or platform ownership.
Verdict
Worth investigating, with conditions
Read the conditions and evidence below.
Time window
Evidence before a timetable
Reassess after a bounded task and vacancy checks
Single risk
Supervision is unconfirmed
A junior title does not establish who approves changes
What this verdict is not
An invented editorial illustration, not a customer result, hiring prediction or assessment of a real person.
Assumptions under test
The conditions this call rests on, named so you can disagreeThis verdict holds if
It weakens if
“Check the work and the supervision before committing to the title.”
What would change this call
Named conditions, not personal developmentThis call depends on the scope and supervision of the proposed work.
A named reviewer and a clear escalation route are confirmed.
That supports the proposed supervised move, while leaving Alex's task evidence to be examined.
The vacancy requires independent incident or platform ownership.
The current fictional evidence does not support that responsibility. Investigate a differently scoped role.
The completed task exposes a gap Alex cannot yet explain.
Narrow the task and seek feedback before treating it as evidence for an application.
Section 02
Alex can explain a difficult ticket and a guide improved after feedback. That supports investigation and communication. It does not establish experience controlling cloud permissions, reviewing infrastructure changes or recovering a service. A lab should remain labelled as a lab.
Troubleshooting practice
The invented history includes investigating access issues. Alex should explain the checks and escalation decision in one specific example.
Clear handovers
Alex writes guidance for the support team and can explain a revision made after feedback.
A bounded study plan
Four hours a week can support a small task. It does not justify an assumed exam or hiring date.
No production cloud ownership
A lab may demonstrate learning. It cannot be presented as responsibility for a production platform.
Unconfirmed vacancy requirements
Cloud-support titles vary. Check the actual work, change approval and incident expectations.
No verified recovery example
The fictional inputs do not establish that Alex can recover a cloud service. Record the limits and choose a supervised or sandbox check.
An honest aside
Keep the support experience visible. Explain one investigation and one useful handover before adding another list of tools. The next task should answer a gap in a vacancy, not manufacture an impressive title.
Section 03
Compare vacancies, confirm supervision, complete one bounded task and revisit the gaps. These are decision checkpoints, not promised promotion dates. Repeat a step when the evidence or opportunity is missing.
Plateau zone
IT support
Now
Compare vacancies
Check
Confirm supervision
Ask
Bounded task
Practise
Review gaps
Review
Cloud-support applications
If ready
A cloud qualification will establish readiness for a cloud-engineering job.
An exam can support relevant study. The responsibilities, supervision and evidence in the vacancy determine whether this particular move is appropriate.
Why this matters for you
Alex has four study hours a week and no production cloud ownership. Choose one bounded gap rather than two platform exams.
Tradeoff spectrum · this route, not in general
where this plan sits
Section 04
If the chosen team uses Azure, use its administration syllabus to identify learning gaps. If it uses AWS, use the relevant AWS syllabus instead. Neither is a universal prerequisite. Before paying, check the current vendor requirements, full cost and whether the vacancy actually asks for the credential. Do not buy both simply to cover uncertainty.
How to read this section
Certs aren't a shopping list, they're a sequencing problem. Each card carries a verdict pill (top right) judging the cert against this move and your stage, not the cert in the abstract. Read the pill first, then the reasoning underneath. The order the cards appear in is the order to tackle them.
Use this platform's administration syllabus if the chosen team uses Azure. Practise a relevant task first, then check current exam requirements and total costs before booking.
Use the relevant AWS syllabus if the vacancy uses AWS. This is an alternative to the Azure study above, not a second required qualification.
Alex has not yet selected a platform or demonstrated the practical gap. Another exam would divide the four-hour weekly allowance without resolving that uncertainty.
Verdicts are judged against your target window and current stage. A "useful, later" today can become a "useful" once experience gates or prerequisites are cleared. Re-issue free within 30 days if your situation shifts.
Section 05
A larger certificate list could hide the same practical gap.
Study without a checked task
The certificate list grows, but Alex still cannot explain an access decision, a failed change or a recovery check. Keep the practical task small enough to finish.
Supervision assumed from the title
A vacancy labelled junior may still require independent incident work. Ask who approves changes and who takes an escalation before treating it as a supported move.
A plan that will not fit
Studying two platforms at once could exceed Alex's four hours a week. Prioritise one requirement and revisit the scope if the task repeatedly overruns.
The review checkpoint
Revisit the plan when the task is complete or the vacancy assumptions change. Repeating a stage is reasonable if supervision or evidence is still missing; elapsed time alone does not establish readiness.
“A lab should remain labelled as a lab.”
Section 06
No salary figures are inferred where the supplied context does not support them.
No figures given here, deliberately.
No offer, location or current salary was supplied in this fictional case, so no pay increase is inferred. Compare actual local vacancies, base pay, on-call terms and travel costs. Set an affordable minimum before accepting a move; a higher title does not settle the financial decision.
The shape
No salary figures are inferred: this case has no location, current salary or offer.
What moves you inside the band
Compare actual vacancies and total employment costs before deciding whether a move is affordable.
Section 07
Within the next week, compare the two vacancies and write one question for each. Next, complete a bounded task and record an expected result, a failure case and what changed. Review the route once those examples and supervision expectations are clearer. This is a proposed sequence, not a promised hiring timetable.
Check the supervision
Identify who approves changes and takes escalations. Treat unanswered questions as unknown, not as evidence of support.
Explain one checked task
Show the expected result, an unexpected observation and what changed. Separate personal contribution, reviewer input and remaining limits.
Keep the plan affordable
Stay within the four-hour weekly allowance and a budget Alex can sustain. Compare actual employment terms before accepting a move.
Last word
The support experience is a foundation. Use the next piece of work to discover what it supports, where help is still needed and whether the proposed role supplies that help.
TechWaymark
TechWaymark · 13 October 2026
Free re-issue within 30 days · techwaymark.com/verdicts
The sample illustrates the report format and the information behind a call. It is not evidence of customer outcomes. Open it when you want to inspect the detail before buying.
The call
The assessment, its assumptions and what would change it.
Where you stand
What your supplied experience supports and what remains unproven.
The route
A proposed sequence, dependencies and tradeoffs, with review checkpoints.
Certification rulings
What to study, defer or skip in the context of this move.
Failure modes
Where the plan could stall and which conditions to investigate.
Salary reality
Relevant pay context and its limits; no personal salary prediction.
Progression conditions
Practical priorities, evidence to gather and reasons to revisit the call.
Seven core sections, with supporting detail where useful. The PDF page count varies with the report.
Before you pay
What you get
A written dossier of seven sections, on screen as a private link and as a PDF. No account, no renewal.
When you get it
Usually within minutes of payment. Always within 24 hours. A draft that fails the writing checks is held rather than released as if it passed. You get an email either way. If 24 hours passes with nothing, you get a full refund.
How it is produced
The judgement layer is a practitioner-authored, rules-based framework informed by two decades across infrastructure, cloud and cybersecurity. Your inputs are assessed against that framework. A model writes the prose inside strict rules; it does not decide the call.
If it is wrong
Email and say so. Wrong inputs you could not correct at the time get a corrected dossier at no cost. If a verdict cannot be honestly written for your situation, or the dossier does not arrive, you get a full refund, no argument. Disagreeing with the call is not a fault; the verdict is meant to be argued with.
Your data
Your answers and email are held to produce and re-deliver your dossier, and for nothing else. No accounts, no profiling, no selling on. Your report, your inputs and your access link are kept for 24 months from purchase so you can come back to them. After that they are deleted and the link stops working. You can request deletion at any time. We respond without undue delay and normally within one month, and explain any records we must retain or any permitted extension.
What it will not do
It will not promise a salary, a timeline or a job. It will not hand you a course or a step-by-step roadmap. It is a point-in-time call on the route you described, and it is allowed to come back unwelcome.
Questions before buying go to contact. Terms and privacy sit on the legal page.
Partly, and worth being honest about. The judgement layer is human-authored: whether each cert is useful, where the plateau sits, whether the call is realistic, what the decisive factors are. The narrative around those calls is assembled by a language model inside strict style rules. If a verdict reads like generic AI content, that is a bug.
A verdict is point-in-time. It is the call on your route as you have described it today. If your situation changes, run the Guided Route again and request a fresh one. Recurring access to a static judgement would be dishonest.
No. After payment you get an email with a link that grants access on whichever device you open it on.
Your report, your inputs and your access link are kept for 24 months from purchase so you can come back to them. After that they are deleted and the link stops working. You can request deletion at any time. We respond without undue delay and normally within one month, and explain any records we must retain or any permitted extension.
How your information is handled
Price