We're hiring a Work-From-Home AWS Cloud Engineer, full-time, $128,000 a year, open to applicants anywhere.
What you'd be doing
- Design, deploy, and maintain infrastructure on AWS, from initial architecture through the messy reality of keeping it running
- Automate provisioning with infrastructure-as-code tools instead of clicking through the console for every change
- Keep an eye on systems for both performance and cost, since a service that's fast but wildly overpriced isn't actually doing its job
That last one trips people up more than they expect. We had a service last year that ran fine for months on an EC2 instance sized for three times its actual load, and nobody noticed until a quarterly cost review flagged it. Catching that kind of thing before finance does is part of the role, not a side project.
Deployment work makes up a good chunk of a normal week too. New environments get spun up for projects that are just getting started; existing ones get patched and updated; and old resources that nobody's touched in months get tracked down and either properly documented or torn out. It's not glamorous, but leaving unused infrastructure running quietly in the background is how a cloud bill gets out of control.
What we're looking for
You'll need a bachelor's degree, generally in computer science, and 30 months of hands-on experience managing AWS infrastructure. We'd also like to see an AWS certification, something like Solutions Architect Associate, along with solid scripting and automation habits. That's roughly two and a half years of real AWS work, not classroom exposure or a handful of side projects, and it's the part of the resume we look at closest.
People come into this role from a few different directions. Some have spent their whole short career on AWS specifically. Others cut their teeth on a different cloud and picked up AWS more recently. Both paths work as long as the AWS time adds up to the amount listed above.
The certification piece deserves a note of its own. It's not a hard requirement in the sense that a candidate without one gets an automatic pass, but it does signal that someone's put in the study time beyond whatever they've picked up on the job, and for a role at this experience level, that matters. If you don't have the Solutions Architect Associate certification yet but have the practical experience to back it up, apply anyway; the certification reimbursement mentioned below exists in part so new hires can close that gap quickly.
Tools and skills
- Core AWS services, especially EC2, S3, and Lambda
- Infrastructure as Code, ideally Terraform or CloudFormation
- Linux administration
- Scripting for automation
- Networking fundamentals
A CloudFormation background is welcome, even if the team leans toward Terraform day-to-day, since the underlying concepts transfer and we're not precious about which tool someone learned first. Kubernetes experience isn't on the required list, but if you've got it, mention it, since a couple of services are quietly moving that direction next year.
Pay and benefits
The role pays $128,000 annually. Beyond salary, it comes with health insurance, paid time off, and 401(k) matching, plus reimbursement for AWS certification costs, since we'd rather pay for the exam than have someone avoid it to save money. There's also a learning stipend for continuing training, which past hires have used for everything from advanced AWS certs to general cloud architecture courses.
If you've looked around at AWS cloud engineer remote salary numbers before applying, this one sits toward the higher end for a role at the two-and-a-half-year experience mark, which reflects how much of the job is genuinely hands-on rather than supervisory.
Reviews happen twice a year, and raises are tied to what someone has actually taken ownership of rather than to tenure alone. An engineer who's brought a messy corner of the infrastructure under control tends to see that reflected in their next review, sometimes faster than the calendar would suggest.
How the team works
This posting is being run through Naukri Mitra, and the engineering team behind it is small, with everyone taking ownership of specific parts of the AWS environment rather than everyone touching everything. Meetings are kept short and mostly async, which matters given the team spans several time zones. Among AWS cloud engineer jobs worldwide, that's not unusual, but it does mean writing things down clearly matters more here than it would on a team that's all in one office.
If you're weighing whether to become a remote AWS cloud engineer or stay in an on-site role, the honest answer is that the work itself doesn't change much. What changes is communication. Decisions that used to happen by walking over to someone's desk now happen in a shared doc or a quick call, and the engineers who do well here tend to be the ones who write clearly under no pressure to be terse.
On-call is shared across the team on a rotating basis, roughly one week in five depending on headcount at any given time. It's not heavy. Most weeks pass without a page, and when something does come up, it's usually a capacity alert rather than a full outage, since the automation work described earlier is largely aimed at preventing the bigger fires before they start.
Applying
Send a resume along with a short note on the AWS environment you've managed most recently, roughly how large it was, and one cost or performance problem you caught before it became a bigger issue. Interviews run in two stages: a technical discussion covering AWS architecture and automation, and a shorter conversation about schedule and time zone overlap with the rest of the team. Given the distributed setup, expect at least one of those conversations to land outside a typical nine-to-five.
There's no fixed deadline on this posting. Applications are reviewed as they come in, and the team would rather take an extra week to find the right fit than fill the seat quickly with someone who's only a partial match for the AWS experience.
