APIs are like opinions. Everybody’s got one. But when you manage hundreds of different mobility APIs, you don’t want a chorus of conflicting opinions. You want the nice, smooth conformity of a (checks notes) benevolent dictatorship. Whether it’s a transit agency API, or one provided by a carshare/bikeshare/scooter/ridehail operator, it’ll be your job to work with those disparate sources—however messy they might be!—find the relevant endpoints, and make sure they’re all speaking the same language: ours.
You’ll be adding deep partner integrations. Ones that let Transit riders unlock a shared bike or scooter, book a carshare vehicle, hail a ride, compare prices and ETAs between operators, and pay/sign-up for the aforementioned services. (Yes, madame! All within one app.) You’ll also help us make it less cumbersome to purchase transit tickets: we’re adding mobile ticketing for multiple transit agencies, and you’ll be that project’s overseer.
What to expect? This job is ~20% back end, ~80% front end. “Back end” is codeword for creating consistency out of chaos, making sure every rider can expect a reliable experience when they go to a different Transit city, or try a different mode. “Front end” is codeword for breathless simplicity, sweating the details to ensure Transit isn’t just one place you can procure different modes of transport — it’s your default, because we make it so dang easy.
Examples of what you'd be working on:
- Creating a new bikeshare, ridehail, scooter, or ticketing integration.
- Working with product designers to create web-based user experiences in the app.
- Setting up the required server-side components (proxies, vaults, etc.)
- Creating dashboards to follow performance metrics.
- Triaging, investigating bugs, fixing ones found in our current integrations.
- Improving our internal sales reporting tools.
- Working on our internal release and integration toolkits.
If you're interested, here’s what we need on your end: