Launch League

Technology · Analyzing & Problem-solving

Business systems analyst: what the job actually is

The person who works out what the business actually needs from a system and writes it down so builders can deliver it.

Published Last reviewed How we research and correct this

Business systems analyst: quick facts

Business systems analyst salary in Ontario: the median pay is $45.13 an hour, according to Job Bank (reference period 2023-2024). Its three-year outlook in Ontario is limited. The job usually needs a university degree.

Median pay in Ontario
$45.13 an hour
Pay range (low to high)
$33.33 to $62.50 an hour
Job outlook, 2025-2027
Limited
People working in it in Ontario
18,200
Usually needs
Usually a university degree

Source: Job Bank wages (updated 19 November 2025) and job prospects (updated 10 December 2025), NOC 21221. Pay varies by region and experience.

The work

What this job actually is

  • Standing between the people who need something from a computer system and the people who build it, and making sure both are talking about the same thing.
  • Job Bank's group is called business systems specialists. The title varies by employer, and you will see business analyst, systems analyst and requirements analyst on postings for much the same work.
  • Most of it is asking questions and writing the answers in a form that can be tested. 'The system should be fast' is not a requirement. 'A cashier can finish a return in under a set time' is one, and you are the one who pins that down.
  • You often work on a project with a start and an end: a new system, a replacement, a change. You sit with the users, map how they work, find the gaps, and produce documents, diagrams and test cases.
  • You are not the one who writes the code, and you are not the one who owns the budget. Your influence comes from being accurate and being listened to.

A Tuesday

What a normal day looks like

Not a good day or a bad one. The ordinary version, which is what you would actually be living.

  1. 8:30 — Open the project notes. A stakeholder changed their mind last night about what a report should show.
  2. 9:00 — Interview a user at their desk, watching what they do rather than what they say they do. They keep a paper note on the monitor that the system never mentioned.
  3. 10:15 — Back to the desk to write the requirement in plain words, then a second version in testable ones.
  4. 11:00 — Meet two stakeholders who want opposite things from the same screen. You do not decide, but you lay out the trade-off.
  5. 12:00 — Lunch. Somebody asks you what a 'use case' is, and you answer without using the word.
  6. 13:00 — Walk the developers through a requirement. They ask a question you cannot answer, so you write it down and find out.
  7. 14:30 — Update a process diagram. Boxes, arrows, and one box labelled 'manual workaround' that nobody is proud of.
  8. 15:30 — Test a build against the requirements and log the three places it does not match.
  9. 16:30 — Status update. Say what is late, why, and what you need. Do not dress it up.
  10. 17:00 — Tidy the document. A requirement nobody can find is a requirement nobody follows.

Honestly

Who loves this, and who should not do it

The second list is the useful one. Nearly every careers page leaves it out, which is why nearly every careers page reads like an advert.

You may like this if
  • You are the person who asks 'but what do you actually mean by that?' and enjoys the answer.
  • You like making a vague mess precise, even if the precise version is less exciting.
  • You are comfortable in a room with two people who disagree and want someone to lay it out fairly.
  • You can write clearly enough that a developer and an executive both understand the same page.
  • You like technology but do not need to be the one writing it.
You may hate this if
  • You want to build the thing yourself. You will watch other people build it and sometimes build it differently from what you wrote.
  • You dislike writing, diagrams and documents. They are the product.
  • You cannot stand meetings or ambiguity. Requirements change, stakeholders change, and your document changes with them.
  • You need a firmly growing field. Job Bank rates the Ontario outlook for this group as Limited: it describes a few new positions, a moderate number from retirements, and several unemployed workers with recent experience.
  • You do not like being blamed for gaps in a project you did not control. When a system misses what users needed, the finger tends to point at whoever wrote the requirements.

The route in

How you actually get there in Ontario

  1. Finish high school with English, maths and a computing course

    Writing clearly matters as much as anything technical here. Job Bank's page asks for a bachelor's degree in computer science, business administration, information systems or a related discipline, or a college computer science programme.

  2. Pick a business-and-technology programme

    Look at ontariocolleges.ca for computer systems and engineering technology programmes, and at business or information systems degrees on ontariouniversitiesinfo.ca. Either route is listed by Job Bank.

  3. Get a first job near the work

    Many analysts arrive from somewhere else: tester, support, a business role who got involved in a system. Being the person in the room who knows both the work and the screen is how the move usually happens.

  4. Know the vendor and tool side if an employer asks

    Job Bank says certification or training from software vendors may be required by some employers. Job Bank also says the occupation is not regulated in Canada, so no licence is needed.

  5. Consider the CBAP much later

    The International Institute of Business Analysis offers a Certified Business Analysis Professional credential. Its page says it needs five or more years of work experience in the last ten (7,500 hours), 35 hours of professional development in the last four years, and two references, and the exam is 210 minutes with 120 questions. It is for someone already in the work, not a way in.

Where this comes from: Job Bank — Requirements for business systems specialists in Ontario · IIBA — CBAP certification · ontariocolleges.ca — Computer - Systems / Engineering Tech programs

The money

Business systems analyst salary in Ontario

Job Bank's own figures, quoted rather than summarised, with the period they describe — so you can tell how old they are and go and check them.

$33.33
Low (hourly)
$45.13
Median (hourly)
$62.50
High (hourly)

Ontario, NOC 21221. Reference period 2023-2024, last updated by Job Bank on 19 November 2025. Wages vary a lot by region inside Ontario and by how long you have been doing it — the low figure is roughly where you start, not what the job is worth.

Source: Job Bank — Business systems analyst wages in Ontario

Where it is heading

The outlook for the next three years

Job Bank publishes a three-year outlook for every job in every province. It is the closest thing to an honest forecast, and it moves, so read it as a weather report rather than a verdict.

Ontario, 2025-2027

Limited2 out of 5 stars

  • Employment growth will lead to a few new positions.
  • A moderate number of positions will become available due to retirements.
  • There are several unemployed workers with recent experience in this occupation.

What that rating means: how many openings Job Bank expects in Ontario for this kind of work against how many people are likely to be looking — not whether it is a good job. A “limited” rating means more competition for each opening; it does not close the door, and it can change before you are ready to walk through it.

18,200
people work in this job in Ontario
45%
are women (48% across all jobs)
12%
are self-employed (15% across all jobs)

Source: Job Bank — Business systems specialists job prospects in Ontario (NOC 21221). Outlook updated by Job Bank on 10 December 2025; read by us on 5 October 2026.

Before you leave school

Things you can do now

  • Take English and a business or computing course. Being able to write a clear paragraph is the single most transferable skill here.
  • Volunteer to run something with a process, like a club's sign-ups or a fundraiser, and write down how it works so someone else could do it.
  • Ask an adult who uses a work system, a nurse, a clerk, a manager, what the most annoying part of it is. That is a requirement waiting to happen.
  • If your school offers co-op, ask for an office or IT placement and ask to shadow somebody in a meeting.

Test it

Do this before you decide anything

Reading about a job tells you almost nothing. This is designed to be done alone, this week, for free.

Write requirements for something that annoys you

About 75 minutes
  1. Pick an app or a school process that irritates you, such as booking a room, ordering lunch, or submitting a form.
  2. Watch two people use it, or use it yourself while writing down every step and every pause. Do not fix anything yet.
  3. Write five requirements in the form 'a student can do X in under Y', where each can be tested with a yes or no. Notice how hard the first draft is.
  4. Read them to someone and ask them to find one that could be understood two ways. Rewrite that one.

What it tells you. If you enjoyed the precision and the hunt for the ambiguous sentence, this is a strong fit. If you only wanted to build a better version yourself, look at software development instead. If writing five testable sentences felt like punishment, a more hands-on technical role will suit you better.

Better than any article

Questions for somebody who does this job

Most people say yes to a teenager who asks good questions. These are the ones that get real answers rather than encouragement.

  1. “How much of your week is writing and how much is talking?”
  2. “What was the worst misunderstanding between users and developers you have seen?”
  3. “How did you get from your first job into analysis?”
  4. “Did a certification help, or did experience do the work?”
  5. “How do you handle two stakeholders who want opposite things?”
  6. “What do you wish somebody told you before you took the job?”

Could you own one of these?

The part other career sites never mention

Yes, as an independent consultant or contractor, but not early. Clients pay for an analyst who has seen projects go wrong, so you build experience as an employee first. Self-employment is a smaller share in this group than across all jobs in Job Bank's figures, so most people do it as employees.

Business 101 is free and teaches that part

Quick answers

Questions people ask about this job

How much does a business systems analyst make in Ontario?

The median pay for a business systems analyst in Ontario is $45.13 an hour, according to Job Bank (reference period 2023-2024, updated 19 November 2025). The range Job Bank publishes runs from $33.33 to $62.50 an hour. Pay varies by region, employer and experience.

What is the job outlook for a business systems analyst in Ontario?

Job Bank rates the employment outlook for this work in Ontario as limited for 2025-2027 (updated 10 December 2025). Employment growth will lead to a few new positions. A moderate number of positions will become available due to retirements. There are several unemployed workers with recent experience in this occupation. A lower rating means more competition for each opening, not that no one is hiring.

What do you need to become a business systems analyst in Ontario?

Job Bank says this work usually needs a university degree. The usual route in Ontario, in order: Finish high school with English, maths and a computing course; Pick a business-and-technology programme; Get a first job near the work.

How many people work as a business systems analyst in Ontario, and how many are women?

Job Bank counts about 18,200 people working in this job in Ontario. 45% of them are women, compared with 48% across all jobs. That describes who does the work today, not who can.

Tech and engineering jobs: who is hiring What can you do with your degree?

Not sure this is the right list to be reading

Start from yourself, not from the job.

Future Finder is free, takes about ten minutes, needs no account and stores nothing. It will tell you which kinds of work you lean toward, and which of these pages are worth your time.

Try Future Finder — freeAll jobs

Parent of a teenager weighing this up? Career coaching for teens gets them talking to people who do the work, anywhere in Ontario.

If this appeals, look at these too

information systems specialist software tester data analyst it support technician management consultant software developer

Read next

Careers that match your strengths Figuring out what fits you University vs college vs apprenticeship All careers guides

Wages and training requirements change. Every figure on this page is linked to the body that publishes it, and the review date above says when we last checked. If you find something out of date, tell us and we will fix it.