The company builds an AI workspace that brings knowledge, projects, meetings, and AI tools into one place, so teams can work faster with less fragmentation. Millions of individuals, small teams, and large companies already use it.
Employees here are the first users of the product. The team cares about craft, durable work, and the view that good work still depends on people. The aim is to define how people work together in the AI era, from keeping a business's core records to building and managing AI agents and removing routine work.
This team sits between infrastructure and product. It builds backend architecture that improves the database experience and gives other teams a platform to build on. Databases drive views, boards, charts, forms, and customer workflows. As customers move to larger enterprise setups and AI-driven work, these systems must get faster, more reliable, and able to handle much higher concurrency.
Problems you may work on include database load performance, microservices, heavy write volume from agents, and the flexible data model that makes databases useful but hard to scale.
Responsibilities
In your first 90 days, learn how Collections Infra supports the database block, ship changes that improve database performance or reliability, and learn the scale problems that come with large enterprise workspaces and heavy AI write traffic.
Help make databases faster and more reliable at P95 scale, especially as customers build large central databases with many concurrent users.
Use AI as a working partner for engineering tasks: picking up unfamiliar systems, following debugging leads, writing tests, summarizing traces and logs, and stress-testing plans before release.
Within a year, raise the quality of Collections infrastructure through stronger architecture, observability, documentation, or clearer system boundaries that make later work easier.
Work with senior engineers and product-facing teams to grow Collections into a platform, balancing the needs of internal developers with the customer experience of databases.
Requirements
Solid backend engineering skills and interest in performance, reliability, and scalability, especially in systems that must handle real customer load.
Curiosity about distributed systems, microservices, and trade-offs in the data layer. Prior experience here helps, but the priority is learning fast and reasoning from first principles.
Working knowledge of JavaScript or TypeScript, or the ability to get productive quickly in a codebase that relies on them.
Persistence in solving technical problems: you keep iterating when a first approach does not improve P50 or P95 performance, and you focus on finding the real bottleneck.
Self-directed learning: you use documentation, code, teammates, and AI to build context, ask sharper questions, and make steady progress through ambiguity.
Deep AI expertise is not required for every role, but everyone is expected to be curious, enjoy experimenting, and use AI as a real collaborator. The team values people who use AI to think more clearly and to make their work easier for others to build on.
Conditions
Based in San Francisco.
Work from the office on Mondays, Tuesdays, and Thursdays, which the company calls Anchor Days, since in-person time is central to how the team works.
On-site role.
Base salary estimate for San Francisco: $150,000 to $168,000 per year. Final pay depends on location, role scope and complexity, and your experience, and may fall outside this range.
Benefits
Competitive cash compensation, equity, and benefits.