Senior/Staff Software Engineer

Quarterhill•UNAVAILABLE, UNAVAILABLE

About The Position

The Senior/Staff Software Engineer designs, builds, and operates the services at the heart of our next-generation tolling and intelligent transportation platform — a cloud-native, event-driven system that processes high volumes of roadway transactions and payments for agencies and their customers, reliably and around the clock. This is a hands-on senior individual contributor role with end-to-end ownership: you will take services from design through development, deployment, and production operation. Engineers hired at the Staff level additionally carry cross-team technical leadership — shaping architecture, raising the engineering bar, and driving multi-quarter initiatives. This role directly impacts the company by ensuring the accuracy, security, and scalability of the systems that collect and account for customer revenue.

Requirements

Must be self-motivated and a strong individual contributor, able to own ambiguous, multi-service problems end to end and deliver incrementally.
Strong written and oral communication skills — design documents, RFCs, and reviews that other engineers can build on.
Communicate clearly and concisely with all levels of leadership, both internal and external (customer), to lead meetings and presentations.
Interface with and support customers, executive staff, product management, project management, QA, and operations teams.
Exhibit a fundamental understanding of all aspects of a tolling platform from roadside to back office — including operations, integrations, and the rigor (idempotency, auditability, failure-mode analysis) demanded of systems that move money.
BS in Computer Science, Software Engineering, or equivalent work experience.
Senior level: 5+ years of professional software engineering experience. Staff level: 8+ years, including a demonstrated track record of technical leadership across teams.
Experience designing, building, and operating distributed backend systems in production — ideally event-driven and/or high-volume transaction processing — with a modern strongly typed language (e.g., Rust, Go, Kotlin, C#) and TypeScript.
Hands-on experience with cloud platforms (AWS, Azure, or Google Cloud) and containerized deployment on Kubernetes (Helm; code-first CI/CD pipelines such as Dagger or GitHub Actions).
Experience with relational and distributed SQL databases (e.g., PostgreSQL, YugabyteDB, CockroachDB); event-streaming systems (e.g., NATS, Kafka) preferred.
Proficiency working in Linux environments.

Nice To Haves

Experience in payments, financial systems, tolling, or intelligent transportation systems strongly preferred.

Responsibilities

Design event-driven, event-sourced microservices for a multi-tenant SaaS platform — from domain modeling through API contracts (GraphQL, including federated schemas, and REST) and data schemas.
Build high-throughput, low-latency transaction-processing services in a modern strongly typed language (e.g., Rust, Go, Kotlin/Java).
Implement event sourcing and CQRS patterns over an event-streaming backbone (e.g., NATS, Kafka) with strong delivery and idempotency guarantees.
Handle money correctly by construction: typed monetary amounts, auditable ledgers, idempotent effects, and defensive integration with third-party payment providers.
Contribute to TypeScript front ends built with a modern component framework (e.g., Svelte/SvelteKit, React/Next.js), including backend-for-frontend patterns, shared packages, and generated client SDKs in a monorepo.
Write thorough unit, integration, and end-to-end tests, including parallel test suites that surface concurrency defects.
Apply secure-by-design practices: least-privilege access, tenant isolation (e.g., row-level security), policy-as-code authorization (e.g., OPA), and centralized secrets management — within payment-industry (PCI DSS) and audit (e.g., SOC 2) requirements.
Own services in production: instrument with metrics, logs, and traces (e.g., OpenTelemetry, Prometheus, Grafana); lead root-cause analysis.
Deploy to Kubernetes via Helm and code-first CI/CD pipelines; keep services healthy through capacity planning and performance tuning.
Author and review design documents and RFCs; conduct architecture and peer code reviews to critique and improve engineering design.
Lead, mentor, advise, and assist in the training of junior engineers; at the Staff level, drive cross-team technical initiatives and align architecture across services.