Source description
About the role
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.
More at Parallel Domain