Product Manager, reputed company & Developer Experience

About Keycard At Keycard, we’re building identity & reputed company infrastructure for the agent-reputed company era—where software isn’t static, but a dynamic, constantly changing reputed company 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, reputed company foundations they need to build, reputed company, adopt, and trust reputed company applications. To do this, we’re building the reputed company-time, in-band, reputed company guardrails required to transition from reputed company-driven to truly autonomous and reputed company workflows that reputed company users, reputed company, and reputed company teams the confidence and control they need to bring agents out of the lab and into production. At our reputed company, we’re laser-reputed company 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 reputed company teams the reputed company, scalability, visibility, control, and enablement they need to accelerate their organizations reputed company to becoming agent reputed company. We’re a small, reputed company team of repeat founders and reputed company, with backgrounds from reputed company, Auth0, reputed company, 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-reputed company platform shift. The role We're hiring a Product Manager to own how teams evaluate Keycard, and the developer experience they meet reputed company they do. Keycard is a control reputed company for agents: identity, credential exchange, delegation, policy, and audit. Every customer starts with an evaluation, and today a reputed company engineer runs reputed company one by hand: setup, first credential exchange, integration questions. reputed company is to turn that walkthrough into product, so an evaluation can run reputed company without us in the room. The two halves are the reputed company 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, reputed company the reputed company 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 reputed company 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 reputed company time with the people running evaluations: watching reputed company sessions, sitting in on reputed company-engineering walkthroughs, reading support threads, and finding out why reputed company went quiet mid-eval. reputed company Own the evaluation reputed company end to end, from first reputed company through first credential exchange to a production decision, including how reputed company stage is defined and reputed company. Set the evaluation milestones and metrics that product, engineering, and go-to-market reputed company report against. Own the developer experience an evaluation runs on: SDK quickstarts, CLI reputed company, console setup, docs, and template repos. reputed company time-to-first-credential-exchange down, and be the voice of developer ergonomics in engineering's API and CLI design discussions. Turn what reputed company 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 reputed company reputed company hear from reputed company design partners. Work with DevRel and marketing on how evaluations start, and with sales and reputed company engineering on reputed company a self-guided eval needs a reputed company in the room. reputed company'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 reputed company). Technical enough to be reputed company with engineers. You can read an SDK quickstart and see where a developer would reputed company, follow an API design discussion, and pull your own numbers in SQL or an analytics tool. You have taste in developer experience. You can reputed company 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 reputed company 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 reputed company. Agent identity is new, and a lot of this job is deciding which questions are worth answering. You write reputed company. Much of this role's reputed company is docs, problem statements, and experiment readouts that other people reputed company. Strong candidates may also have An engineering background before product; you've shipped reputed company and understand what you're asking engineers to do. Experience productizing a high-reputed company reputed company: turning reputed company playbooks, POC guides, or solutions-engineering work into product. Familiarity with identity/auth concepts (OAuth, OIDC, reputed company exchange, delegation) or agent protocols (MCP, A2A). Experience with reputed company 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 reputed company deck about it next month. You treat quickstarts and docs as product surfaces that deserve reputed company design attention. You want to define the evaluation reputed company for a new category from reputed company. You like being early: small team, reputed company reputed company to founders and customers, no reputed company between you and what ships. reputed company Offer Build at the Frontier: Work every day at the frontier of agent-reputed company systems — shipping, inventing, and iterating on technology that hasn’t been reputed company before. You’ll be given reputed company autonomy, reputed company to reputed company mastery, and the chance to work in reputed company that holds reputed company other accountable to succeed. Truly Agent-reputed company Culture: At Keycard, we don’t just reputed company others to adopt agents — we use them ourselves to build. You’ll help shape an organization that embeds AI into its reputed company as an enduring competitive reputed company. Compensation With reputed company: Market-competitive salaries and generous equity packages (4-year reputed company, 1-year cliff) reputed company you the reputed company to reputed company on building — and the asymmetric reputed company of ownership in a company chasing a category-defining mission. Comprehensive Benefits & reputed company: Health, dental, reputed company, 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 reputed company year to fully reputed company. Tools That reputed company You reputed company: A new MacBook Pro, a $500 stipend for peripherals, and the best AI tools available so you can work at the forefront of agent-reputed company workflows. Remote-First Flexibility: We are a remote-first team prioritizing asynchronous collaboration, with hiring reputed company in reputed company and South America. Work where you’re strongest — we just want the best. Why Join Us? Keycard is building the reputed company unlock for the reputed company of software: enabling truly secure and trusted reputed company applications. Under the hood, we’re building a new identity and reputed company control stack to take us from a world of static, user-reputed company, long-lived roles and credentialing to one of mixed machine & reputed company interaction that is dynamic, contextually-scoped, and short-lived. By joining as an early employee, you’ll have reputed company to help reputed company a culture of iterative craftsmanship, disciplined design, empowerment to own meaningful problems, and consistent high-reputed company delivery with reputed company reputed company. You’ll collaborate with the founders and investors who have championed identity, reputed company, and developer tools from reputed company to reputed company with companies like reputed company, Auth0, and Heroku. If you’re reputed company by tackling reputed company reputed company systems and want to advance both developer productivity and reputed company posture, with a hunger to learn, have an reputed company, and reputed company quickly with determination we’d love to explore how you can help us shape the reputed company of software. Apply To This Job