Want to get hired at Ryan?

Staff Engineer DevOps

Ryan

IndiaOn Site

Original Job Summary

Job Overview

The Staff Engineer DevOps at Ryan is a highly experienced technical leader in an individual contributor role. You will drive architectural decisions, set engineering standards, and enhance platform reliability and scalability across teams and environments.

Key Responsibilities

  • Architect cloud-native, secure, scalable infrastructure using Azure and AWS.
  • Design and optimize CI/CD pipelines with Azure DevOps and GitHub Actions.
  • Drive observability and reliability standards using OpenTelemetry, Grafana, and Prometheus.
  • Guide cross-team technical decisions and advocate DevOps best practices.
  • Research and implement emerging technologies to reduce development complexity.

Technology and Competencies

The role requires deep expertise in cloud (Azure, AWS), container orchestration (Kubernetes), infrastructure as code (Terraform, Bicep), CI/CD automation, and observability tools. Strong scripting skills in Bash, Python, or Go are required, along with a robust understanding of secure SDLC and compliance.

Key Skills/Competency

  • DevOps
  • Cloud
  • Kubernetes
  • Terraform
  • CI/CD
  • Observability
  • Automation
  • Platform
  • Security
  • Infrastructure

How to Get Hired at Ryan

🎯 Tips for Getting Hired

  • Research Ryan's culture: Understand their mission and benefits.
  • Customize your resume: Highlight DevOps and cloud expertise.
  • Prepare technical answers: Focus on CI/CD and observability.
  • Practice clear communication: Demonstrate leadership in examples.

📝 Interview Preparation Advice

Technical Preparation

Review cloud service fundamentals for Azure and AWS.
Practice Kubernetes and container orchestration scenarios.
Test infrastructure coding with Terraform and Bicep.
Study CI/CD pipeline design and automation frameworks.

Behavioral Questions

Describe a challenging cross-team technical decision.
Explain your process in mentoring engineers.
Discuss a time you influenced system architecture.
Share how you handle incident retrospectives.