IT Data Analyst Job Description

An IT data analyst studies the records a technology department generates about itself. Every password reset, outage, laptop shipment, software license and cloud invoice leaves a trail in some system, and the analyst's job is to turn those trails into numbers an IT leader can act on. Where a general data analyst answers questions about customers, sales or patients, this role answers questions about the IT function: how fast the service desk closes tickets, which applications fail most often, how many paid licenses sit unused, and what the cloud bill bought last quarter.

The raw material comes from operational platforms. Ticket and change records live in an IT service management tool such as ServiceNow or Jira Service Management. Uptime, latency and error counts come from monitoring tools such as Datadog, Splunk or SolarWinds. Device and software inventories come from endpoint managers like Microsoft Intune or Configuration Manager, identity data from Microsoft Entra ID or Okta, and spending detail from AWS, Azure or Google Cloud billing exports. None of these systems was designed to agree with the others, so a large part of the job is knowing which one is the system of record for a given fact and reconciling the rest against it.

Inside ServiceNow, much of this work runs through Platform Analytics. ServiceNow's documentation describes Performance Analytics as a tool that "utilizes indicators (KPIs) to answer key business questions," and its KPI Signals feature "notifies you when the behavior of a process changes significantly." An analyst who owns those indicators decides what counts as a resolved incident, which breakdowns matter (assignment group, priority, business service) and when a spike deserves a closer look rather than an alert to a manager.

A working week mixes recurring output with requests nobody planned for. Recurring work might be a monthly service-level report for the CIO, a capacity view for the infrastructure team, or a license reconciliation ahead of a vendor renewal. Unplanned work arrives after a major outage, when the problem manager wants a timeline built from change records and alert logs, or when finance asks why the Azure line jumped. O*NET's profile of business intelligence analysts, the occupation this job is closest to, lists a matching core task: to "generate standard or custom reports summarizing business, financial, or economic data for review by executives, managers, clients, and other stakeholders."

The tools are familiar ones: SQL against the reporting database or a warehouse copy of the ITSM tables, Python or R for cleaning and scheduled extracts, and Power BI, Tableau or Looker for dashboards. The judgment is what sets the role apart. A mean time to resolve that looks great may hide tickets reopened three times; a falling incident count may mean users stopped reporting problems, not that fewer happened. Spotting those traps, and explaining them to people who are not analysts, is the daily craft.

The work is desk-based, in an office or hybrid setup, with meetings concentrated around reporting cycles and incident reviews.

Education. The usual starting point is a four-year degree in a quantitative or computing field: information systems, statistics, computer science or analytics. BLS lists a bachelor's degree as the typical entry-level education for data scientists, the occupation that includes business intelligence work. Candidates who come up through the service desk or systems administration, rather than a degree program, can make the move by showing they already understand how IT operations data is produced and where it goes wrong.

Experience. As a rough guide, entry-level openings suit people with an internship, a portfolio or a year or two in IT support, while mid-level roles tend to look for 2 to 5 years of reporting or analysis work. Time spent on a service desk or in an operations center is useful background: it teaches what a ticket category actually means and why a closure code gets misused.

Technical skills.

• SQL, including joins across incident, change, problem and configuration item tables, window functions and common table expressions
• A BI tool such as Power BI (DAX and Power Query), Tableau or Looker
• Python or R for cleaning, scheduling extracts and simple statistics
• Working knowledge of ITSM data models, especially ServiceNow tables and their reference fields
• Familiarity with cloud billing exports and tagging conventions on AWS, Azure or Google Cloud
• Spreadsheet skill for the quick reconciliations that never justify a full dashboard

Process knowledge. Analysts who understand IT service management practice read their data better. Knowing how incident, problem and change management are supposed to work explains a lot of strange numbers.

Certifications. All are optional. Credentials that match the work:

• Microsoft Certified: Power BI Data Analyst Associate, from Microsoft
• CompTIA Data+, from CompTIA
• ITIL Foundation (Version 5), from PeopleCert; PeopleCert plans to sunset its ITIL 4 modules on Dec. 31, 2027
• ServiceNow Certified System Administrator, from ServiceNow
• FinOps Certified Practitioner, from the FinOps Foundation, for analysts who own cloud cost reporting

Public-sector hiring. The Office of Personnel Management's April 13, 2026 memo issuing a new classification standard for federal IT positions describes "a governmentwide shift toward skills based hiring," and says the standard "supports the shift away from outdated credential centric models toward validated skills and behaviors." The memo also ties these policies to assessment modernization.

Soft skills. Clear writing, patience with stakeholders who want a single number, and the discipline to document every metric definition so the next analyst can rebuild it.

BLS does not report IT data analysts separately, so the closest official outlook is the one for data scientists, the occupation that contains business intelligence analysts. The Occupational Outlook Handbook counts 275,600 data scientist jobs in 2025 and projects employment to grow 35 percent from 2025 to 2035, much faster than the average for all occupations, an increase of 95,400 jobs. That projection covers the whole occupation, including machine-learning roles that look little like IT operations reporting, so read it as context for analytics work in general rather than as a forecast for this title.

Federal classification was rewritten in 2026

One dated change for this kind of work came from the federal government. On April 13, 2026, OPM Director Scott Kupor issued a competency-based position classification standard for the Information Technology Management series, 2210, which the memo says provides "updated classification guidance, titling instructions, occupational information, and grading criteria for administrative IT positions governmentwide." It replaces the earlier IT job family standard and organizes IT work into three clusters: IT Operations & Security, IT Development & Analysis, and IT Strategy & Planning.

The standard also takes a position on automation. It says AI and digital tools "do not change the fundamental nature or purpose of the work itself," and that positions must be classified on the knowledge the duties require, "not on the tools used to execute those duties." For an analyst, that is a useful frame well beyond government: the value sits in knowing which metric answers the question, not in which product drew the chart.

What AI changes day to day

Where ITSM and BI tools offer generative AI features, a manager can ask for a quick chart or a plain-language answer directly. That does not settle whether a number is right. Someone still has to define the indicator, check that the underlying filter matches the agreed definition, and notice when a source table changed its meaning after an upgrade. An analyst who owns those definitions, and who can explain why two dashboards disagree, does the part of the job these features depend on.

Where the job leads

Paths from the role include:

• Senior or lead IT analyst, owning the reporting for a whole service area such as end-user computing or infrastructure
• Analytics engineer, building the modeled tables and semantic layers other analysts query
• ITSM platform analyst or administrator, specializing in the tool that produces the data
• FinOps or IT financial analyst, focused on cloud and software spending
• Service delivery or IT operations manager, for analysts who want to run the processes they measure

Domain depth helps in each direction. An analyst who understands how a change advisory board decides, or how a software vendor counts a license, can spot errors that a generalist will miss, and that knowledge carries from one employer to the next.

Dear Hiring Manager,

I am applying for the IT Data Analyst position on your service management team. For the past three years I have worked as a reporting analyst inside a regional health system's IT department, where I built and maintained the reporting that our CIO and service desk leadership use to run the function.

Most of my work starts in ServiceNow. I write SQL against our reporting copy of the incident, change and configuration item tables, and I publish the results in Power BI. When I joined, the service desk's resolution metric included tickets that had been reopened, which made the team look faster than it was. I rebuilt the measure, documented the definition with the service desk manager, and set up a weekly view of reopened tickets by assignment group. That view became the agenda for the team's Monday meeting.

I also took on license reporting. Our software spend was tracked in three places that did not agree, so I reconciled the endpoint inventory against the identity directory and the vendor's own counts before a major renewal. The finance team used that reconciliation in the negotiation, and I turned the one-off work into a monthly report.

After a major outage last year, I assembled the timeline for the post-incident review from change records and monitoring alerts. Building it showed me how much our problem management depends on clean data, and I have since worked with the change team to tighten the fields engineers fill in.

I hold the Microsoft Power BI Data Analyst Associate certification and am studying for ITIL Foundation (Version 5). I would welcome the chance to bring the same care with definitions to your team.

Sincerely, Jordan Ellison