Cloud Platform Engineer

About the role

Operational decision superiority for aviation systems depends on cloud infrastructure that is reliable, scalable, and continuously deployable. Collaboration with backend, product, and platform engineers structures daily work for the Civil Aviation team in this mission-critical environment.

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 and deployment pipelines are created and maintained to improve reliability and performance for engineers using cloud platforms.

Production cloud environments are operated and maintained to keep systems resilient, continuously deployable, and highly available. Management of 24/7 services supports uptime, performance, and stability for critical aviation workloads through hands-on operation.

Deployment of services together with observability improvements drives faster response to production issues. Debugging, reliability strengthening, and operational standard elevation happen through collaboration with backend, product, and platform teams.

Automation is built to reduce repetitive operational toil while distributing compute and optimizing release safety for complex aviation environments. System scaling and smooth operation are advanced through automation that lowers manual effort on routine tasks.

Requirements

Demonstrated experience building and operating production-grade cloud infrastructure is required for success in this role.

Designing and maintaining infrastructure-as-code with tools such as Terraform and Helm is necessary, along with ownership of CI/CD pipelines for frequent, reliable releases. Understanding of distributed systems and scalability is mandatory for effective contributions.

Using observability and monitoring tools such as Grafana and Prometheus is expected, following production safety practices including testing, rollout strategies, and rollback mechanisms. Operating and supporting 24/7 production systems is required, with participation in design reviews and architectural decisions.

Exposure to regulated cloud environments like FedRAMP and progressive deployment techniques such as canary releases is a strong advantage. High-availability systems, including "four nines" reliability, are a significant plus for this position.

Practical notes

Government data, requiring U.S. Employment offers depend on timely authorization for required duties. 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

Teams often use cloud platforms, Kubernetes, and observability tools to handle real-time optimization at scale. Modern development workflows commonly rely on infrastructure-as-code, CI/CD pipelines, and automated monitoring for safety and reliability.

Questions to ask

Useful questions for the interview: what a typical week looks like, how work is assigned, what tools the team uses, and how feedback works. Asking how the role has changed recently and what the team wishes it had known when joining is also reasonable. Questions about the manager's priorities are especially valued.

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.