> Markdown version of [/jobs/ext/4622625-devops-security-engineer](https://www.wearedevelopers.com/jobs/ext/4622625-devops-security-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# DevOps & Security Engineer

- **Company:** StudyFetch, Inc.
- **Location:** Beverly Hills, CA, United States
- **Experience:** Expert
- **Contract:** Permanent contract
- **Skills:** Kubernetes Security, Microsoft Access, Artificial Intelligence, Audit Trail, Cloud Computing, Continuous Integration, DevOps, Domain Name System (DNS), Identity and Access Management, Key Management, Network Security, PostgreSQL, MongoDB, Network Segmentation, Reliability Engineering, Zero Trust Network Access, Next.js, Software Vulnerability Management, Pulumi, Google Cloud, Caching, Amazon Virtual Private Cloud (VPC), Kubernetes, Cloudflare, Machine Learning Operations, Hardware Infrastructure, Terraform, AIOps, Jenkins
- **Published:** November 7, 2026
- **Apply:** https://www.juju.com/job/28_25197_4e2f6c4fcb7dc4e217ce7f705eea0eea

## About the Role

You're a strong fit if either of these is true:

 * 5+ years in security engineering, DevOps, SRE, or infrastructure, with real depth in securing and operating production systems, or
 * You were an early engineer who owned security and operations for a real product as it grew, and can demonstrate what you built and defended., You don't need every item below, but you should be deep in most and able to ramp quickly on the rest:
 * Security: IAM and least-privilege access, secrets management and rotation, network security, zero-trust access, vulnerability management, audit logging
 * Compliance: SOC 2 and continuous compliance tooling; awareness of frameworks like FedRAMP
 * DevOps & CI/CD: build and deploy pipelines (Jenkins or similar), container builds, GitOps-style automation, infrastructure-as-code (Pulumi or Terraform)
 * Cloud & orchestration: GCP, Cloudflare, Vercel; Kubernetes (GKE), Helm
 * Networking: VPC design, firewalls, DNS/TLS, and - for the colo work - datacenter and network segmentation
 * Observability & operations: monitoring, alerting, incident response, on-call
 * Data & AI ops: PostgreSQL and MongoDB, managed caches, plus operating and securing GPU/model-serving workloads

## Description

You'll work alongside our Lead Infrastructure & Platform Engineer as a partner, not a report. They set the direction of the platform; you focus on the security and DevOps side, deepening our posture and the automation that keeps us shipping safely. As we build out our own GPU infrastructure inside a colocation facility, you'll help make sure it's secured, monitored, and operable from day one. If you want deep ownership of security and operations for a product that reaches millions of learners, this is it., * Security posture, end to end. Identity and least-privilege access across our cloud and tooling, secrets management and rotation, network security, and the day-to-day work of keeping the platform hard to break into and easy to audit.

 * Compliance, made real. We hold ourselves to a serious bar (SOC 2, continuous scanning, evidence you can actually produce). You own the controls, the audit readiness, and the roadmap toward frameworks like FedRAMP, without turning the team into a ticket queue.
 * The DevOps backbone. CI/CD, build and deploy pipelines, and the automation that lets engineers ship safely and often. You make the paved road, and you make the secure way the easy way.
 * Reliability and incident response. Monitoring, alerting, on-call, and the postmortems that make the next incident less likely. When something breaks at 2am, you're calm, methodical, and the reason it doesn't happen twice.
 * Securing the GPU and colocation buildout. As we stand up GPU capacity in a colo facility, you own its security and operability: network segmentation, access controls, monitoring, and hardening across the hybrid of on-prem and cloud.
 * Raising the security bar for the team. The practices you set for how we handle secrets, access, and incidents are the ones everyone else follows., * You've secured and operated production systems that real users depend on. You can walk us through an environment you hardened, an incident you ran, which parts were yours, and what you changed afterward.
 * You think like an attacker and build like an operator. You understand cloud and Kubernetes security, identity and access, secrets, and network security, and you close gaps without grinding the team to a halt.
 * You've carried real compliance. SOC 2 or similar isn't a mystery to you, and you know how to make controls that hold up in an audit without becoming theater.
 * You automate by default. Manual, click-through processes bother you; you'd rather codify them. Infrastructure-as-code and pipelines are how you work.
 * You use AI every day and have informed opinions about it, including how to operate and secure AI workloads. Genuine curiosity is the one thing we can't teach.
 * You're candid about tradeoffs and steady under pressure, including launch crunch and live incidents.
 * The mission is why you're here. What sustains you through the hard weeks is the learner on the other end, the one whose data you protected and whose experience stayed up because of something you built., * You'll have significant ownership and autonomy with limited oversight. The role suits engineers who do their best work with room to run.