Recruiter

We need to output HTML fragment with sections: About the role? Actually the posting includes "About The Company", "The Role", "Responsibilities", "What You Bring", "Big Pluses", "Applicants must be currently authorized...", "Benefits", "Equal Employment Opportunities", "Compensation Range". We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content accordingly. The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. We have: - About The Company: description of company. Could be "About the company" but they said use headings like About the role, Responsibilities, etc. Not "About the company". However they gave examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list "About the company". But we could still include a section with heading maybe "About the company"? 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 suggests those are typical. However they also say "Do NOT repeat the job title as a heading (the page already shows it)". So we can include other headings as needed, but we should follow the pattern. Better to include sections: About the company (maybe as

About the company

), The Role (maybe

About the role

), Responsibilities, What You Bring (could be Requirements/Qualifications/Skills), Big Pluses (maybe Skills), Benefits, Compensation Range (Pay). Also note they said never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated, so include Benefits. Pay: compensation range is stated, so include Pay. Schedule: not mentioned (they said U.S.-based remote role, but no schedule details). So we should not include Schedule. We need to remove EEO boilerplate, application instructions, etc. Also remove duplicated lines. We need to preserve all substantive information. Let's extract substantive content: About The Company: "Kodex revolutionizes how organizations handle sensitive subpoenas and data requests from law enforcement and government agencies. Founded by a former FBI agent and backed by leading investors including Andreessen Horowitz, Y Combinator, Peak XV and Thiel Capital, Kodex has become the industry standard for secure data exchange. Our platform supports over 15,000 government agencies in 190 countries and is trusted by industry leaders like Coinbase, Stripe, and AT&T. By transforming a traditionally complex and manual process into a streamlined digital workflow, Kodex helps organizations strengthen compliance, enhance security, and reduce operational costs by millions each year. We bridge the gap between companies and authorized requestors, ensuring that sensitive data is handled with uncompromising security, transparency, and efficiency." The Role: "Kodex is hiring our second recruiter to work across the full surface area of the business. You’ll own your reqs end-to-end from day one, and report directly to our Founding Recruiter as we scale. Our search bench spans it all: threat intelligence specialists, go-to-market and customer-facing roles, and increasingly technical seats on engineering teams. This is not a coordinator role or a specialist seat — you'll run full-cycle recruiting on any roles thrown your way. This is a rare seat. Kodex created the category we work in: lawful data exchange between the public and private sectors, and the need only grows as the tech landscape shifts. The team you help hire here will be the one that defines this space. We're building with velocity: rapid product launches, expansion into new verticals, top-tier venture backing, and strong momentum. The recruiting function is high-visibility here — you'll partner with individual contributors and hiring managers across the org, and the quality of the people you help hire shows up directly in a product that has real-world impact for people who never touch it. This is a U.S.-based remote role." Responsibilities: List bullet points: - Own your roles — full-cycle recruiting from intake through offer, across a shifting mix of GTM, customer, and technical searches - Partner with hiring managers — run intake calls, define profiles, calibrate on candidates, and drive the process end-to-end - Build roles and hiring plans in Ashby — you know your way around the tool and improve how we structure searches inside it, not just in intake conversations - Source creatively — you know how to build your own pipeline. Whether that's technical, strategic, network-driven, event-driven, or AI-assisted, you have a point of view on what works. - Screen and evaluate — recruiter screens, deep-dive assessments, candidate calibration - Manage offers and close — negotiate, build the pitch, get the yes What You Bring: - 3–5 years of full-cycle recruiting. - Series A / B or high-growth startup experience — this is not the seat for a FAANG or big-co recruiter. You've operated in real ambiguity and built process where none existed. - Owner mentality — you've launched reqs from scratch, built your own pipeline, and closed candidates without a team of coordinators behind you. You take a req from zero and see it through. - Ambition — this role is demanding. You're comfortable with velocity, high context-switching, and a search mix that shifts month to month. - Proven ability to ramp on new domains — you've picked up unfamiliar technical or specialized roles before and gotten to signal fast. You lean into learning. - Sharp candidate assessment — you form clear reads quickly and can articulate them - Excellent communication — with candidates, hiring managers, and in writing. Big Pluses: - Prior agency background before going in-house - Recruiting experience in regulated or sensitive-data industries (fintech, legaltech, security, govtech) - Experience recruiting for GTM roles (Sales, Customer Success, BDR) or technical roles (engineering, security, platform) - Fluency in Ashby — you know how to build roles, workflows, and interview plans inside the tool Applicants must be currently authorized to work in the United States on a full-time basis. We are unable to sponsor or transfer employment visa sponsorship for this position. Benefits: - Remote-first within the U.S. - Offsites in exciting locations. Past trips include Seattle, Miami, Nashville, and San Francisco. - Competitive salary and meaningful equity - Unlimited Vacation plus 14 company holidays - 12 weeks of fully paid parental leave, with a flexible return-to-work policy - Comprehensive medical, dental, and vision plans - 401(k) retirement plan - Dynamic Environment — you'll help build the team at a Series A that's actively defining a new market Compensation Range: $110K - $140K EEO boilerplate to remove. We need to format using

headings and

• for lists,

  for prose. We need to decide which headings to use. Potential sections: - About the company (maybe

  About the company

  ) - About the role (maybe

  About the role

  ) – but we already have The Role description; could combine with About the company? But they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could have:

  About the role

  (contains The Role description)

  Responsibilities

  (list)

  Requirements

  (maybe combine What You Bring)

  Qualifications

  (maybe Big Pluses? Actually Big Pluses are nice-to-have, could be Skills)

  Skills

  (maybe Big Pluses)

  Benefits

  Pay

  (Compensation Range) We should not include Schedule. We need to ensure we don't create sections with filler text. All have content. We need to preserve all substantive information. So we need to include the company description somewhere. Could be under About the role? But that would mix. Perhaps we add an

  About the company

  even though not in examples; but 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 we should follow the pattern. However we could embed company description in a

  before the first heading? The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. It doesn't forbid a heading for About the company. But they gave examples of typical headings; we could still add About the company as a heading. However to be safe, we could incorporate company description into a

  under About the role heading? But that would be mixing. Better to follow the pattern: we have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We need to place company description somewhere. Could be under About the role as a brief intro? But the About the role section currently contains the role description. We could prepend company description as a paragraph before the role description within the same section? That might be okay: the section heading About the role, then a paragraph about company, then paragraph about role. But the instruction says "About the role" heading likely expects role description. However we can include company description as a separate paragraph; it's still substantive. Alternatively, we could add a heading "About the company" even if not in examples; risk of being considered extra but likely acceptable. However they said "include a section ONLY when the posting has real, specific content for it". So we can include About the company. I'll include About the company heading. Thus sections:

  About the company

  ...company description...

  About the role

  ...role description...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...
  (What You Bring)

  Skills

  • ...
  ...
  (Big Pluses)

  Benefits

  • ...
  ...

  Pay

  $110K - $140K

  We should not include Schedule. We need to remove EEO, visa sponsorship line? The visa sponsorship line is substantive: "Applicants must be currently authorized to work in the United States on a full-time basis. We are unable to sponsor or transfer employment visa sponsorship for this position." This is a requirement about work