Skip to main content

LEAD SITE RELIABILITY ENGINEER (SRE) – DEVOPS

Posted 7 days ago

software technologyAustin (TX)

SENIORITY

Lead

Apply (opens in a new tab)

About the role

Lead Site Reliability Engineer (DevOps)
Qualifications:
  • Minimum of 5+ years of relevant professional experience.
  • Minimum of 2+ years of experience in CI/CD tooling and capabilities.
  • Minimum of 2+ years of experience in implementing quality frameworks with quality gates within a CI/CD framework.
  • Minimum of 2 years of experience in Cloud, ideally AWS.Ideally experience in C# and dotnet, comfortable in writing tools in and for this environment.
  • Ideally experience in Infrastructure as Code, ideally Terraform.
  • Knowledge on these technologies is plus:
  • AWS (Lambda, ECS/EKS orchestration of containers, SQS/Kinesis, ElastiCache, ElasticSearch, Aurora, DynamoDB)
  • Infrastructure as code (ideally Terraform)API Gateway and/or Service
  • MeshObservability with Splunk and NewRelic
What We Look For:
  • Experience and understanding of working in AWS environments.
  • Experience in Cloud native containerized applications, with a focus on microservice architectures and an API first development methodology.
  • Experience in Cloud pub/sub event driven architecture patterns.
  • Experience in Cloud application security and governance.
  • Experience in one/more professional engineering practices:
  • Site Reliability practices
  • Automated CI/CD – Continuous integration and delivery
  • Automated IaC – Infrastructure as code
  • Automated quality frameworks (SonarQube, Veracode, automated testing)
  • Consistent observability and telemetry frameworks
  • Experience in modern OO language, ideally C# and dotnet (Java is acceptable).Experience in Terraform.
  • High energy, confident, ambitious and self-motivated individual.
  • End-to-end ownership of product design, delivery and operational support.
  • Must be an effective communicator and able to communicate with all levels of the organization.
  • Willingness to mentor Software Engineers.

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this