SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Throne is a continuous tracking device for personalized gut health and hydration insights, co-founded by John Capodilupo (co-founder and former CTO of WHOOP). The company is bringing rigorous continuous health tracking to signals that have traditionally been guesswork.
You will own major backend and infrastructure problems end-to-end across product APIs, async systems, media/ML indexing pipelines, and cloud infrastructure. This is a hands-on technical ownership role where you will frequently receive an objective rather than a detailed specification, and you are expected to understand the problem, determine the right architecture and implementation plan, identify risks and dependencies, execute the work, and operate the resulting system in production.
Key responsibilities include:
- End-to-end technical ownership: translating company and product needs into technical requirements, architecture, implementation plans, and production systems without requiring pre-defined engineering specifications
- Backend architecture across Go services, including gRPC, grpc-gateway, REST, internal APIs, and shared libraries
- Indexing and processing pipeline for large media/session workloads: object storage ingest, queueing, worker orchestration, ML inference integration, session indexing, and downstream metric generation
- Cloud infrastructure and deployments, primarily in Terraform across AWS ECS/Fargate, networking, storage, queues, IAM, secrets, databases, and ML endpoints
- Performance, reliability, and cost optimization across APIs, worker fleets, databases, queues, storage, and model-serving integrations
- Database and data-flow design, including schema changes, migrations, concurrency patterns, throughput tuning, and operational safeguards
- Observability and operational excellence: tracing, metrics, alerting, incident response, runbooks, capacity planning, and failure analysis
- Engineering process improvements for the backend: design reviews, code reviews, testing strategy, rollout safety, and technical standards
The backend at Throne sits at the intersection of connected devices, high-volume media, ML inference, data processing, and customer-facing health products. This is not a narrow CRUD API role—you will own the full backend surface and follow problems across boundaries. A performance issue might require changes to an API, database schema, worker architecture, inference service, storage strategy, or observability stack.
Requirements:
- 7+ years of backend/infrastructure engineering experience, including substantial ownership of production systems and at least several examples of leading complex technical work from ambiguous problem statement through deployment and operation
- Deep Go experience building and operating distributed backend systems
- Capable of working well with modern LLM tools to scale your work efficiently
- Strong PostgreSQL experience, including query tuning, migrations, transactional design, and high-throughput worker-backed systems
- Strong Terraform and AWS experience, especially ECS/Fargate, S3, SQS, IAM, networking, Secrets Manager, and managed databases
- Experience scaling large async or indexing/data-processing systems built on object storage, queues, and worker fleets
- Experience operating systems that process large files, media pipelines, ML/AI inference workflows, or similar high-volume compute pipelines
- Strong API design instincts, especially around protobuf/gRPC contracts, service boundaries, and backward compatibility
- Strong operational discipline: observability, capacity planning, autoscaling, incident handling, and cost/performance tradeoffs
- Comfort acting as the backend technical lead: making architecture decisions, raising code quality, and improving team execution
Nice to have:
- Experience with SageMaker, Vertex AI, pgvector/vector search, FFmpeg/media processing, Honeycomb, Sentry, Auth0, River, and GitHub OIDC-based deploy workflows
- Experience working across both application backend and ML/data platform boundaries
- Experience inheriting messy systems and making them simpler, more explicit, and easier to operate
