Work History
Your role, actions, outcome, dates, skills, and supporting sources stay together.
Save your work.Reuse it in every application.
Save the work, your contribution, the outcome, and the source together so the details can be reused later.
A resume is the short version. Keep the evidence behind it.
Project details disappear long before the work loses value. Work History keeps your decisions, contribution, outcome, and sources ready for the next resume, application, or interview.
Bring in the materials you already have
Add notes, docs, links, GitHub work, Notion pages, or AI session summaries. refresh.cv turns them into editable records of what you did and what changed.
Write manually
Type what happened: the goal, what you did, what changed, the dates, skills you used, and links that support it.
Files
Upload a brief, report, slide deck, screenshot, meeting note, or retrospective. We’ll turn the useful details into a draft.
Saved resume
Choose an existing experience or project. Add the background, your contribution, results, and proof that did not fit.
Notion
Choose pages that show your role and results, such as plans, decision logs, launch notes, research, or retrospectives.
GitHub
Choose a repository, pull request, issue, or commit. We’ll capture the problem, what you changed, and what shipped.
MCP
After an agent finishes a task, ask it to save the task, key decisions, result, and links to the finished work.
Apps you can connect with MCP
Connect your account, then ask the app to save a completed conversation or task to Work History.
ChatGPT
Codex
Claude
Claude Code
Cursor
Cline
Poke
OpenClaw
OpenCode
Hermes
See the guides for each app’s setup and access requirements.
What goes in a Work History record
Start with rough notes. Capture what happened, what you did, what changed, and where the proof lives. You can edit the record later.
- Context
- Where and when the work happened, who it was for, the goal, and why it mattered.
- Work
- The problem you faced, the constraints, the decisions you made, and the work completed.
- My part
- What you personally owned and did, who you worked with, and the skills you used.
- Outcome and proof
- What changed: numbers, shipped work, or lessons, plus links that support the result.
From source material to a saved record
Choose the evidence, check the draft, and save only what is accurate.
- Pick your sources
Select the notes, files, Notion pages, GitHub work, or completed agent task that shows the work. Remove confidential details first.
- Check the draft
Check the title, company or project, dates, your work, your contribution, results, skills, and source links. Fix names and numbers.
- Save the record
Save the version you can support. Keep it editable and reuse only the relevant details in each resume, application, or interview.
Use one record across the next application
Choose the evidence that fits the task instead of reconstructing the same project from memory each time.
People from these schools and companies are already here.
Frequently asked questions
Work History keeps detailed records of completed work. A resume uses only the parts that matter for a particular application.
Start manually or use files, notes, a saved resume, a Notion page, a GitHub repository, or material from an authorized AI or MCP session. Review the generated title, work, action, result, dates, skills, and source references before saving.
Use only material you are allowed to process. Remove employer, client, project, and personal secrets, and keep a concise source note that supports the claim without copying restricted content into the record.
Add the project, your role, what you did, the result, dates, skills, and any useful file or link.
Yes. Import a supported file or connected source, then review and edit the draft before saving it.
Yes. Choose a relevant record and bring only the details you need into the resume or interview answer.
Save the work before the details fade.
Create one record now and reuse it in your next resume, application, or interview.