Business Systems Analyst

telMAX•Markham, ON

3d•CA$60,000 - CA$75,000•Hybrid

About The Position

Reporting to the Head of Network & Systems, the Business Analyst is the connective tissue between what the business needs and what the Systems Engineering team builds. This role owns the systems request intake process, translates operational problems into clear specifications that developers can build from, and ensures the work that gets prioritized is the work that matters most. On any given day that might mean writing requirements, managing the backlog, pulling data for a quick report, or answering a question before it becomes a meeting. The Business Systems Analyst works closely with Network Engineering, Visibility & OSS, and Systems Engineering teams, and occasionally with Finance, Customer Operations, and external vendors.

Requirements

2 years in a business analyst, project coordinator, operations analyst, or similar role - ideally in a technical or infrastructure environment.
Demonstrated ability to write requirements, manage a backlog, and ship work across a team.
Comfortable with project management and documentation tools. Domain fit matters more than a specific tool set.
Structured Thinking: Able to take an incomplete or half-formed problem and turn it into a structured brief quickly. Comfortable sitting with ambiguity long enough to ask the right questions before jumping to solutions.
Effective Communication: Communicates clearly in writing and in conversation. Can explain a technical constraint to a non-technical stakeholder and a business requirement to a developer and knows which version of the message each audience needs. Follows through without being reminded.
Curiosity About the Domain: Does not need a telecom background, but brings genuine curiosity about how an ISP operates — the network, the systems, the business model. Will invest the time to understand the domain and ask questions until the full picture is clear.
Practical with Data: Comfortable working directly with data to answer a question or support a decision. That might mean writing a SQL query, building a pivot table, or pulling together a quick dashboard. Not a data engineering role, but data fluency is expected.
Self-Directed: You can own a process without being told exactly how to run it. Knows when to escalate and when to just get it done.

Nice To Haves

Telecom, ISP, or network operations exposure is a meaningful asset but not required.
Degree or diploma in Business, Computer Science, Information Systems, or equivalent. Credentials are an asset, but not required.

Responsibilities

Own the systems request intake process, gather requirements, clarify scope, and work with the development team to prioritize against the existing backlog.
Translate business needs into clear, actionable specifications that developers can build from. Know when a requirement is ready and when it is not.
Build and maintain reports that give operational teams visibility into what they need to make decisions. Comfortable working with data directly and presenting findings clearly.
Keep projects moving. Track milestones, surface blockers early, and communicate status to stakeholders without being asked.
Identify where the team is losing time to friction and propose practical improvements.