PlaysbyMoat8
Back to the library
The workflow guideHR

Match an experience summary to role requirements

Compare target vacancies with a person’s factual experience to improve a professional profile or application.

5 implementation stepsSimple

How this works

Compare target vacancies with a person’s factual experience to improve a professional profile or application. Use this when someone wants to adapt a professional profile or application to target roles. The workflow should make relevant experience clearer while preserving factual limits and avoiding invented achievements.

Extract recurring job-related requirements from selected vacancies, map them to verified experience and rewrite only supported sections. Separate missing evidence from genuine skill gaps. Every claim, date, qualification and result remains subject to the person's confirmation before sharing.

Before you start

Target roles

Choose representative vacancies or role descriptions.

Experience record

Collect factual work history, projects and qualifications.

Output format

Confirm the profile, résumé or application sections to revise.

Prepare the inputs

vacancies
Required

role text and date

Distinguish common requirements from one employer's preference.

experience_facts
Required

roles, dates, responsibilities and evidence

Mark uncertain metrics and unsupported claims.

existing_profile
Required

current document version

Preserve the original for comparison.

writing_constraints
Required

length, tone and required sections

Do not add facts merely to fill space.

Implementation, step by step

  1. Extract requirements

    • Group recurring competencies and concrete responsibilities across target roles.
    • Keep essential and preferred requirements distinct.

    Checkpoint: A target-requirement map exists.

  2. Map experience

    • Find factual examples supporting each relevant requirement.
    • Mark partial or absent evidence without manufacturing equivalence.

    Checkpoint: The mapping is traceable.

  3. Choose relevant examples

    • Prioritize experience that directly addresses the target work.
    • Retain scope and personal contribution rather than claim a team's entire result.

    Checkpoint: The profile has a defensible emphasis.

  4. Rewrite the document

    • Use clear action, context and outcome language where supported.
    • Leave unknown metrics out or phrase the contribution without a number.

    Checkpoint: A targeted draft is ready.

  5. Verify every claim

    • Compare revised text with the experience facts and ask the person to confirm it.
    • List unsupported requirements as development or clarification opportunities.

    Checkpoint: The final draft is accurate for sharing.

Decisions along the way

Requirement has no supporting experience

Do not fabricate it; identify a gap or transferable example honestly.

Metric is remembered imprecisely

Omit the number or mark it for confirmation in the draft.

Team achievement is supplied

Describe the person's contribution without taking unsupported sole credit.

What you will produce

targeted-profile.docx

DOCX or Markdown

A factual application draft adapted to the target roles.

Include: summary · experience · skills · qualifications · status

requirements-evidence.csv

CSV

A map of supported and missing evidence.

Include: requirement · experience_ref · coverage · question

Check the result

  • Verify dates, titles and qualifications against supplied facts.
  • Check numerical achievements have a confirmed basis.
  • Confirm target wording does not imply experience the person lacks.
  • Inspect the final document for consistency and unintended exaggeration.

When something goes wrong

Experience sources conflict

Ask the person to resolve the specific fact before finalizing.

Vacancy text is outdated

Use current role material or state its date.

Rewriting changes the meaning

Restore the factual scope and revise the phrasing.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Synthetic: adapt a profile for an analyst role.

Inputs

Target asks for dashboard reporting. Experience says the person maintained a weekly spreadsheet report for one team; no BI-platform experience or measured time saving is documented.

Expected result

Synthetic result: describe the weekly reporting responsibility accurately. Do not add a BI tool or claim a percentage efficiency improvement.

Run a small pilot

Start small

Adapt one profile to a small set of related roles.

Record the baseline

Record revision time and factual corrections.

Agree success criteria

Agree relevance and claim accuracy before preparing more applications.

Stop or revise

Stop if matching the vacancy requires unsupported qualifications or results.

Keep the scope clear

  • The workflow improves presentation of real experience rather than inventing credentials.
  • Drafting does not submit applications or contact employers.

Check before using

Do not invent experience, results, or qualifications.

Business activities

  • Deliver recurring client work
  • Support and develop employees

Editorially adapted workflow; not independently tested.

FROM A RECIPE TO YOUR WORKFLOW

Bring the company context together.

This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.

For this recipe: Target job descriptions · Verified experience · Existing profile or resume

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗