Go Engineer Backend · Remote View

Own the services that move sports data. Odds, scores, injuries, and lineups arrive from a dozen upstream feeds at different shapes and cadences, and every feature in the product is only as good as that pipeline. You'll build the Go services that ingest, normalize, and fan that data out, and keep them correct while games are live.

• Build and operate high-throughput ingestion services in Go, running as containers on ECS Fargate and Cloud Run.
• Design the normalization layer that turns a dozen upstream provider schemas into one internal model in Postgres.
• Use DynamoDB for the hot read paths that back live scores and odds, and Postgres for everything relational behind them.
• Archive every raw upstream payload to S3 so a bad transform can be replayed instead of re-fetched.
• Keep latency low and correctness absolute during live games, when a stale score is worse than no score.

• Production Go experience with concurrent systems — go routines, channels, context, and back pressure.
• Strong Postgres fundamentals: schema design, indexing, and query performance at scale.
• DynamoDB experience beyond CRUD — access-pattern-first table design, partition keys, and secondary indexes.
• Comfort shipping containers to AWS (Fargate, ECR, S3) and GCP (Cloud Run, Pub/Sub) without treating either as magic.
• A bias toward observability: you ship metrics and traces alongside the feature.

• Experience with a provider integration that changed its schema without telling you, and what you did about it.
• Event-driven work on Pub/Sub, Kafka, or Kinesis.
• Sports data domain knowledge — or the appetite to learn how a line actually moves.