The IT Director resume,
and the budget behind it.
An IT Director inherits an estate and a service level, and writes about neither. The page fills with platforms, certifications and vendor names, a parts list for a machine whose output is never stated. The CIO reading it wants one thing: what the estate cost to run before you arrived, and what it cost after.
What gets read first
The title covers at least three jobs. One runs infrastructure and the service desk and is judged on whether things stay up. One owns business applications and is judged on whether finance, supply chain and HR can do their work. One is a country or regional IT lead putting a group standard into a local market and fighting for the exceptions. A CIO hiring for the first will not spend an interview on a resume that reads like the third.
After that the reading is arithmetic. Seats supported, sites, annual run budget, the size of the application estate, and who signs the vendor contracts. Those figures place the job on a chart. Most IT Director resumes substitute a product list, which tells a reader what was installed but never how many people depended on it, what it cost to keep alive, or whether you had the authority to switch it off.
The estate in countable units: seats, sites, applications owned, annual run budget, and whether capital sat with you or with the CIO.
Which of the three IT Director jobs you held. Infrastructure and service, business applications, or a regional lead delivering a group standard into a market with its own regulator.
Contract authority. The value you could sign alone, which suppliers you owned end to end, and whether renewals landed on your desk or in procurement.
Whether any service figure appears at all. An IT Director who states no ticket volume and no restore time has left out the two numbers their own team publishes every Monday.
The numbers that carry weight
Nobody can prove what an outage would have cost, which makes inflated availability the easiest claim in this function to write and the easiest to disbelieve. Ratios and trends survive that problem. Each of the six below already existed in a system you ran, can be confirmed by anyone who sat near you, and means something to a reader who has never seen your architecture.
The share of spend going to change rather than to keeping the lights on, given for the year you arrived and the year you left, because a flat budget with a different internal shape is the strongest available evidence that an estate was reshaped rather than administered.
Cost per seat per year with the seat count beside it, because it is the one technology figure a finance director can compare across companies, and it survives a business that grew.
Tickets per seat per month and first-contact resolution, because together they separate a service desk that was redesigned from one that was simply staffed harder.
Priority-one incidents counted rather than availability quoted, with mean time to restore and the SLA you were held to, because a percentage averages away the week that mattered.
Applications retired against the starting count, with decommission dates and the licences cancelled behind them, because rationalisation is an argument with business owners and the count is the only scoreboard it has.
Supplier consolidation stated as recurring run-rate with contract numbers at both ends, because a one-off discount and a repriced multi-year agreement are different achievements and only one of them is still there next year.
Where these profiles go quiet
Three sentences appear on almost every IT Director resume. Each is probably true. None can be checked as written, and each has a checkable version that takes the same space on the page.
"Maintained 99.9% uptime across business-critical systems." Uptime means nothing without the measurement window, the exclusions and the SLA it was scored against. Give the incident count, the worst month, and what changed after it.
"Skilled in VMware, Azure, Cisco, ServiceNow, Fortinet and SAP." That is an inventory. Name what one of them bought: a cost that fell, a process that lost two handoffs, a site restored in twenty minutes instead of two days.
"Managed relationships with strategic technology partners." Managing a relationship is attendance. State the renewal you repriced, the contract you exited, or the supplier you replaced, and what the change was worth every year afterwards.
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 IT infrastructure and support operations for the organisation, ensuring high availability of critical systems.
Ran infrastructure and service desk for 4,200 seats across 11 sites on a $6.8M annual run budget. Tickets fell from 3.1 to 1.9 per seat per month over two years after fixing the five recurring causes behind a third of the volume. Priority-one incidents went from 23 a year to 6, and mean time to restore from 4 hours 10 minutes to 52 minutes.
Led the migration of the company's email and collaboration platform to Microsoft 365.
Merged three Microsoft 365 tenants into one following two acquisitions: 5,600 mailboxes in 9 months with no cutover window longer than 4 hours. Retired 2 on-premise Exchange estates and 14 file servers, removing $410k of annual run cost, and new-joiner setup went from 3 days to under 2 hours.
Rationalised the application portfolio and reduced software licensing costs across the business.
Cut the application estate from 214 to 128 in 15 months, each retirement carrying a named business owner and a decommission date. Cancelled 3,900 unused licences across 6 vendors and moved 4 contracts onto a single agreement: $1.2M off the annual run-rate, recurring, and confirmed in the following year's budget.