Job description

ABOUT KEYCARD At Keycard, we're building identity and access infrastructure for the agent-native era, where software isn't static but a dynamic, constantly changing system of AI agents working on behalf of people and businesses. Keycard gives every agent a verified identity and issues short-lived, task-scoped credentials at runtime, so agents can only do what they were asked to do, and every action is fully auditable. We're backed by a16z, Boldstart, and Acrew, and our founding team built and scaled Snyk, Auth0, HashiCorp, and Heroku. THE ROLE We're hiring a Product Manager to own how teams evaluate Keycard, and the developer experience they meet when they do. Keycard is a control plane for agents: identity, credential exchange, delegation, policy, and audit. Every customer starts with an evaluation, and today a field engineer runs each one by hand: setup, first credential exchange, integration questions. Your job is to turn that walkthrough into product, so an evaluation can run well without us in the room. You'll define what a successful evaluation looks like for an agent-identity product, instrument the journey so we can see where evaluators stall, then work with engineering to fix the worst spots. Sometimes the fix is a feature, more often it's a better quickstart, a template repo, an error message that says what to do next, or a docs page that assumed too much context. Expect to spend real time with the people running evaluations: watching onboarding sessions, sitting in on field-engineering walkthroughs, reading support threads, and finding out why a team went quiet mid-eval. WHAT YOU'LL DO - Own the evaluation journey end to end, from first touch through first credential exchange to a production decision, including how each stage is defined and measured. - Set the evaluation milestones and metrics that product, engineering, and go-to-market all report against. - Own the developer experience an evaluation runs on: SDK quickstarts, CLI onboarding, console setup, docs, and template repos. - Drive time-to-first-credential-exchange down, and be the voice of developer ergonomics in engineering's API and CLI design discussions. - Turn what field engineering does by hand into self-guided paths: eval guides, reference architectures, in-product guidance. Run experiments and cut the ones that don't work. - Work with DevRel and marketing on how evaluations start, and with sales and field engineering on when a self-guided eval needs a human in the room. WHAT WE'RE LOOKING FOR - You've been a PM on a developer product where evaluation and adoption were your numbers (dev tools, infrastructure, API platforms, or security). - Technical enough to be credible with engineers. You can read an SDK quickstart and see where a developer would bounce, follow an API design discussion, and pull your own numbers in SQL or an analytics tool. - You have taste in developer experience. You can articulate why one CLI feels good and another doesn't, and you notice error messages, defaults, and docs structure the way a designer notices spacing. - You build with AI tools yourself and follow the agent ecosystem closely enough to have real opinions about it. - You start from instrumentation. If the data you need doesn't exist, you get it added before forming theories about where evaluations drop off. - Comfortable in a category with no playbook. Agent identity is new, and a lot of this job is deciding which questions are worth answering. - You write clearly. Much of this role's output is docs, problem statements, and experiment readouts that other people act on. STRONG CANDIDATES MAY ALSO HAVE - An engineering background before product; you've shipped code and understand what you're asking engineers to do. - Experience productizing a high-touch motion: turning field playbooks, POC guides, or solutions-engineering work into product. - Familiarity with identity/auth concepts (OAuth, OIDC, token exchange, delegation) or agent protocols (MCP, A2A). - Experience with growth tooling: product analytics, experimentation frameworks, lifecycle messaging. - Docs, quickstarts, or templates you shipped that developers actually used. WHO WILL LOVE THIS JOB - You'd rather ship a fix this week than present a strategy deck about it next month. - You treat quickstarts and docs as product surfaces that deserve real design attention. - You want to define the evaluation motion for a new category from scratch. - You like being early: small team, direct access to founders and customers, no layers between you and what ships. WHAT WE OFFER - Build at the Frontier: Work every day at the frontier of agent-native systems — shipping, inventing, and iterating on technology that hasn’t been built before. You’ll be given huge autonomy, the opportunity to gain mastery, and the chance to work in a team that holds each other accountable to succeed. - Truly Agent-Native Culture: At Keycard, we don’t just enable others to adopt agents — we use them ourselves to build. You’ll help shape an organization that embeds AI into its foundation as an enduring competitive advantage. - Compensation With Upside: Market-competitive salaries and generous equity packages (4-year vest, 1-year cliff) give you the security to focus on building — and the asymmetric upside of ownership in a company chasing a category-defining mission. - Comprehensive Benefits & Recharge: Health, dental, vision, and paramedical coverage for you and your family, plus 4 weeks vacation, 11 statutory holidays, and 1 volunteer day annually. We encourage at least 2 weeks off each year to fully recharge. - Tools That Keep You Ahead: A new MacBook Pro, a $500 stipend for peripherals, and the best AI tools available so you can work at the forefront of agent-native workflows. - Remote-First Flexibility: We are a remote-first team prioritizing asynchronous collaboration, with hiring focused in North and South America. Work where you’re strongest — we just want the best.

Requirements

Must-haves

We're hiring a Product Manager to own how teams evaluate Keycard, and the developer experience they meet when they do.
Expect to spend real time with the people running evaluations: watching onboarding sessions, sitting in on field-engineering walkthroughs, reading support threads, and finding out why a team went quiet mid-eval.
Own the evaluation journey end to end, from first touch through first credential exchange to a production decision, including how each stage is defined and measured.
Set the evaluation milestones and metrics that product, engineering, and go-to-market all report against.
Own the developer experience an evaluation runs on: SDK quickstarts, CLI onboarding, console setup, docs, and template repos.
Drive time-to-first-credential-exchange down, and be the voice of developer ergonomics in engineering's API and CLI design discussions.
Turn what field engineering does by hand into self-guided paths: eval guides, reference architectures, in-product guidance. Run experiments and cut the ones that don't work.
Work with DevRel and marketing on how evaluations start, and with sales and field engineering on when a self-guided eval needs a human in the room.
You've been a PM on a developer product where evaluation and adoption were your numbers (dev tools, infrastructure, API platforms, or security).
Technical enough to be credible with engineers. You can read an SDK quickstart and see where a developer would bounce, follow an API design discussion, and pull your own numbers in SQL or an analytics tool.
You have taste in developer experience. You can articulate why one CLI feels good and another doesn't, and you notice error messages, defaults, and docs structure the way a designer notices spacing.
You build with AI tools yourself and follow the agent ecosystem closely enough to have real opinions about it.
You start from instrumentation. If the data you need doesn't exist, you get it added before forming theories about where evaluations drop off.
Comfortable in a category with no playbook. Agent identity is new, and a lot of this job is deciding which questions are worth answering.
You write clearly. Much of this role's output is docs, problem statements, and experiment readouts that other people act on.
An engineering background before product; you've shipped code and understand what you're asking engineers to do.
Experience productizing a high-touch motion: turning field playbooks, POC guides, or solutions-engineering work into product.
Familiarity with identity/auth concepts (OAuth, OIDC, token exchange, delegation) or agent protocols (MCP, A2A).
Experience with growth tooling: product analytics, experimentation frameworks, lifecycle messaging.
Docs, quickstarts, or templates you shipped that developers actually used.
You'd rather ship a fix this week than present a strategy deck about it next month.
You treat quickstarts and docs as product surfaces that deserve real design attention.
You want to define the evaluation motion for a new category from scratch.
You like being early: small team, direct access to founders and customers, no layers between you and what ships.

Nice-to-haves

None flagged.

Application prep

Use the role’s language and application details while tailoring your materials.

Keywords to mirror

aigoapisql

Platform: ashby
Effort: quick

Benefits

Benefits detected in the listing.

Dental

Vision