Go Engineer

Role overview This is a senior seat for an engineer who writes Go because it is fast, concurrent, and predictable to run, not because it is fashionable. The work spans agent runtimes, high-throughput ingestion, webhook fan-out, and the integration glue between commerce storefronts and back-office systems. Expect to own services end to end, from design through on-call.

Responsibilities - Design and ship Go services that handle sustained throughput, using worker pools, backpressure, bounded queues, and graceful degradation patterns. - Take responsibility for the concurrency model in the code you write, including context propagation, cancellation, and goroutine lifecycle. - Build the integration layer between commerce platforms, ERPs, and internal agent systems, where retries and idempotency are central. - Instrument services with structured logging, metrics, and tracing before launch, then profile and fix real performance issues using pprof and load testing. - Containerize and deploy services to Cloud Run, Fargate, or Kubernetes, keeping the deployment path reproducible for the on-call rotation. - Review pull requests with substance and document the failure modes of the systems you build so knowledge survives team changes.

Requirements - 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. - Comfort with gRPC or REST API design, Postgres, and at least one message broker or event bus. - Ability to test the things that matter and explain why you did not test the things you did not.

Nice to have - Experience building agent runtimes, job orchestrators, or workflow engines. - Kubernetes operator or controller experience. - Exposure to a second language used heavily, such as TypeScript or Python.