Sr. Software Engineer (Backend)

Signadot is building the validation layer for agentic coding. As AI agents generate more code, verifying that it works against real systems becomes the bottleneck. This is a senior backend IC role building the Go control plane and APIs behind that validation layer, along with the enterprise features that let large organizations roll it out to thousands of developers.

What you'll do

• Build and own core backend services in Go: the control plane, public APIs, and request routing
• Design and maintain HTTP and gRPC APIs, and the SDKs generated from them
• Build enterprise features such as RBAC, SSO, audit logging, and multi-tenancy
• Work with Kubernetes, including controllers and operators
• Own features from design through production, including testing and rollout
• Keep the systems you own reliable and observable

What we're looking for

• 4 to 6 years building backend systems in production
• Strong Go, or strong experience in another systems language and willing to work primarily in Go
• Solid distributed systems fundamentals: you can reason about a multi-service system and where it fails
• Experience designing APIs that other teams build on
• Working knowledge of Kubernetes
• Interested in both hard distributed systems problems and the enterprise features (RBAC, multi-tenancy, SSO) that make the product usable at scale
• Clear written communication. The team works asynchronously and relies on written design docs

Nice to have

• SRE or DevOps experience (a strong plus): production Kubernetes (EKS), CI/CD, IaC, observability
• Experience working on validation/testing oriented products and/or agentic validation
• Building or operating Kubernetes controllers or operators (controller-runtime, client-go)
• gRPC, protobufs, or OpenAPI-driven SDK generation
• Multi-tenancy, request routing, or service mesh internals (Istio, Linkerd)
• Database design and operations, especially MySQL at scale
• Contributing to or operating CNCF projects

Interview Process

1. Fit chat: Background, motivation, and how you approach backend systems.
2. Coding exercise: A take-home or live Go problem, or extending a small service.
3. System design: Design a distributed component, covering APIs, failure modes, and trade-offs.
4. Panel with engineers: Walk through the exercise and discuss a problem from our domain.
5. 1:1 interviews: Engineers and founders you'd work with.
6. References