Senior SDET, Agentic Quality

About Onfleet Onfleet’s mission is to power the future of commerce by enabling businesses of all sizes to move goods more efficiently and delightfully. Our product includes intuitive smartphone apps for drivers, a powerful modern web dashboard for logistics teams, and automatic notifications and real-time tracking for recipients. Onfleet powers millions of deliveries every week for thousands of businesses around the world across a range of industries, from grocery and prepared meals to pharmacy, flowers, and furniture. About the role Onfleet is hiring two senior SDETs to shape how our engineering teams build and trust automated quality. At Onfleet, the team that builds a feature owns its quality. Developers write and maintain their own tests. Your job is to make those teams better at it: you pair with them, teach, review, and find the cases they missed. You will not be the person who tests everyone else's work. Together with our quality leads, you’ll own our test frameworks and the shared quality tooling every team depends on. You’ll also do feature development in production code and internal tooling. You’ll be part of our core quality engineering group, sometimes embedded on one team and sometimes working across several. You’ll start by taking ownership of our existing automation and making it more reliable and complete, alongside greenfield work on new platform services. We measure this role by what the teams can do because you were there. How We Work We code using agents, and nearly 100% of our code is written this way. Generating code is the easy part. Knowing what good looks like, and holding the bar, is the job. The engineers who thrive here are scrutinizing and questioning: they reject AI slop and catch the wrong call before it ships. Every engineer helps improve how we work instead of only following it. For this role that means building and improving the agentic tooling itself: test generation, review, verification, and the workflows around them. We are candid and have a low ego. Challenge us on tooling direction, and expect to be challenged back. What You’ll Do: Strengthen the current suite. Improve reliability, extend coverage, and modernize patterns. A flaky test is a failing test. Own the test frameworks. Unit, integration, and end-to-end, treated with the same care as production code. Own the quality gates in CI/CD (continuous integration and continuous delivery). Pipelines, checks, and gates, so standards are enforced by the system and not by people. Build agentic quality tooling. Extend the agents and workflows we use for test design, review, and verification. Raise the bar through teams. Pair on test design, review code, help make hard-to-reach code testable, and write things down so the practice outlives any one person. Ask the testability question early. In planning, ask how we'll test it and how we'll know it broke in production. Know when a release is healthy. Metrics, dashboards and alerts that tell us something is wrong before a customer does, and that tell a team whether a release is safe to keep rolling out. Ship features. Full-stack work in production code and internal tooling, alongside the teams you support. What You'll Bring (required): 8 or more years of professional software development experience, in any role. 5 or more years where building and maintaining test automation was a core part of your job, as an SDET, test automation engineer, or software engineer who owned test infrastructure. Your title matters less than the work. You build software, not just tests: test frameworks, internal tools, CI tooling, or product features. You want feature development in production code and internal tooling to be part of your job here. Depth across unit, integration, and end-to-end testing, including hands-on work with a browser framework such as Playwright or Cypress. Hands-on CI ownership: you have created, configured, or fixed a CI pipeline (GitHub Actions or equivalent), not just used one. A track record of being the person who drove automated test coverage on a team, whatever your role was. Working knowledge of DevOps practice: how code is built, deployed and monitored in production. You have added metrics, dashboards or alerts so a team knew when something broke. Daily professional use of AI coding agents, and experience building or improving agentic tooling, not just using it. A multiplier mindset: you get your satisfaction from the team shipping safer and faster, not from your own test count. Excellent written and spoken English, roughly C1 level, and experience working day to day on an international team. Nice To Have: Mobile development (Android or iOS) and mobile test automation, using native frameworks such as Espresso or XCUITest, or cross-platform tools such as Appium or Maestro. TypeScript, Node.js, and React. Rust, or another statically typed language. Clear evidence of driving CI/CD practice for a whole team or company. Production canaries and progressive delivery: you have used production signals (error rates, latency, business metrics) to decide whether a release continues or rolls back, through canaries, feature flags or automated rollback. Test data and environment management: getting a realistic system into a known state quickly and repeatably. Test-driven development (TDD). AWS and cloud-native services. Location and Benefits: Remote, open to candidates based in Canada or Latin America. The team works on US Pacific Time. You'll need to reliably work a schedule that frequently matches US Pacific business hours (9am to 5pm PT). Flexible PTO. Laptop and work-from-home setup stipend. Monthly technology stipends (internet and AI tooling). Onfleet is an Equal Opportunity Employer Onfleet's culture is one that strongly values diversity in its workplace and we are committed to working with potential team members who can bring diverse perspectives and experience to our company and culture. We do not make hiring or employment decisions on the basis of race, color, religion, creed, gender, national origin, age, disability, veteran status, marital status, pregnancy, sex, gender expression or identity, sexual orientation, citizenship, or any other basis protected by applicable local, state or federal law. We highly encourage members of underrepresented groups to apply and we will consider qualified applicants with arrest and conviction records. Compensation The base salary range for this role is $70,000 to $95,000 USD per year for candidates in both Canada and Latin America, depending on experience, skills, and background. Where an offer lands within that range reflects the depth and experience a candidate brings to the role. How We Hire You need an identity-verified LinkedIn profile to apply. That's the free "Verified" badge, the shield icon next to your name. We check for it, and applications without it don't move forward. Before any offer, we verify your identity and work history. That includes a live video ID check and reference calls. We use AI, automated systems, and a person to review applications: every application that meets the requirements is also read by an engineering leader or a recruiter. If you misrepresent your identity or experience, the process ends.

Strengthen the current suite. Improve reliability, extend coverage, and modernize patterns. A flaky test is a failing test. Own the test frameworks. Unit, integration, and end-to-end, treated with the same care as production code. Own the quality gates in CI/CD (continuous integration and continuous delivery). Pipelines, checks, and gates, so standards are enforced by the system and not by people. Build agentic quality tooling. Extend the agents and workflows we use for test design, review, and verification. Raise the bar through teams. Pair on test design, review code, help make hard-to-reach code testable, and write things down so the practice outlives any one person. Ask the testability question early. In planning, ask how we'll test it and how we'll know it broke in production. Know when a release is healthy. Metrics, dashboards and alerts that tell us something is wrong before a customer does, and that tell a team whether a release is safe to keep rolling out. Ship features. Full-stack work in production code and internal tooling, alongside the teams you support. What You'll Bring (required): 8 or more years of professional software development experience, in any role. 5 or more years where building and maintaining test automation was a core part of your job, as an SDET, test automation engineer, or software engineer who owned test infrastructure. Your title matters less than the work. You build software, not just tests: test frameworks, internal tools, CI tooling, or product features. You want feature development in production code and internal tooling to be part of your job here. Depth across unit, integration, and end-to-end testing, including hands-on work with a browser framework such as Playwright or Cypress. Hands-on CI ownership: you have created, configured, or fixed a CI pipeline (GitHub Actions or equivalent), not just used one. A track record of being the person who drove automated test coverage on a team, whatever your role was. Working knowledge of DevOps practice: how code is built, deployed and monitored in production. You have added metrics, dashboards or alerts so a team knew when something broke. Daily professional use of AI coding agents, and experience building or improving agentic tooling, not just using it. A multiplier mindset: you get your satisfaction from the team shipping safer and faster, not from your own test count. Excellent written and spoken English, roughly C1 level, and experience working day to day on an international team.