SDR

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: About Keycard (company description), What You'll Build (responsibilities), What You Bring (requirements/qualifications), What we offer (benefits, compensation, etc). Also maybe "Why Join Us?" could be part of About the role? But we need to follow rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content to appropriate headings. We must not repeat job title as heading (not present). No Job ID etc. We must include a section only when posting has real specific content for it. So we need sections: About the role? The posting includes "About Keycard" which is company overview, not exactly role. Could treat as "About the role"? But maybe better to use "About the role" heading for description of role? However the posting has "What You'll Build" which is responsibilities. "What You Bring" is qualifications/requirements. "What we offer" includes compensation, benefits, etc. "Why Join Us?" could be more about company culture, maybe part of About the role or separate but we can include as "About the role"? Actually "Why Join Us?" is more about motivations, could be part of "About the role" or separate "Why Join Us?" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to use. We need to map content. We have responsibilities: "What You'll Build" includes bullet points (though not bullet list but sentences). We'll turn into

• . Requirements/Qualifications: "What You Bring" includes bullet-like sentences. Benefits/Pay: "What we offer" includes compensation, benefits, tools, remote flexibility. So we can have Benefits section (health, dental, vision, paramedical, vacation, holidays, volunteer day). Pay section: "Compensation With Upside: Market-competitive salaries and generous equity packages (4-year vest, 1-year cliff)". Also maybe "Tools That Keep You Ahead" could be part of Benefits or separate but we can include under Benefits as tools. Or we could have a separate "Benefits" covering health, vacation, etc, and "Pay" covering salary/equity. Also "Remote-First Flexibility" could be under Benefits or Schedule? Schedule not specified. So we may not include Schedule heading because no specific schedule info. We also have "Why Join Us?" which is more motivational; could be part of About the role or maybe we can omit if not fitting headings. But we need to preserve ALL substantive information; we cannot drop it. So we need to include that content somewhere. Could put under "About the role" heading as a paragraph describing why join. Or we could create a separate heading not in list? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. But we could still use other headings if needed? Safer to stick to those. We can incorporate "Why Join Us?" content under "About the role" or maybe under "Benefits"? Probably under "About the role" as it's about the role and company. Thus sections:

  About the role

  - include company description (About Keycard) and Why Join Us? maybe combined.

  Responsibilities

  - What You'll Build.

  Requirements

  - What You Bring (0-1+ years experience, curiosity, writing, resilience, founder-stage instincts). Also maybe "Extra Signal" could be under Requirements or Skills. Could treat as "Skills". But we have Skills heading allowed. Could put extra signal under Skills. Thus:

  Skills

  - Extra Signal: Experience selling into developers, security, cloud infrastructure, or AI platforms. Comfort using AI tools and automation to research and prospect at scale.

  Benefits

  - Comprehensive Benefits & Recharge: health, dental, vision, paramedical coverage, 4 weeks vacation, 11 statutory holidays, 1 volunteer day, encourage at least 2 weeks off each year.

  Pay

  - Compensation With Upside: Market-competitive salaries and generous equity packages (4-year vest, 1-year cliff). Also Tools That Keep You Ahead: new MacBook Pro, $500 stipend for peripherals, best AI tools. Remote-First Flexibility: remote-first team, hiring focused in North and South America. We need to ensure we don't include filler like "commensurate with experience". Not present. We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We must not repeat job title as heading. Not present. We must not put Job ID/requisition numbers as headings. Not present. We must preserve ALL substantive information. Let's capture all: From About Keycard: paragraphs about mission, building identity & access infrastructure for agent-native era, mission to unlock agent economy, building real-time guardrails, delivering delightful developer experience, small distributed team of repeat founders, backgrounds from Snyk, Auth0, HashiCorp, Heroku, joining means helping define technology and culture, once-in-a-generation platform shift. From What You'll Build: Generate qualified pipeline with developers, platform teams, security leaders bringing agents into production. Research accounts deeply and find signals that show a team is ready for agent-native identity. Write sharp, personal outreach across email, LinkedIn, phone, community channels that makes a new category make sense. Work closely with AEs, SEs, marketing, founders to turn events, content, product-led interest into real conversations. Test, measure, document what works, leave behind a playbook the next ten SDRs can run. From What You Bring: 0-1+ years of outbound or sales development experience, ideally selling technical B2B software. The curiosity to learn how identity, security, and AI agents work well enough to hold a credible conversation with an engineer. Excellent writing, resilience, and the discipline to hit activity and pipeline goals every week. Founder-stage instincts: resourceful, low-ego, coachable, eager to grow into a closing role. Extra Signal: Experience selling into developers, security, cloud infrastructure, or AI platforms. Comfort using AI tools and automation to research and prospect at scale. What we offer: Build at the Frontier: Work every day at the frontier of agent-native systems — shipping, inventing, iterating on technology that hasn’t been built before. You’ll be given huge autonomy, opportunity to gain mastery, 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. We encourage at least 2 weeks off each year to fully recharge. Tools That Keep You Ahead: A new MacBook Pro, a $500 stipend for peripherals, and the best AI tools available so you can work at the forefront of agent-native workflows. Remote-First Flexibility: We are a remote-first team prioritizing asynchronous collaboration, with hiring focused in North and South America. Work where you’re strongest — we just want the best. Why Join Us?: Keycard is building the fundamental unlock for the next generation of software: enabling truly secure and trusted agentic applications. Under the hood, we’re building a new identity and access control stack to take us from a world of static, user-focused, long-lived roles and credentialing to one of mixed machine & human interaction that is dynamic, contextually-scoped, and short-lived. By joining as an early employee, you’ll have the opportunity to help curate a culture of iterative craftsmanship, disciplined design, empowerment to own meaningful problems, and consistent high-quality delivery with real impact. You’ll collaborate with the founders and investors who have championed identity, security, and developer tools from seed to scale with companies like Snyk, Auth0, and Heroku. If you’re energized by tackling complex distributed systems and want to advance both developer productivity and security posture, with a hunger to learn, have an impact, and move quickly with determination we’d love to explore how you can help us shape the future of software. We need to include all that. Now produce HTML fragment. We'll structure:

  About the role

  About Keycard paragraph + Why Join Us? paragraphs combined maybe two

  elements.

  Responsibilities

  • ... each bullet.

  Requirements

  • ... each bullet.

  Skills

  • ... each bullet.

  Benefits

  • ... each bullet.

  Pay

  • ... each bullet.
  We must not include empty sections. Let's craft content. About the role: combine About Keycard and Why Join Us? maybe two paragraphs. Paragraph1: 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." Paragraph2: Why Join Us? content: "Keycard is building the fundamental unlock for the next generation of software: enabling truly secure and trusted agentic applications. Under the hood, we’re building a new identity and access control stack to take us from a world of static, user-focused, long-lived roles and credentialing to one of mixed machine & human interaction that is dynamic, contextually-scoped, and short-lived. By joining as an early employee, you’ll have the opportunity to help curate a culture of iterative craftsmanship, disciplined design, empowerment to own meaningful problems, and consistent high-quality delivery with real impact. You’ll collaborate with the founders and investors who have championed identity, security, and developer tools from seed to scale with companies like Snyk, Auth0, and Heroku. If you’re energized by tackling complex distributed