Cloud Security / DevSecOps Engineer

Help build the platforms that the world's best teams rely on.

Our work starts with the real artifacts of engineering: architecture notes, pull requests, runbooks, dashboards, incidents, and the constraints teams face every day. We make that context visible, then help turn it into systems that are clearer, stronger, and easier to operate.

We work from artifacts

Architecture notes, pull requests, runbooks, dashboards, incidents, and the actual constraints your team works inside.

We make context visible

The block gives the page more texture without making it feel like a stock-photo agency site.

Embark on a rewarding journey with us. Find opportunities to grow, learn and make a lasting impact.

Join a team that embraces forward-thinking ideas, fosters innovation, and cultivates an environment where your creativity can flourish.

People-First Mindset:

We think deeply about the real-world impact of every solution on teams, customers, and stakeholders.

Technical Integrity

Our work is grounded in best practices, thoughtful design, and sustainable engineering.

Long-Term Perspective

We’re invested in outcomes that endure, not quick fixes that falter.

A practical process for practical engineers.

The interview path should feel like the work: clear communication, systems thinking, technical judgment, and the ability to collaborate without ego.

01

A lightweight conversation about your background, what you want next, and the kinds of platform problems you like solving.

02

Walk through a real platform scenario and talk about tradeoffs, sequencing, observability, reliability, and team enablement.

03

Working session

Pair on a small practical exercise or artifact: architecture notes, implementation plan, review, or operational improvement.

04

Discuss role shape, expectations, compensation, client work, team norms, and how you do your best engineering work.

What working here should feel like

The benefits are designed around focus, trust, craft, and the reality that deep engineering work needs room.

Room for architecture, implementation, writing, review, and careful technical judgment.

A team that values context, humility, strong opinions, and better systems.

Work directly on the platform constraints that are slowing real engineering teams down.

Craft and learning

Kubernetes, cloud, modernization, AI workflows, and delivery systems in production contexts.

We care about secrets, access, change safety, auditability, and operational guardrails.

Modern tools

Use automation and AI carefully, with bounded context and human approval.

No mystery process, no puzzle interviews.

Open Positions

Be a part of a winning culture that fosters collaboration, creativity, and success in every career path

Cloud Security / DevSecOps Engineer

Location

United States

Employment Type

Full time

Location Type

Remote

Department

About the Role

We are seeking a Cloud Security / DevSecOps Engineer to help maintain and strengthen the security, compliance, and reliability of a FedRAMP-compliant environment running on AWS.

This is a highly hands-on role focused on cloud infrastructure, security automation, vulnerability remediation, and compliance. You’ll work across infrastructure and application security to identify and resolve vulnerabilities, address cloud misconfigurations, and ensure the environment continues to meet stringent security and compliance requirements.

This is also an opportunity for a high-performing engineer to take on increasing technical and organizational responsibility, with the potential to grow into a Head of Engineering role.

What You'll Do

Maintain and improve FedRAMP compliance within an AWS environment.

Manage and improve infrastructure using Terraform and infrastructure-as-code best practices.

Identify and remediate Golang/container vulnerabilities and other security issues.

Investigate and resolve cloud infrastructure misconfigurations.

Review systems and infrastructure against NIST security guidelines and controls.

Develop and maintain CI/CD automation using GitHub Actions.

Partner with engineering teams to integrate security into the software development lifecycle.

Monitor infrastructure and applications for security vulnerabilities and compliance gaps.

Help establish repeatable processes for security, compliance, and infrastructure management.

Contribute to architectural and engineering decisions as the organization scales.

Required Qualifications

Strong professional experience with Terraform and infrastructure as code.

Hands-on experience with Go (Golang).

Experience building or maintaining CI/CD pipelines using GitHub Actions.

Experience with AWS cloud infrastructure.

Strong understanding of cloud security and infrastructure security principles.

Experience identifying and remediating vulnerabilities in containers and cloud environments.

Familiarity with NIST security guidelines and frameworks.

Experience working in a security-conscious or regulated environment.

Preferred Qualifications

Experience with AWS security services and controls.

Kubernetes and container security experience.

Experience with vulnerability management and remediation.

Familiarity with automated security testing and DevSecOps practices.

Experience working with government or highly regulated customers.

Experience with additional infrastructure/security tooling such as Rust is a plus.

What Will Set You Apart

We're looking for someone who is comfortable operating at the intersection of engineering, cloud infrastructure, security, and compliance.

The ideal candidate isn't simply checking compliance boxes—they can understand the underlying infrastructure, troubleshoot technical vulnerabilities, and work directly with engineering teams to implement practical solutions.

Strong Golang experience is particularly valuable for this role, as it will be used to address vulnerabilities and maintain components within the existing containerized environment.

This role offers significant opportunity for growth. While the initial focus will be on AWS infrastructure, FedRAMP compliance, security remediation, and DevSecOps, the right candidate can take on broader technical leadership and architecture responsibilities over time.

For the right individual, there is a potential path toward Head of Engineering as the organization continues to grow.

OpenTelemetry is best understood as a standard telemetry pipeline: APIs and SDKs create signals, context propagation links work across services, semantic conventions make data consistent, OTLP transports it, Collectors process it, and exporters deliver it to observability backends.

Coding-agent cost is not mainly the price of one clever prompt. It is the recurring cost of moving repository state, tool output, and loop history through paid models until useful work is accepted. Gateway observability makes that spend attributable and governable, while agent-loop discipline determines how much context gets sent.

Tool-using AI agents need more than prompt guidance. If an action can create a real side effect, enforcement should live in executable policy that can allow, deny, stop, or elevate before the tool call happens.

A practical way to distinguish DevOps, Platform Engineering, and SRE by responsibility instead of buzzword: collaboration, paved roads, and explicit reliability ownership.

Discover content that will transform your engineering organization.

#J-18808-Ljbffr Jobleads-US