CTO
Resume Metrics

Lean on qualitative metrics. A hard figure is ideal, and scope plus direction carry weight even alone. Saying you built the company's first engineering org, steadied a team through a rough reorg, or set the architecture standard every team now follows all read as real leadership, and none of those need a number you do not have. The qualitative cards up top give a worked example for each.

They can, when it is a sound estimate you stand behind. If you remember the org roughly doubling after a reorg, with no saved headcount snapshot, "grew the org about 2x" works. Lean on relative percentages while the raw figures stay locked. The single check: you can talk a board through how you reached it.

Never. An invented number falls to pieces the minute anyone digs in, and CTO figures invite digging: a board member may ask how the budget you cut was measured or which teams adopted the standard. A single bogus stat can tank an otherwise solid interview. Use a qualitative point instead; it reads honest and still does real work.

Not every one. Keep a figure on the few bullets carrying the most heft in your most recent role, the ones a recruiter sees first. Stamp a number on every row and the solid ones blur into the clutter, and you slide into padding with thin ones. A few you can vouch for beat a page full of filler.

Use whichever hits harder while keeping it honest. A wide relative shift reads cleanly in percentage form ("cut cloud spend 40%"); a sizable raw figure stands alone ("a $22M engineering budget"). Drop a naked percentage that has no reference point, as "improved efficiency 40%" just prompts the question of compared to what. When possible, give both: "lifted margin 12 points, from 58% to 70%."

They do, and those numbers sit nearer at hand than most first-time CTOs expect. The team you grew before the title, the roadmap you shipped, the uptime you held, or the budget you managed as a VP or director are all reachable from the role you ran earlier. Company-scale revenue figures are not the bar; evidence your leadership moved something is.

Most of it is closer than you think. Delivery and uptime sit in your engineering dashboards and incident history; headcount and retention are in your HR system; budget and cost live in finance reports; revenue impact shows in the company's own metrics. If that work sits well behind you, give a careful honest estimate and own that openly.

One does it. A lone headline figure up high, the org you scaled or your biggest revenue or reliability win, earns you those first ten seconds. Leave the others to the work-experience lines and keep the summary easy to skim. The CTO resume guide covers shaping that summary.