How do I become a business analyst in tech?

What a business analyst in tech actually does

A business analyst, or BA, works out what a change must achieve and describes it clearly enough that a team can build it and test it. In a software team that means interviewing people, watching how work is really done, mapping processes, writing requirements and user stories with acceptance criteria, checking data, answering developers' questions and helping business users test the result before it goes live.

It is different from product management. A product manager decides which problems are worth solving. A BA makes sure the chosen change is understood, specified and delivered correctly. In small teams one person often does both, which is why so many product managers started as analysts.

It is not a way to avoid technology. You will read API responses, write SQL, sit in sprint planning and review test results. You just will not write production code as your main output.

A business analyst roadmap you can actually follow

I would learn it in this order, practising each step on something real:

1. Technical literacy. How software is built, how the web and APIs work, what a pull request is, and enough SQL and spreadsheet skill to pull your own numbers. Engineers trust analysts who have done these basics themselves.
2. Elicitation and stakeholders. Who is affected by a change, what each group cares about, and how to interview and observe people without leading them.
3. Process mapping. Draw how work flows today and how it should flow after the change. Learn the handful of BPMN symbols most people use; the free bpmn.io modeler is enough.
4. Requirements and acceptance criteria. Functional and non-functional requirements, user stories, and Given/When/Then scenarios that a tester could turn into test cases.
5. Data and evaluation. Profiling a dataset, a simple data model, prioritising with MoSCoW, tracing requirements to tests, and checking after launch whether the change worked.

I have put this whole path, stage by stage, in the Business analyst option of the Tech roles beyond coding roadmap, with a matching cheat sheet for revision. For the vocabulary, IIBA's free Business Analysis Standard is the best short read, and the free SQL tutorial for data analysis covers the queries you will actually use.

Practise on something real

The biggest mistake I see is building a portfolio from invented case studies. Reviewers notice. Instead, find a small real organisation you can reach: a family shop, a clinic, a university office or a society. Map one process that annoys them, interview the people who do it, write ten user stories with acceptance criteria, and propose a better process. Ask permission before you publish, and remove anything sensitive.

If you want a project with a technical side, pair up with a developer friend on something like an approval workflow for small offices: you own the analysis, they build it, and both of you get a real portfolio piece.

Do you need a certification?

Not to start. IIBA's entry certification, ECBA, has no experience requirement, and some banks and consultancies do mention IIBA certifications in postings. It can give you structure and vocabulary. But the higher levels, CCBA and CBAP, require years of BA experience, so do not pay for training towards them yet. Check the official IIBA certifications page for current eligibility and fees before you spend anything. Three strong work samples will say more about you than any certificate.

Where the entry-level jobs are

Business analysis hires more fresh graduates than product management does. Look at:

• Banks, telecoms, insurers and large retailers, which run graduate or associate BA roles.
• Consultancies and IT services companies, where the same work is often called functional consultant, implementation analyst or systems analyst.
• Product companies, which hire product analysts and sometimes BAs inside delivery teams.
• Internal moves from QA, support or operations, where you already know the product and the users.

Your domain knowledge is an asset, not a detour. If you studied finance, health, logistics or education, target that industry first; you will understand the business faster than someone who only knows the techniques. If you are coming from outside computer science, my answer on getting into tech without a CS degree covers the rest.

A realistic first three months

• Month 1: technical literacy and SQL basics, plus ten real BA job postings read and highlighted.
• Month 2: one real organisation analysed end to end: stakeholders, as-is and to-be processes, stories and acceptance criteria.
• Month 3: one data analysis sample, a simple portfolio page, and applications to every title variant in two target industries.

If you want a structured path with progress tracking, create a free Sefism account and pick the Business analyst option on the roadmap. If you want to talk through your own situation, book a session with me.