A stack is not a decision.
Technology records list what was used. The reader wants to know what was chosen, what was refused, and what you were accountable for when it broke.
Three things this function leaves off the page.
None of them are missing from the career. They are missing from the document, which is the only version a reader ever sees.
The choice, not the change
Every migration in a senior record was chosen over at least two alternatives. The alternatives are the interesting part, and they are almost never on the page.
What you refused to build
A technology leader is judged as much on what they declined as on what they shipped. Nothing signals judgement faster, and nothing is omitted more reliably.
The operating model you set
How the function was organised, what it reviewed and when, and what triggered escalation. It is the closest engineering analogue to how a board itself runs.
Longer only on facts.
No adjective is strengthened and nothing is added to the career. What changes is which part of the sentence carries the weight.
“Led the migration to a microservices architecture and managed a 60-person engineering organisation.”
Two facts, no decision. The reader cannot tell whether you set the architecture or inherited it, and cannot size the organisation you ran.
“Chose to decompose the monolith rather than re-platform it, holding the availability commitment through the transition, and kept two systems bought rather than built — across a 60-person engineering function and its infrastructure budget.”
Nothing was added to the career. What was added is the alternative you rejected, which is where the judgement lives.
An illustrative composite, not a client. We do not publish client material, and your own lines are only ever rewritten from sources you supply.
The rule that bounds every rewrite. We will not write a claim your record cannot support. Ever. A claim without a source stays marked open in the evidence register and stays out of the résumé until you supply one.
Four readings that matter most in a technology record.
The seven dimensions are the same for everyone. Which of them usually carries the gap is not.
Scale you can name
Not "large scale". Requests, sites, environments, users, spend — whichever unit your part of the industry actually counts in.
Accountability under failure
What you were called about, what you could authorise without asking, and what you were answerable for afterwards.
A discipline, not a stack
A record organised around named technologies dates within two years. One organised around the decisions you are trusted to make does not.
The receiving dialect
Platform, infrastructure, SRE and architecture mean measurably different jobs from one company to the next. Alignment is being legible to the one you are writing to.