About the role
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.
What You'll do We're hiring a software engineer to build the surfaces where agents and humans interact with Keycard: the console, the CLI, the APIs, and whatever new interaction patterns emerge as agents become first-class users of developer platforms. Agents won't on-board to Keycard by clicking through web interfaces alone. They'll use CLIs, APIs, and machine-readable configuration. The web console is still a large part of this role — humans need to set policy, investigate events, and understand what their agents are doing — but it's not the only interface. You'll work on the primary customer-facing team, building across the full stack. Some days that's React. Other days it's CLI commands or API ergonomics for agent onboarding. You care about how things feel to use, whether the user is a person or a program.