Workflow demonstration / Resume evidence
Read the evidence. Keep the decision human.
Compare a fictional résumé excerpt with an explicit role criterion. This example organizes evidence and follow-up questions; it does not score, rank or reject people.
Simulation · fictional records · prepared outputs
01 / Select the context
Try the workflow
All records are fictional. Choices display prepared text locally; no model or integration is connected.
Fictional source record
Fictional résumé A, excerpt 1: “Built a React interface and a Node.js service for an internal inventory tool.” Excerpt 2: “Paired with a designer and wrote handover notes.”
Fictional résumé B, excerpt 1: “Wrote Python scripts to reconcile inventory files.” Excerpt 2: “Supported operations colleagues during a reporting change.”
Fictional résumé C, excerpt 1: “Created a React scheduling prototype and tested keyboard navigation.” Excerpt 2: “Documented open questions for the project reviewer.”
02 / Inspect the output
Prepared evidence note
Showing the first prepared example. Change the inputs to explore another.
Profile A · web development
- Role context
- Illustrative software role: deliver web features and collaborate with colleagues. No seniority or suitability conclusion is made.
- Source scope
- Two self-reported excerpts only; no references, code or employment history verified.
Technical delivery
Evidence: excerpt 1 names React and Node.js delivery. Follow-up: ask for a walkthrough of the feature, personal contribution and testing approach.
Team collaboration
Evidence: excerpt 2 names pairing and handover notes. Follow-up: ask how feedback changed the work and how colleagues used the notes.
Profile B · data operations
- Role context
- Illustrative software role: deliver web features and collaborate with colleagues. Transferable experience needs discussion, not an automatic rejection.
- Source scope
- Two self-reported excerpts only; web development is not described in this sample.
Technical delivery
Evidence: excerpt 1 describes Python reconciliation, not React or Node.js. Follow-up: ask about related web work or a relevant work sample; do not assume inability.
Team collaboration
Evidence: excerpt 2 mentions support during a change, without detail. Follow-up: ask what support involved and how questions or disagreements were handled.
Profile C · frontend project
- Role context
- Illustrative software role: deliver web features and collaborate with colleagues. Prototype work is not assumed to be production experience.
- Source scope
- Two self-reported excerpts only; backend delivery and team context are unspecified.
Technical delivery
Evidence: excerpt 1 names a React prototype and keyboard testing. Follow-up: ask about test coverage and any backend contribution; production use is unverified.
Team collaboration
Evidence: excerpt 2 describes documenting questions. Follow-up: ask how the reviewer responded and which decisions changed; team leadership is not established.
Start with the real workflow.
Discuss the process, its exceptions and who stays accountable—not a promise of automation.
Talk to Gary