virtru

Site Reliability Engineer

Apply Now

At a Glance

Location
Washington, District of Columbia, United States
Work Regime
remote
Experience
2–5 years
Department
Engineering
Posted
2026-03-03T17:29:48-05:00

Key Requirements

Required Skills

AWSDevOpsGCPKubernetesLinuxPython

Domain Knowledge

  • Automation
  • Engineering

Requirements

2-5 years of experience in SRE, DevOps, infrastructure, or a related engineering role

Experience with cloud platforms (AWS, GCP, or similar)

Familiarity with containers and Kubernetes (production experience is a plus)

Comfort writing automation in a language like Python or Go

Understanding of Linux fundamentals

Compensation & Benefits

$125,000 - 155,000 base salary

At Virtru, we believe people do their best work when their wellbeing is put first. This is why we make your wellbeing our priority with a thoughtful and holistic program that encompasses Occupational, Mental, Social, Physical, and Environmental Wellness by offering benefits such as…

A Flexible PTO policy — we strongly encourage you to take time off (in addition to 14 holidays) to ensure that you are getting the proper time needed to unplug and recharge.

A $1,500 annual Learning & Development Stipend focused on providing you the resources to continually learn and professionally grow.

Frequent company-sponsored team celebrations that provide ample opportunities to connect with teammates and be social!

Responsibilities

As a Site Reliability Engineer, you'll join a team of 6 engineers building and maintaining Virtru's cloud-native infrastructure.

We collaborate closely with the Security team and multiple other engineering teams at the company.

The SRE team owns cloud infrastructure, CI/CD systems, the Kubernetes platform, developer tooling, and observability.

Help build and maintain cloud infrastructure using Infrastructure as Code

Contribute to CI/CD pipelines and delivery automation that development teams rely on

Support Kubernetes workloads: troubleshoot issues, implement improvements, and pick up platform best practices as you go