Let's slow down for 10 minutes.
Before we talk about courses or programs, let's get clear on what these jobs actually are. Plain English. No jargon. No pressure. By the end of this page you'll recognise these roles — because you've probably already seen them in action without knowing the names.
The IT landscape
Four roles. You've probably seen all of them without knowing the names.
Imagine a company wants to build a new online booking system. Someone needs to figure out exactly what the business needs, write it down clearly, and make sure the tech team builds the right thing. That's the Business Analyst — the translator between the people with the problem and the people who build the solution. They write requirements, draw simple diagrams, and ask "but what does that actually mean in practice?" until everyone agrees.
If you're good at asking questions, listening carefully, and turning messy ideas into clear plans — this might be you.
Before any software reaches real users, someone needs to check it actually works — not just "does it turn on" but does it do exactly what it's supposed to do, in every situation, including the ones nobody planned for. That's the Systems Tester. They read the requirements, design tests, find the gaps, and write clear defect reports so developers know exactly what to fix.
If you notice when things don't work the way they should, and you like being thorough and precise — this might be you.
Developers take the requirements the BA wrote and build the actual software. They write code. This is the role most people think of when they hear "IT job" — but it's just one of four, and it's not what GAP2IT trains. We mention it because you'll work alongside developers every day as a BA or Tester, and it helps to know what they do.
Not what we train — but good to know they exist and what they do.
BI Analysts work with data. They take the numbers a business collects — sales figures, customer behaviour, operational metrics — and find the story inside them. They use tools like Excel or Power BI to turn raw data into insights that help the business make better decisions.
If you like patterns, numbers, and the question "why did that happen?" — this is worth exploring later.
See it in action
Four roles. One project. Here's what it looks like.
The scenario: A supermarket chain wants to add a self-checkout option to their app.
Meets with the supermarket managers, asks what they need, and writes a clear list of requirements — how it should work, what happens if a barcode doesn't scan, how refunds are handled.
Takes that list and builds the feature in the app.
Checks every requirement against the actual app. Does the scanner work? What happens on slow internet? Scan the same item twice? Finds the gaps and reports them clearly.
Watches the data after launch — are people using it? Where are they dropping off? What's going wrong on Tuesday afternoons?
Four different roles. One project. Each one essential. None of them requires you to write complex code.
The question everyone asks
What about AI? Honest answer.
AI is changing IT. That's real. But here's what's also real: AI needs humans who can think clearly, ask the right questions, spot what's wrong, and communicate across a team.
A Business Analyst's job is to understand what a business actually needs — not what it thinks it needs. AI can't have that conversation with a room full of stakeholders.
A Systems Tester's job is to think adversarially — to ask "what could go wrong?" in ways nobody planned for. AI generates tests. Humans decide what matters.
The roles AI is replacing are repetitive, rule-based, no judgment required. BA and QA are judgment roles. That's why they're still being hired.
You're more ready than you were 10 minutes ago.
That's all the orientation you need. The Starter Pack will show you what BA and QA work actually feels like — with a tiny hands-on activity, plain English explanations, and no pressure to commit to anything.
Enter the Starter PackDoor 2 people are already inside. You're joining them now — on equal ground.