Engagement Engineer, Applied AI Lead the engagement. Design the system. Ship the code.
LOC A T ION
Toronto, Ontario. Hybrid, with travel to client sites.
EM PL OYM EN T T YPE
Full-time
REPOR T S T O
Founder and Chief Science Officer
EXPER IENC E
Approximately five years
TEA M
Delivery pod of two to four engineers
T H E P R O B L E M Y O U W O U L D B E W O R K I N G O N
Large enterprises have IT problems that do not have reference implementations. Schemas that were never designed to talk to each other and now have to. Engineering change processes that depend on a handful of people holding twenty years of context in their heads. Customer health signals scattered across four systems that nobody has ever joined. These are not problems you solve by wiring up a chatbot.
We solve them by building agentic systems that are genuinely novel each time: new decomposition, new evaluation criteria, new places to put a human in the loop. There is no playbook to run. The work is figuring out what the system should be, then building it, inside an organization that measures revenue in billions and has strong opinions about how software gets deployed.
A B O U T CLIENT
Our client is a Toronto-based AI and HCI research company. We build agentic systems and document intelligence products for enterprises in property technology, financial services, industrial manufacturing, and site selection advisory. Our engagements are not pilots that die in a slide deck. They are production systems with named business owners, acceptance criteria, and real users on the other end.
We are small and deliberately so. Every engineer here talks to clients, and the client work feeds the product work.
T H E R O L E
You would lead client engagements end to end.
That means being the person who understands the client's problem well enough to argue with them about it, designs the system that addresses it, writes a meaningful share of the code, and owns the weekly conversation about what is on track and what is not. You will be talking to CTOs, heads of architecture, and business owners who have been living with the problem far longer than you have. You need to be credible in that room and still be shipping on Thursday.
This is roughly 60 percent hands-on engineering and 40 percent engagement leadership. If you want to be heads-down in a repo all week, this is the wrong seat. If you want to build systems that a Head of Global Architecture will be depending on six weeks from now, and have their phone number, this is the right one.
W H A T Y O U W I L L D O
- Own one or two concurrent engagements as the primary technical lead and the client's main point of contact.
- Translate ambiguous enterprise problems into scoped, shippable technical workstreams with defensible acceptance criteria.
- Design and ship agentic systems end to end: ingestion, orchestration, tool use, retrieval, evaluation, and the human-in-the-loop surfaces