A pack someone else can inspect.
Connect one requirement to a small investigation, then export the reasoning, source files and replay instructions.
Make your first pack
Confirm one requirement
Choose a specific skill to demonstrate. Add the wording in Role map, check its meaning and priority, then save it.
Run and explain the rollout lab
Run the baseline, change the settings and test again. Explain your reasoning and assistance, then save the run with its eight replay files.
Inspect what you will share
In Review & export, select your artifact, preview the pack and download the ZIP. Check the files and limitations before sharing.
Work is saved in this browser when storage is available. Keep a backup and export source files before clearing browser data. The lab runs a simulation; it does not certify a skill. Opening this guide never replaces your work.
Make your experience inspectable.
Start with a role. Connect each requirement to work you can explain.
Target role
Keyword suggestions need your judgment. “Not required” is still a match.
Practice areas & other constraints
Requirement → evidence
0 linkedAdd one specific requirement at a time. Confirm its meaning before linking an artifact.
Add or edit a requirement
Practice an operational decision
Browser rollout lab + three Python labsBuild your evidence
Keep the observation, decision, and test together.
Recover a failed rollout.
A new release fails readiness. Keep three replicas available and recover the previous release when the candidate fails.
No cluster, cloud resources or network probes are used. Unsaved lab settings and results stay in this tab until you save an artifact. The replay requires Node.js 20 or newer, with no packages to install.
1. Observe the failure
The starting configuration probes /health:8080, permits one unavailable replica and does not retain the old artifact.
2. Make and test a change
The v2 app serves readiness on /ready:8080. Surge capacity is reserved. The recovery target is the known-good v1 release.
Baseline
Your latest run
3. Save reproducible evidence
Both failed and passing attempts are useful. Explain your reasoning and any assistance. Saving adds a new artifact, your connection, and eight replay files; it does not certify a skill.
Run the baseline and your configuration before saving.
Investigation record
0 / 6 writtenWritten sections measure completeness, not capability. Include tests someone can reproduce.
Give each claim a source.
Record an artifact, then explain exactly which requirement it supports.
Add an artifact
Connect requirement to artifact
A link is a self-reported claim. Explain its scope; it is not a verification badge.
Your artifacts
Evidence links
Build a pack someone can inspect.
Choose the evidence to include, inspect the shared view, and download a self-contained pack.
Share an evidence pack
The ZIP includes your role title, confirmed requirements, selected linked artifacts, explanations, limitations and selected source files. Private requirement notes, applications, job description, exercise drafts and reviewer identities stay out. Review the content before sharing.
Attach source files
Text source files only. Up to 2 MB each and 10 MB total. File checks do not guarantee that content is free of secrets; inspect your files yourself.
Opening browser file storage…
Choose artifacts to share
Handoff check
File hashes identify exported bytes; they do not verify authorship. Recorded reviews are excluded from this handoff. Attach files again after editing an artifact.
Private workspace preview & review records
Record a review
Use with the reviewer’s permission. Attribution is entered by you; identity is unverified.
You can build and export on your own. The recruitment kit includes an opt-in request and a 15-minute review guide.
Evidence pack
Full workspace text includes your drafts and private context. Use the selected ZIP handoff above for sharing.
Keep track of what happens next.
Record applications and whether you shared a pack. Look for questions to test.
Add or update an application
Application outcomes have many causes. These records cannot show that a pack caused an interview or offer.