Work & money · A fictional story
Can the work show it?
A job asks for more than “good with AI”. Open a work sample. What does it actually prove?
Match the evidence.
Fictional posting · Operations assistant
No excerpt pinned yet
Open a work sample.
“Check an AI-written summary against its source rows.”
Its contents will appear here, matched to the job requirement.
Open a file. Then switch the requirement and see what still holds.
This compares a fictional sample with a task. It does not predict a hiring decision.
Read the evidence matches
A fictional operations-assistant posting and an invented order-summary folder. Each excerpt supports a limited claim, not a hiring prediction.
Requirement: Check an AI-written summary against its source rows.
Course record: “Completed a short course: AI for operations.”
The record names a completed course. It does not show a source check. A worked correction would make that skill visible.
Review log: “Draft: “Every order shipped.” Rows 12–14: pending. Revised: “Three orders are pending.””
The sample catches and corrects one unsupported AI claim. It shows this check on these rows. It does not establish that every claim or file was checked.
Read-me file: “Open orders.csv, total the shipped rows, then compare summary.md. If totals differ, pause and ask the owner.”
The sample explains how to run a check. Instructions do not show the check actually being done. The review log supplies that example.
Requirement: Leave instructions another person can follow.
Course record: “Completed a short course: AI for operations.”
The record names a completed course. It does not show a handoff. The instructions themselves would make that work visible.
Review log: “Draft: “Every order shipped.” Rows 12–14: pending. Revised: “Three orders are pending.””
The sample records a specific correction. A correction does not give the next person a working sequence. The read-me supplies that example.
Read-me file: “Open orders.csv, total the shipped rows, then compare summary.md. If totals differ, pause and ask the owner.”
The sample gives a file sequence and a stop condition for a colleague. It shows written instructions. Whether someone else can follow them still needs a real trial.
A claim gets stronger when someone can inspect it.
A small finished example can make a skill easier to discuss. Show the work, the checks and the handoff, then be precise about what it demonstrates. One example never proves every part of a job.
Practice the evidence, not a hiring prediction
This is a fictional evidence-matching exercise. The posting and sample are invented. It does not assess the reader, predict hiring outcomes or certify a skill.
In a real application, use work you are allowed to share. Explain your contribution and the limits of the example, and remove confidential or identifying material. A claim about testing should point to a test, rather than relying on a fluent description of one.
All scenarios and outputs are invented. Choices stay in page memory and reset on reload. No real work, subscription, application or message is changed.