The Senior Manager resume,
and the authority behind the title.
Senior Manager is the hardest title to write, because the reader is deciding whether you already work a level above it. The band means four people in one company and forty in another, so the words themselves carry no information. What the page must establish is not what filled your week, but what you were allowed to decide.
Locate the band before describing the job
A director reading this page is comparing you with other senior managers and, quietly, with people already one level up. That comparison needs coordinates. Who you reported to by title, what titles reported to you, and what you could commit without a signature above yours will place the role in under ten seconds. Three paragraphs of description will not.
The second coordinate is reach. Somebody who worked only inside their own function reads as a strong individual contributor with a team attached. Somebody who delivered across functions, sites or markets reads as a director in waiting, and the difference is usually one sentence that never got written.
The title above you and the titles below you, which locates the band across companies where identical words describe different sizes.
Budget owned outright, kept separate from budget you influenced, with the amount you could approve alone.
Whether you hired, rated, promoted and exited people yourself, or recommended and had somebody else decide.
The functions, sites or markets your work reached beyond your own, because scope that stops at the team boundary is what keeps a good senior manager at this level.
Six things a director looks for
None of these needs a bigger job than the one you had. They need the parts involving judgement to be visible, which is where most resumes at this level fail: they record activity, because activity is easier to remember than the moments authority got used.
The largest decision you took without escalating, with its value and your approval limit, because that pair says more about seniority than any headcount.
Budget owned with the year-end variance against it, because landing within 2% of a plan you built yourself is a different skill from spending what you were handed.
People hired, and people managed out through a formal process, because the second is the part most avoided at this level and every director reading knows it.
The forum you presented in and how often, because a monthly review with your director plus two appearances in front of the executive team price your visibility exactly.
Delivery across functions that did not report to you, with the number of people involved and the sponsor named, because that is the working condition of every job above yours.
One metric your team owned end to end, at both ends, with the mechanism that moved it, because the mechanism is what a director tests to see whether you understood your own result.
Task sentences, and what they cost
Each line below describes what occupied the week. None describes a judgement. Written this way, an experienced reader files the page at the level it claims rather than the level it deserves.
“Responsible for the team's day-to-day operations.” That is attendance. Name the decisions that ended with you and how often they arrived.
“Collaborated with cross-functional stakeholders.” Collaboration is the floor, not the achievement. State what you were accountable for delivering through people you could not instruct.
“Supported the director in delivering the annual plan.” Supported places you a level below where you are asking to be read. Say which part of the plan was yours and what it produced.
Three lines, rewritten.
The same fact, made checkable. Every figure is illustrative of the shape an evidenced line takes — nothing here is invented on your behalf.
The claim on the left is not wrong. It is simply unreadable as evidence: nothing in it can be checked, compared or priced. The version on the right makes the same statement in a form a search partner can act on.
Managed a team of 8 and supported delivery of departmental objectives.
Ran an 8-person team with 2 team leads reporting in and 19 people beneath them. Owned a $2.4M operating budget with authority to commit $50,000 unaided, and closed three consecutive years within 2% of plan. Hired 11, promoted 3, exited 2 through a formal process.
Worked with product, operations and finance to improve customer onboarding.
Led the onboarding rebuild across product, operations and finance — 14 people, none of them mine — sponsored by the operations director, with a decision at each of four stage gates that was mine to take. Time to first order fell from 21 days to 9, and 90-day churn on new accounts from 14% to 6%. Two scope items I cut in month 3 have not been reinstated.
Handled escalations and reported progress to senior leadership.
Presented monthly to the review chaired by the operations director, and twice to the executive team: once to get $600,000 of automation approved, once when the November backlog reached 4,000 cases. Cleared it in six weeks by moving five people off project work and renegotiating two customer service levels, both decisions taken without escalation.