Product Manager, Growth & Developer Experience

About Keycard At Keycard , we’re building identity & 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 to complete dynamic tasks at runtime. Our mission is to unlock the agent economy by empowering developers and enterprises with the secure, scalable foundations they need to build, deploy, adopt, and trust agentic applications . To do this, we’re building the real-time, in-band, contextual guardrails required to transition from human-driven to truly autonomous and agentic workflows that give users, builders, and security teams the confidence and control they need to bring agents out of the lab and into production. At our core, we’re laser-focused on delivering a delightful, best-in-class developer experience that gives them the tools they need to create category-defining applications and experiences while giving platform and security teams the security, scalability, visibility, control, and enablement they need to accelerate their organizations journey to becoming agent native. We’re a small, distributed team of repeat founders and builders, with backgrounds from Snyk , Auth0 , HashiCorp , and Heroku . Joining Keycard now means helping define not just our technology, but also the culture and company we’re building together—during a once-in-a-generation platform shift. 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. The two halves are the same problem. An evaluator forms their opinion of Keycard through the SDK, the CLI, the console, and the docs. If the first keycard run takes an afternoon of fighting config, no eval guide saves it. So you own the developer experience those evaluations run on, and time-to-first-credential-exchange is a number you personally care about.

The job is mostly shipping. 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. - Get what evaluators are telling us into the roadmap alongside what we hear from enterprise design partners. - 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.