A day as an IT Business Analyst
An IT business analyst spends the day making sure the people who use a system and the people who change it mean the same thing. Unlike a general business analyst, almost everything you work on ends in a change to software: a new field, a workflow rule, an integration, a report. The day below follows an analyst in a company's own IT department during a finance system rollout.
What the IT in the title changes
A general business analyst might study why a warehouse ships late and recommend a new staffing plan. You won't. Your problems arrive as requests to the IT team, and your answer is nearly always something a developer, an admin or a vendor has to build or configure. That means you live in Jira, Confluence and the IT service management tool, usually ServiceNow, and you read system screens and data tables as comfortably as you read a process map. You're also the one who explains to finance or HR why the thing they asked for is harder than it looks. Most IT business analysts work on systems the company bought rather than built: an ERP, a CRM, an HR platform. So a good chunk of the job is knowing what the software can do out of the box before anyone writes custom code.
A Tuesday on the finance rollout
Sort the request queue
You open ServiceNow and read what came in overnight. Some tickets are plain bugs that belong to the support team, so you reassign them. A few are small changes, like adding a dropdown value, that an admin can handle this week. One is a manager asking for a whole new approval process, and that one needs a real conversation before anyone estimates it.
Workshop with accounts payable
You sit with the AP supervisor and a couple of clerks and walk through how an invoice gets matched to a purchase order today. You sketch the flow in Visio while they talk. The useful part comes when you ask what happens when the invoice and the PO don't match, because the exceptions are where the real requirements hide.
The release that broke approvals
The service desk messages you: purchase order approvals stopped reaching the right managers after the weekend release. The afternoon writing time is gone. You pull the approval rules from the configuration screen, run a SQL query against the reporting database to list the stuck orders, and spot that a department code mapping changed. Then you write a short plain-language note for the finance director explaining what happened and when it'll be fixed.
Backlog refinement with developers
The integration developers push back on a story you wrote. It assumes the vendor's API sends tax codes with each invoice, and it doesn't. You split the story in Jira, tighten the acceptance criteria, and log the open question for the vendor call on Thursday. Nobody's happy about the delay, but it beats finding out in testing.
Line up user acceptance testing
You write UAT scripts in Excel, picking real invoices as test data because made-up ones never catch the odd cases. Then comes the harder job: booking time with finance users who are heading into month-end close. You trade favours, promise short sessions, and send calendar invites before they fill up.
Where IT business analysts come from
Up from the service desk
Help desk and application support people already know the systems and the users who complain about them. Volunteer to write up enhancement requests properly, sit in on requirements meetings, and you'll often get pulled onto a project team. This is the most common route inside a single company.
Across from the business side
The accountant who became the go-to person for the ERP, or the HR coordinator who configured the new onboarding workflow, has half the job already. You bring process knowledge that IT people lack. What you'll need to add is Jira, user stories and a working grasp of how integrations and data move between systems.
Over from QA or general analysis
QA analysts are already good at acceptance criteria and test scripts, so the jump is mostly toward earlier conversations with stakeholders. General business analysts moving over need to get more technical: reading API docs, writing basic SQL, and learning how change management works in IT.
The part that wears people down
You're in the middle, all the time. The business wants more, sooner. The developers want clearer requirements and fewer changes. The vendor says the feature is on their roadmap. You don't control the budget or the team, so you get things done by being prepared and by writing things down so clearly that nobody can argue later about what was agreed. Scope creep is constant, and the phrase you'll say most is "let's log that as a separate request." People who need a finished product they can point to sometimes find this work thankless, because a well-run project looks like nothing happened.
What IT Business Analyst postings ask for
Hiring the most
- L3Harris Technologies, Inc.11
- Collabera210
- Smithfieldfoods7
- Citi5
- IntegratedResourcesINC5
Remote
11% of openings are fully remote.
Posted pay
$71,885 – $111,836
Typical range in the 20 of the newest 60 postings that list pay.
Questions people ask
Is an IT business analyst the same as a business systems analyst?
They overlap heavily and many companies use the titles interchangeably. When there's a difference, a business systems analyst tends to do more hands-on configuration of the system, while an IT business analyst spends more time on requirements, stakeholders and testing. Read the posting's duties rather than trusting the title.
Do I need to know how to code?
No, but you need to be comfortable near code. Basic SQL is the skill that pays off fastest, because it lets you check data yourself instead of waiting on a developer. You should also be able to read an API spec and understand a JSON payload well enough to write a field mapping.
What comes after IT business analyst?
The common next steps are senior or lead business analyst, product owner for an internal platform, or IT project manager. Some people go deeper into one system and become a solution architect or an ERP functional lead. Which fork you take depends on whether you'd rather own decisions or own the technical design.
149 IT Business Analyst jobs are open today
HeroApply applies to them for you, so you can keep doing the job you have.