Reports To: Director, Technology
Department: Technology
Location: Mississauga, Ontario (hybrid)
Compensation: 85k-105k + Performance Bonus
The Reality of This Role
Logistics Alliance runs on software. We coordinate carriers, warehouses and crossdocks for Canadian retailers and manufacturers, and we don't own a single truck. What we own is the information: where freight is, what it costs, and what happens next. When that information is late or wrong, our operations team feels it within hours.
This role exists because our business teams have more good ideas for tools than we have people to build them. You'll take a problem from an operations, finance or sales team, figure out what they actually need, and ship a working solution. You'll do that mostly by directing AI coding agents rather than writing every line yourself. You'll write the requirements, review and test what gets built, deploy it, and make sure people use it.
This is not a ticket queue. You'll sit close to the business, often literally, and you'll be judged on whether the thing you built made someone's day measurably better. It's a small team, so there's no one to hand the hard parts to.
What Your Day Actually Looks Like
- Morning: You check alerts and the help desk queue for anything touching your projects. Then you join the technology huddle to hear what broke yesterday. A crossdock team mentions they're still tracking arrivals in a spreadsheet because the system doesn't show what they need. You note it.
- Mid-Morning: You sit with the crossdock team for an hour, watch how they work, and write a one-page requirement in plain language. You confirm it with the team lead before anything gets built, then log the work in Jira.
- Afternoon: You build. You break the work into tasks for AI coding agents, review what they produce, catch the parts that are wrong, and test against real shipment data in a staging environment. You check in with the Director, Technology on an integration question within our systems and tools.
- Late Afternoon: You deploy a fix from last week, walk two users through it, and update the documentation. Before signing off, you write a short note on what shipped, what's next and what's blocked.
You'll Thrive Here If...
You'd rather ship something useful this week than something perfect next quarter
- You enjoy talking to the people who'll use what you build, and you ask why before you ask how
- You already build with AI coding tools and know where they're brilliant and where they quietly get things wrong
- You test your own work because there's no QA team behind you
- You can explain a technical tradeoff to a dispatcher and a finance lead in the same afternoon
- Messy, real-world data doesn't scare you
What You Should Know
- You won't manage a team of human developers. AI agents are your build capacity, and you're accountable for what they produce.
- Priorities shift with the business. A carrier change or a new customer can reorder your week.
- Some of our tools are mature, some are spreadsheets. Part of the job is retiring the spreadsheets without breaking anyone's day.
- We work with real customer and shipment data, so you'll follow our data handling rules for AI tools.
Key Accountabilities
Understand the problem
- Work directly with internal stakeholders (operations, finance and sales teams) to turn pain points into clear, testable requirements
- Shadow users where the work happens before proposing a solution
Build and ship
- Architect solutions and direct AI agents to build internal tools, integrations and automations
- Review, correct and test everything before it goes live
- Deploy to production and own the fixes that follow
Run the work
- Manage your projects in Jira with honest status, scope and timelines
- Flag risks and tradeoffs early to Director, Technology and the requesting team
Make it stick
- Train users, write simple documentation and confirm the tool is used
- Measure whether it worked, and retire the spreadsheet or manual step it replaced
What We're Looking For
- Hands-on experience building with AI coding tools, with examples you can walk us through
- Experience writing requirements and owning project delivery
- Clear writer and communicator with non-technical teams
- Comfortable across the stack: APIs, databases, integrations and cloud deployment
- 3-6 years building and shipping software that real users depend on
- Nice to have: logistics, supply chain and/or transportation experience
- Nice to have: experience in a small company or startup where you wore several hats
