Stop 13 · BA Domain SpecializationsTopics · 1/7

IT Business Analyst

Part of the Business Analyst Roadmap

In short

The most common BA job title in India's IT services and product companies. You sit between people who say 'make it easier' and developers who need to know exactly which field, rule and error message.

Focuses on translating business needs into technical requirements for software development teams — requires the strongest technical fluency (Phase 8) of the common BA specializations.

The purple blob stands in a garage between a worried customer and a mechanic under a car, passing a wrench.

Think of it like this

The garage translator

The customer says 'there's a khat-khat sound when I turn left'. The mechanic needs 'check the front-left CV joint'. Someone has to turn a feeling into a precise job card. An IT BA does that between business users and developers.

Watch it happen

Turning a request into a buildable spec

Business user
IT BA
Developer
System

Make refunds faster

1/5The business user describes a pain in business words.

The big ideas

What you need to know

Strongest tech fluency

You'll read API docs, understand databases and talk about integrations. You don't code daily, but you can't be scared of it.

Precise requirements

User stories, acceptance criteria, data mappings and wireframes, detailed enough that developers don't have to guess.

Two languages

Business words with stakeholders, technical words with engineers. Your value is translating without losing meaning.

Where you'll work

IT services firms, product companies, and internal tech teams at banks, retailers and telecoms.

See it in code

Walk through the code

json
1{2  "endpoint": "POST /refunds",3  "request": {4    "orderId": "string, required",5    "reason": "one of: damaged, late, wrong_item",6    "amount": "number, <= order total"7  },8  "errors": {9    "409": "Refund already raised for this order",10    "422": "Amount exceeds order total"11  }12}

1/3Which call this spec is about.

A simple field and error spec an IT BA might attach to a story. It's not code, but it tells the developer exactly what to build.

Save yourself the pain

Common mistakes

Oops

Passing the business request to developers word for word.

Do this instead

Break it into clear stories with rules, fields and edge cases. That translation is your job.

Oops

Avoiding technical conversations because 'I'm not a developer'.

Do this instead

Learn enough about APIs, databases and system design to ask good questions and spot impossible asks.

Your mission

Spec one small feature

~30 min

Quick check

Which skill most sets an IT BA apart from other BA specialisations?

Go deeper

  1. 1Read 2-3 IT BA job descriptions and note the recurring required skills.
  2. 2Revisit Phase 8 (Systems & Technical Understanding) as the core skill set for this track.
  3. 3Consider if you enjoy working closely with engineering teams more than pure business process work.

More topics at this stop

Stuck on this topic? Ask an Insider

Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.

Download
InsideEdge