Mogo Finance Technology Inc.
DevOps Staff Platform Engineer
About this role
DevOps Staff Platform Engineer Location: Remote (Canada) Compensation: $135,000 - $170,000 CAD + bonus + meaningful equity About Orion Digital Orion Digital Corp (NASDAQ/TSX: ORIO) is a publicly listed Canadian fintech operating a multi-engine financial platform spanning lending (Mogo), payments (Carta), and wealth (Intelligent Investing). We have moved past the traditional fintech model. Capital allocation, decisioning, and risk management sit at the core of how the business creates value, and AI runs as an enabling layer across the platform rather than as a standalone product narrative. That layer is real and in use, and the work now is making it faster, safer, and harder to break. Why this role exists This role builds that layer. Platform engineering here is not a support function. Multiple business lines, regulated entities, and a public company's reporting obligations all run on infrastructure this team owns. Every deployment path, permission boundary, and audit trail either makes faster decisioning possible or quietly caps how fast the business can move. Which means the platform is where the strategy succeeds or stalls. If deploying takes a day, if an agent cannot safely touch production, if nobody can tell what changed and why, the enabling layer stays theoretical. We are hiring a Staff Platform Engineer to build it properly. The shift we are hiring for Most platform teams build for human developers. Ours builds for humans and agents, across multiple business lines and regulated entities. That changes the job:
- Golden paths become machine-executable contracts, not wiki pages. An agent has to be able to discover them, invoke them, and verify the result.
- Every probabilistic step needs a deterministic gate behind it. Tests, policy checks, and schema validation stop being hygiene and become the control system that lets autonomy scale safely.
- Agents are identities. They need scoped credentials, bounded blast radius, and audit trails that hold up across lending, payments, and securities regulation.
- Observability has to answer a new question. Not just "is the service healthy" but "did the agent do the right thing, and how do we know." If that is already how you think about the problem, keep reading. What you will do Build the substrate for agentic engineering
- Design and run the execution environments agents work in: sandboxed, reproducible, permissioned, disposable.
- Stand up and own our MCP and tool-gateway layer so agents reach infrastructure through governed interfaces instead of ad hoc credentials.
- Turn CI/CD into a validation loop: fast deterministic gates an agent can retry against until it passes, with humans on the loop rather than in it. Own the platform
- Multi-cloud Kubernetes, infrastructure as code, and GitOps (ArgoCD) delivery. Hands on keyboard, not diagrams.
- Drive infrastructure modernization across our cloud environments, including the unglamorous parts: dependency mapping, and documentation that survives your absence.