RoleSailor homeExplore the fictional sample

A practical evidence-review guide

Review a platform-engineering job against your evidence before rewriting your CV

For experienced technical professionals considering their next role. This English-first guide starts with one job passage and what your experience actually establishes.

Use your own records and judgment. This process does not independently verify career claims or predict hiring outcomes.

1. Review the evidence before changing the wording

  1. Keep the exact job passage. Copy a short passage without rewriting it. Retain the full job description and where you found it so you can read the surrounding responsibilities and qualifications.
  2. Find the closest career fact. Use a specific assertion from your project or career notes. Retain its source label. Separate your contribution from the wider team’s work.
  3. Separate fact from interpretation. Write down what the fact says, why you think it relates to the passage, and which details it does not establish. Related experience is a judgment you make.
  4. Record questions rather than fill gaps. Check your records or ask for clarification. If you cannot establish a result, date, scale or responsibility, keep it unknown instead of adding a plausible detail.
  5. Review each proposed draft claim. Keep wording no stronger than its source. Read the claim again after editing; a clearer sentence can still overstate what happened.

2. Work through a fictional platform example

FICTIONAL EXAMPLE · Alex Morgan and Example Studio are sample identities. These assertions are not independently verified.

Job source: Senior Platform Engineer · Example Studio

Build reliable internal platforms, collaborate with product teams, and improve the developer experience using TypeScript and PostgreSQL.

Exact passage to review: Build reliable internal platforms. Read the full fictional job source.

Career fact: Alex Morgan

Led a team of four engineers building internal developer tools.

Source label: Career notes · fictional example. Confirmed by the fictional candidate; confirmation records a self-assertion, not independent verification.

Interpretation: related experience

Leading a team building internal developer tools may be relevant to internal-platform work. That is a person’s interpretation, not an automated suitability judgment.

Unknown: reliability, scale and operational responsibility

The fact does not establish reliability results, service scale, incident response, on-call duties or ownership of production operations. Do not turn it into a claim that Alex improved uptime or operated a platform at a particular scale.

Missing evidence is not proof of a missing skill. It means this source does not answer the question.

Useful questions to record

  • What did the tools do, and which part did Alex personally lead or build?
  • Are there records of reliability work or results that Alex can accurately describe?
  • What operational responsibilities does this opportunity actually include?

Use these questions as review prompts. If no additional source is available, retain the original fact and leave the unanswered details open.

Return to the exact career fact · See the fictional evidence review

3. Check every claim before using a draft

  • Can I point to the career source for this sentence?
  • Does it describe my contribution accurately, including team context?
  • Is each number, date, technology, result and level of responsibility supported by that source?
  • Have I kept interpretation and unanswered questions separate from factual claims?
  • Did an edit add stronger wording that the source cannot support?
  • Have I reviewed the whole draft for missing contact details, career history and context before considering it ready to use?

A checklist is a review aid, not verification or approval. There is no ATS score, hiring-fit score or promise of an interview or job here.

Compare the fictional prepared draft excerpts. They are incomplete and unapproved; the follow-up example makes no claim of an earlier application or employer response.

Keep the limits visible

This is a manual preparation process. The guide does not send an application, collect career data or offer an export.

Keep unanswered questions visible and return to your sources when checking a new draft. Clear wording should preserve the limits of what you know.

Explore the fictional, read-only sample