Please mention DailyRemote when applying
See how much of this job your resume covers, and what’s missing.
Want a recruiter to go through it line by line?
Get professional reviewQuestions interviewers often ask for this role, with sample answers.
One click makes a copy of your resume for this role, scores it against the posting, and proposes edits line by line. Your default resume is never changed.
Upload your resume and we draft a letter for this exact role, tailored to what it asks for.
You will own and consolidate the company's cloud infrastructure, transitioning it to an infrastructure-as-code model while ensuring security, reliability, and cost-efficiency. You will also manage CI/CD pipelines and provide clear, plain-language architectural guidance to non-specialist leadership.
Cell Tech Inc. is a US-based device repair business with multiple shop locations. Our shops are hands-on with hardware; our software and infrastructure teams are distributed across Pakistan, India, and Australia. Our internal IT (endpoints, identity, network edge) is handled by a separate team. This role is about everything our applications and tooling run on.
Here is the state of that today: we have production workloads and internal tools spread across AWS Lightsail, Supabase, Render, Lovable, and some local hosting. Some of it is locked down well, some is not. There is no infrastructure-as-code, no configuration management, no centralized health monitoring, and we currently run two separate Bitbucket environments that should be one. Everything works, but it grew rather than being designed.
If reading that paragraph made you start forming opinions, keep reading.
About the role
You will own our cloud infrastructure from day one. Not a piece of it — the environment. Your job is to look at what we have, propose where it should go, and then take it there: consolidate the sprawl onto a deliberate architecture, bring it under infrastructure-as-code, make security and patching systematic instead of per-project, stand up centralized monitoring and alerting, and get our costs matched to what we actually use.
We will not hand you a target architecture, because defining it is the job. Leadership here thinks in outcomes: everything centrally managed, secure and kept current, economical, and easy to live with for the teams that build and run things on it. You translate those outcomes into concrete choices — which workloads belong on which services, what the migration order is, what we monitor and where it alerts, what gets a WAF in front of it — and you explain those choices in plain language to smart people who are not infrastructure specialists. If your proposal only makes sense to another DevOps engineer, it doesn't make sense.
You will report to our CIO and CTO, who set direction and priorities and will back your decisions once they understand them. You will work alongside our Systems Administrator where infrastructure meets internal IT; where exactly those lines sit, we will work out together as they come up.
What you will do
Consolidation and migration
Infrastructure as code and central management
Security and currency
Monitoring and reliability
Developer and team tooling
Cost
Documentation
What we need from you
Must have
Nice to have
How we think about skills
We have named the tools we use today, and we have guesses about where things should go — but we are deliberately not prescribing the target stack, because evaluating those guesses is your job. We care that you know the disciplines (provisioning, configuration, observability, access control, cost) deeply enough that any given tool is just the current spelling of them. If you disagree with something we've assumed, we want to hear it — after you've asked why we assumed it.
Working arrangement
Stop the endless job search. Our AI finds and applies to the best jobs for you.
Featuring 223,918+ Jobs in DevOps Engineer
Answer easy questions
223,918+ jobs across 15+ categories
Get your best job matches
Only hand-screened, legit jobs
Find a remote job faster
No ads, scams, or junk
“I was the first applicant for a remote marketing position that got listed on the company website the same day I applied. Had an interview within 48 hours!”