Tenable, Inc.
Software/Site Reliability Engineer - FedRAMP
About this role
Tenable seeks a Software/Site Reliability Engineer to ensure their cloud-based vulnerability management platform remains reliable and highly available across private and government cloud environments. You'll develop automation tools, respond to production incidents, and collaborate with cloud and software engineering teams to scale and optimize infrastructure.
What you'll do
- Ensure reliability and high availability of Tenable cloud products in production environments
- Troubleshoot complex technical issues and resolve escalations within SLO targets
- Develop automation tools and scripts for deployment, management, and monitoring of distributed systems
- Collaborate with cloud engineers on new technologies and infrastructure improvements
- Participate in on-call rotation to support 24/7 availability and incident response
- Create operational documentation and drive standardization across SRE practices
What they're looking for
- Site Reliability Engineering (2+ years)
- Terraform or Infrastructure-as-Code tooling
- Public cloud platforms (AWS, GCP, Azure)
- Kubernetes and container orchestration
- Docker and containerization
- Bash scripting and Python/Node.js
- Distributed systems and microservices architecture
- AWS managed services (EKS, OpenSearch, MSK, Batch)
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Tenable, Inc.
Tenable provides cybersecurity solutions including vulnerability analysis and threat detection products. The company is hiring Technical Support Engineers to assist customers with these platforms, Pre-Sales Engineers to drive enterprise sales, and a Salesforce Developer to support internal business technology operations.
- Website
- tenable.com
Likely interview questions
- Describe a production incident you resolved and how you prevented similar issues going forward.
- Walk us through your experience with Terraform—what infrastructure have you defined, and what challenges did you face?