Logo for Cell Tech Inc.

Senior DevOps Engineer

Role overview

Summary

This role is for managing and optimizing Cell Tech Inc.'s cloud infrastructure. You will consolidate existing systems, implement infrastructure-as-code, and enhance security and monitoring practices. Your work will support the company's distributed software and infrastructure teams, ensuring a reliable and efficient environment for application deployment.

Qualifications

  • 5 or more years in DevOps, platform, cloud, or infrastructure engineering.
  • Deep AWS experience in production, including compute, managed databases, networking/VPC, and IAM.
  • Infrastructure-as-code experience in production, preferably with Terraform.
  • Experience planning and executing migrations of live workloads.
  • CI/CD pipeline infrastructure experience with tools like Bitbucket Pipelines or Jenkins.

Responsibilities

  • Consolidate and migrate existing workloads to a target architecture.
  • Bring the environment under infrastructure-as-code using Terraform or a similar tool.
  • Establish centralized health monitoring and alerting for production systems.
  • Build and maintain CI/CD pipeline infrastructure.

Key facts

Hard skills

Key skills for this role

Other skills

  • Communication
  • Problem Solving
  • Teamwork
  • Adaptability

About the company

Cell Tech Inc. logo

Cell Tech Inc.

  • IT Services & Consulting
  • Startup
  • 11–50
Cell Tech started in 2010 as a small cell phone repair shop, grounded in quality service, quick repairs, and a customer-first approach. This foundation proved valuable when a local school approached Cell Tech, asking if its core values could extend to school device repairs. Ready to take on the challenge, Cell Tech built a dedicated workshop and a team of trained technicians. To support these operations, Cell Tech's development team created "Repair Genie," a custom repair management system that streamlined the entire repair process. Over time, Cell Tech’s tailored repair services and innovative software met and exceeded client expectations, allowing the company to expand. Today, with workshops across Virginia, North Carolina and South Carolina. We today cater to 200+ schools supporting over 200K students while adapting to the evolving needs of educational institutions while upholding its original commitment to quality, efficiency, and customer delight. Cell Tech is and always will be dedicated to providing service with our initial values: quality repairs, a quick turnaround time, and a customer-first focus.

Your match analysis

See how your profile stacks up against this role.

We compared the job requirements to your profile to show where you're strong and where you fall short.

Job description

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

  • Inventory everything we run and where it runs, and build the case for where each thing should live.
  • Plan and execute migrations off scattered hosting onto the target architecture, without breaking the teams that depend on it. Staged, communicated, reversible.
  • Consolidate our two Bitbucket environments into one.
  • Retire what should be retired. Part of this job is deleting things safely.

Infrastructure as code and central management

  • Bring the environment under infrastructure-as-code (Terraform or make the case for your tool of choice) so that what we run is written down, reviewable, and reproducible.
  • Establish configuration management where it earns its keep.
  • Organize our AWS accounts, IAM, and access so that who-can-touch-what is deliberate.

Security and currency

  • Make patching and updates systematic across everything we run.
  • Lock down what isn't locked down: least-privilege access, no public things that shouldn't be public, secrets out of code.
  • Subscribe us to the security advisories that matter and be the person who acts on them.
  • Evaluate and propose protective layers (WAF, DNS filtering, and similar) as discussion items with a recommendation, not as surprises.
  • Choose and connect a centralized logging/SIEM destination so security events from across the environment land somewhere someone looks.

Monitoring and reliability

  • Stand up centralized health monitoring and alerting for everything production. If it matters and it goes down, someone finds out from a page, not from a user.
  • Establish backups and recovery that are tested, not assumed.
  • Write the runbooks and handoff SOPs so that off-hours issues have a path even when you're asleep.

Developer and team tooling

  • Build and maintain the execution side of CI/CD: build/task runners, pipeline infrastructure, integrating services like AI-assisted code review into the pipeline. (Branch strategy, PR and commit practices stay with the dev teams — you build the rails, they drive.)
  • Keep our Atlassian environment organized and sensibly administered.
  • Treat the internal teams as your customers. The measure of your work is that their lives get easier.

Cost

  • Right-size what we run. Find what's oversized, duplicated, idle, or on the wrong pricing model, and fix it.
  • Make cost visible: leadership should be able to see what we spend and what it buys.

Documentation

  • Document the architecture and the reasoning behind it, so the environment survives any one person — including you.

What we need from you

Must have

  • 5 or more years in DevOps, platform, cloud, or infrastructure engineering, with real production ownership — environments where you made the architecture calls and lived with them.
  • Deep AWS experience in production: compute, managed databases, networking/VPC, and IAM at minimum.
  • Infrastructure-as-code in production. Terraform preferred; fluency in the discipline matters more than the brand.
  • You have planned and executed migrations of live workloads — moved production systems between platforms or providers without burning the business down.
  • Security as a habit, not a department: least privilege, patching discipline, secrets management, and the instinct to ask "what's exposed?" before "does it work?"
  • You have set up monitoring and alerting from scratch somewhere, not just inherited a dashboard.
  • CI/CD pipeline infrastructure experience (Bitbucket Pipelines, GitHub Actions, Jenkins, or similar).
  • Clear plain-language communication, spoken and written. You will regularly explain trade-offs to non-specialists, and we will test for this.
  • Comfortable with ambiguity: given an outcome and a messy starting point, you produce the plan rather than waiting for one.

Nice to have

  • Experience migrating off PaaS platforms (Supabase, Render, Heroku-style hosting) onto AWS.
  • Cloudflare (WAF, DNS, or Zero Trust).
  • SIEM selection or administration.
  • Atlassian administration (Jira, Confluence, Bitbucket).
  • Configuration management (Ansible or similar).
  • A cost-optimization story with numbers attached.
  • Exposure to compliance frameworks (SOC 2 or similar).

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

  • Fully remote from India.
  • Standard local business hours. This is not a night-shift US-overlap role.
  • If something you own becomes 24/7-critical down the road, we will solve that together with handoff SOPs or an on-call arrangement — it is not the default.
  • No travel.

Compensation: TBD

Related jobs

See all DevOps Engineer jobs