Most engineers have a vague sense of where they are in their career — roughly what level they’re operating at, roughly what the gaps are, roughly what they’re working toward. But “roughly” is usually not enough when the questions that matter get asked: in a performance review, in a promotion conversation, in a job search.

Career tracking is the habit of converting that vague sense into something specific and current. It doesn’t require a lot of time — 10-15 minutes a week, done consistently, produces a picture that is dramatically more actionable than the one you’d reconstruct from memory at review time.

This post is about what to track, how to track it without it becoming a burden, and what to do with the information when it matters.

What Career Tracking Is Not

Career tracking is not the same as task tracking. Knowing that you closed 14 tickets in a sprint is not career progress — it’s execution. Career progress is the layer above execution: what skills are you developing, what impact are you having beyond your immediate deliverables, what relationships and reputation are you building, and how does your trajectory compare to where you want to be in 12–24 months?

It’s also not a replacement for good performance review prep. It’s the input that makes good performance review prep possible. The engineer who tracks continuously writes a strong self-assessment in a few hours. The engineer who hasn’t tracked tries to reconstruct from memory and ends up with something vague and generic.

The Four Things Worth Tracking

1. Impact Evidence

The running record of contributions that have meaningful outcomes. Not a task list — a curated evidence set. The entries that belong here are the ones where:

  • You made a decision or created an artifact that changed how something was built or operated
  • You unblocked or accelerated someone else’s work in a meaningful way
  • You prevented a mistake or failure that would have had real consequences
  • You led or contributed to something whose outcome you can quantify, even roughly

For each entry: what you did, what the outcome was (or your best estimate), and what the scope was (your team, multiple teams, org-wide). Outcomes you can quantify are better — “reduced P99 latency by 340ms” is more useful than “improved performance” — but qualitative outcomes are worth logging too.

The goal is 2–4 entries per month. Most months, you’ll have more; slow months you’ll have fewer. The point is to capture things when they’re fresh, not to manufacture evidence that isn’t there.

2. Skill Development

A running log of what you’re learning and how your capabilities are changing. This is distinct from evidence because skill development is about future capability, not past impact.

The entries that belong here are:

  • A new domain or codebase you’ve started working in
  • A skill you deliberately practiced (public speaking, technical writing, system design in a new area)
  • A gap you identified and took action on
  • Feedback you received that you’re working to internalize

Skill tracking is valuable both for its own sake and because it connects the work you’re doing to the trajectory you want. If you’re trying to get to staff and one of the gaps is “cross-team influence,” and you’ve been deliberately taking on cross-team work for three months, your skill log is the record of that investment.

3. Relationship Map

Who do you have real working relationships with, and what is the quality of those relationships? “Real working relationship” means: they know your work directly, they would advocate for you if asked, or they provide a consistent source of feedback or context.

This doesn’t need to be exhaustive — it’s useful to track 15–25 relationships that matter most, with a note on how you met, what you’ve worked on together, and what the relationship status is. The relationship map has three practical uses:

  • It tells you where you have visibility and where you don’t (if no one above your manager’s skip-level knows your work, you have a visibility gap)
  • It identifies the relationships you need to build before a promotion or job search, not after
  • It surfaces relationships that are fading because you haven’t worked together recently — relationships that are worth maintaining with a deliberate touchpoint

4. Goals and Gaps

The clearest element to track: where do you want to be in 12 months, and what is the gap between where you are now and that goal?

Goals worth tracking at this level are typically:

  • A promotion or level change
  • A domain or technical capability you want to develop
  • A scope or responsibility expansion you want to own
  • A kind of work you want to get to do more (or less)

For each goal, write down: the goal, the current state, the gap, and what you’re actively doing to close it. Update this once a quarter, or when something meaningfully changes.

The gap list is the most honest part of career tracking. It’s easy to log evidence and feel productive. It’s harder to sit with “I’ve been saying I want to improve cross-team influence for six months and I haven’t actually done anything differently.” That discomfort is useful — it’s the signal that something in the plan isn’t working.

How Often to Update

Weekly (10 minutes): Log one or two impact evidence entries from the past week. Anything significant — a review that shaped a design, a conversation that unblocked a team, a decision you made that others relied on. While the context is fresh.

Monthly (20 minutes): Review the skill development log. Add entries for any new skills engaged this month. Review the relationship map and note any changes (new relationships, relationships worth refreshing).

Quarterly (60 minutes): Review goals and gaps. Update current state for each goal. Adjust priorities. Review the past quarter’s evidence and identify 2–3 entries that would be strong in a performance review or promotion conversation. Note any patterns in the gap list that need attention.

The quarterly review is the most important session because it’s when you get perspective on the trajectory, not just the individual entries. The weekly and monthly habits feed it.

Making It Lightweight

Career tracking fails when it becomes a system that requires maintenance. The most common failure mode is a complicated tool with lots of fields, categories, and views — it’s satisfying to set up and burdensome to maintain, and it gets abandoned after a few weeks.

The lightest workable version:

  • A running document with four sections (evidence, skills, relationships, goals)
  • Timestamps on every entry
  • No required format — just enough detail to be useful in 6 months when you’ve forgotten the context

The heaviest workable version is a structured tool (like VividMap) that organizes entries by category, connects evidence to skills and goals, and surfaces patterns over time. The extra structure is valuable if you’re actively managing toward a specific goal like a promotion, less necessary if you’re in a stable phase where you just want to maintain visibility into your trajectory.

Either way, the habit matters more than the tool.

What to Do With the Data

Before a performance review: pull the impact evidence from the review period. Identify 3–5 entries that demonstrate the scope and judgment required at your level. Write your self-assessment around those entries rather than trying to cover everything. Use the skills log to articulate what you’ve developed, and the goals/gaps log to frame your forward-looking section.

Before a promotion conversation: assemble the evidence for the promotion criteria as they’re stated at your company. The evidence log is your raw material. The relationship map tells you who should be advocating for you and whether you have the right coverage. The goals/gaps log tells you where the case is weak and what you need to address before making the ask.

Before a job search: the evidence log becomes your accomplishments list. The skills log tells you how to represent your capabilities. The relationship map tells you who can provide referrals and warm introductions. Having maintained these continuously means a job search doesn’t start with “I need to reconstruct my resume from scratch.”

During a 1:1 with your manager: bring one or two entries from the evidence log to share. Not as a status update — as evidence of the level you’re operating at. Over time, your manager’s picture of your work is shaped by what you surface to them, not just what they observe directly. The career tracking habit creates a natural cadence for surfacing what matters.

VividMap is a career tracking tool for Senior+ engineers. It organizes your impact evidence, skill development, relationship map, and goals in one place — with views that help you see patterns and prepare for the conversations that matter. See how it works.