Senior Site Reliability Engineer (Event-Engagement)

Overview:

Our Culture and Impact

Cvent is a leading meetings, events, and hospitality technology provider with more than 6,000+ employees and 34,000+ customers worldwide, including 60% of the Fortune 500. Founded in 1999, Cvent delivers a comprehensive event marketing and management platform for marketers and event professionals and offers software solutions to hotels, special event venues and destinations to help them grow their group/MICE and corporate travel business. Our technology brings millions of people together at events around the world.

In short, we’re transforming the meetings and events industry through innovative technology that powers the human connection.

Cvent's strength lies in its people, fostering a culture where everyone is encouraged to think like entrepreneurs, taking risks and making decisions confidently. We value diverse perspectives and celebrate differences, working together with colleagues and clients to build strong connections.

AI at Cvent: Leading the Future

Are you ready to shape the future of work at the intersection of human expertise and AI innovation? At Cvent, we’re committed to continuous learning and adaptation—AI isn’t just a tool for us, it’s part of our DNA. We’re looking for candidates who are eager to evolve alongside technology. If you love to experiment boldly, share your discoveries, and help define best practices for AI-augmented work, you’ll thrive here.

Our team values professionals who thoughtfully integrate AI into their daily work, delivering exceptional results while relying on the human judgment and creativity that drive real innovation.

Throughout our interview process, you’ll have the chance to demonstrate how you use AI to learn, iterate, and amplify your impact. If you’re excited to be part of a team that’s leading the way in AI-powered collaboration, we’d love to meet you.

When a Fortune 500 company runs their annual sales conference, a software company broadcasts their product launch, or 500 exhibitors scan leads on the trade show floor — this team is why it works. We keep the infrastructure running for Cvent's event product suite, and we're rebuilding how SRE operates along the way.

In This Role, You Will:

Own reliability across a complex, global product portfolio.

You'll be the embedded SRE partner for dev teams across the suite — knowing each product's architecture, failure modes, and customer impact zones well enough to be genuinely useful, not just present. Deep product knowledge isn't a bonus; it's what separates great SRE work from good SRE work.

Move legacy systems forward — and absorb what acquisitions bring.

A meaningful portion of this team's work is migration: getting legacy EC2 and Ruby estates onto Cvent's paved road, and onboarding acquired companies onto Cvent's platform. When an acquisition lands, you're doing the discovery — what are they running, what does the architecture look like, what's the migration path — then building it out in CDK and executing the transition without disrupting their product teams. You're not inheriting clean infrastructure. You're making it clean.

Build AI agents that close tickets while you're not watching.

Walk-Up Triage, Migration pre-flight checks, PR review automation, incident postmortems — the team's agent portfolio exists to absorb repeating work so SREs can focus on the judgment calls AI can't make. You'll build, tune, and operate these agents using Claude Code and Cvent's internal AI platform. We track what each agent closes and what it should have escalated.

Drive SLOs and observability from the ground up.

Journey SLO programs are live and evolving across the portfolio. Some products generate customer-impacting incidents that PagerDuty alone doesn't surface. You'll instrument journey health, define meaningful SLIs, conduct incident retrospectives, and build the alert posture that makes on-call bearable — and eventually, boring in the right way.

Embed with dev teams and make the work compound.

This team doesn't operate as a central gatekeeper. You'll do architecture reviews and co-own production readiness decisions. The knowledge base — runbooks, postmortems, playbooks, agent training sets — is a team product, and you help build it.

Champion standards without becoming a bottleneck.

Cvent's paved road exists. CI/CD standards, IaC practices, security posture — you guide dev teams toward them and flag what's genuinely dangerous versus what's just imperfect. You know the difference.

Here's What You Need:

• CI/CD and IaC in production
• — you've shipped pipelines, watched them fail at 2am, and improved them
• AWS operational depth
• — ECS, EKS, or Kubernetes in production at a scale that serves real customers
• Scripting fluency
• — Python, TypeScript, or Bash; enough to automate your own toil, not just run scripts others wrote
• Observability tooling
• — Datadog, Splunk, or equivalent; you build the dashboards, you don't just read them
• Incident command
• — you've led the call, written the postmortem, and closed the loop with stakeholders
• SRE fundamentals
• — SLIs, SLOs, error budgets, toil accounting; not as buzzwords but as tools you've actually used

Agile SDLC

— you've worked embedded with product dev teams, not as an external review layer

Strong Plus

• Daily use of Claude Code, Cursor, or AI coding assistants as an engineering accelerant — not occasional dabbling
• Experience integrating LLM-based tooling into CI/CD or operational workflows
• EKS/Kubernetes cluster operations — upgrades, ArgoCD, node pool management
• Legacy modernization — EC2 to containers, old monolith to services, you've done the before-and-after
• Configuration management: Chef, Ansible, or equivalent

Tech Stack

AWS ECS - AWS EKS - AWS Lambda - CloudFront - ArgoCD - ProxySQL - RabbitMQ - Redis / ElastiCache - Datadog - PagerDuty - Jenkins - Octopus Deploy - Terraform / CDK - Docker - Ruby / Rails - Elixir - Node.js - Python - TypeScript - Bash - Chef - Claude Code

What we don't list but care about

• You measure what matters and let data change your mind
• You'd rather automate the fifth repetition than do it a sixth time manually
• You're comfortable saying "I don't know yet" and uncomfortable with "that's just how it works"
• You understand the difference between toil and real work, and you track which is which
• Hybrid: 2 days in office
• This job posting is intended to comply with all applicable laws. If we learn during the course of our recruitment process that, due to an applicant’s location, further information about the position is required, including certain salary information, this information in this posting will be supplemented accordingly.

The estimated base salary range for new hires into this role is $120,000 - $150,000 annually + bonus depending on factors such as job-related knowledge, relevant experience, and location. We also offer a competitive benefits package, details of which can be found here.

We are not able to offer sponsorship for this position

Physical Demands

Responsibilities

• Own reliability across a complex, global product portfolio.
• You'll be the embedded SRE partner for dev teams across the suite — knowing each product's architecture, failure modes, and customer impact zones well enough to be genuinely useful, not just present. Deep product knowledge isn't a bonus; it's what separates great SRE work from good SRE work.
• Move legacy systems forward — and absorb what acquisitions bring.
• A meaningful portion of this team's work is migration: getting legacy EC2 and Ruby estates onto Cvent's paved road, and onboarding acquired companies onto Cvent's platform. When an acquisition lands, you're doing the discovery — what are they running, what does the architecture look like, what's the migration path — then building it out in CDK and executing the transition without disrupting their product teams. You're not inheriting clean infrastructure. You're making it clean.
• Build AI agents that close tickets while you're not watching.
• Walk-Up Triage, Migration pre-flight checks, PR review automation, incident postmortems — the team's agent portfolio exists to absorb repeating work so SREs can focus on the judgment calls AI can't make. You'll build, tune, and operate these agents using Claude Code and Cvent's internal AI platform. We track what each agent closes and what it should have escalated.
• Drive SLOs and observability from the ground up.
• Journey SLO programs are live and evolving across the portfolio. Some products generate customer-impacting incidents that PagerDuty alone doesn't surface. You'll instrument journey health, define meaningful SLIs, conduct incident retrospectives, and build the alert posture that makes on-call bearable — and eventually, boring in the right way.
• Embed with dev teams and make the work compound.
• This team doesn't operate as a central gatekeeper. You'll do architecture reviews and co-own production readiness decisions. The knowledge base — runbooks, postmortems, playbooks, agent training sets — is a team product, and you help build it.
• Champion standards without becoming a bottleneck.
• Cvent's paved road exists. CI/CD standards, IaC practices, security posture — you guide dev teams toward them and flag what's genuinely dangerous versus what's just imperfect. You know the difference.

Qualifications

• CI/CD and IaC in production
• — you've shipped pipelines, watched them fail at 2am, and improved them
• AWS operational depth
• — ECS, EKS, or Kubernetes in production at a scale that serves real customers
• Scripting fluency
• — Python, TypeScript, or Bash; enough to automate your own toil, not just run scripts others wrote
• Observability tooling
• — Datadog, Splunk, or equivalent; you build the dashboards, you don't just read them
• Incident command
• — you've led the call, written the postmortem, and closed the loop with stakeholders
• SRE fundamentals
• — SLIs, SLOs, error budgets, toil accounting; not as buzzwords but as tools you've actually used
• Agile SDLC
• — you've worked embedded with product dev teams, not as an external review layer
• Strong Plus
• Daily use of Claude Code, Cursor, or AI coding assistants as an engineering accelerant — not occasional dabbling
• Experience integrating LLM-based tooling into CI/CD or operational workflows
• EKS/Kubernetes cluster operations — upgrades, ArgoCD, node pool management
• Legacy modernization — EC2 to containers, old monolith to services, you've done the before-and-after
• Configuration management: Chef, Ansible, or equivalent
• Tech Stack
• AWS ECS - AWS EKS - AWS Lambda - CloudFront - ArgoCD - ProxySQL - RabbitMQ - Redis / ElastiCache - Datadog - PagerDuty - Jenkins - Octopus Deploy - Terraform / CDK - Docker - Ruby / Rails - Elixir - Node.js - Python - TypeScript - Bash - Chef - Claude Code

What we don't list but care about

• You measure what matters and let data change your mind
• You'd rather automate the fifth repetition than do it a sixth time manually
• You're comfortable saying "I don't know yet" and uncomfortable with "that's just how it works"
• You understand the difference between toil and real work, and you track which is which
• Hybrid: 2 days in office
• This job posting is intended to comply with all applicable laws. If we learn during the course of our recruitment process that, due to an applicant’s location, further information about the position is required, including certain salary information, this information in this posting will be supplemented accordingly.

The estimated base salary range for new hires into this role is $120,000 - $150,000 annually + bonus depending on factors such as job-related knowledge, relevant experience, and location. We also offer a competitive benefits package, details of which can be found here.

We are not able to offer sponsorship for this position

Physical Demands