We're a small team on purpose — everyone here talks to customers, touches the infrastructure, and knows why the work matters. If that sounds appealing, keep reading.
Not the polished version — the parts people usually ask about after they've accepted the offer.
Forty-some people, not four thousand. What you ship and what you decide actually shows up in the product.
Rotating on-call with a real handoff, not one poor engineer holding a pager every weekend of the year.
Our office and data center are both in Riyadh. Most roles get a hybrid schedule once you're settled in.
Several of the team have run infrastructure at scale before. It's a genuinely good place to get better at this.
Salary bands are set before we post the role, not negotiated down because you didn't ask for enough.
We'd rather ship something useful this month and improve it than debate a perfect version for a quarter.
We've turned down candidates who were technically brilliant but wouldn't have been good to our customers on a bad day. We'll always pick for that first — the rest, we can teach.
What candidates usually want to know first.
A short call, a practical exercise related to the actual role, then a conversation with the team you'd join. No five-round marathon, no take-home project that takes a weekend.
For most roles, hybrid — a few days in our Riyadh office, the rest wherever you're productive. Some support and infrastructure roles need to be on-site more often; we'll be upfront about that per role.
It helps but it's not required. We've hired strong Linux admins from adjacent industries and taught them the hosting-specific parts. What matters more is that you're genuinely good at the underlying skill.
Yes. We've created roles around the right person more than once. Send us what you're good at and we'll tell you honestly if there's a fit.
Ask before you apply — no pressure, just a real conversation about whether it's a fit.
Email the Hiring TeamSend us what you're good at — we've created roles around the right person before.