In this role you will be responsible for the most critical in-vehicle component for what we call “Ride Management”. It's the primary source of truth of the ride state and makes critical decisions about what to present to riders and other systems at any point in the ride as well as when to react to input from various other software and hardware components. (i.e. is the requested mutation possible?).
This component interacts directly with much of the in-vehicle hardware responsible for serving the riders. For example, if the rider presses the button to open the door, this goes through a secure gateway into this Ride State Machine which in-turn decides if and how to interact with all the needed components to accomplish rider’s request. If it's possible given the current vehicle and ride state. Most in-vehicle functionality that will serve riders needs corresponding work in the Ride State Machine, so this role requires not just a great CS thinking, but also a passion towards providing the best experience to the end users/riders as well as cross-teams collaboration with teams of engineers for other in-vehicle components.