Original listing text, shown exactly as published by the company.
About The Role
As a Product Engineer, you can focus on frontend, backend, or full-stack work building the shared systems other teams depend on.
The work is guided by a few simple questions
- Are our shared systems fast, reliable, and cost-efficient as traffic grows?
- Are we making product development safe by default, consistent, and faster?
- Can a builder connect a third-party service once and have it work safely across every app they build?
- Are user-facing surfaces consistent and fast, with shared primitives teams can build on?
- Is our codebase easy to navigate, change, and extend, including for AI coding agents?
What you’ll do
- Design reusable primitives and interfaces with clear contracts and documentation that other teams adopt
- Work directly with product teams to turn their friction into platform improvements
- Profile and instrument shared systems, then ship the improvements that move latency, cost, and reliability
- Harden systems against failure and abuse, and make safe defaults the path of least resistance
- Set technical direction in architecture and design reviews, and document the decisions and rollout plans behind them
Areas you might work in
- Backend infrastructure: the data and service infrastructure the product runs on, including caching, databases, APIs, and the observability that keeps it healthy. For example, improving SLOs and cutting latency and cost through caching and data-access work.
- Connectors: the platform that lets a builder connect a service once (communication, payments, developer tools, cloud storage, CRM, data warehouses, and more) and have Agent read and write to it across every app, without managing API keys. The work spans OAuth, permissions, and multi-tenant infrastructure. For example, making connections enterprise-grade: letting organizations govern who can use which integrations, and keeping hundreds of them healthy and observable so a broken connection is caught before a builder hits it.
- Product primitives: the building blocks teams reuse instead of rebuilding, such as identity and entitlements, localization, and configuration. For example, designing an entitlements model product teams use without needing to understand the underlying permission graph.
- Frontend platform: the architecture and platform layer behind core product surfaces, including frontend frameworks, the data layer, shared UI primitives, and client performance. For example, cutting time-to-interactive on a core surface by reworking how it loads and renders data.
Required skills and experience
- Experience shipping and operating software in production (reliability, performance, incidents, observability)
- Built and operated platform systems that other teams depend on
- Able to make and communicate tradeoffs across UX, correctness, delivery speed, and long-term maintainability
- Comfortable collaborating cross-functionally with engineering, design, and product partners
- Fluent in modern web stacks (TypeScript, React, Node.js, Postgres), with depth in frontend, backend, or full-stack
If you’re excited about this role but don’t meet every requirement, we still encourage you to apply
This is a full-time role that can be held from our Foster City, CA office. The role has an in-office requirement of Monday, Wednesday, and Friday.
