# Quantifying Honestly — Resume & GitHub Portfolio

Source: https://www.skillbyai.com/en/resume-portfolio/b-metrics

> Numbers when you have them, specifics when you do not.

## Real numbers or concrete detail

Numbers make impact concrete, but only **real, defensible** numbers. Good sources are dashboards, release notes, tickets, performance tests you ran and feedback you received. Approximate honestly ("about", "roughly") and be ready to explain how you measured. **Never invent metrics** or inflate percentages; interviewers often ask "how did you measure that?" and an invented number damages trust. When you have no metrics, use other concrete details: **scale** (number of users, services, records, teammates, if you know them), **scope** (end-to-end ownership), **who benefited**, **what it replaced**, or **qualitative outcomes** such as "adopted by two other teams". Respect confidentiality: do not reveal private business figures your employer would not want shared.

## Without a metric, add specifics

Fictional examples.

```text
No metric available? Use scope, users, what changed, or adoption.

Vague:     Improved the deployment process.
With data: Cut average deploy time from about 40 to about 15 minutes by
           caching Docker layers in CI (measured from pipeline logs).
No data:   Replaced manual SSH deploys with a GitHub Actions pipeline,
           letting any engineer on the 6-person team ship safely.

Vague:     Wrote tests.
No data:   Added integration tests for the payments module, which caught two
           regressions before release during the following quarter.

Ask yourself: Could I explain how I know this, in an interview?
```

## Keep a brag document

Keep a running private note of what you shipped, numbers you saw and feedback you got. It makes honest bullets much easier to write later.

**Quiz:** You improved a process but have no measurements. What should you do?

- [ ] Leave the bullet as "Improved process"
- [ ] Estimate a large percentage that sounds impressive
- [x] Describe scope, who benefited and what changed, without inventing numbers
- [ ] Copy metrics from a colleague's resume

*Answer:* Describe scope, who benefited and what changed, without inventing numbers. Concrete specifics are better than invented numbers.