Product Manager, Growth & Developer Experience

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate. We need to parse the posting. First part: "About Keycard" is description of company. Could be "About the role"? Actually "About the role" heading is for role description. The posting includes "The role" section describing responsibilities. Also "What you'll do" is responsibilities. "What we're looking for" is requirements/qualifications/skills. "Who will love this job" maybe not needed. "What we offer" includes benefits, compensation, etc. We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: Could be a brief description of the role (maybe from "The role" paragraph). Use that. - Responsibilities: from "What you'll do" bullet list. - Requirements: maybe from "What we're looking for" first paragraph (experience, technical enough, etc.) - Qualifications: maybe from "Strong candidates may also have" bullet list. - Skills: maybe from "What we're looking for" includes technical skills, etc. Could combine. But we must not create sections with filler. We need to ensure each section has substantive content. We can combine some: maybe we don't need all headings; only include those with content. Let's extract content. Company description: "At Keycard, we’re building identity & access infrastructure for the agent-native era..." This is about company, not role. Could be placed under "About the role"? Actually "About the role" could include role description and maybe company context. But guidelines: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role heading with a paragraph describing the role and maybe company. Responsibilities: from "What you'll do" list. Requirements: from "What we're looking for" first paragraph (You've been a PM on a developer product where evaluation and adoption were your numbers... Technical enough... You can read an SDK quickstart... You have taste... You build with AI tools... You start from instrumentation... Comfortable in a category with no playbook... You write clearly.) Qualifications: from "Strong candidates may also have" bullet list. Skills: maybe we can extract specific skills: experience with product analytics, experimentation frameworks, lifecycle messaging, familiarity with identity/auth concepts, agent protocols, SQL, etc. Could be a subsection but we might not need separate Skills if covered. Benefits: from "What we offer": Build at the Frontier, Truly Agent-Native Culture, Compensation With Upside, Comprehensive Benefits & Recharge, Tools That Keep You Ahead, Remote-First Flexibility. Also "Why Join Us?" maybe. Pay: from "Compensation With Upside": Market-competitive salaries and generous equity packages (4-year vest, 1-year cliff). Schedule: maybe remote-first flexibility indicates remote work, but not explicit schedule. Could be "Remote-First Flexibility" but schedule not given. Might not include Schedule if no specific schedule. We must not create Pay or Schedule sections unless posting actually states them. Pay is stated: "Market-competitive salaries and generous equity packages". That's pay info. So we can include Pay section. Schedule: Not explicitly stated; only remote-first flexibility but not schedule like full-time, hours. Might not include Schedule. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We need to ensure we don't repeat content. Let's craft HTML. We'll use

for each heading, then

for prose,

• for lists. We need to preserve all substantive information; do not invent or summarize away detail. Must keep details. We need to be careful not to omit details. Let's extract exact sentences. About the role: Could combine company description and role description. Company description paragraph: "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." Then role description: "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." We can combine these into About the role section. Responsibilities: from "What you'll do" list: - 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. We'll put each as
• . Requirements: from "What we're looking for" first paragraph (multiple sentences). Let's extract: "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." We'll put as

  . Qualifications: from "Strong candidates may also have" bullet list: - 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. We'll put as

  • . Skills: Could be derived from requirements and qualifications but we need a separate Skills section if we have specific skills not covered. However we might combine; but guidelines: prefer a few substantive sections over many thin ones. We already have Requirements and Qualifications; Skills might be redundant. Could omit Skills if no distinct content. But we need to decide if we include Skills. The posting mentions "Technical enough to be credible with engineers", "You can read an SDK quickstart...", "You have taste in developer experience", "You build with AI tools", "You start from instrumentation", "You write clearly", "Familiarity with identity/auth concepts", "Experience with growth tooling". Those are skills. Could put them under Skills. But we already have Requirements covering many of those. To avoid duplication, we could merge Requirements and Qualifications into one section? But headings are prescribed; we can still include Skills if we have distinct content not already covered. However we risk duplication. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we should not include Skills if it's thin. But we have enough content for Skills? Let's see: we could list specific skills: SDK quickstart analysis, API design discussion, SQL/analytics, CLI/UX taste, AI tool usage, instrumentation, data collection, writing, identity/auth concepts (OAuth, OIDC, token exchange, delegation), agent protocols (MCP, A2A), product analytics, experimentation frameworks, lifecycle messaging, shipping docs/quickstarts/templates. That's substantive. Could be a Skills section. But we already have Requirements (experience) and Qualifications (background). Skills could be separate. Let's include Skills. Benefits: from "What we offer": Build at the Frontier, Truly Agent-Native Culture, Compensation With Upside, Comprehensive Benefits & Recharge, Tools That Keep You Ahead, Remote-First Flexibility, Why Join Us? (maybe not needed). We'll need to capture details. We need to avoid duplication with Pay section. Pay section will contain compensation details. Benefits section will contain other benefits. Let's extract: 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