• Impressive technical work you can go deep on, with impact in the world. That can take three years or twenty.
• Multi-tenant systems: You have built authorization, organizations, and data separation between tenants.
• Kubernetes fluency: You have built against the Kubernetes API, not only deployed to it.
• Telemetry pipelines: You have built the metrics, logs, or event pipelines behind dashboards and alerts people act on.
• Backend depth: You have shipped production services in Go, or you have the systems background to ship production Go within your first month.
• Enough front end to ship: You build the front end for each feature you own.
• Production on-call experience: You have carried a pager for a system customers depend on, and made it quieter afterward.
• Front end only: Most of this role is backend and infrastructure.
• You need a spec: Requirements here arrive as a customer problem and a rough sketch.
• You want a mature product: We have not shipped the first version yet.
• You want to manage: This is an IC role.
• STRONG CANDIDATES MAY HAVE
• ML or HPC infrastructure: Training clusters, Slurm, or job schedulers, from the operator's or the researcher's side.
• Cloud consoles or developer platforms: Products where the user is an engineer running real workloads.
• Enterprise identity: SSO, SCIM, and identity provider integrations.
• Data movement: Syncing or replicating large datasets across clusters or regions.