Senior Site Reliability Engineer

The ReWork Group; New York (NY); On-site; USD 120,000 - 160,000; Full time

Job summary

A leading technology consultancy in New York seeks a Senior Site Reliability Engineer (SRE) to build robust infrastructure for a client at the forefront of finance and decentralized economies. Responsibilities include leading incident responses, developing observability solutions, and maintaining infrastructure as code on AWS. Candidates should have 5+ years in SRE or DevOps, strong incident management skills, and deep AWS fluency. Join us to enhance the reliability and efficiency of essential systems.

Qualifications

• 5+ years in SRE or DevOps, or 7+ years in software engineering with an infrastructure focus.
• Experience leading incident responses for high-availability production systems.
• Familiarity with designing deployment architectures across multiple cloud targets.

Responsibilities

• Lead incident response and establish on-call practices.
• Develop self-service observability solutions using monitoring tools.
• Create infrastructure as code for secure cloud environments on AWS.

Skills

Incident response

Infrastructure as code

Monitoring and observability solutions

CI/CD pipelines

AWS expertise

Tools

Terraform

Datadog

Prometheus

ELK

Job description

At The ReWork Group, we partner with high-growth startups and forward-thinking companies to build the future.

To support our client's immediate Data Science endeavors, we're on the lookout for a Senior SRE. Our client sits at the intersection of two worlds that have long operated in parallel: the incumbent financial system, with its entrenched rails, opaque pricing, and gate kept access, and the decentralized economy, where programmable money, self-custody, and on-chain transparency are rewriting the rules of ownership and trust.

They're scaling from thousands to millions users and they need the infrastructure to match. As a Senior SRE, you're not inheriting a mature system and maintaining the status quo. You're building the reliability foundation from the ground up, architecting resilient infrastructure, designing proactive monitoring that catches problems before users feel them, and standing up on-call processes that actually scale with the team.

The challenges are real and immediate: database optimization, async workflow infrastructure, data pipeline reliability. You'll own them. And in doing so, you'll give the engineering team something invaluable — the confidence to ship fast without breaking things.

This is the kind of role where your fingerprints end up everywhere.

What You'll Do:

• Lead incident response and establish sustainable on-call practices, including comprehensive runbooks, blameless postmortems, and systematic improvements that reduce MTTR
• Develop and maintain self-service observability solutions using modern monitoring tools that provide actionable insights for troubleshooting and performance optimization
• Create and maintain infrastructure as code (using Terraform, CloudFormation) that allows for consistent, scalable, and secure cloud environments on AWS
• Partner closely with feature teams to architect resilient infrastructure for critical components (databases, networking, async workflows, data pipelines) that scale seamlessly
• Work closely with DevX to design and implement robust CI/CD pipelines with advanced deployment strategies (blue/green, canary) that enable teams to ship confidently and rapidly
• Advocate for best practices early in feature design, ensuring we design with reliability in mind and future-proof our services

What You'll Bring:

• 5+ years in SRE or DevOps — or 7+ years in software engineering with a serious infrastructure focus and the scars to prove it
• You've led incident response for high-availability production systems — you run tight RCAs, you drive blameless postmortems, and you leave every incident with a team that's smarter than before
• You've designed highly available deployment architectures across multiple targets — EC2, Fargate, and beyond — with real expertise in auto-scaling, health checks, and graceful degradation when things get hard
• You've implemented monitoring and observability solutions that actually get used — Datadog, Prometheus, ELK, or comparable — and you've made the case internally for why observability isn't optional
• Deep AWS fluency and a strong infrastructure-as-code practice — Terraform is your default, not your fallback
• You've built and improved CI/CD pipelines that give engineering teams the confidence to ship fast and reliably