Operator-first product, distributed team. We are hiring across backend, SRE, design and solutions — and we pay our customer-operator advisors. The application portal is in build; until it lands, the path is a direct email to the role you want.
Whether you write code, run on-call or hold the operator pager, this is the operating model you would be joining.
Every engineer rotates through an on-call shift inside a customer NOC during onboarding. You see how the product is used before you write code for it.
We work across time zones, but at least 3 hours of daily overlap with your customer's NOC team. Async by default, sync where it matters.
Our customers run critical infrastructure. We are the operator surface, not the science experiment. Boring well is the goal.
Salary bands published internally. Equity grants reviewed every cycle. Healthcare paid 100%. No surprise levelling, no salary-negotiation theatre.
Own the telemetry ingest pipeline and the runbook execution engine. We process operator-grade events at carrier-network scale; "boring + correct" is a feature.
Run our production environment with the same discipline our customers run theirs. Multi-region, customer-managed-key, NFPA 1221 evidence — without panic.
Lead the design system across the marketing site, the operator console and the embedded customer-facing portals. The bar is the design language of the home page; keep it.
Sit between the customer NOC and engineering. Translate operator pain into product spec, run sandboxes for prospects, own onboarding through first ingest.
Half-time engagement: review every release as a working operator before it ships. Roadmap input, acceptance calls, post-release feedback. Paid honorarium + warrant.
Mail the role-specific address above with:
We read every email. We respond within 7 business days, even if the answer is no.
Talented people often do not fit a published role. If that's you, write to the general address — a real human reads it within the week.