Software Engineer, C1

• We hire across levels, but the baseline is consistent: you can operate independently and deliver in a modern engineering environment. That usually maps to a strong senior level or above. We hold a high bar, and every new hire is expected to raise it
• Have built and operated real production systems
• Are comfortable moving across the stack, and know when to go deep
• Prefer getting things done over debating ownership or process
• Communicate clearly, especially in writing
• Use AI tools because they make you more effective
• Impact matters more than ownership
• We’d rather ship something real than talk about it
• People here are trusted to operate independently
• If something isn’t working, we fix it properly—we don’t paper over it
• Using AI effectively is expected, not optional

Desirable

• Most work comes from a shared pool of high-impact projects, and we assign it based on where it matters most. Some teams own specific areas where deep expertise pays off, but we don’t optimize for rigid ownership. We optimize for shipping
• By default, engineers here are generalists. You’re expected to take things end-to-end: design the data model, build the API, ship the UI, roll it out, and talk to customers. The lines between frontend, backend, and infra aren’t where the real work happens
• That said, we do hire specialists. If you’ve gone deep in areas like connectors, performance, security, or distributed systems—and you’ve shipped meaningful work there—we want to talk. Just know that even specialists here step outside their lane when needed
• Take on projects that matter and see them through to production
• Build features end-to-end, from data model to UI, and own them after launch
• Make decisions about architecture, scope, and tradeoffs without waiting around for direction
• Work closely with customers, design, and product to figure out what’s actually worth building
• Contribute to a high standard of code quality, system design, and operational reliability