About the Role

Long before an autonomous vehicle is ever tested in one of our virtual worlds, an engineer at Parallel Domain has to build, test, and ship the software that creates that world. The Development Platform team owns the systems that lets them ship safer features, faster.

Parallel Domain builds the synthetic data and simulation platform that autonomous-vehicle and robotics teams use to develop and validate their systems. Our team owns the connective tissue of the engineering org: the SDK and platform services every other team builds on, the tooling and CI that move our code, and the contracts that hold our products together. When we do our job well, every engineer at the company ships faster and more safely.

We're hiring a senior software engineer for our team. Our area of ownership and work spans the entire engineering org, and our tech stack is wide and varied: Python and C++, data pipelines, databases, CI and build systems, transport layers, and cloud infrastructure. The engineers that thrive here are excited about following a problem wherever it leads instead of staying inside one technology. You'll own meaningful, ambiguous projects from definition through delivery, with real autonomy over how they get done.

The base pay range for this role is between CA$155,000 and CA$175,000.

Responsibilities

• •Own ambiguous projects end to end, taking on broad loosely-defined problems and driving them to a clean outcome, deciding the approach yourself rather than waiting for a plan.
• •Take a high-level product view of the features you ship, thinking past the immediate task to the user and the product: why a feature matters, who depends on it, and what done really means.
• •Think architecturally about complex systems, seeing how a large system fits together and influencing their collective design: which component owns what, how responsibilities are divided, and the interfaces between constituent parts.
• •Work across the whole platform over time: Python pipelines and SDK, control-plane services and databases, CI and build systems, and the C++/gRPC service layer.
• •Collaborate regularly with reconstruction/ML, content, and product engineers, often connecting work that spans more than one team.
• •Raise the bar by making sound architectural calls, weighing tradeoffs pragmatically, and improving how the team designs, tests, and ships.

What You Need to Succeed

• •Autonomy and ownership: a track record of owning ambiguous, cross-team projects end to end and driving them to completion.
• •Strong software engineering background with a proven track record of delivering complex projects involving multiple connected components.
• •Experience building and operating production data or service pipelines, with comfort in databases and data modeling.
• •Ability to move comfortably across unfamiliar, under-documented systems and get your footing to drive value quickly.
• •Strong collaboration and clear communication skills with both engineers and non-engineers.

Skills and Technologies

• •Languages and Frameworks: Python, C++, gRPC, Proto, FastAPI, Flask, PostgreSQL, CMake
• •Systems and Infrastructure: Apache Airflow, AWS (including EKS, ECR, S3, RDS, and Lambda), Kubernetes, Docker, Jenkins, GitHub Actions
• •Domain Experience: Build, CI/CD and Release Engineering; Cross-Product and Cross-Service Interfaces; Test Strategy and Quality Infrastructure; Familiarity with Simulation in Autonomous Systems

What Makes a Great Candidate

The best person for this role is energized by breadth and ambiguity. You would rather own a hard, fuzzy problem that crosses four systems than a well-defined ticket in one. Most of all, you take ownership: you can be handed a goal instead of a plan and trusted to deliver, while making the team and the platform better as you go.