FULLTIME
Site Reliability Engineer
Hydden
Not specified · onsite · Posted 82d ago
About a minute. You'll make an account on the way through.
agent · working
- Read this posting0.6s
- Found the form on Instahyre · 13 questions to answer1.1s
- Decided the answers for all of them2.7s
- Tailor your résumé to this role
- Waiting for you
Section · 01
About this role
We are hiring a Site Reliability Engineer to own the reliability, cost, and hygiene of our cloud environments. You will be the hands-on owner of how we deploy, promote, and operate our product labs across dev, test/staging, prod, and demonstrating on Microsoft Azure, with a clear mandate to lead migration to AWS. This is a test/staging and product demonstration of who has lived in both Azure and AWS as a DevOps/SRE practitioner and treats environment stability, cost discipline, and clean release paths as first-class product outcomes.
The core responsibilities for the job include the following:
Cloud environments and reliability:
- Own stability and availability across Azure (and later AWS) environments: dev, test/staging, prod, and demo.
- Drive environment hygiene: cleanup of unused resources, stale deployments, orphaned storage, and configuration drift.
- Establish and enforce right-sizing so capacity matches demand and utilization stays high, minimizing waste without sacrificing reliability.
Cost and COGS:
- Own cloud COGS for Azure today and AWS as we migrate.
- Continuously review spend, utilization, and reservation/savings opportunities; make cost a measurable operating metric, not an afterthought.
CI/CD, promotion, and release management:
- Own GitHub Actions CI/CD pipelines and workflows end-to-end.
- Own promotion and release management from development through production (and demo), with clear gates, auditable releases, and safe rollback paths.
- Build once, promote consistently, and keep the release process boring, repeatable, and secure.
Azure-AWS migration:
- Lead the eventual migration from Azure to AWS, including architecture, cutover.
- planning, parity across environments, and operational readiness.
- Bring strong dual-cloud fluency so migration reduces risk instead of introducing it.
What Success Looks Like:
- Environments are stable, recoverable, and boring in the best way.
- Spend and utilization are visible, justified, and trending in the right direction.
- Releases move through environments predictably via owned pipelines, not ad hoc deploys.
- Azure stays healthy now; AWS readiness improves steadily toward a clean cutover.
Requirements:
- Hands-on Azure and AWS experience as a DevOps / SRE engineer (not only architecture slides).
- Proven ownership of production cloud environments, including availability, incident response hygiene, and operational runbooks.
- Strong CI/CD background, ideally with GitHub Actions.
- Experience with release/promotion workflows across multiple environments.
- Bias toward cost-aware engineering: tagging, right-sizing, cleanup, and utilization accountability.
- Comfort leading a cloud migration while keeping current platforms running.
- Clear communicator who can set standards and enforce them without slowing the team down.
Nice to Have:
- Background in cybersecurity, security tooling, or regulated/high-trust environments.
- Infrastructure as Code (Terraform, Bicep, CloudFormation/CDK).
- Observability, FinOps practices, and container/Kubernetes operations.
- Experience running customer-facing demo environments alongside production.
Sourced from instahyre
Section · 02