Worked example
A clearer next move.
This is a synthetic example, not anyone's workspace. The route is plotted by the real engine; the progress notes and evidence claims are invented so the fully populated layout can be reviewed. Nothing on this page is saved.
Your position
Build the bridge to cloud.
Your next seat is Sysadmin, with the study time you have recorded. Start with the evidence that step asks for, below.
- Target
- IT Support to Cloud Engineer, 2 stages
- Horizon
- Roughly 3 to 7 years from where you are now
How this is worked out
POST has not assessed your own evidence. What you see here is how this route usually runs, plus what you have written down yourself.
- 01You are hereIT Support
- 02Next seatSysadmin
- 03TargetCloud Engineer
Pick up here
Documentation you wrote that someone else used
One useful piece of work. Record what you did and what it demonstrates.
- Evidence recorded
- 1 / 8
- Work underway
- 1
- Progress journal
- 2
Self-reported, not assessed
Items you have started
Dated notes saved
Your next three moves
The nearest gaps on your own route, not the job titles at the end of it. Each one opens the checklist row it belongs to.
Documentation you wrote that someone else used
It is the cheapest proof that your work outlived your shift.
What good evidence looks like
Done when someone outside your own memory can read it, and you can answer questions on it in a Sysadmin interview: documentation you wrote that someone else used.
A build, rebuild or migration you ran, with the scope and the date
Scope and date are what turn a task list into ownership.
What good evidence looks like
Done when someone outside your own memory can read it, and you can answer questions on it in a Sysadmin interview: a build, rebuild or migration you ran, with the scope and the date.
Something from your IT Support work that a Sysadmin panel would count
Most sysadmins pass through support; the leap is autonomy, not skills.
What good evidence looks like
Done when someone outside your own memory can read it, and you can answer questions on it in a Sysadmin interview: something from your IT Support work that a Sysadmin panel would count.
Evidence, not a score.
What you have recorded is your own account of it. POST marks nothing as proven on your behalf.
- Done, self-reportedA recurring problem you removed rather than reprocessed
- In progressDocumentation you wrote that someone else used
- Not startedA build, rebuild or migration you ran, with the scope and the date
- Not startedSomething from your IT Support work that a Sysadmin panel would count
1 self-reported, 1 in progress, 6 not started. None of it has been assessed by POST.
View all 8 itemsYour monthly check-in
What changed since you last looked?
Use your own record of the work. No automated readiness score or market prediction.
- 1. Record one useful change
A task you owned, feedback you received, or a blocker you uncovered.
Add a dated note → - 2. Strengthen one example
Explain your decisions and the result. Label labs and remove confidential details.
Review my evidence → - 3. Decide the next move
Keep the route, adjust a constraint, or choose one manageable action.
Revisit my plan →
Prepare to explain your work
Practise a question for your target role.
Try an answer, compare the reasoning and choose an example from your own evidence. Technical references and follow-up questions help you check the detail.
Open interview practice →Your record of the work
Small steps. A visible trail.
Took over patching for the Windows estate at work.
Booked AZ-900 for October.
Since your last review
You recorded 1 evidence item you had not written down before. These are your own notes, not a POST assessment.You changed where you stand on 1 evidence item.POST widened or corrected its role registry since your last review, so the wording on some stages may read differently.Last note 28 Aug 2026: Took over patching for the Windows estate at work.My reports