Why senior CVs read two levels down
The gap between what you were accountable for and what you spent Tuesday doing. Most CVs document the Tuesday.
A CV that lists what you did will be read at the level of the person who does it. Seniority is not asserted by a title. It is inferred from the kind of problem the document keeps returning to.
This is the most common failure in the records of genuinely senior people, and it is rarely a writing problem. It is a selection problem. The wrong things were kept.
The tell is the object of the verb
Most advice fixates on the verb. At Director level and above the verb barely matters; the noun after it does all the work. When the object is a process, a system or a department, the line describes the function. When the object is a decision, the line describes you.
Managed the monthly S&OP process across the region.
Owned the regional S&OP call: one forecast, signed monthly, that the plants were held to and the P&L was built on.
The first names a meeting you attended. The second names the one decision in that meeting only one person could make, and what depended on it.
Remit goes first, task goes second
Remit is what you were answerable for. Task is how you discharged it. Almost every senior CV inverts the order, opening a role block with three task lines and burying the reporting relationship at the bottom, if it appears at all.
Give each role block a first line that settles the size of the thing you carried. A reader is trying to size you before they are willing to be interested in you, and they will do it from whatever sits nearest the top.
- What you were answerable for, in one clause.
- What you could decide or sign without asking.
- The span: budget, headcount, sites, geography, legal entities.
- Who you answered to, by role rather than by name.
- Over what period, because scope moves and readers assume the smallest version.
Head of Supply Chain. Responsible for planning, procurement, warehousing and logistics across India operations.
Head of Supply Chain, India. Eleven sites, 300 people, a 900-crore cost base. Single point of accountability to the Managing Director for service level and working capital.
The first lists the departments that reported in. The second states what you carried and to whom you answered for it, which is the question the reader actually had.
A reader is not asking what you did. They are asking what would have gone wrong if you had not been there.
Hands-on detail is not humility
Senior operators keep craft detail out of genuine pride in the craft, and it reads as the level at which the craft is done. One line of hands-on detail per role is a credential. Four lines is a role description, and the document quietly resets to the level that role description implies.
This matters more in India and the Gulf than people expect, because group structures inflate and deflate titles differently and experienced readers know it. Arguing about the title never works. A precise remit line settles it without an argument.
The same logic applies to tooling. Naming the systems you personally configured tells a reader where your hands were. Naming the systems you chose, funded and held someone accountable for tells them where your authority was. Both can be true; only one belongs above the fold.
A ten-minute pass
Print the document. Highlight every line whose grammatical subject is a process, a system or a department rather than a person. Those lines describe the function you sat in, not the seat.
For each highlighted line, ask two questions. What did I decide here, and what would have happened if somebody else had held the seat? Keep the three strongest answers per role and compress the rest into one line of context.
If you cannot answer the second question, the line is task. Task belongs in your evidence register, where it can support a claim under questioning. It does not belong in the top third of the page, where it sets your level for everything that follows.