Online Infrastructure Engineer position, full-time and fully remote, paying $118,000 a year, open to candidates located anywhere.
Responsibilities
- Design, deploy, and maintain the servers, networks, and systems that support business operations
- Troubleshoot performance and reliability issues as they come up, from isolated slowdowns to full outages
- Own the infrastructure roadmap for the systems under your care, not just react to tickets
Troubleshooting is where this role earns its keep. A recent example: intermittent packet loss that looked, for the better part of a week, like a bug in a specific application. It turned out to be a failing top-of-rack switch that only dropped connections under load. Finding that root cause, rather than patching around the symptoms, is what separates this job from basic system administration.
Deployment work makes up the rest of a typical week. New servers get racked or spun up, existing systems get patched on a rolling schedule, and capacity gets reviewed before it becomes a problem rather than after. None of it is flashy, but a business that depends on this infrastructure staying up notices immediately when any of it gets skipped.
Skills
- Linux and Windows administration
- Networking
- Virtualization
- Cloud platforms
- Scripting
- Monitoring tools
The mix of on-premises and cloud skills matters more here than at a company that runs entirely on one cloud provider. Comfort moving between a physical data center and a cloud console in the same afternoon is genuinely part of the job, not a rare edge case.
Monitoring tools get used to catch problems before they escalate, not just to log what already happened. Someone who's primarily worked with dashboards built by a separate observability team will need to get comfortable building and tuning alerts directly, since ownership of that sits with this role rather than with a specialist elsewhere in the org.
Qualifications
A bachelor's degree is required, typically in computer science or information technology. Along with the degree, this role requires 30 months of hands-on experience managing infrastructure, whether on-premises, in the cloud, or a mix of both. Strong troubleshooting instincts are expected from day one; this isn't a position where someone learns to diagnose problems on the job for the first time.
Candidates coming from a pure cloud background sometimes underestimate how much on-premises knowledge still applies here. Physical network topology, hardware failure patterns, and the operational discipline of a data center environment come up regularly, even in infrastructure that's now mostly cloud-hosted.
The 30 months required doesn't need to be continuous at one employer. A candidate who spent 18 months managing on-premises infrastructure and another year on cloud systems at a different company brings the same practical range as someone who did all of it in one place, and the interview process is built to draw that range out rather than penalize a resume with more than one job on it.
Pay and benefits
This role pays $118,000 annually. The benefits package covers medical coverage, paid time off, and a 401(k) match, along with support for relevant certification costs. Larger accounts on this team also come with a learning stipend that past hires have used for anything from vendor-specific networking courses to broader cloud architecture training.
Naukri Mitra is running the hiring process for this opening, and the salary is fixed at the posting rather than shifting meaningfully during negotiation, so the figure above is a reliable reference point to go in with.
Reviews happen twice a year, and increases are tied to the scope of someone's responsibilities rather than a flat annual bump. Taking ownership of a previously neglected corner of the environment, and visibly improving its reliability, is usually the fastest path to a meaningful raise on this team.
Compared to typical infrastructure engineer remote salary figures at this experience level, this one sits on the higher side, largely because the on-premises component adds a layer of complexity that pure cloud roles don't carry.
How the team operates
The infrastructure team is distributed across several countries, and coverage windows are built around that rather than forcing everyone onto a single schedule. On-call rotates roughly monthly, and it's genuinely rare for a week to pass without at least one page, which is a fair trade-off given how much of the environment still runs on physical hardware that doesn't always fail gracefully.
Documentation gets taken seriously here, partly because a hardware issue diagnosed at 2 am by someone three time zones away from the last engineer who touched that rack needs a clear paper trail to work from. Out-of-date runbooks cause real problems on this kind of team, not just minor annoyances.
New hires typically spend the first few weeks pairing with an existing engineer on live incidents before taking their own on-call shift. It's a practical way to learn the specific quirks of this environment, since every infrastructure setup accumulates its own history of workarounds and half-documented exceptions that no amount of reading can fully substitute for.
Among infrastructure engineer jobs worldwide, roles that still carry meaningful on-premises responsibility are becoming less common as more companies move fully to the cloud. This one hasn't made that shift yet, and it's not clear when or if it fully will.
Applying
Submit a resume along with a short account of an infrastructure problem you diagnosed that turned out to have a root cause different from what it first looked like. Interviews consist of a technical round covering networking, virtualization, and troubleshooting methodology, followed by a conversation about on-call expectations and time zone coverage. Most candidates complete the process within two to three weeks of applying.
