Go Developer

About Phaseshift Phaseshift is building the data infrastructure for industrial operators in renewables and other heavy-asset industries. We pull high-frequency telemetry off real plants — equipment that's actually generating power, right now — and turn it into something operators can run their business on. We're a small team shipping into production with named design partners, and we move fast because our customers do. The role You'll write Go in a distributed-systems codebase that's run by real operators in the field. Day to day that means designing services, building APIs, working on the data path between edge and cloud, and owning what you ship, from first line of code through production incidents. This is hands-on work. You'll be debugging across process and network boundaries, reasoning about throughput and backpressure, and making tradeoffs between latency, durability, and cost. The problems are real, the deadlines are real, and the systems are running on hardware we can't always reach. What we're looking for We hire on judgment more than years. Strong candidates show some mix of:

Solid Go fundamentals — concurrency, context, error handling, the standard library. You write Go that reads cleanly and is easy to test.

Comfort with distributed systems: services that talk to other services, message brokers, retries, timeouts, graceful degradation. You've thought about what happens when the network is slow or the other side is down.

An instinct for high-throughput data: batching, streaming, knowing when an extra allocation matters and when it doesn't.

A bias toward small, tested, working code. Our codebase has tests next to almost every package and we expect new code to follow suit.

Willingness to debug at the edge of your knowledge. Most real bugs live at the seam between systems, that's where you'll spend time.

Curiosity about the physical world. You don't need an industrial background; you do need to be interested in learning how the gear we talk to actually works. Nice-to-haves Time-series data, edge or on-prem deployments, performance work, profiling and benchmarking, prior startup experience, or any background in energy, manufacturing, or industrial controls. How we work Small team, short feedback loops, no committees. You'll ship code in your first week. We read each other's PRs, we write tests, we move fast, and we don't paper over breakage, when something is broken we fix it. Expect a fair amount of autonomy and a fair amount of ambiguity; both come with the early-stage territory. Show more Show less