Senior Backend Engineer (Go)
About the role
The Go order pipeline — number allocation, SMS polling, OTP delivery, payment processing — is the spine of DogeSMS. Today the founding engineering team owns it end-to-end. This radar role exists for the moment we need a dedicated senior engineer who treats the pipeline as their primary surface: performance profiling, integration health monitoring, payment-rail expansion, on-call ownership. It is intentionally not an active opening right now because the upstream protocol-stack hire (Telecom Network Engineer) is the higher-leverage move first — the order pipeline only gets more valuable once we have more direct-operator footprints feeding it.
What you'll do
- Own the Go backend order pipeline — number allocation, SMS polling, OTP delivery — including performance profiling, query optimization, and carrier route fallback logic.
- Maintain and extend the integration layer: implement new carrier API contracts, write mock servers for testing, keep existing integrations current as upstream APIs change.
- Extend payment processing flows — blockchain polling, card webhooks, asynchronous confirmation — with a focus on idempotency and partial-failure resilience.
What we expect
- 5+ years writing Go in production — not just services, but systems: connection pools, goroutine lifecycle management, context propagation, graceful shutdown.
- Direct experience with PostgreSQL at meaningful scale: query planning, index design, transaction isolation, `FOR UPDATE` vs `FOR UPDATE SKIP LOCKED`.
- Demonstrated ability to own production systems — you have been paged, triaged, fixed, and written up what happened. On-call experience is not optional.
Stack we use
Go 1.26 (Gin, pgx v5, golang-migrate, go.uber.org/mock), PostgreSQL 18, Redis, OpenTelemetry into SigNoz, Lark for incident notifications. Deliberately boring infrastructure — no Kubernetes, no microservices for microservices' sake, no Kafka.
Compensation
On the radar. Compensation is calibrated to local cost of living when we open this role — we publish bands when we begin interviewing, not before. USD-denominated regardless of jurisdiction, contractor or employment depending on your legal situation.
Hiring process
- Not actively interviewing right now — this role sits on our 12-month hiring roadmap rather than today's pipeline.
- Submit the talent pool form below; we reach out when we begin interviews, typically 4-8 weeks before a public hire.
- When the role opens, expect a process similar to our current active openings: a short async exercise, 1-2 conversations with the relevant team, and a scoped paid trial project. We do not run leetcode-style screens.
Join the talent pool
Submit the form below to be considered when this role opens. We typically reach out 4-8 weeks before we begin interviews.