# Managing Resume Versions — Resume & GitHub Portfolio

Source: https://www.skillbyai.com/en/resume-portfolio/t-versions

> Keep variants organised and consistent.

## One master, a few focused variants

Keep one **master resume** containing every bullet you might use, then create a small number of **focused variants** (for example backend, full-stack, data) by selecting and ordering bullets. Track which version you sent to which company, because interviewers will ask about what is on the copy they have. Some engineers keep their resume in a plain text format such as Markdown or LaTeX under version control so changes are easy to compare; a document editor with named copies works too. Whatever you use, keep facts (dates, titles, employers) identical across versions: only emphasis should change.

## Resume in a private Git repository

Commands shown for illustration; adapt to your own setup.

```bash
# a private repository for your resume source
mkdir resume && cd resume
git init
# files: master.md, backend.md, fullstack.md, applications.csv
git add master.md
git commit -m "Add master resume with all bullets"

# create a variant for a backend role
cp master.md backend.md
# edit backend.md: reorder bullets, trim unrelated projects
git add backend.md
git commit -m "Backend variant: lead with Spring Boot and Postgres work"

# tag what you sent so you can find it later
git tag sent-acme-payments-2026-09

# compare two variants
git diff --no-index master.md backend.md
```

## Keep an application log

A simple spreadsheet with company, role, date, resume version and status helps you prepare for each interview and spot which variants get responses.

**Quiz:** What should differ between resume variants for different roles?

- [ ] Job titles and dates
- [x] Which true bullets are included and their order
- [ ] Employers you worked for
- [ ] The degree you earned

*Answer:* Which true bullets are included and their order. Facts stay fixed; emphasis changes.