Privacy-friendly analytics help us see which jobs people explore. They stay off unless you agree.Analytics off unless you agree. Details

Read the record
Back to the river
Skip to sources
Time Machine

IT managers

Official title Computer and Information Systems Managers (SOC 11-3021)

Also called CIO, Chief information officer, CTO, Chief technology officer, IT director

In brief

In May 2025, BLS counted 670,570 US IT managers, with median pay of $175,140 a year. Of the BLS counts since 2003, the May 2025 count is the highest. The earliest figure here is an estimate of 250,000 from 1980, not measured the same way as today's count. The last full technology era for IT managers: Cloud-native + CISO board elevation + digital transformation mandate, 2015 to 2023.

What the sources say

Official outlook

BLS projects employment to grow 15.8% from 2025 to 2035.

BLS Employment Projections 2025-35

AI exposure studies

  • 56.1% of this job's tasks are exposed to large language models. Not a forecast of job losses. Eloundou and others, 2023
  • 0.035 estimated probability that the whole occupation could be computerised, over an unspecified number of years. Not a forecast of job losses. Frey and Osborne, 2013

Since the 2013 prediction

In 2013, Frey and Osborne put this job's probability of computerisation at 0.035. BLS counted 319,080 of these jobs in May 2013 and 670,570 in May 2025 (+110%, a change derived by Future History).

Data as of BLS OEWS May 2025; BLS Employment Projections 2025-35. BLS publishes these counts as yearly survey snapshots and cautions against reading them as a precise trend. In May 2021 BLS changed how it estimates these counts (a model-based method using three years of survey data) and moved fully to the 2018 occupation codes, so part of a change across 2021 can come from the method rather than the work.

Last updated .

Cite this page
APA

Future History. (2026, October 11). IT managers: jobs and pay since 1980 [Data set; data as of BLS OEWS May 2025; BLS Employment Projections 2025-35]. https://futurehistory.earth/timeline/11-3021

Chicago

Future History. "IT managers: jobs and pay since 1980." Data as of BLS OEWS May 2025; BLS Employment Projections 2025-35. Last modified October 11, 2026. https://futurehistory.earth/timeline/11-3021.

BibTeX

@misc{futurehistory_11_3021, author = {{Future History}}, title = {IT managers: jobs and pay since 1980}, year = {2026}, month = oct, howpublished = {\url{https://futurehistory.earth/timeline/11-3021}}, note = {Last updated 2026-10-11. Data as of BLS OEWS May 2025; BLS Employment Projections 2025-35}, }

The access date is today's date on your device.

drag to travel through time
19752000now
Country
2026
Known then as Data Processing Manager / EDP Manager
Known then as MIS Director / Data Processing Director / DP Manager
Known then as MIS Director / Information Systems Manager / IT Manager
Known then as CIO / IT Director / VP of Information Technology
Known then as CIO / CTO / IT Director / VP Engineering (BLS SOC 11-3021)
Known then as CIO / CTO / CISO / Chief AI Officer / VP Engineering (BLS SOC 11-3021)
Known today as CIO / CTO / CISO / Chief AI Officer / VP Engineering (BLS SOC 11-3021)
Projected to still be called CIO / CTO / CISO / Chief AI Officer / VP Engineering (BLS SOC 11-3021)
Data from the May 2025 survey
US Employment
671K
Est.

Stated in source: BLS OEWS

Official statistic
Report an error
Median Annual Wage
$175,140
Est.

≈ $170,650 in 2024 prices (derived by us, CPI-adjusted)

Official statistic
Report an error
Beat · 1962

The US federal government begins systematically creating dedicated senior IT management positions in the early 1960s. By 1962 (with IBM's 7090 mainframes running the Census Bureau, the Social Security Administration, and the Department of Defense) the function of "the executive accountable for enterprise computing" was institutionalized in government agencies and beginning to appear in large private-sector corporations. The title was Data Processing Manager or Chief of ADP (Automatic Data Processing), not CIO, but the accountability structure was the same: one person responsible for technology strategy, vendor relationships, and IT operations on behalf of an entire organization.

Beat · 1965

The Brooks Act (Public Law 89-306) is signed on October 22, 1965, requiring all US federal agencies to procure information technology through the General Services Administration and to maintain ADP management standards. The law implicitly codified "information technology management" as a distinct government function requiring dedicated professional oversight: the first US federal legislation to treat IT management as a formal organizational discipline. The Brooks Act governed federal IT procurement for 31 years until the Clinger-Cohen Act of 1996 replaced it and, for the first time, explicitly mandated that each federal agency designate a Chief Information Officer.

Beat · 1981

William Synnott and William Gruber publish "Information Resource Management: Opportunities and Strategies for the 1980s": the book that introduced and defined the Chief Information Officer title to a broad management audience. Synnott was senior vice president of Bank of Boston; Gruber was a professor at MIT Sloan School of Management. Their argument was that information was a corporate resource requiring executive-level management just as capital, people, and facilities did, and that the person managing it needed to sit at the senior leadership table. The CIO concept spread rapidly through the 1980s. By 1990, CIO Magazine had launched (1987) and the title was standard at major US corporations.

Beat · 1984

Cisco Systems is founded in December 1984 by Stanford computer scientists Leonard Bosack and Sandy Lerner, who had developed a multi-protocol router to solve the problem of connecting Stanford's incompatible departmental computer networks. Cisco's IOS-based routers became the backbone of corporate networking through the 1980s and 1990s, creating the enterprise WAN infrastructure that IT managers would spend much of the next two decades deploying, securing, and upgrading. Cisco went public in 1990 with a $224 million market capitalization; by 2000 it briefly exceeded $500 billion, making it the most valuable company in the world at the peak of the networking boom. For IT managers, Cisco's dominance meant that Cisco certification (CCNA, CCNP, CCIE) became a baseline credential for the network management staff they supervised.

Beat · 1996

The Clinger-Cohen Act (Division E of the National Defense Authorization Act for FY 1997) is signed on February 10, 1996, explicitly mandating that each federal agency designate a Chief Information Officer with defined accountability for IT strategy, procurement, and performance measurement. This is the first US law to require a CIO by name at the federal agency level. The Act's framing, treating the CIO as a strategic executive rather than an IT functionary, influenced private-sector CIO role design and codified IT management as a C-suite function for the entire US government.

Beat · 1999

The Y2K remediation effort reaches peak intensity in 1999. Approximately $300-600 billion was spent globally on Y2K remediation, with US organizations spending an estimated $100+ billion. For CIOs, Y2K was the first instance of an IT risk that required direct board and CEO engagement: the business consequence of a technical failure was existential for some organizations, and the CIO had to explain the risk, quantify it, and certify remediation to non-technical leadership. The Y2K episode permanently elevated the CIO's board visibility and established the pattern of the CIO presenting technology risk to senior leadership: a pattern that would recur with every major security breach and cloud outage in subsequent decades.

Beat · 2006

Amazon Web Services launches commercially in 2006: Simple Storage Service (S3) on March 14, 2006, and Elastic Compute Cloud (EC2) in August 2006. The cloud computing model (compute and storage on demand, billed by consumption, accessed via API) is the single most disruptive technology change to the CIO's role since the PC. For IT management, cloud shifted the fundamental governance question from "how do we build and maintain infrastructure" to "how do we govern consumption, cost, and security in an environment we don't control." The data center capital budget conversation was replaced by the cloud contract conversation. AWS generated $17.5 billion in revenue in 2017 and $128.7 billion in 2025, validating the demand IT managers created.

Beat · 2009

Patrick Debois organizes the first DevOpsDays conference in Ghent, Belgium, on October 30-31, 2009, formalizing the DevOps movement. For IT managers, DevOps meant a fundamental reorganization of how software was delivered and operated: the traditional handoff from Development to QA to Operations was replaced by cross-functional teams owning their services end-to-end. Engineering Director and VP Engineering titles expanded rapidly as this model required management structures oriented around product delivery systems rather than technology silos. Puppet Labs' inaugural "State of DevOps" report (2012) established quantitative metrics for DevOps adoption; by 2016, the DORA metrics (deployment frequency, lead time, MTTR, change failure rate) were standard engineering management KPIs.

Beat · 2023

Major US corporations begin announcing dedicated Chief AI Officer appointments through 2023-2024. Walmart, Morgan Stanley, and dozens of other Fortune 500 companies create CAIO roles tasked with overseeing AI strategy, governance, and implementation across the enterprise. The function typically reports to the CIO or CEO and sits alongside existing IT management rather than replacing it: the AI governance mandate adds a new management layer rather than compressing the existing one. Microsoft 365 Copilot GA (November 1, 2023) gives IT managers a new governance surface: every enterprise AI tool deployment requires data classification policy, access control decisions, and compliance verification that the IT management function owns.

How to read this number

OEWS is a point-in-time survey snapshot, not a continuous time series; BLS advises against using it for year-over-year trend comparison.

Each dot is a cited figure over time; the dotted line only links them (values between aren't measured). Hollow dots are estimates.

Official statistic: Copied by a script from a statistics agency table or a published study's table, not retyped by hand. BLS figures and the forecast and exposure tables are also re-checked against that table on every data run. Researched context: Researched from the cited source rather than copied from it by a script, so it is not machine-checked yet. Spot a mistake? Each figure has a “Report an error” link.

Cited forecasts · present → 2035

Will AI replace IT managers? What the research says

Each figure is stated by the named source; we publish no forecasts of our own. Where sources disagree, we show the disagreement rather than an average.

Each figure is stated by the named source; we publish no forecasts of our own. Where sources disagree, the spread is the honest signal.

What published forecasts say
Forecast change in the number of people doing this work, as published by each named source. Bars share one scale on every role, centred on zero and reaching the end at ±30%. Grey marks a small change, 3% or less either way.
BLS Employment Projections 2025-35
→ 2035
+15.8%
BLS National Employment Matrix, 2025-35 cycle, line for SOC 11-3021 (Computer and information systems managers): 685.8 thousand jobs in 2025, projected 793.9 thousand in 2035, a change of +108.1 thousand (+15.8%). Matrix employment counts all jobs in the occupation, including self-employed workers (0.7% of this occupation in 2025). The average for all occupations in this cycle is +3.5%.
Official statisticReport an error
How exposed is this work to AI (research measures)
Scores as published by each study. Each row says what it measures. These measure what AI could technically do, not forecasts of jobs lost.
Eloundou et al. (2023), "GPTs are GPTs"
2023 study · Share of tasks exposed to LLMs (β, human-rated)
56.1%
of tasks
What this measures

Published occupation-level exposure from the paper's occ_level.csv for O*NET-SOC 11-3021.00 Computer and Information Systems Managers. Shown: human-rated β = 0.561, the share of the occupation's tasks an LLM could do in at least half the time at equal quality, counting tasks that need LLM-powered software at half weight (β = E1 + 0.5 × E2). Other published measures for this occupation: human-rated α (LLM alone) 0.303 and γ (all LLM-assisted) 0.818; GPT-4-rated β 0.53. This measures how much of the work an LLM could touch, not how many jobs disappear.

Official statisticReport an error
Frey & Osborne (2013), "The Future of Employment"
2013 study · Probability of computerisation (2013 model)
3.5%
probability
What this measures

Published appendix value for SOC 2010 11-3021 Computer and Information Systems Managers: probability of computerisation 0.035, rank 118 of 702 (rank 1 is least computerisable). Frey and Osborne estimated in 2013, with a Gaussian-process classifier on O*NET variables, how likely the whole occupation is to be technically automatable over "some unspecified number of years, perhaps a decade or two". It is a probability for the occupation, not a share of tasks and not a forecast of jobs lost.

Official statisticReport an error
Today, in this role

What's changing day to day for IT managers

Three parts of your work where AI is already doing real lifting, and what stays yours.

AI is sitting alongside you hereGovern the AI-augmented ITSM layer using ServiceNow Now Assist, configuring AI agents for incident triage, ticket routing, resolution-note generation, and knowledge-article drafting

Govern the AI-augmented ITSM layer using ServiceNow Now Assist, configuring AI agents for incident triage, ticket routing, resolution-note generation, and knowledge-article drafting; setting exception-handling rules for escalations that require human judgment; reviewing AI-summarized service desk metrics to identify systemic issues; and managing the platform's AI agent orchestration as Now Assist expands to cross-system enterprise workflows.[9],[10],[1]

Where your edge is

The value shift is from ticket supervision to platform orchestration. Develop expertise in ServiceNow Flow Designer and agent configuration so you can tune automation rules, define escalation criteria, and measure AI agent accuracy rates rather than just reviewing dashboards. The CIO who can identify which a sizeable share of incident types generate most escalations, and close that loop in the AI config, is compounding operational leverage.

AI is sitting alongside you hereDrive engineering productivity with GitHub Copilot Enterprise, making the platform and licensing decision (Business vs

Drive engineering productivity with GitHub Copilot Enterprise, making the platform and licensing decision (Business vs. Enterprise tier), setting IP and public-code filtering policies, establishing a 90-day adoption playbook with leading indicators (acceptance rate, code review turnaround, PR volume), tracking ROI against the $39/user/month cost, and governing coding-assistant vendor selection as Cursor, Replit Agent, and Amazon Q Developer compete for the enterprise slot.[11],[12],[13]

Where your edge is

The ROI case for GitHub Copilot Enterprise is strong (Accenture: 55% faster task completion, positive ROI within one quarter at even 10-11% productivity gain) but only materializes with disciplined adoption governance. Define leading metrics before rollout, plan for the ramp-up period Microsoft research identifies, and review code-quality signals (PR merge rate, defect density) alongside speed metrics to avoid trading quality for velocity.

AI is sitting alongside you hereDirect IT budget planning and financial governance: using Microsoft 365 Copilot and AI-assisted financial models to compress variance-analysis and forecast-preparation time

Direct IT budget planning and financial governance: using Microsoft 365 Copilot and AI-assisted financial models to compress variance-analysis and forecast-preparation time; building the ROI case for major AI platform investments (GitHub Copilot Enterprise, ServiceNow Now Assist, security toolchain upgrades) that must justify 25-40% price premiums over prior-generation tools; modeling multi-year TCO for AI platforms where the hidden costs (integration, training, governance overhead) routinely dwarf license fees; and defending IT capital allocation to the CFO and board with business-outcome framing rather than technology-feature arguments.[3],[9],[1]

Where your edge is

AI compresses the financial modeling work: data aggregation, variance explanation, forecast sensitivity analysis. Your leverage is the judgment layer: which AI investments are worth the premium, which legacy platforms to sunset to fund new ones, and how to frame technology spending as revenue protection and competitive positioning rather than cost. Build the habit of connecting every major IT budget line to a business outcome the CFO already cares about.

Where IT managers go next

Natural next steps for someone with your foundation: not exits, evolutions.

What each move takes

A direction you could grow

General and Operations Managers

Senior CIOs who have delivered AI governance programs, managed large IT budgets, and earned board-level trust through transparent cybersecurity reporting are increasingly moving into General and Operations Manager or COO roles. The 2026 AI governance mandate means the CIO is already doing the work of a strategy-setting, risk-managing executive: the pivot formalizes that scope expansion. The primary skill gap is P&L ownership depth: most CIO careers involve managing a cost center, not a revenue-generating business unit. CIOs who have driven measurable business-outcome ROI from technology investments are the strongest candidates.

What you'd add
· Board and investor communication: translating operational performance into capital-allocation language
· MBA or executive education program for the financial and commercial frameworks that CIO backgrounds often lack
What it takesA real upskill, but a natural one
Tools of the era

How has the work of IT managers changed since 1955?

The tools that defined the work, one line per era. Select an era to see how it reshaped the work.

  • Mainframe batch computing: IBM 1401 (1959), System/360 (1964)

    The EDP Manager of the 1950s-1960s ran a physical computing plant. The IT manager's job in this era was essentially plant management: scheduling batch-processing jobs, managing the keypunch operator pool, maintaining the physical hardware, and negotiating with IBM's field engineers on maintenance contracts. Strategic influence was minimal: the machines processed payroll and ledgers. The CIO concept did not yet exist; the title was Data Processing Manager, and the role reported to the Finance Director or Controller rather than to the CEO.

    Effect on the work

    Each IBM System/360 installation created demand for a Data Processing Manager plus a supporting staff of operators, keypunch clerks, and systems programmers. By 1970, most Fortune 500 companies had a dedicated EDP department.

  • Management Information Systems (MIS): IBM System/370 (1970), minicomputers (DEC PDP-11)

    The 1970s saw the MIS Director concept emerge: the idea that the IT department's job was not just to run batch jobs but to give management real-time information. IBM's System/370 (1970) brought virtual memory; DEC's PDP-11 and VAX minicomputers brought computing to mid-sized organizations that couldn't afford mainframes. The IT manager's scope expanded from plant operations to information architecture, deciding what data to collect, how to store it, and how to deliver it to decision-makers. Management Information Systems as a discipline entered business schools in this decade, and the MIS Director began reporting higher up the corporate hierarchy. The role was still fundamentally technical, but the strategic framing had begun.

  • PC and LAN era: IBM PC (1981), Ethernet, Novell NetWare (1983), Cisco routers (1984)

    On August 12, 1981, IBM announced the IBM Personal Computer, and within three years corporate IT departments had a new challenge: thousands of PCs on employees' desks, connected (or not) to each other and to corporate data. Novell NetWare (1983) provided the dominant LAN operating system; Cisco Systems (founded December 1984 by Stanford computer scientists Leonard Bosack and Sandy Lerner) produced the multi-protocol routers that made heterogeneous corporate networks possible. The IT manager's job exploded in complexity: the centralized mainframe was now supplemented by a distributed PC estate. The IT Director or VP of Information Technology emerged as a distinct leadership role, managing both legacy mainframe infrastructure and the new PC/LAN ecosystem. The title CIO, first formally defined in 1981 by Synnott and Gruber in "Information Resource Management: Opportunities and Strategies for the 1980s", gained currency as organizations recognized that information management was a strategic function.

    Effect on the work

    The PC/LAN era expanded the IT department from a centralized DP function to a distributed enterprise service organization, substantially increasing the headcount managed by IT directors and the corresponding demand for IT management positions.

  • Internet era: NCSA Mosaic (1993), Netscape (1994), SAP R/3 (1992), Y2K remediation

    NCSA Mosaic (January 1993) and Netscape Navigator (1994) brought the World Wide Web to corporate desktops. For the IT manager, the Internet introduced an entirely new security threat model, an external-facing presence (the corporate website), and a new communication channel (email at scale). SAP R/3 (released 1992), the first client-server ERP, made IT infrastructure a strategic business decision: the implementation of SAP determined how the entire enterprise operated. IT directors became de facto business transformation leads. Y2K (the Year 2000 date remediation effort, peak activity 1997-1999) was the first instance of an enterprise-wide IT risk that required the CIO to present directly to the board: a milestone in the elevation of IT management to C-suite accountability. The Netscape IPO on August 9, 1995, catalyzed the dot-com era, creating thousands of new CTO and VP Engineering titles at startup and corporate digital initiatives.

  • Google SRE (2003) + virtualization (VMware 2001) + first cloud (AWS S3 2006, EC2 2006)

    Benjamin Treynor Sloss founded Google's Site Reliability Engineering function in 2003, establishing the principle that software engineers, not operations staff, should run production systems, and that reliability should be measured and managed through software tooling rather than manual procedures. VMware ESX Server (2001) made server virtualization practical, enabling IT managers to consolidate dozens of physical servers onto fewer physical machines and manage them programmatically. Amazon Web Services launched commercially in 2006 (S3 [Simple Storage Service] on March 14, 2006; EC2 [Elastic Compute Cloud] on August 2006) providing compute and storage on a consumption-based model. For IT managers, cloud was a paradigm shift: infrastructure became an operating expense line managed through a dashboard rather than a capital budget line managed through physical procurement. The IT director's vendor negotiation skills, always important, became paramount as the cloud contract became the most consequential IT purchasing decision in most organizations.

  • DevOps movement (first DevOpsDays 2009) + Azure GA 2010 + multi-cloud management

    On October 30-31, 2009, Belgian consultant Patrick Debois organized the first DevOpsDays conference in Ghent, Belgium, establishing a name and community for the practice of breaking down the wall between software development and IT operations. For IT managers, DevOps was a structural challenge: the traditional siloed organization (separate development, QA, and operations teams with handoffs between them) was replaced by cross-functional product teams that owned the entire software delivery lifecycle. The VP of Engineering and Director of Engineering titles expanded rapidly as this new organizational model required management focused on software delivery systems rather than infrastructure operations. Microsoft Azure launched commercially in February 2010, completing the major public cloud triad (AWS, Azure, GCP launched broadly 2011-2013). Multi-cloud governance (managing costs, security, and compliance across multiple cloud providers) became a core IT management competency. CISO (Chief Information Security Officer) titles proliferated as cloud-era security perimeters became indefinite.

  • Cloud-native + CISO board elevation + digital transformation mandate

    By 2015, 'cloud-first' had become the default enterprise IT strategy rather than an experimental posture. Kubernetes (launched by Google in 2014, Cloud Native Computing Foundation formed 2016) standardized container orchestration and gave IT managers a new infrastructure governance layer. The CIO's mandate expanded beyond 'keep the lights on' to driving digital transformation: the re-architecting of business processes around digital-native capabilities. This elevated the CIO into a CEO-adjacent strategic role: a 2016 CIO Magazine survey found that the share of CIOs reporting directly to the CEO had risen substantially, and CIOs were increasingly presenting at board meetings. Security posture became a board-level concern after a series of high-profile breaches (Target 2013, Equifax 2017, SolarWinds 2020), expanding the CISO role from IT sub-function to independent C-suite position. The COVID-19 pandemic (March 2020) compressed five years of planned digital transformation into several months, requiring IT managers to stand up remote work infrastructure at enterprise scale in weeks: the largest peacetime IT management test in history.

  • Generative AI governance: ChatGPT enterprise (2023), Chief AI Officer titles, AI security surface

    OpenAI released ChatGPT on November 30, 2022, and within several months it was the fastest-growing consumer application in history with more than a hundred million users. Enterprise adoption followed rapidly: Microsoft 365 Copilot GA on November 1, 2023; GitHub Copilot Business broadly available 2023; major enterprises announcing AI transformation programs. For IT managers, generative AI created an entirely new governance mandate: AI vendor selection, data privacy compliance (what data can the LLM touch?), AI security risk (prompt injection, model poisoning, deepfake-enabled social engineering), AI cost governance (token consumption can spike unpredictably), and AI tool standardization across a workforce that was adopting shadow AI spontaneously. Chief AI Officer titles began appearing at major US corporations in 2023-2024: Morgan Stanley, Walmart, and dozens of others announced dedicated CAIO positions. The function usually reports to the CIO or CEO and often sits alongside the existing IT management structure rather than replacing it. IT managers who could govern AI adoption (evaluate models, set usage policy, manage vendor risk) became among the most sought-after technology executives in the 2024-2025 market.

    Effect on the work

    BLS projects +15% employment growth 2024-34, faster than the all-occupation average, driven substantially by AI governance demand alongside continuing cloud and cybersecurity expansion. The addition of a "Chief AI Officer" layer at large organizations has generally added headcount rather than replaced existing IT management.

Part of Management · see all 36 roles →
Different role?

See the same long-arc view for your own profession.

Browse the directory by industry, or search by title or SOC code.

Browse all roles

Computer and Information Systems Managers employment and pay by year

On record since1962
Latest US employment670,570 (May 2025)Source: BLS OEWS May 2025Official statisticReport an error
Latest US median pay$175,140 (May 2025)Source: BLS OEWS May 2025Official statisticReport an error
Outlook+15.8% by 2035Source: BLS Employment Projections 2025-35Official statisticReport an error

In other countries

The latest figure each country's statistics agency publishes for this job. Each uses its own occupation definition, survey basis and currency, so the numbers are not directly comparable with each other or with the US figures.

  • Canada (NOC 20012)

    Employment, 2020
    82,235, Statistics Canada Census 2021 Official statistic Report an errorStatistics Canada Census of Population 2021: number of persons with employment income in NOC 20012 Computer and information systems managers, Canada, reference year 2020. A recipients basis (anyone with employment income during the year), slightly broader than a point-in-time employed count. Statistics Canada Open Licence.
    Median pay, 2020
    C$117,000, Statistics Canada Census 2021 Official statistic Report an errorStatistics Canada Census of Population 2021 (Table 98-10-0586): median employment income for NOC 20012 Computer and information systems managers, Canada, reference year 2020, full-year full-time workers (the basis comparable to the US OEWS full-time median). Statistics Canada Open Licence.

  • United Kingdom (UK SOC 1137)

    Employment, 2025
    60,000, ONS ASHE 2025 Official statistic Report an errorONS Annual Survey of Hours and Earnings (Table 14): employee jobs in SOC 1137 Information technology directors, United Kingdom, 2025 (ASHE "number of jobs", thousands x1000; excludes self-employment). Open Government Licence v3.0.
    Median pay, 2025
    £90,081, ONS ASHE 2025 Official statistic Report an errorONS Annual Survey of Hours and Earnings (Table 14.7a): median gross annual pay for all employee jobs in SOC 1137 Information technology directors, United Kingdom, 2025. Open Government Licence v3.0.

  • Australia (ANZSCO 1351)

    Employment, 2025
    87,800, ABS Labour Force Survey Official statistic Report an errorABS Labour Force Survey (Detailed), table EQ08: employed persons in ANZSCO 1351 ICT Managers, national (summed across sex and state/territory), annual average of 4 quarterly estimates.
    Median pay, 2025
    A$172,120, ABS Employee Earnings May 2025 Official statistic Report an errorAnnualised (x52) from A$3,310 median weekly earnings. ABS Survey of Employee Earnings and Hours, May 2025: median pay for full-time non-managerial employees paid at the adult rate, before tax. Surfaced via the Jobs and Skills Australia occupation profile.
View all 26 years of cited US data, each linked to its source
YearUS employmentAnnual pay (median unless marked)SourceReport
1980250,000$32,000Est., BLS Researched contextReport
1990350,000n/aEst., BLS Researched contextReport
2000283,480$78,830BLS OEWS 2000 Official statisticReport
2003266,020$89,740BLS OEWS May 2003 Official statisticReport
2004267,390$92,570BLS OEWS May 2004 Official statisticReport
2005259,330$96,520BLS OEWS May 2005 Official statisticReport
2006251,210$101,580BLS OEWS May 2006 Official statisticReport
2007264,990$108,070BLS OEWS May 2007 Official statisticReport
2008276,820$112,210BLS OEWS May 2008 Official statisticReport
2009287,210$113,720BLS OEWS May 2009 Official statisticReport
2010288,660$115,780BLS OEWS May 2010 Official statisticReport
2011300,830$118,010BLS OEWS May 2011 Official statisticReport
2012309,740$120,950BLS OEWS May 2012 Official statisticReport
2013319,080$123,950BLS OEWS May 2013 Official statisticReport
2014330,360$127,640BLS OEWS May 2014 Official statisticReport
2015341,250$131,600BLS OEWS May 2015 Official statisticReport
2016352,510$135,800BLS OEWS May 2016 Official statisticReport
2017365,690$139,220BLS OEWS May 2017 Official statisticReport
2018391,430$142,530BLS OEWS May 2018 (employment) Official statisticBLS OEWS May 2018 (pay) Official statisticReport
2019433,960$146,360BLS OEWS May 2019 Official statisticReport
2020457,290$151,150BLS OEWS May 2020 Official statisticReport
2021485,190$159,010BLS OEWS May 2021 Official statisticReport
2022533,220$164,070BLS OEWS May 2022 Official statisticReport
2023592,600$169,510BLS OEWS May 2023 (employment) Official statisticBLS OEWS May 2023 (pay) Official statisticReport
2024645,970$171,200BLS OEWS May 2024 Official statisticReport
2025670,570$175,140BLS OEWS May 2025 Official statisticReport
Embed this timeline on your site

Free for any site. Paste this where the timeline should appear; it stays interactive, every datapoint stays cited, and it sets no cookies on your page. How embedding works

<iframe src="https://futurehistory.earth/embed/11-3021"
  width="100%" height="430" style="border:0"
  title="Computer and Information Systems Managers, a Future History timeline"
  loading="lazy"></iframe>
<p style="font-size:13px;margin:4px 0 0"><a href="https://futurehistory.earth/timeline/11-3021">Computer and Information Systems Managers: jobs and pay over time</a>, from Future History</p>

See all roles in Management