Infrastructure Ops Engineer
- Remote-friendly · fits your timezone
- Posted yesterday · via Himalayas
Full Description
Infrastructure Ops engineers are our human to metal interface. Infrastructure Ops engineers are our human to metal interface. They manage the foundation that everything else is built on, and provide the tools to support our Platform team and Fly .io end customers. This is one of the most important roles in the company. This role is a good fit for you if: You care about users. You can empathize with the problems they encounter using our products and build solutions that treat reliability as a feature. You’re excited about building tools and systems to safely operate a fleet of bare metal servers that outnumber your team 1000:1. You like working with all the weird Linux things, from eBPF to LVM2 to WireGuard to policy routing. You’re comfortable building things that are imperfect and solve the problems we’re facing right now; our infrastructure is evolving rapidly as we scale. You want to help the team develop green-field automation, infrastructure-as-code, observability and alerting work; we’re up to our eyeballs in fun infra projects. You know you’re succeeding in this job if: You bring experience, pragmatism, composure, and positivity to interactions with teams outside of the Infra Ops organization. You get that code doesn’t matter unless the rest of the team knows how to use it. You have a habit of writing guides, docs, and frameworks so the wheels keep turning when you’re not online. You never waste a crisis. You treat each failure as a chance to learn and improve so it doesn’t happen again. You consider it a crisis when users notice a problem before we do. You know how to prioritize when everything is vying for your attention. Even if it means letting some fires burn while you put out more important ones. We’re building something big and ambitious with a very tight team; small fires are common! You know the helpless feeling when us-east-1 is on fire while the status page stays green. You communicate with users clearly and transparently, the way you’d want as a user. You seek out ways to take the systems and best-practices we use to run our own infrastructure and bring them to life in ways that our users can benefit. More Details This is an early career to senior level fully-remote full-time position. You can live anywhere in the world; your work hours and holidays observed are up to you. The salary ranges from $90k to $200k USD. We offer competitive equity grants with a long exercise window. Hopefully that’s enough to keep you intrigued; here’s what you should really care about: We’re a small team that is deeply technical. Engineers at Fly .io have an unusual amount of autonomy and decision-making power. You will be making real product decisions that directly impact users, on a daily basis, without anyone standing over your shoulder telling you what to do. We are active in developer communities, including our own at community.fly.io. Virtually all customer communication, documentation and blog posts are in writing. We are a global company, but most of our communication is in English. Clear writing in English is essential. The infrastructure work we encounter is varied. One day we might be debugging a kernel issue and the next we’re looking at how to make our platform more observable for our users. You’re not expected to be amazing at everything, but an enthusiasm for learning is critical. How We Hire People We’re weird about hiring. We’re skeptical of resumes and we don’t trust traditional interviews. We respect career experience but we’re more excited about potential. The premise of our hiring process is that we’re going to give you a series of challenges that each simulate the kind of work you’ll actually be doing here. Unlike a lot of places that assign “take-home problems”, our challenges are the backbone of our whole process; they’re not pre-screeners for an interview gauntlet. Checkoutour hiring documentationto learn more than you probably ever wanted to know. If you’re interested, send a message . You can tell us a
Why This Role?
Perusahaan ini menyediakan fleksibilitas waktu kerja dan liburan, serta kompensasi yang kompetitif.
Key Responsibilities
- Membangun dan mengelola sistem untuk mengoperasikan server bare metal
- Mengembangkan otomatisasi dan infrastruktur-as-code
- Membuat dokumentasi dan panduan untuk memastikan kelanjutan operasional
- Mengidentifikasi dan memprioritaskan masalah kritis dalam infrastruktur
- Mengkomunikasikan dengan pengguna secara jelas dan transparan
Requirements
- Pengalaman dalam mengelola infrastruktur Linux
- Kemampuan untuk membangun sistem yang praktis dan efektif
- Kemampuan untuk menulis dokumentasi dan panduan
- Kemampuan untuk bekerja dengan tim di luar organisasi Infra Ops
- Pengalaman dalam observability dan alerting
Required Skills
Indonesia Context
- Working Hours Overlap:
- Flexible — work your own hours
View Original Description from HimalayasShow more
Original description from Himalayas
Infrastructure Ops engineers are our human to metal interface. Infrastructure Ops engineers are our human to metal interface. They manage the foundation that everything else is built on, and provide the tools to support our Platform team and Fly .io end customers. This is one of the most important roles in the company. This role is a good fit for you if: You care about users. You can empathize with the problems they encounter using our products and build solutions that treat reliability as a feature. You’re excited about building tools and systems to safely operate a fleet of bare metal servers that outnumber your team 1000:1. You like working with all the weird Linux things, from eBPF to LVM2 to WireGuard to policy routing. You’re comfortable building things that are imperfect and solve the problems we’re facing right now; our infrastructure is evolving rapidly as we scale. You want to help the team develop green-field automation, infrastructure-as-code, observability and alerting work; we’re up to our eyeballs in fun infra projects. You know you’re succeeding in this job if: You bring experience, pragmatism, composure, and positivity to interactions with teams outside of the Infra Ops organization. You get that code doesn’t matter unless the rest of the team knows how to use it. You have a habit of writing guides, docs, and frameworks so the wheels keep turning when you’re not online. You never waste a crisis. You treat each failure as a chance to learn and improve so it doesn’t happen again. You consider it a crisis when users notice a problem before we do. You know how to prioritize when everything is vying for your attention. Even if it means letting some fires burn while you put out more important ones. We’re building something big and ambitious with a very tight team; small fires are common! You know the helpless feeling when us-east-1 is on fire while the status page stays green. You communicate with users clearly and transparently, the way you’d want as a user. You seek out ways to take the systems and best-practices we use to run our own infrastructure and bring them to life in ways that our users can benefit. More Details This is an early career to senior level fully-remote full-time position. You can live anywhere in the world; your work hours and holidays observed are up to you. The salary ranges from $90k to $200k USD. We offer competitive equity grants with a long exercise window. Hopefully that’s enough to keep you intrigued; here’s what you should really care about: We’re a small team that is deeply technical. Engineers at Fly .io have an unusual amount of autonomy and decision-making power. You will be making real product decisions that directly impact users, on a daily basis, without anyone standing over your shoulder telling you what to do. We are active in developer communities, including our own at community.fly.io. Virtually all customer communication, documentation and blog posts are in writing. We are a global company, but most of our communication is in English. Clear writing in English is essential. The infrastructure work we encounter is varied. One day we might be debugging a kernel issue and the next we’re looking at how to make our platform more observable for our users. You’re not expected to be amazing at everything, but an enthusiasm for learning is critical. How We Hire People We’re weird about hiring. We’re skeptical of resumes and we don’t trust traditional interviews. We respect career experience but we’re more excited about potential. The premise of our hiring process is that we’re going to give you a series of challenges that each simulate the kind of work you’ll actually be doing here. Unlike a lot of places that assign “take-home problems”, our challenges are the backbone of our whole process; they’re not pre-screeners for an interview gauntlet. Checkoutour hiring documentationto learn more than you probably ever wanted to know. If you’re interested, send a message . You can tell us a
Opens on Himalayas — you may need 1–2 more clicks to reach the real application.
Explore related
Market data & reports
Salary & skill-demand research built from our own listings data.
- Skills Remote Employers Ask For in the AI EraMost-named skills in active listings by kind, AI-named skills and the fastest risers. Weekly data.
- Indonesia IT Jobs vs Global Remote (2026)Primary analysis of 2,049 listings: methodology, classification rules, downloadable datasets.
- AI-Skill Demand: Indonesia vs Global Remote (2026)10,000+ postings, taxonomy-first classifier, Wilson CIs, pre-registered before analysis.
- Remote ≠ Remote: The Skills That Open Global Work to Indonesians (2026)12,891 remote listings: the highest-paid coding skills are the most geo-locked for Indonesia-based applicants. CC BY 4.0 aggregate dataset.
- The Compliance Layer of the AI Hiring Stack (2026)6,349 remote listings: 77.2% never state who may apply. Methodology and a CC BY 4.0 aggregate dataset.
- AI in Job Ads: Indonesia vs Global (2026)Global engineering ads naming AI rose from 3.4% to 23% after ChatGPT; Indonesian ads went from 2.2% to 2.8%. 2027 scenarios and a CC BY 4.0 dataset.
- Cron vs LLM vs LangGraph vs Agent for Social Posts (2026)A pre-registered test of four ways to turn a blog post into social posts, on two models. Automated checks picked a cron template; the model mattered more than the framework.
- Indonesia Hiring Report: Tech vs Non-TechJob demand by field from aggregate open-job counts — never individual listings.
- Indonesia Salary BenchmarkAggregate salary ranges across roles, with open methodology and dataset.
- Indonesian Remote Work Salary & Demand IndexHow much of the global remote job corpus is open to Indonesia, and what it pays (USD) by role.
- Indonesia Quarterly Labor Market ReportLayoffs, funding, salaries & skills per quarter — open aggregates.
- Remote Market Reports by RoleAuto-generated per role family — skills, seniority, companies, salary.
- Global Remote Salary BenchmarkAnnual salary by role & currency, plus the share of listings open worldwide.