Engineering
Forward Deployed Engineer
Sit inside a client's operations, find the work that is actually costing them, and ship AI into the systems they already run on — then stay accountable for the number it moves.
- Location
- Montreal, Canada
- Type
- Full-time
- Workplace
- Hybrid
- Compensation
- Competitive base plus outcome-linked upside, discussed openly in the first conversation.
This is not a consulting role and it is not a platform role. You spend the first two weeks alongside the people doing the work: reading tickets, tracing one request end to end, and finding the twenty minutes a day that a hundred people are all losing to the same thing. Then you build into their systems directly — with our own agent tooling behind you — and you stay long enough to be answerable for whether it held. One engineer covers ground that used to take a team, because the factory does the repetitive half and you do the judgment.
AWhat you will own
- Spend the first weeks of an engagement inside the client's operations, mapping how the work really runs rather than how the org chart says it does.
- Agree one number with the client before building, and report it monthly from their own data for as long as we are there.
- Ship production software into existing systems — their stack, their exceptions, their edge cases — and own what happens after it deploys.
- Drive our agent factory: write the work orders, review what the agents produce, approve what deploys. None of it runs autonomously.
- Meet people in the tools they already have open instead of asking them to adopt a new place to log in.
- Say no to the work that will not survive real use, including when it is the work the client asked for.
BWhat we need
- You have shipped and operated production software that other people depended on, and you have been on the hook when it broke.
- You are comfortable in someone else's codebase and someone else's business, without needing either to be rewritten first.
- You can talk to an operations lead and a CFO in their language, and come back with the constraint rather than the feature request.
- You work fluently with coding agents and can tell a plausible diff from a correct one.
- You would rather be measured on an outcome than on a deliverable.
- Comfortable travelling to client sites within your market.
↓