Zūm is revolutionizing mass mobility with its Connected Mobility Experience ( Zūm CMX ™) system that connects and coordinates people, vehicles, and operations in real time. In the $50 billion student mobility market – the largest segment of the mass mobility industry – Zūm CMX is transforming a daily source of anxiety and disruption into a reliable, transparent, and efficient mobility experience for students and families. Today, more than 7,500 schools rely on Zūm CMX . Recognized globally for its innovative approach and operational execution, Zūm has been named to Fast Company’s World’s Most Innovative Companies, CNBC Disruptor 50 and Changemakers, the World Economic Forum, and the Financial Times’ Fastest Growing Companies lists. Zūm is backed by leading investors including Sequoia Capital, GIC, TPG, and Softbank.
This role is based at the Company’s headquarters in Redwood Shores, CA and requires you to be onsite 3x/week (Monday, Tuesday, and Thursday). We will only consider candidates already based in the Bay Area. Who You Are:
- You care as much about how software gets built as what it does, and you measure a platform by the features it enables.
- You want to build scalable infrastructure and technologies that enable Zūm products to grow and adapt at the pace today's AI makes possible.
- You lead through execution and influence through adoption of the platforms you build.
- When someone asks for "the best" solution, you map out the tradeoffs, present real options, and commit to a recommendation.
- You start simple, add complexity only when the data proves you need it, and lean on experience when measuring isn't worth the cost.
- Products created on your platform are easy to maintain and a joy to build on.
What You'll Do:
- Own the architecture and roadmap for Zūm's product platform, and build it - our product engineering team uses TypeScript/Node.js, Kubernetes, PostgreSQL, OpenSearch, Redis, Kafka, and gRPC.
- Stay hands-on with the product: build and review features, so foundational layers stay grounded in how they're actually used.
- Work with product teams to decide what stays in the monolith and what becomes its own service, and make that extraction process routine and low-risk when it happens.
- Make security and compliance part of the platform by design: build shared primitives for authentication and access rules to sensitive data, so product teams build on secure, policy-aligned foundations.
- Watch how the platform behaves under real production load and evolve it ahead of need: spot emerging bottlenecks (event-loop stalls, slow queries, locking, index design, partition skew, consumer lag, RPC latency, retry storms, etc.), trace them to the architectural cause, and turn recurring problems into platform improvements.