Launch League

Technology · Analyzing & Problem-solving

Information systems specialist: what the job actually is

Working out how an organisation's computer systems should fit together, then making sure they do.

Published Last reviewed How we research and correct this

Information systems specialist: quick facts

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

Median pay in Ontario
$47.00 an hour
Pay range (low to high)
$28.59 to $72.60 an hour
Job outlook, 2025-2027
Moderate
People working in it in Ontario
115,000
Usually needs
Usually a university degree

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

The work

What this job actually is

  • Deciding how an organisation's software, data and networks should be arranged so that they work together, then writing that down well enough that other people can build it.
  • Job Bank files several job titles under this one group, including systems architect and solutions architect. It is a broad group, so the day-to-day varies a lot between a bank, a government department and a small consulting firm.
  • Much of the work is conversation. You talk to the people who use a system, find out what they actually do rather than what the manual says, and turn that into a design somebody can build.
  • A lot of it is old systems. Few organisations start from nothing, so the job is often connecting a thing built years ago to a thing being built now without breaking either.
  • You are usually accountable for a decision long after you have made it. If the design was wrong, somebody will find out in eighteen months and the document has your name on it.

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:45 — Read the overnight messages. A system you designed has a problem somebody wants explained, and the explanation is in a diagram you drew last spring.
  2. 9:15 — Stand-up with a team who build the thing. You are not the boss of this meeting, you are the person who knows why the odd part is odd.
  3. 10:00 — Workshop with the finance people about how invoices move between two systems. Half of it is discovering that two departments use the same word for different things.
  4. 11:30 — Draw. A diagram of the new arrangement, redrawn three times because the first two hid a problem.
  5. 12:15 — Lunch at the desk, reading the supplier's documentation for a product you are being asked to approve.
  6. 13:00 — Review a design somebody else wrote. Your job is to find the sentence that will cause trouble later, politely.
  7. 14:30 — Argue gently with a developer about whether a shortcut is acceptable. Sometimes it is.
  8. 15:30 — Write the decision down, with the reasons and what you rejected. Future you, and whoever replaces you, will need it.
  9. 16:30 — Answer the question nobody asked in the meeting but everyone wanted answered.
  10. 17:15 — Update the document and close the laptop. The system you work on is invisible when it works.

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 like seeing how the pieces of a big thing connect and you get irritated when a diagram leaves out a box.
  • You can explain a technical idea to someone who does not want the technical version.
  • You would rather decide and document than spend all day writing the code yourself.
  • You are comfortable being wrong in writing and fixing it in writing.
  • You are patient with legacy: old systems, old decisions, and the colleague who built them.
You may hate this if
  • You want to see something you built running on a screen by the end of the day. This job produces documents and decisions, and the proof arrives months later.
  • Meetings drain you. A large part of the week is people, and the people are often vague about what they need.
  • You dislike being responsible for choices you do not fully control. You advise, others may overrule you, and you are still associated with the outcome.
  • You do not want to keep learning. Products and approaches change, and last year's good design can be this year's old habit.
  • You hate documentation. The deliverable is, to a surprising degree, writing.
  • You need the job to be a guaranteed growth area. Job Bank's own outlook text for this group mentions some positions being lost alongside retirements, so it is a steady field rather than a booming one.

The route in

How you actually get there in Ontario

  1. Finish high school with maths and some computing

    Job Bank's requirements page for this group asks for a bachelor's degree in computer science, computer systems engineering, software engineering, business administration or a related discipline, or a college computer science programme. Maths and any computing course keep both doors open.
  2. Choose a degree or a college programme

    Ontario colleges list computer systems and engineering technology programmes on ontariocolleges.ca, and universities list computer science and related degrees on ontariouniversitiesinfo.ca. A diploma gets you working sooner; a degree is the more common entry on the Job Bank page.
  3. Work as a builder first

    Job Bank's page says experience as a computer programmer is usually required. In practice that means you do not start as the person who designs the system; you start building parts of one, and earn the right to draw the big picture.
  4. Move toward design

    From programmer or analyst work, the step is taking on designs, reviews and decisions. The title on the door varies; what changes is that people start asking you why, rather than how.
  5. Add credentials only if an employer or a niche asks

    Job Bank says this occupation is not regulated in Ontario, so there is no licence to get. It lists some professional credentials that may be useful, for example in auditing information systems, but none is required to hold the job.

Where this comes from: Job Bank — Requirements for information systems specialists in Ontario · ontariocolleges.ca — Computer - Systems / Engineering Tech programs · ontariocolleges.ca — Computer - Repair / Maintenance programs

The money

Information systems specialist 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.

$28.59
Low (hourly)
$47.00
Median (hourly)
$72.60
High (hourly)

Ontario, NOC 21222. 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 — Information systems specialist 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

Moderate3 out of 5 stars

  • Employment decline will lead to the loss of some positions.
  • Several positions will become available due to retirements.

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.

What is changing in this work

  • The extensive use of advanced digital tools across all industries
  • The growing use of cloud technology should also support job openings
  • However the pace of job growth may be affected by recent restructuring in the technology sector

Who hires for it

  • Various industries, with the leading share employed in computer systems design services
  • Finance and insurance, mainly banks
  • Public administration, largely federal government departments
115,000
people work in this job in Ontario
28%
are women (48% across all jobs)
17%
are self-employed (15% across all jobs)

Source: Job Bank — Information systems specialists job prospects in Ontario (NOC 21222). 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 computer science and the hardest maths you can handle. The thinking in this job is structured: parts, connections, rules.
  • Build a small project with two parts that talk to each other, such as a form that saves into a spreadsheet. The talking-to-each-other part is the job in miniature.
  • Ask your co-op teacher about a placement in an IT department. Watching how an organisation's computers are actually looked after is more useful than a pamphlet.
  • Join a school club or team that needs a system, like a booking sheet or a results tracker, and be the person who works out how information moves.

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.

Draw how your own school actually runs on information

About 60 minutes
  1. Pick one thing your school does with data: attendance, a club sign-up, a cafeteria order, a timetable change. Write down every person and every list or tool it passes through, in order.
  2. Draw it as boxes and arrows on paper. Mark every arrow where information gets retyped by hand, because that is where things break.
  3. Ask one person who is part of the process, a teacher, an office worker or a student, what goes wrong with it. Add their answer to the drawing without defending the system.
  4. Redraw it once with one fix, and write two sentences on what the fix costs somebody and who would hate it.

What it tells you. If you were happily lost in the arrows and kept noticing the next broken one, that is the temperament this job runs on. A yes also means testing it against programming: you may prefer designing the arrangement or building it. If you found it dull, or wanted to just build the fix instead of drawing it, a hands-on developer or technician role may suit you better, and that is a good thing to learn at this stage.

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 designing and how much is persuading people?”
  2. “What did you build or support before you moved into design, and did that matter?”
  3. “What is the worst decision you have seen get made, and how did anyone find out?”
  4. “How much of this work is old systems rather than new ones?”
  5. “Which credential or course did you actually need, and which ones were optional?”
  6. “What would you tell a 17-year-old to learn first?”

Could you own one of these?

The part other career sites never mention

Yes, as a consultant or contractor. Job Bank's figures for this group show some people are self-employed, and consulting is a common way that happens. Realistically you need years of employed experience first, because clients are paying for judgement they can trust, and you also need to quote, invoice and chase payment.

Business 101 is free and teaches that part

Quick answers

Questions people ask about this job

How much does an information systems specialist make in Ontario?

The median pay for an information systems specialist in Ontario is $47.00 an hour, according to Job Bank (reference period 2023-2024, updated 19 November 2025). The range Job Bank publishes runs from $28.59 to $72.60 an hour. Pay varies by region, employer and experience.

What is the job outlook for an information systems specialist in Ontario?

Job Bank rates the employment outlook for this work in Ontario as moderate for 2025-2027 (updated 10 December 2025). Employment decline will lead to the loss of some positions. Several positions will become available due to retirements. A lower rating means more competition for each opening, not that no one is hiring.

What do you need to become an information systems specialist in Ontario?

Job Bank says this work usually needs a university degree. The usual route in Ontario, in order: Finish high school with maths and some computing; Choose a degree or a college programme; Work as a builder first.

Where does an information systems specialist work in Ontario?

Various industries, with the leading share employed in computer systems design services. Finance and insurance, mainly banks. Public administration, largely federal government departments. (Job Bank.)

How many people work as an information systems specialist in Ontario, and how many are women?

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

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.

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

it support technician software developer business systems analyst data analyst it manager cybersecurity specialist

Read next

University vs college vs apprenticeship Careers that match your strengths What to do after high school 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.