The IT director who runs enablement for the business
$327,300top of the range in Washington · middle $175,140 / yr
AI is transforming this role
IT Directors in the United States earn a median of $175,140 a year. Pay starts near $107,550. Pay reaches $327,300 at the top of the range in Washington, the best-paying state for this work among those with at least 500 people in the job.
Source: U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics, May 2025 (Computer and Information Systems Managers, SOC 11-3021). Last checked 9 September 2026.
Entry level
$107,550
Top of the range · Washington
$327,300
Education
Bachelor's degree in IT; MBA preferred
Wages — U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics, May 2025 (Computer and Information Systems Managers). Top of the range is the highest state-level figure among states with at least 500 people in the job. AI-impact rating is PayCrunch's editorial assessment. Updated September 2026.
🆕 New & Trending AI Tools for IT DirectorReviewed September 2026
We track new AI-tool launches every week and refresh this list — here’s what’s gaining traction for IT Director work right now.
Claude CodeNEWFree / usage-based
Terminal coding agent that reads your repo, runs tests, and ships multi-file changes.
How an IT Director uses it: describe a feature and let it implement and test it across the codebase
OpenAI CodexNEWIncl. w/ ChatGPT plans
Agent that runs longer, deterministic multi-step coding jobs on its own.
How an IT Director uses it: delegate a well-defined build or migration and review the finished result
WindsurfNEWFree / $15 mo
Agentic IDE that keeps context across a whole project.
How an IT Director uses it: make large, coordinated changes without losing track of the codebase
AWS KiroNEWPreview / see site
Spec-driven coding agent that turns written specs into working code.
How an IT Director uses it: write the spec first and let it build to that spec
NotebookLMNEWFree / $7.99 mo
Google tool that answers questions grounded only in the documents you give it — with citations.
How an IT Director uses it: load your own manuals, policies, or PDFs and ask questions that stay accurate to the source
CursorFree / $20 mo
AI-native code editor that edits across an entire project.
How an IT Director uses it: describe a change in plain English and let it rewrite and refactor whole files
GitHub Copilot (Agent Mode)$10–19 mo
AI pair-programmer built into VS Code and GitHub that now completes multi-step tasks.
How an IT Director uses it: hand off a task and have it plan, edit multiple files, and open a pull request
ChatGPTFree / $20 mo
The most-used AI assistant — writing, analysis, research, and images from a plain-language chat.
How an IT Director uses it: draft emails and documents, summarize long files, and get instant answers to on-the-job questions
ClaudeFree / $20 mo
AI assistant known for careful writing, long-document analysis, and coding.
How an IT Director uses it: analyze big reports or spreadsheets and turn messy notes into clean, finished writing
The executive staff meeting starts while the overnight incidents are still being sorted. Finance wants the variance. Operations wants a date. The chief executive wants to know whether the customer project is actually going to ship. An IT director is in that room because the job is larger than any one team. Several managers report in. One budget has to cover them. The director is the person who can say, in plain language, what technology will deliver, what it will cost, and what is at risk.
Several teams and a single set of priorities
A director's week is a conflict among reasonable teams. The infrastructure manager needs a maintenance window. The applications manager needs that same window to launch a feature the sales team already dated. The support manager is carrying a backlog that will get worse if either plan slips. Security or data may sit in the group as well, each with a mandate that can stop a launch. The director does not do all of their jobs. The director decides the order, names the trade, and stays with the decision when someone is unhappy. Leaving the teams to negotiate it alone feels collaborative and usually produces a delay nobody owns.
The practical tools are ordinary: a portfolio of projects, a staffing picture, a risk list, and a rhythm of one-to-ones with the managers. In those conversations the director listens for what is stuck, what is quietly failing, and what a manager is afraid to say in the larger room. Then the director clears obstacles that sit above a single team: a vendor contract, a hiring freeze, a dependency on finance or on a business sponsor who has gone silent. Hands-on technical work still happens in small companies, where the director may review an architecture or sit in a serious incident. In a larger company the failure mode is the opposite, a director who never understands the systems well enough to challenge a confident manager. Both extremes hurt. The job is enough technical fluency to see through a status report, and enough distance to run more than one function.
People decisions dominate. Hiring a weak manager multiplies across every person on that team. Keeping a strong manager who cannot collaborate taxes the rest of the organization. The director coaches, reassigns, and sometimes removes. That work is slower than a technology choice and more consequential. A director who hides inside projects and avoids the personnel file will be surprised by attrition and by quality problems that were visible to everyone except the top of the org chart. The teams experience the director mostly through their own manager. If those managers cannot explain the priorities, the director has not led. The all-hands speech will not repair that.
Scope should be visible on a chart. Typical clusters are applications, infrastructure, and support, sometimes with security, data, or program management alongside. A company may use different names. What matters is that more than one team, with more than one manager, rolls to this seat, and that conflicts between them land here. A single-team leader who shares the word director on a business card is doing a different job. When you evaluate an offer, count the managers, the headcount, and the functions. The title is cheap. The span is the work.
The budget you will have to defend
The budget is the other half of the authority. It covers people, vendors, software, equipment, and the projects the business has asked for. The director builds it with the managers, then defends it with finance. A credible budget separates what keeps the current systems running from what changes them, and it says what happens if a request is cut. Wish lists that treat every project as mandatory get trimmed by someone who understands the company less well than you do. You would rather do that trimming yourself, with a sentence about risk the chief financial officer can repeat.
During the year the budget is a management tool, not a souvenir of the planning cycle. Vendors renew. Projects slip. A team runs hot on contractors. The director sees the variance early and chooses: delay a project, renegotiate a renewal, or ask the executive staff for a change. Surprising finance in the last month is how technology leaders lose the next planning cycle. The managers underneath need a clear number they can spend and a rule for what must come back up. A director who approves everything informally, then acts shocked by the total, has not run a budget. The spreadsheet will say so even if the meeting is polite.
Capital versus day-to-day spending matters in the conversation with finance, and so does the contract you are willing to sign. Multi-year software deals can look small in month one and dominate the plan later. The director reads those deals, asks what leaving would cost, and refuses to let a single team lock the company in without a review. Procurement and legal are partners here. Using them is a sign of control, not a delay to be embarrassed about. The executive staff will ask, eventually, why the company is paying for three tools that do one job. Have the answer before they do.
What you say in the executive staff meeting
The meeting is the job, not a side appointment
The executive staff meeting is where the director sits with finance, operations, and the other department heads. The report is status, risk, and cost. A director who cannot be clear there will be managed by the people who can, regardless of the org chart.
Prepare as if the room has a short span of attention and a long memory. Lead with the decisions you need and the risks that can hurt the company, not with a tour of every ticket. Translate outages into customer or operational impact. Translate project slips into the business date that moves. Translate a hiring gap into the work that will not get done. Bring a recommendation. A director who only brings problems trains the room to tune out, and a director who only brings good news trains the room to be surprised later. Both habits are expensive.
The rest of the room has its own pressures. The chief financial officer is protecting a forecast. The chief operating officer is protecting a promise to customers. A business-unit leader wants a feature and does not want a lecture about technical debt. You can acknowledge the pressure and still hold the constraint. Say what you can move, what you will not pretend is free, and what you need from them: a priority, a date they will actually defend, or a cut they will accept. After the meeting, tell your managers the same story you told the executives. A staff meeting that produces one message upstairs and a different message downstairs is how trust dies inside the department.
Incidents are the unscheduled version of the same skill. When a serious outage happens, the director coordinates communication upward and keeps the managers focused on restoration and on a factual timeline. Blame in the first hour is useless. A fuzzy timeline in the review the next day is also useless. The executive staff will ask what failed, who was affected, and what will change. You owe them answers that match the logs and the decisions, including your own. Leaders who rewrite the story to protect a favorite team lose the room permanently. The teams notice too.
How companies hire someone for that chair
There is no licence that makes you an IT director. The path runs through the work: an individual contributor in engineering, support, or applications; a manager of one team; then a director who has several teams, a budget, and the executive staff meeting. Some people arrive from consulting with a record of running programs inside clients. Some are promoted when their company grows and the single manager seat splits. The evidence is the same. You have managers who improved under you, a budget you can explain, and a business leader who will say you told the truth when a date slipped.
Searches are often run by the executive you will report to, with a recruiter who knows technology leadership. The materials that matter are a resume that names span, not tools: headcount, number of managers, size and character of the budget in words finance would accept, and two or three outcomes. In the interviews you will meet peers, a finance partner, and sometimes the board's audit or technology interest if the company is large. They will test whether you can disagree without theater. Bring a story about a cut you recommended, a manager you coached through a hard performance issue, and a project you stopped. Anyone can describe a launch. Fewer people can describe a no.
Read the offer for the actual span. Who reports to you. Whether security is in or beside your group. Whether you own the budget or merely advise on it. Whether you have a seat in the executive staff meeting or a slot to present once a quarter. Those facts determine both the work and the pay conversation. A company that wants director judgment and offers manager authority will frustrate you, and you will frustrate them. Walk away from a title that is doing decorative work, or negotiate the authority until it matches the title. References should include a manager you led and an executive who sat in the staff meeting with you. They will be asked if the teams and the budget were really yours.
After the director seat, some people become a vice president or a chief information officer, with a wider portfolio and a closer tie to the board. Some prefer to stay a director in a larger, harder environment rather than take a top title in a company that is too small for the problems they want. Either path is coherent if the span keeps growing in reality. A move that adds prestige and removes the budget, the managers, or the staff meeting is a step into a different kind of job. Name that before you accept it. The market will not sort the titles for you.
May 2025 wages for this level of responsibility
The Bureau of Labor Statistics Occupational Employment and Wage Statistics for May 2025 reports wages for Computer and Information Systems Managers. Entry pay is $107,550. The national median is $175,140. The high end of the published range in Washington is $327,300, where the rolls were full enough for the Bureau to show a high end. From entry to the national median is $67,590. From the national median to that Washington high end is $152,160. Read those figures as a director: several teams, a budget, and a place in the executive staff meeting. A narrower seat should not borrow the top of the range just because the business card uses a similar noun.
State medians put California at $218,290, Massachusetts at $214,960, New York at $214,300, Washington at $209,370, and New Jersey at $203,460. California's median sits $43,150 above the national median. Puerto Rico's median is $99,780. The gap between the California median and the Puerto Rico median is $118,510. Separate Washington's two numbers before you negotiate there. The median is $209,370. The high end of the published range is $327,300. A median is typical pay. The high end is the top of the published range. Treating $327,300 as an ordinary Washington offer, or treating California's $218,290 median as if it were that high end, mixes statistics that do different work.
Put the figure next to the span. Someone stepping from a single-team manager role toward a first director seat can set $107,550 beside the offer and ask what, in this company, accounts for movement across the $67,590 toward the national median of $175,140. The honest answers are the number of managers, ownership of the budget, and whether you are in the executive staff meeting. A sitting director who already has that span can treat $175,140 as the national reference and then use the state median where the job sits: California $218,290, Massachusetts $214,960, New York $214,300, Washington $209,370, or New Jersey $203,460. The $43,150 difference between the national median and the California median is a relocation fact about the middle of the occupation, worth writing down before you move for a title.
The Washington high end of $327,300, which is $152,160 above the national median, belongs in the conversation only when the role is senior leadership in that market's published range: a wide span, a large budget, and executive responsibility that matches. Quoting it for a first director role in a smaller company ends the discussion. The $118,510 gap between California's median and Puerto Rico's median shows how far place moves typical pay. Bring the managers you have led, the budget you have defended, and a clear account of the executive staff meeting you have already survived. Then choose one number that fits the seat. Several teams and one budget are the job. The wage talk should describe that job, not a title floating above it.
The top of IT Director pay — and how to get there with AI
$327,300what IT Director pay reaches in Washington
Highest state-level top-of-range annual wage for Computer and Information Systems Managers, among states with at least 500 people in the job. U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics, May 2025.
And the role it leads to — Chief Executives — reaches $772,840 in Oregon.
$107,550entry$175,140middle$327,300top end
An IT director in the middle of this range keeps the systems running and the projects approved; the one at the top of the range has taught the whole organisation to use what it bought and can show what changed because of it.
Evaluating the organisation's technology use and needs, recommending upgrades, and assessing whether a data processing proposal is feasible are the tasks the title is defined by, and they are also where most directors stop. Buying a capability is not the same as installing it in how people work. Departments keep their old process and the licences sit unused. The directors who move up run the adoption themselves: they meet department heads and vendors, set what is permitted and what is not, train staff, and report on operations against a number that existed before the purchase. That is also the evidence an executive committee reads when deciding whether this seat is a cost or a lever.
Your playbook, by where you are now
Just startingFind out how work actually happens
Sit with three departments for a full day each and write down every workaround they use, because that list is your real requirements document.
Review the systems charts and programs you are approving closely enough to ask one hard question about each.
Keep the support queue in Atlassian JIRA categorised by cause, so you can see which recurring problem deserves a purchase.
Turn your vendor documentation into a study set with NotebookLM and be the person in the room who read it.
Run one clinic where staff bring their own tasks, and fix them live rather than delivering a presentation.
What proves it: A written account of how three departments actually work, with the workarounds named.
Realistic span: the first year in the seat
A few years inWrite the rules, then teach them
Publish what staff may and may not put into an assistant, with examples from your own industry rather than a generic warning.
Roll out Microsoft Copilot or an equivalent to one department first, train them properly, and measure a task time before and after.
Rebuild one high-volume process with Power Automate so the improvement is structural rather than dependent on enthusiasm.
Recruit and train staff who can teach as well as build, since an implementation team that cannot explain itself creates the next backlog.
Put the adoption numbers into your operational reports beside uptime, so the executive reads capability alongside availability.
What proves it: A department-level rollout with a measured before-and-after on a real task.
Realistic span: years two through five
ExperiencedOwn the portfolio and its return
Evaluate data processing proposals on what the organisation will be able to do afterwards, not only on cost and feasibility.
Negotiate with vendors from usage evidence, which is the only argument that reliably moves a renewal.
Build an internal curriculum so each new hire arrives into a trained department rather than a helpdesk ticket.
Retire the systems your own usage data shows nobody uses, and say publicly what that funded instead.
Take the executive conversation seriously, since Washington pays this occupation best and the chief executive route runs through directors who changed how a business operates.
What proves it: A technology portfolio review where you cut, kept and retrained on evidence you collected.
Realistic span: six years and up
The next 90 days
Choose one department in the next ninety days and take responsibility for what it can do, not just for what it runs. Spend a day watching how the work is really done and write down the tasks that eat the most hours. Time two of them. Pick the tool you already pay for that would change them, set the rules for using it in that specific context, and train the team in person rather than by email. Come back in six weeks and time the same two tasks. Bring the executive team one page: the tasks, the two timings, and what it cost. An IT director with that page is describing a capability the business now has, which is a different conversation from reporting that the systems were available.
Wage figures: BLS OEWS, May 2025. The playbook is PayCrunch editorial guidance, not a guarantee of pay or placement.
Every figure is the national median from the U.S. Bureau of Labor Statistics (OEWS) shown on that role’s own page.
Never used AI before? Start here (2 minutes).
Own the enterprise AI roadmap, this quarter. The highest-leverage thing an IT director can do now is define how the whole organization adopts AI: which use cases, which tools, what governance. Draft that roadmap and an AI-use policy, and get hands-on with Microsoft Copilot Studio or the Power Platform so you can speak to what is actually buildable.
Use Microsoft 365 Copilot for your own strategic work, Power BI Copilot for portfolio and spend analytics, and Claude or ChatGPT (enterprise plans, no confidential data in consumer tools) to structure strategy, business cases, and board materials. You own the strategy, the governance, and every decision; AI accelerates the analysis and the writing.
The one rule, forever: As you drive enterprise AI adoption, you own its governance: never roll out AI tools without data-governance, access, and security controls in place, and require human accountability for decisions AI informs. Never paste confidential business data, credentials, or PII into a consumer AI tool, and ensure every enterprise AI system has a named owner accountable for its security, compliance, and cost.
The plays — exact steps, exact prompts
Do these in order. Each one is copy-paste ready. You do not need to know anything about AI going in.
1
Own the enterprise AI adoption roadmap and governance
Why this pays: The single most valuable thing an IT director can own right now is how the enterprise adopts AI — the roadmap, the tool choices, and the governance. Leading that, rather than reacting to shadow AI, makes you the strategic center of the company's most important technology shift, the position that earns a CIO-track mandate.
Microsoft 365 CopilotMicrosoft Copilot StudioMicrosoft PurviewOneTrust
1
Define the enterprise AI roadmap — priority use cases, approved tools, and the governance framework (data controls via Purview, an AI-use policy, model and tool inventory via OneTrust) — so the organization adopts AI deliberately, not through ungoverned shadow use.
2
Draft the roadmap and governance with an AI-structured plan you own.
Copy-paste this prompt
Act as an IT strategy director. Draft a 12-month enterprise AI adoption roadmap for a [1,000-person company]: the priority use cases by business value and feasibility, the approved-tools and data-governance framework, the AI-use policy essentials, the org capabilities we need to build, and the metrics to judge success. Flag the biggest risks and the decisions that need executive sign-off.
Align the roadmap with business and security leaders before publishing; governance and buy-in make or break enterprise AI.
What you'll haveAn owned enterprise AI roadmap and governance framework — the strategic position that puts an IT director on the CIO track.
2
Ship internal AI copilots and agents that deliver ROI
Why this pays: A director is judged on business value delivered, not systems maintained. Building internal AI agents and copilots that automate real workflows produces visible, measurable ROI — the delivery record that separates a strategic director from a caretaker and justifies a bigger mandate.
Microsoft Copilot StudioMicrosoft Power PlatformServiceNow (Now Assist)Azure AI
1
Build internal copilots and agents for high-value workflows (HR and IT self-service, knowledge search, document processing) with low-code platforms (Copilot Studio, Power Platform, ServiceNow) grounded in governed data.
2
Pick the highest-ROI use cases with an AI-structured business case you own.
Copy-paste this prompt
Act as an AI product advisor for internal IT. We want to build internal AI agents for [employee IT and HR support and document-heavy processes]. Propose the top 5 use cases ranked by ROI and feasibility, the data and integrations each needs, the governance and accuracy guardrails, a rough build-versus-buy call for each, and how to measure value. Note where a human must stay in the loop.
Ground every agent in governed, accurate data and keep humans in the loop — a confidently wrong internal agent erodes trust fast.
What you'll haveInternal AI copilots delivering measurable ROI — the delivery record that marks a strategic director and justifies a broader mandate.
3
Cut IT spend with AI-driven FinOps and portfolio rationalization
Why this pays: An IT director owns the budget, and AI-plus-cloud spend is now a major, fast-growing line. Using AI-driven IT financial management to rationalize the application portfolio and control cloud and license costs frees budget for innovation — the fiscal discipline that earns executive trust and funds your roadmap.
ApptioFlexeraMicrosoft Power BI (Copilot)Microsoft Cost Management
1
Use IT financial management and FinOps tooling (Apptio, Flexera, cloud cost tools) with AI analytics to see true cost by service, spot underused licenses and cloud waste, and rationalize a bloated application portfolio.
2
Build the rationalization and savings plan with an AI-structured draft you refine.
Copy-paste this prompt
Act as an IT financial-management advisor. Given our [application portfolio and cloud and SaaS spend: paste a summary], identify the biggest savings opportunities (redundant apps, underused licenses, cloud waste, renegotiable contracts), rank them by savings and risk, recommend an action for each, and outline how to reinvest the savings into AI and modernization. Note where I must validate usage first.
Validate usage and dependencies before retiring anything; portfolio rationalization fails when a quiet dependency is cut.
What you'll haveA leaner IT budget and a rationalized portfolio that funds innovation — the fiscal discipline that earns executive trust and a bigger mandate.
4
Modernize service delivery and the AIOps strategy
Why this pays: A director sets the service and reliability strategy the whole IT organization runs on. Modernizing ITSM with AI and setting an AIOps strategy raises service quality and uptime across the enterprise — the operational excellence, at scale, that a director is measured on.
ServiceNowDynatrace (Davis AI)DatadogPagerDuty
1
Set the enterprise strategy for AI-modernized service management (ServiceNow with AI) and AIOps (Dynatrace Davis AI, Datadog, PagerDuty) — standardizing how the whole IT org detects, responds to, and prevents incidents.
2
Define the strategy and success metrics with an AI-structured draft you own.
Copy-paste this prompt
Act as an IT service-management strategist. Draft an enterprise strategy to modernize our IT service delivery with AI: the target service model (self-service deflection, AI-assisted agents, automated fulfillment), the AIOps approach for reliability, the platform and integration decisions, the rollout phases, and the KPIs a director should report (deflection, MTTR, uptime, cost-per-ticket). Flag the biggest risks.
Standardize on governed platforms and metrics; a fragmented sprawl of AI tools costs more than it saves.
What you'll haveA modern, AI-driven service and reliability model across the enterprise — the operational excellence at scale that defines a strong IT director.
5
Lead vendor and portfolio strategy for the AI era
Why this pays: A director owns major vendor relationships and technology bets, and AI is rewriting every contract and platform decision. Using AI to sharpen vendor strategy, negotiations, and architecture choices means better deals and smarter bets — directly protecting the budget and reducing costly lock-in.
SAP LeanIXClaudeChatGPTMicrosoft Excel (Copilot)
1
Maintain a clear view of the application and technology landscape (SAP LeanIX for enterprise architecture) and use AI to structure vendor evaluations, negotiation prep, and build-versus-buy decisions for AI-era platforms.
2
Pressure-test a major vendor or platform decision with an AI-built analysis you own.
Copy-paste this prompt
Act as a technology-sourcing advisor and devil's advocate. We are deciding whether to [standardize on one vendor's AI platform versus a best-of-breed approach]. Lay out the decision: the evaluation criteria (cost, lock-in, capability, integration, security, roadmap), the strongest case for and against each option, the negotiation levers, the key risks, and a recommendation. Challenge my likely biases.
Use it to structure and challenge the decision; the call and its consequences are yours, validated with the vendors and your team.
What you'll haveSharper vendor deals and technology bets with less lock-in — the strategic sourcing that protects the budget and the roadmap.
6
Master the executive narrative and the CIO track
Why this pays: An IT director's comp and trajectory track their scope and their ability to lead technology as a business. Using AI to translate IT into business value for executives and the board builds the strategic presence that earns a broader mandate, equity in some firms, and the path to CIO — where the top of the band and beyond lives.
ClaudeChatGPTGamma
1
Draft and pressure-test your technology narrative for executives, then make it your own.
Copy-paste this prompt
Act as an IT director's chief of staff. Help me write the technology update for our executive team. Raw points: [paste bullets on the AI roadmap, delivered ROI, cost savings, reliability, and risks]. Turn it into a crisp one-page narrative for non-technical executives: what we delivered in business terms, what is next, what I need from leadership, and the top risks I am managing. Confident, concrete, jargon-free.
Never paste confidential financials or sensitive data into a consumer tool; keep it high-level or use an enterprise plan.
2
Benchmark and negotiate your scope and title deliberately, and build the results (AI roadmap, ROI, savings) that make the CIO track credible — top-of-band pay comes from a broader mandate, not the title alone.
What you'll haveA business-framed technology story and a broader, CIO-track mandate — the strategic presence that carries an IT director toward $327,300 and beyond.
Your 12-month sequence to the top of the range
How the plays above stack into a path from median pay toward the $327,300 tier.
Month 1
Draft the enterprise AI roadmap and AI-use policy; get hands-on with Copilot Studio and the Power Platform.
Months 2-3
Ship the first internal AI copilot on a high-ROI workflow with governance guardrails.
Months 3-6
Stand up AI-driven FinOps; rationalize the app portfolio and free budget for innovation.
Months 6-9
Set the enterprise AIOps and service-delivery strategy; standardize platforms and metrics.
Months 9-12
Sharpen vendor and platform strategy for the AI era; renegotiate key contracts.
Year 2
Own the executive and board narrative and build the CIO-track case — toward $327,300 and beyond.
Gear for this job
As an Amazon Associate, PayCrunch earns from qualifying purchases. Links to books and tools are for the job on this page; we only recommend what we’d use in the work.
Same live Jossey-Bass 3rd already on high-school-teacher / middle-school-teacher / math-teacher / test-prep-instructor / substitute-teacher / science-teacher / music-teacher / drama-teacher / adult-education-teacher / corporate-trainer / instructional-designer / stem-teacher / pe-teacher / speech-teacher / curriculum-developer / education-consultant / college-professor / assistant-principal / financial-literacy-educator / school-principal / vice-principal / homeschool-consultant / school-administrator / edtech-specialist / education-administrator / distance-learning-coordinator / capitol-police-officer / tsa-agent / piano-tuner / birth-doula / dive-master / translator / voice-over-director / wordpress-developer / balloon-artist / circus-performer / nutritionist / academic-advisor / dermatologist / train-conductor / calligrapher / choreographer / motivational-speaker / marble-polisher / compensation-analyst / fleet-manager (ASIN 1119712610). This leftover page is BLS Computer and Information Systems Managers (SOC 11-3021); title is Teach the Whole Company Its Tools; H1 is The IT director who runs enablement for the business; few-years track is Write the rules, then teach them; the playbook centers writing the rules then teaching them, training a department properly, and building an internal curriculum so each new hire arrives into a trained department rather than a helpdesk ticket; start-here is Own the enterprise AI roadmap, this quarter; one-rule is As you drive enterprise AI adoption, you own its governance. Classroom technique for leftover company-wide / enablement / curriculum instructional work — not leftover Wong as the lead (that is spa-manager / admissions-director) and not leftover Praxis as a dump. Confirm 1119712610. Live page HTTP 200, no PC_GEAR / amazon.com/dp / tag=paycrunch-20 at 2026-09-18 4:37 AM PT. Source page: corporate-trainer.
Next steps for an IT Director
Some links below are affiliate or partner links. PayCrunch may earn a commission if you enroll or subscribe through them, at no extra cost to you. Wage figures on this page still come from the Bureau of Labor Statistics, not from these programs.
IT Director work is specific enough that a stamped 'check out these courses' block would be noise. BLS files this work as Computer and Information Systems Managers (SOC 11-3021). O*NET Job Zone 4 is typical: a bachelor's degree, so the honest next credential is a professional certificate or bachelor's-level coursework — not a random catalog dump.
The occupation's listed knowledge areas include Engineering and Technology and Personnel and Human Resources; the links search those subjects, not a generic 'career courses' list.
IT Directors in this dataset list Amazon Web Services AWS software among the tools in use, so a program that names that stack is a better fit than a survey course.
Coursera search for engineering and technology — a professional certificate or bachelor's-level coursework that lines up with management, not a generic professional-development aisle.
FlexJobs screens remote, hybrid, freelance, and flexible listings so you are not wading through unverified ads. This is a job-board search for IT Director work, not a claim that they list a counted SOC 11-3021 inventory.
Write an IT Director resume, or one aimed at Chief Executives, instead of a blank template. Resume Now is a resume builder; we are not claiming a counted template set for this SOC.
An IT Director resume that names the actual tasks on this page, or the step-up title Chief Executives, beats a blank template when you apply.
What IT Directors earn by state
These are the Bureau of Labor Statistics’ own figures for Computer and Information Systems Managers, state by state — not a cost-of-living adjustment applied to the national number. Only states employing at least 500 people in the occupation are shown, because a state median drawn from a handful of workers is noise rather than a signal.
California
$218,290
highest of them · +25% vs the national median
Puerto Rico
$99,780
lowest of the 50 states and territories that qualify · -43% vs the national median
The same job pays $118,510 more a year at the median in California than in Puerto Rico — 119% higher. That gap is what the Bureau measured, before any question of what it costs to live in either place. The top-of-range figure quoted at the head of this page, $327,300, is a different statistic in a different place: it is the 90th-percentile wage in Washington. The state that pays the typical worker most and the state where the best-paid go highest are not always the same one.
Source: U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics, May 2025, SOC 11-3021. 50 states and territories clear the 500-employee reporting floor for this occupation; those below it are left out rather than shown with a wide error band.
Free data. Use any of it.
PayCrunch publishes verified, BLS-sourced salary + AI-playbook data on 1,000+ professions — free, no signup.
No — it is transforming the role. AI cannot own technology strategy, set the portfolio and budget, lead the IT organization, or carry accountability to executives. What it changes is the agenda: enterprise AI adoption, governance, and spend are now the director's biggest levers. Those who own that shift become CIO-track strategists; those who do not stay caretakers of legacy systems.
What is the difference between an IT director and an IT manager?
An IT manager runs day-to-day operations and a team; an IT director sets strategy, owns the project and application portfolio and the budget, and translates business goals into the technology roadmap. In the AI era, the director's defining work is owning how the whole enterprise adopts and governs AI.
Is it safe to drive enterprise AI adoption?
Only with governance you own. Roll out AI tools with data-governance, access, and security controls in place, give every AI system a named accountable owner, and keep humans accountable for decisions AI informs. The director's value is enabling adoption safely — ungoverned shadow AI is the real risk you exist to prevent.
Is it safe to use ChatGPT for IT strategy work?
Not with confidential business data, credentials, or PII — those never go into consumer AI. Use enterprise tools with data controls, and reserve general tools for structuring strategy, business cases, and executive materials phrased without sensitive specifics. Modeling safe use is part of leading enterprise adoption.
How does AI actually raise an IT director's pay?
By expanding the mandate. Comp tracks scope and business impact. A director who owns the enterprise AI roadmap, ships internal AI with real ROI, cuts spend with FinOps, and frames technology as business value becomes the front-runner for CIO — which is what earns a broader mandate, equity in some firms, and top-of-band pay and beyond.
Methodology & sources
Salary (median, 10th, top of the range) — U.S. Bureau of Labor Statistics, OEWS.
By state — the Bureau of Labor Statistics’ own state medians, limited to states employing at least 500 people in the occupation. No cost-of-living arithmetic is applied to a wage anywhere on this page.
The plays — PayCrunch's own step-by-step guidance using publicly available AI tools. Tool names/URLs are real and current as of August 2026; prompts written to work as-is. Verify any professional output before relying on it.