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
To achieve our mission of making programming more accessible around the world, we need our team to be representative of the world. We welcome your unique perspective and experiences in shaping this product. We encourage people from all kinds of backgrounds to apply, including and especially candidates from underrepresented and non-traditional backgrounds