About Aptible

Large language models are transforming software engineering — developers can now go from idea to code faster than ever. But that just shifts complexity downstream: deployment, observability, cost, security, reliability — all of that has to scale too, and LLMs don't yet solve the problem.

That's where Aptible comes in. Since 2014, our cloud delivery platform has been automating security, compliance and reliability for engineering teams whose apps handle the most sensitive data, in the most highly regulated industries.

The need for a platform like Aptible has never been greater. If you're passionate about cloud infrastructure and ensuring DevOps evolves to meet the pressure of AI-assisted development — and you're excited to join a small and highly talented team — we’d love to hear from you.

NEW! Aptible is part of Opti9 Technologies, a cloud solutions provider specializing in managed cloud, security, disaster recovery, and compliance. Joining forces with Opti9 gives Aptible the resources to invest more aggressively in the platform — expanding what we can deliver to the engineering teams who depend on it.

Our Commitment to Diversity and Inclusion

We see great value in bringing together a team with different perspectives, educational backgrounds, and life experiences, and we prioritize diversity within our team. We encourage people from underrepresented backgrounds to apply.

About This Role

Overview

In this role, you'll be a hands-on security engineer defending and hardening a platform that regulated companies build their businesses on. This is an engineering role first; you'll design security-by-default infrastructure, run our vulnerability management program, drive our pentesting program (including working with tools like XBOW) from finding to fix, and lead incident response when things go wrong. You'll also bring the organizational rigor to run a compliance recertification when the underlying technical controls are already sound, but this is not a policy-writing or audit-management role, and it's not the core of the job.

This role reports to the VP of Security, but works day-to-day in close collaboration with the Engineering team — not as a siloed security function reviewing work from a distance, but as an embedded partner co-owning the fixes, the infrastructure, and the outcomes.

What You'll Do

Engineering

• Design and build security-by-default infrastructure across our AWS-based PaaS, which spans Ruby on Rails backend systems, a web app (React-TypeScript), a Terraform client (Go), a CLI client (Go), and several other distributed components (Python, Go, Ruby)
• Own and mature our vulnerability management program — triaging findings and working findings from scanning tools and the AWS Security Agent in collaboration with the Engineering team, prioritizing by real-world exploitability and risk
• Own our pentesting program end to end — running automated assessments with XBOW, coordinating manual and third-party testing, and driving remediation to closure in our codebase (Ruby, Go, TypeScript) and infrastructure alongside Engineering, rather than just filing tickets and waiting
• Lead incident response operations: detection, containment, eradication, and post-incident review, with a bias toward fixing root causes in the code and infrastructure, not just symptoms
• Build and maintain detection tooling, alerting, and runbooks — including tuning and extending the AWS Security Agent — to reduce time-to-response
• Participate in on-call rotation for security-relevant incidents and help drive follow-ups that prevent repeats

Compliance

Run point on compliance recertifications and maintaining current standards (e.g., renewing SOC 2 or HITRUST) when the technical controls are already in place, this means being organized, coordinating evidence collection, and working with auditors, not authoring new policy from scratch

Use AI tools to improve your development and investigation workflow

What We're Looking For

General Experience

• 5+ years of experience in security engineering, with a track record of owning security-critical systems in production
• You have experience as a hands-on security engineer, not just a security reviewer or policy writer — you can read and write code, operate infrastructure, and get into the weeds of a system under attack
• You communicate extremely well — clear, effective, and proactive, both in writing and live during an incident
• Developer tools or platform engineering experience is a plus

Technical Expertise

• Strong engineering fundamentals and coding ability, with comfort working across a fullstack codebase — our stack includes Ruby on Rails, React/TypeScript, Go (Terraform client), and Ruby (CLI)
• You're a prolific and thoughtful developer in at least one mainstream language, and can pick up new languages/frameworks quickly
• Deep, hands-on experience with cloud infrastructure security (AWS strongly preferred), including AWS-native security tooling (e.g., AWS Security Agent, GuardDuty, Security Hub), and distributed systems
• Real pentesting experience, including with automated/AI-assisted tools like XBOW, and a track record of driving remediation rather than just reporting findings
• Experience running or significantly contributing to a vulnerability management program, from scanning and triage through verified remediation
• Experience leading or heavily participating in incident response — you stay calm and methodical under pressure
• Comfort working across identity management, network security, and detection tooling

Organizational Strength

• You're organized enough to run a compliance recertification as a project — tracking evidence, coordinating stakeholders, and hitting deadlines — without that becoming your whole job
• You know the difference between operating existing controls well and designing net-new policy, and you're energized by the former

Startup Compatibility

You want to be part of a small, highly collaborative team, and you work closely with Engineering rather than operating at arm's length

You don't let ambiguity or bumps in the road stop you: you identify what's blocking you, take ownership, and drive to get unblocked

You Should Apply If

• You appreciate working in a highly autonomous, trusted role, where the day to day priorities may shift.
• You want to do hands-on security engineering, designing, building, breaking, and fixing in real code — not just governance and paperwork
• You're a deeply curious problem solver, and you're not tied to a specific language or technology
• You're energized by incident response, vulnerability management, and pentesting, and see compliance as something you keep running smoothly, not something you build from scratch
• You're invested in team ownership — you care about what your teammates are building, not just your own corner

Aptible's Employee Benefits

Aptible's Values & Principles

Why Aptible

Aptible has been around for over a decade. We have a real product, real customers who depend on it, and a profitable business. We're not a rocketship chasing hypergrowth — we're a small, tight-knit team doing meaningful work in a complex system. Together, we wield genuine ownership to drive lasting impact: the kind where our work shapes the whole product, not just a corner of it.

We'll be honest: this isn't an “everything is figured out” moment. We're navigating real change, with more on the way — and we're doing it together. We're not looking for someone who thinks they have all the answers already. We're looking for someone who wants to find them with us.

What keeps us here is each other. We're a team that genuinely cares — about the work, the customers (and the cool things they're building), and each other. If you want to do hard things alongside people you actually like and respect, and leave a lasting mark on a system that matters, this is that place.

Interview Process

We want to make the experience of interviewing with us as delightful, efficient, fair, respectful, and transparent as possible. A typical process at Aptible might include the following steps. Please note that this may vary by role, and details will be provided to you early on in the process.

• Introduction to Aptible with the Hiring Manager
• 2-3 Skills-Based Interviews with Aptible Team Members
• Take-Home Project (You will be compensated for completing this)
• References
• Final in-person onsite

If you have a disability or special need that requires accommodation, please let your Recruiter and/or Hiring Manager know.

AI at Aptible

👉 tl;dr — Aptible is a good fit for pragmatic AI skeptics and for AI enthusiasts who are clear-eyed about its limitations and risks.

We are a security and compliance company, and our primary goal is to make it easy for our customers to stay secure and compliant in the cloud. To do that these days, we simply have to have our hands in AI. There's no avoiding it.

We don't believe that AI is the answer to everything. In fact, we carry healthy skepticism about it and have clear eyes about its negative impacts on society, the environment, engineering culture, and more.

But we engage with it for two reasons:

• Because our customers do. And to best serve them, we need expertise in AI use, AI risk, AI development, and more.
• Because sometimes AI is the right tool for the job, and sometimes it accelerates our work. And at heart, we are pragmatists.

Aptible is a good fit if you're someone who can hold multiple ideas at once about AI — the utility and the risk, the potential and the cost, enthusiasm and skepticism. If you're categorically opposed to working with it in any form or an unbridled enthusiast, this probably isn't the right fit.

AI Usage in the Interview Process

At Aptible, AI is part of how we work every day. We treat it like any other development tool — powerful, expected, and entirely the responsibility of the person using it. Use it with discernment, knowing that you still own the results.

Here's what we expect from you:

• Your resume — Don't submit AI-generated resumes. They will be discarded. Concise and real wins with us. (Why? We review a high volume of applications and aren't using AI for application review. Our human reviewers can't parse through templated, bloated submissions, and resumes highly tailored to the keywords of our JDs don't hold weight for our reviewers)
• Live conversations — Don't use real-time AI to generate answers that you read off to us. It's obvious, and we'll end the interview. Honest and real wins with us. (Why? These are human interactions. We're evaluating you — how you think, how you communicate, how you engage)
• Technical topics/work — Use any tools you normally would, including AI agents. But be honest about what you used, be discerning about what AI outputs, and be ready to explain your thinking. AI output refined by human judgment wins with us. (Why? We want to see what real work looks like. And real work includes shaping what comes from AI, not just accepting it as-is)