Business Analyst

Logistics Alliance; Mississauga; Hybrid; CAD 65,000 - 75,000; Full time

Job summary

Logistics Alliance is seeking a results-driven Business Analyst for our Mississauga head office. This hybrid role splits time between internal requirements sessions and direct client interactions to define system needs for freight routing, reporting, and data integration.

You will translate operations problems into clear user stories, collaborate with IT or vendors during delivery, and create practical guides for users.

Qualifications

• Bachelor's degree in Information Systems or related field.
• 2 to 5 years in business analysis, systems support, or logistics operations.
• Comfortable working directly with external clients, not just internal stakeholders.
• Working knowledge of logistics processes, including freight routing, transportation documentation, and both less-than-truckload and full truckload freight.
• Experience supporting requirements gathering or a system implementation.
• Working SQL skills: this role needs someone who can query and validate data directly, not just talk about it.
• Comfortable writing clear documentation for a non-technical audience, internal or client-facing.

Responsibilities

• Meet with operations teams to understand inefficiencies in freight routing, carrier communication, and daily logistics work.
• Meet with clients to understand how they use LA's systems and what they need from them.
• Turn both into clear requirements, process maps, and user stories the technology team can build from.

Skills

SQL

Client communication

Documentation writing

Process mapping

Education

Bachelor's degree in Information Systems or related field

Tools

Lucidchart

Visio

Atlassian suite

Job description

Department: Technology Reports To: VP, Technology Location: Hybrid, Mississauga Head Office Compensation: $65,000-$75,000

The Reality of This Role

Logistics Alliance is a non-asset based logistics provider. We don't own trucks or warehouses; we coordinate other providers' networks on behalf of our clients. This role is split roughly in half. Half the time you're internal-facing: translating operations problems (freight routing, carrier communication) into requirements the technology team can build from. The other half you're external-facing: working directly with clients on the systems and tools they use to interact with LA, whether that's a visibility portal, a reporting dashboard, or a data integration.

That mix is the job. You need to be equally credible sitting in an internal requirements session and sitting on a call with a client explaining why a feature works the way it does, or capturing what they actually need next.

What Your Day Actually Looks Like

• Morning: A requirements conversation with an operations team, digging into a pain point in freight routing or carrier communication. Mostly listening and asking questions.
• Mid-Morning: Turning what you heard into something usable: a process flow, a set of user stories, a first draft of requirements the technology team can build from.
• Afternoon: Sitting with IT or a vendor to test a feature against what the business actually needs, or putting together a plain-language reference guide for the team that will use it.
• Late Afternoon: Unblocking an operations user who got stuck, or pulling together the data behind a metric someone in leadership asked about.

You'll Thrive Here If...

• You ask "why" until you actually understand the problem: a lot of this job is translating between groups (operations, technology, and clients) that don't naturally speak the same language.
• You're as comfortable on a client call as you are in an internal working session: the tone and stakes shift, and you need to shift with them.
• You write clearly: a confusing process document or a vague client update both create more problems than they solve.
• You don't need a large team around you: this is a small function, and you'll often be the one connecting the dots.

What You Should Know

This is a generalist role inside a small technology function, and it's client-facing on top of that. There isn't a bench of specialists to hand things off to, so you'll typically own something from the first conversation (internal or external) through to the training material or client update left behind after it ships. That autonomy, and the direct client exposure, is the appeal for the right person and the adjustment for the wrong one.

Key Accountabilities

Requirements & Solution Design

• Meet with operations teams to understand inefficiencies in freight routing, carrier communication, and daily logistics work.
• Meet with clients to understand how they use LA's systems and what they need from them.
• Turn both into clear requirements, process maps, and user stories the technology team can build from.

Client & Vendor Liaison

• Serve as the day-to-day point of contact for clients on technology questions: portal access, reporting, data integration issues.
• Serve as the liaison between technical teams and business users, internal and external, throughout implementation.
• Support user testing before a new tool or process goes live, and help resolve issues as people adjust to it.

Training & Adoption

• Build practical guides and training materials for internal users and, where needed, for clients using LA's systems.
• Collect feedback, internal and client-side, and feed it into the next round of improvements.

Reporting & Continuous Improvement

• Help pull together the data and performance metrics operations leadership and clients use to track results.
• Flag opportunities to further streamline freight visibility and client-facing reporting.

What We're Looking For

• Bachelor's degree in Information Systems or a related field.
• 2 to 5 years in business analysis, systems support, or logistics operations.
• Comfortable working directly with external clients, not just internal stakeholders.
• Working knowledge of logistics processes, including freight routing, transportation documentation, and both less-than-truckload and full truckload freight.
• Experience supporting requirements gathering or a system implementation.
• Working SQL skills: this role needs someone who can query and validate data directly, not just talk about it.
• Comfortable writing clear documentation for a non-technical audience, internal or client-facing.

Nice to Have

• Experience with process mapping tools such as Lucidchart or Visio.
• Familiarity with common project tools, such as the Atlassian suite.

Why Logistics Alliance

We're a fast-growing non-asset based logistics company, which means our edge comes from how well we run, not from owning trucks or warehouses. That makes this role more consequential than a Business Analyst title elsewhere: you'll see your work show up in how reliably freight moves for our clients within weeks, not years. If you want ownership over problems that matter and a real shot at building things from scratch, this is the place.