Recebe uma resposta deste empregador
O teu currículo e carta de apresentação, adaptados exatamente ao que estão a contratar.
Cell Tech Inc. is seeking a senior DevOps/Platform engineer to own the cloud environment end-to-end. You will consolidate sprawl, drive infrastructure-as-code, implement centralized monitoring, and secure patching across workloads while partnering with CIO/CTO.
You will plan migrations, define workloads, organize AWS accounts and IAM, and build backups, runbooks, and cost visibility. You will collaborate with software and IT teams to ensure reliable, cost-effective operations.
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.
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.