Overview

We are looking for a Senior Go Engineer to harden and maintain a Go-based build and content-distribution service that moves large volumes of data across a distributed engineering environment. The service mixes Go and Perl, and the immediate focus is transport security and protocol hardening: bringing TLS and the wire protocol up to current standards without disturbing the throughput the system is built for.

Day to day, you work in the Go codebase on the network and distribution layer, upgrade and harden TLS and the protocol, keep performance intact under heavy load, and validate that hardened components behave identically to the system they replace.

Key Responsibilities

• Harden the transport layer of a Go-based distribution service: modern TLS, certificate handling and protocol hardening, with throughput preserved.
• Maintain and extend the Go services that handle build-artifact and content distribution at scale.
• Work across the Go and Perl boundary where the distribution system spans both languages.
• Profile and protect performance on a high-volume path where regressions are immediately visible.
• Build automated tests and validation to confirm hardened components match the current system.
• Support the rollout and cutover of the hardened components into the existing environment.

Required Skills

• 6+ years building production services in Go, including network and systems-level code, not only web APIs.
• Strong, hands-on knowledge of TLS and transport security: certificates, cipher suites, protocol versions, and hardening live services without breaking clients.
• Experience with binary or custom wire protocols and high-throughput data movement.
• Solid concurrency and performance engineering in Go: profiling, the race detector, and tuning under load.
• Comfortable working in a mixed-language codebase and reading adjacent Perl or C.
• Testing discipline for systems code, including integration tests against real network behavior.

Preferred Skills

• Experience hardening or modernizing an existing distribution, caching or proxy system rather than building greenfield.
• Familiarity with version-control or build-distribution systems at scale.
• Exposure to Perl interoperability.
• Systems experience across both Linux and Windows.