Note: The job is a remote job and is open to candidates in USA. Keycard is building identity and access infrastructure for the agent-native era, helping developers and enterprises build secure, scalable agentic applications. The Product Manager will own the evaluation journey and developer experience across SDKs, CLI, console, documentation, and templates, using instrumentation and experimentation to improve adoption and time-to-first-credential-exchange.
Responsibilities
- 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
Skills
- 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
Benefits
- Generous equity packages with a 4-year vest and 1-year cliff
- Health, dental, vision, and paramedical coverage for you and your family
- 4 weeks vacation
- 11 statutory holidays
- 1 volunteer day annually
- Encouragement to take at least 2 weeks off each year to fully recharge
- A new MacBook Pro
- A $500 stipend for peripherals
- The best AI tools available
- Remote-first flexibility with asynchronous collaboration
- Huge autonomy and the opportunity to gain mastery
- The opportunity to work in a team that holds each other accountable to succeed
Company Overview