How I keep track of my resume so I'm never scrambling

For years my resume only existed in one place: a single file I opened maybe once a year, right before I needed it. Which meant every time I opened it, I was trying to remember what I had actually done over the past twelve months. Half the details were already gone.

That's the problem with treating your resume like an emergency document. You only touch it under pressure, so you're reconstructing your own year from memory instead of just writing down what happened.

The fix was embarrassingly simple. I started keeping a running list.

---

A living doc, not a finished one

I keep one document, always open in a tab somewhere, that isn't formatted like a resume at all. It's just bullet points under rough headings, whatever I'm currently working on. When I ship something, fix something painful, learn a new tool, or get a piece of good feedback, I add a line. Takes thirty seconds.

It doesn't matter where you keep it. A doc in your browser, a plain notepad app, a note on your phone, anything works, as long as it's somewhere you'll actually open again and you make a habit of saving it. The tool isn't the point. The habit of writing it down before you forget is.

I'm not trying to write good resume copy in the moment. I'm just capturing the fact before I forget it existed.

Write it down while it's still true

The details that make a resume line actually convincing are the ones you lose first. Not "improved performance" but "cut load time from 4s to 1.2s by doing X." Six months later I don't remember the number. The week it happened, I do.

So the rule I follow now: if something feels worth mentioning, I write it down that day, not at review time. To make that easier, I try to capture a few things every time, not just "what I did":

• The before and after number. For engineers that might be load time or error rate. For PMs it could be adoption rate or churn. For designers, task completion rate or support tickets. For QA, bugs caught before release. Whatever the thing actually measures, not "faster" or "better," the actual before and after.
• The scale. How many users, requests, records, teams, or stakeholders this touched. "Redesigned the onboarding flow" hits different next to "for 40k monthly active users" or "across 3 product teams."
• The time saved or time it took. Hours shaved off a build, days cut from a release cycle, weeks trimmed from a hiring or design process, or how long the project itself took. Time is a metric everyone in tech understands instantly, whatever your role.
• Who else was involved. Solo work reads differently than work you led or coordinated across teams. Worth noting at the time, not reconstructing later, and this applies whether you're an IC, a lead, or working cross-functionally with design, product, or data.
• The tool or method, in one phrase. Not the whole implementation, just enough that future me remembers how, not just what. A framework, a process you introduced, a tool you rolled out, anything that explains how the result happened.

I don't always have all five. Some weeks it's just a number and a sentence. But even a half-filled line with a real metric beats a fully-formed sentence with no number in it, because the number is the part I can't fake later.

And you don't need to word it perfectly in the moment either. Once you've got the raw numbers, you can hand them to a tool like Claude and ask it to turn them into a clean resume line. The AI can shape the sentence. It can't invent the metric. That part's on you, and it's the part worth protecting.

Sort it later, not now

I don't organize by job title or category while I'm capturing. That's a different task and mixing the two just slows down the logging. I dump everything into the running list, and only when I'm actually updating my resume do I go back, pick the strongest lines, and shape them into something polished.

Revisit it on a schedule, not just when job hunting

Once a quarter I skim the list and turn the best entries into real resume bullets. Even when I'm not looking for anything. It keeps the resume current, and it means I'm never starting from a blank page when an opportunity actually shows up.

---

None of this is complicated. It's just the difference between recording your work as it happens versus trying to reconstruct it later under a deadline. The version of me who used to panic-update her resume the night before an interview would not believe how much time this saves.

If you don't have a system yet, start small. One doc, one running list, thirty seconds whenever you do something worth remembering. Future you will be relieved you did.

---

Let me know in the comments if you'd want a follow-up post on how to actually write or format your resume once you've got the raw material.