•
Own ambiguous projects end to end. You'll take on broad, loosely-defined problems and drive them to a clean outcome, deciding the approach yourself rather than waiting for a plan. Autonomy is the heart of the role.
•
Take a high-level product view of the features you ship. You think past the immediate task to the user and the product: why a feature matters, who depends on it, and what "done" really means. You make engineering decisions with that context instead of just building to spec.
•
Think architecturally about complex systems. You see how a large system fits together and influence their collective design: which component owns what, how responsibilities are divided, and the interfaces between constituent parts.
•
Work across the whole platform. You'll range across the full surface of the platform over time: our Python pipelines and SDK, our control-plane services and databases, our CI and build systems, and our C++/gRPC service layer. You go where the work is most valuable rather than staying in one lane.
•
Collaborate across teams. You'll partner regularly with our reconstruction/ML, content, and product engineers, and you'll often be the person connecting work that spans more than one team.
•
Raise the bar. You'll make sound architectural calls, weigh tradeoffs pragmatically, and improve how the team designs, tests, and ships. You make the engineers around you better.
•
Autonomy and Ownership. You have a track record of owning ambiguous, cross-team projects end to end and driving them to completion.
•
Track-record of Delivering. You're a strong software engineer with a proven track-record of delivering complex projects involving multiple connected components.
•
Pipelines and Data Systems. You've built and operated production data or service pipelines, and you're comfortable with databases and data modeling.
•
Comfort in uncertainty . You move comfortably across unfamiliar, under-documented systems and can get your footing to drive value quickly.
•
Strong collaboration . You work well across teams and disciplines, and communicate clearly with both engineers and non-engineers.
This is the surface area our team works across and has ownership over and below are a set of skills and technologies that you will interact with on a daily basis.
. On the Dev Platform Team, we value range, adaptability and flexibility.
•
Languages and Frameworks. Python, C++, gRPC, Proto, FastAPI, Flask, PostgreSQL, CMake
•
Systems & 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 & Cross-Service Interfaces. Test Strategy & Quality Infrastructure. Familiarity with Simulation in Autonomous Systems
The best person for this role is energized by breadth and ambiguity. You'd 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.