Go Engineer
Build the concurrent services and agent runtimes that sit on the hot path of client systems.
- Go
- gRPC
- Postgres
- Pub/Sub
- Docker
- Kubernetes
We reach for Go when a workload has to be fast, concurrent, and boring to operate: agent runtimes, high throughput ingestion, webhook fan out, and the integration services that sit between a client storefront and their ERP.
This role is for someone who has run Go in production long enough to have opinions about it, and scars from the times the concurrency model bit back.
Build the services on the hot path
- Design and ship Go services that handle sustained throughput without falling over: worker pools, backpressure, bounded queues, and graceful degradation
- Own the concurrency model in the code you write. Context propagation, cancellation, and goroutine lifecycle are your responsibility, not an afterthought
- Build the integration layer between commerce platforms, ERPs, and internal agent systems, where retries and idempotency are the whole job
Operate what you ship
- Instrument services with structured logging, metrics, and tracing before they hit production, not after the first incident
- Profile and fix real performance problems using pprof and load testing, and know the difference between a slow service and a slow dependency
- Containerize and deploy to Cloud Run, Fargate, or Kubernetes, and keep the deployment path something a teammate can follow at 2am
Set the standard
- Write code other engineers can read six months later without asking you what it does
- Review pull requests with substance, and push back when a design will not hold under load
- Document the failure modes of the systems you build so the next person inherits knowledge, not archaeology
Required
- Four or more years writing Go in production, including services you were on call for
- Deep working knowledge of Go concurrency: channels, select, sync primitives, and the race detector
- Comfortable with gRPC or REST API design, Postgres, and at least one message broker or event bus
- You test the things that matter and can explain why you did not test the things you did not
Helpful, not required
- Experience building agent runtimes, job orchestrators, or workflow engines
- Kubernetes operator or controller experience
- Exposure to a second language we use heavily: TypeScript or Python
Also hiring.
Engineering Lead and Client Partner
Remote Delivery
A player coach seat that combines technical lead, delivery owner, and second seat on sales.
Forward Deployed Engineer, Agentic Commerce
Remote Applied AI
Embed with commerce clients and ship agent driven discovery, catalog, and checkout systems into production on their stack, not ours.
Forward Deployed Engineer, Enterprise AI Integrations
Remote Applied AI
Wire LLM agents into the ERPs, CRMs, and ticketing systems enterprises already run, inside the client environment, and make the integrations survive production.
Show us something you built.
Send a resume or profile with a short note about work you have shipped. Links to code, systems, or launched projects tell us more than a cover letter ever will.
careers@contracollective.com