Senior Engineer — Go, control plane

About the role

The services between the console and the fleet: carrying policy out to firewalls that may be on any of several versions, bringing results back, and keeping a multi-tenant system strict about which customer is which. The hard parts are distribution, upgrade safety, and never losing a record.

What you would do

• Build and own services that distribute configuration to a fleet and report per device what actually happened — a partial rollout must be visible, not assumed.
• Keep tenancy watertight. In a system holding many customers' records, the boundary between them is the product.
• Make upgrades survivable: several versions in the field at once, migrations that can be run twice, and a way back.
• Own the operational picture of what you build — what it does when it is degraded, and how anyone can tell.

What we are looking for

• Several years of Go in production, on services other teams depended on.
• You have designed something concurrent and then had to debug it, and you can say what you would do differently.
• Real experience with a database under load: transactions, indexes, and what happens when a migration meets live traffic.
• Working English, written and spoken. German is welcome and is not required.

Useful, not required

• You have run what you built, on call, and it changed how you built the next thing.
• Familiarity with WireGuard, or with any system where key material must never be in the wrong place.
• You have written a migration you were glad you could reverse.

What we offer

• A system with real operational weight: what you ship is run by service providers on their own infrastructure.
• Ownership from design to the thing running, without a hand-off in the middle.
• Decisions made in the open, by the people who will have to live with them.