Staff Infrastructure Engineer — Device Cloud

What we're looking for

We are looking for someone who has taken an infrastructure platform from one stage of scale to the next.

You likely have:

• Has 5+ years of software engineering, infrastructure, platform engineering, or SRE experience, with significant technical ownership.
• Has previously helped scale a production infrastructure or compute platform through a meaningful increase in load.
• Can analyze an existing architecture, identify scaling constraints, and turn those findings into a prioritized technical roadmap.
• Understands capacity planning and can translate business forecasts and expected workload growth into infrastructure requirements.
• Is capable of making architectural decisions under uncertainty and knows how to validate assumptions through instrumentation, benchmarking, load testing, and production data.
• Has built or operated distributed systems at meaningful scale.
• Is a strong software engineer who can build infrastructure services and control-plane systems, not just configure infrastructure tooling.
• Understands scheduling, queues, worker pools, concurrency, backpressure, resource allocation, failure recovery, and distributed systems fundamentals.
• Has deep experience with cloud infrastructure such as GCP, AWS, or Azure.

What success looks like

Within your first year, we'd expect you to have materially changed both Revyl's infrastructure and our understanding of how it scales.

That means:

• We have a clear model of the capacity and architecture required to support our next stages of growth.
• We know where our major scaling limits are before customers encounter them.
• Large new customers and partnerships have concrete capacity and load plans before launch.
• Revyl can handle an order of magnitude more concurrent compute without requiring an order of magnitude more operational work.
• Common infrastructure failures are automatically detected and remediated.
• Device scheduling and capacity management are predictable rather than reactive.
• We can confidently answer how much additional traffic the platform can support.
• Infrastructure projects are prioritized based on real scaling constraints rather than whichever fire happened most recently.
• Our existing SRE and engineering team spend substantially less time firefighting.
• The Device Cloud becomes a platform we can scale repeatedly rather than an infrastructure stack that needs to be reinvented every time Revyl grows.

A meeting lands on your calendar

If they’re a yes, I book the chat. You show up — that’s the whole job-hunt.