Job Opportunities API

ABOUT TERMINAL Terminal builds telematics data infrastructure for the commercial fleet industry. Commercial auto insurers and fleet software companies, including industry leaders like Intact Insurance, depend on our platform to access GPS, speeding, and vehicle data from 330+ telematics providers. We recently raised our Series A led by Battery Ventures and are backed by Y Combinator, Golden Ventures, Penske Transportation Solutions, and Intact Private Capital. Our team works together in person in Toronto, combining early-stage speed with late-stage maturity while processing many terabytes of vehicle data every day. For more on working at Terminal, see our careers page at withterminal.com/careers http://withterminal.com/careers. Note that this role is only open to Toronto/GTA-based candidates. ABOUT THE ROLE Post-sales at Terminal is NOT a support function - it is our primary growth engine. Our model compounds through the scaling, expansion, and retention of existing customers, not only through new logos, making this role the operational core of the company’s growth. We’re hiring our first Customer Engineer to own the post-sign technical lifecycle inside Terminal’s enterprise accounts, end-to-end. You won’t inherit a production-readiness standard or an implementation playbook; rather, you’ll have the opportunity to write them. Working in a dedicated pod with a Strategic Account Manager and a Customer Success Manager, you take each customer from signed contract to production readiness and then to technical scaling across the fleets, and you build the system that every Customer Engineer after you will inherit. You own the technical truth of the account: what is integrated, what is certified, and what it will take to scale. You turn integration ambiguity into a dated, defensible path to go-live, and you own every technical escalation until it is closed. You take account-level direction from the SAM and report to the COO. This is a senior, high-accountability role: we’re hiring someone who has delivered enterprise implementations in a post-sales context, specifically, not something adjacent. WHAT YOU OWN, AND WHAT YOU DON’T You own three things: - The technical path to: technical solutioning, integration design, and the Definition of Done for every go-live, the milestone that the whole pod’s time-to-value depends on. - Enablement and technical scaling: getting each customer’s technical team self-sufficient on the platform, then scaling from the first production fleet to full fleet syncing at contracted quality. - Technical escalation ownership: you own incidents and integration escalations end to end, and you pull in a Sales Engineer when load crosses the threshold. You do not own commercial negotiation or pricing (the Strategic Account Manager), or adoption mechanics and the success plan (the Customer Success Manager). You also do not own bespoke professional services, pure support work, or roadmap commitments made without product-team alignment. The pod model exists so each role can go deep rather than broad. Role clarity is a feature, not a limitation: if you find yourself doing someone else’s job, your job is to name it, not absorb it. WHAT YOU'LL DO 1) Own the technical path to production readiness - Own technical solutioning and integration design for each enterprise account: delivery mode (Streaming / Warehouse Replication / API pull), data environment, and known dependencies, confirmed and documented at kickoff. - Own the Definition of Done for go-live across all four domains: technical readiness criteria, data-quality validation gates, security and compliance sign-off, and customer-side readiness. - Publish the readiness checklist to the customer at kickoff, not at go-live: they know the criteria from day one. Proposed ways to measure success and progress - Time-to-readiness: production readiness milestones met on the milestone calendar set at kickoff. - Data q