Staff Product Manager, Acquisition

The posting, as Aptible wrote it

ABOUT APTIBLE

Large language models are transforming software engineering — developers can now go from idea to code faster than ever. But that speed cuts both ways: AI makes attackers more capable, zero-days weaponize faster, and AI-assisted "vibe coding" is shipping more code with less security review. 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 future of Aptible is to be the safe place to run both traditional and AI-native applications: isolated from lateral movement, defended against known and emerging vulnerabilities, and instrumented so that if something does go wrong, the blast radius is contained and the forensics are already in place.

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

We’re looking for a dynamic Product Manager who can set the strategy, roadmap, and feature definition that expands our positioning as the secure PaaS for the AI-native era, for both traditional and generative/agentic applications. In this role, you will partner closely with our engineering team, product designer, and marketing team to:

• Build something our target customers want (create value), and
• Build something that helps us strategically grow the business (capture value)

This PM is responsible for Acquisition (measured by new customers), and will work alongside the PM for Retention (measured by NDR).

WHAT YOU’LL DO

There are two types of outcomes this role will be accountable for:

• (Quantitative) Business outcomes/Key Performance Indicators (KPIs)
• Product signups and new product-led customer conversions
• Count of customers using features delivered against the Acquisition roadmap, across LLM Gateway and PaaS
• New ARR ($) from features delivered against the Acquisition roadmap
• (Qualitative) Role-based outcomes in these criteria:

Discov
[…]
ear 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)