Senior Cloud Engineer

About the role

This position automates and manages media delivery infrastructure to support reliable, scalable cloud-native platforms. The role collaborates daily with development, QA, and platform teams.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Infrastructure-as-code practices are standardized for environment provisioning using Terraform.

Cloud resource orchestration across AWS and Azure optimizes cost and performance for media services.

System health and platform performance are monitored through observability dashboards and New Relic.

CI/CD processes are streamlined with development teams, implementing automation via GitHub Actions and Azure DevOps.

Manual effort is reduced and reliability is increased by automating routine tasks in development, testing, and deployment.

Best practices for containerization and orchestration in production environments are guided for Docker and Kubernetes.

Media platform workflows are accelerated through automation that enables software delivery velocity.

Requirements

Sufficient operational experience is demonstrated with 3+ years in DevOps, Platform Engineering, or related roles.

Deployment pipeline automation is supported through hands-on experience with CI/CD tools like GitHub Actions and Azure DevOps.

Infrastructure-as-code proficiency is required with tools such as Terraform.

Container orchestration is practiced using Docker and Kubernetes in production settings.

Platform observability relies on familiarity with logging, metrics, and distributed tracing platforms like New Relic or CloudWatch.

Hands-on experience managing cloud-native environments on AWS and/or Azure is necessary.

Secure DevOps practices and identity/access management knowledge is required to protect systems.

Comfort with cross-functional teamwork and direct developer support is needed for daily workflows.

Passion for automation, developer productivity, and continuous delivery enables rapid iterations.

Practical notes

US work authorization is required for employment.

The role follows a hybrid schedule with defined team coordination expectations.

Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Cloud roles depend on infrastructure-as-code and automation to reliably deliver media platforms. Modern CI/CD pipelines unify testing, security, and deployment into cohesive workflows. Container orchestration platforms handle service deployment and scaling within dynamic environments. Observability tools measure performance, uptime, and user experience in distributed systems. Media technology teams operate under strict availability and compliance standards.

Questions to ask

Good questions to ask the employer in the interview: what does success look like in the first six months, how is the team structured, what is the current biggest challenge, and how are decisions made. Asking about growth paths and the review process is also well received. Employers expect questions, and good ones show preparation.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.