Lead Technical Recruiter

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or About you?), Benefits, Pay, Schedule? The posting includes Base Salary: $180k–$220k* (Pay). Location: New York, NY (Hybrid) (Schedule? maybe schedule not given). Benefits listed: Competitive salary, equity, 401(k), excellent benefits: 100% covered medical, vision, dental, etc., PTO 20 days, global offsites, stipends, continuing education credits. Also mention "What you'll get:" includes benefits. We must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if real specific content. We have About the role content: description of role, location, base salary? Actually base salary is Pay. So About the role should include description of role and maybe location? The location is part of role but could be in About the role. We'll include location in About the role paragraph. Responsibilities: list bullet points. Requirements: we have "About you:" list of required qualifications. Could treat as Requirements. Also "As a plus:" could be Qualifications or Skills? We'll treat "About you:" as Requirements (mandatory). "As a plus:" could be Qualifications or Skills; but we can put as Qualifications (preferred). Or we could have Skills section for technical skills like fluent in Greenhouse etc. But we can keep simple: Requirements (mandatory), Qualifications (preferred). Benefits: list benefits. Pay: base salary range. Schedule: maybe hybrid location indicates schedule? Not explicit schedule like full-time, etc. Not given. So we should not create Schedule section unless posting actually states them. It does not state schedule explicitly besides Hybrid (location). That's not schedule. So omit Schedule. We must not include boilerplate like EEO etc. Not present. We must preserve all substantive information. Do not invent or summarize away detail. Must not include placeholder like "commensurate with experience". The posting includes "Competitive salary (based on experience level)" which is vague but it's actual content. We can include that in Benefits or Pay? It's under What you'll get. We'll keep as part of Benefits maybe. But we also have Pay section with base salary range. The "Competitive salary (based on experience level)" is redundant with base salary range; but we should keep it as part of Benefits? Actually it's under What you'll get: Competitive salary (based on experience level). Significant equity options package. etc. We'll keep that as part of Benefits list. We must not include duplicated lines. Ensure we capture all bullet points. Let's extract: About Kalepa: (intro) but we might not need to include as it's not a section heading; but we must preserve all substantive information. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include the About Kalepa paragraph somewhere. Since we cannot add arbitrary headings not listed, we could include it as a

before the first heading? The instruction says use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other

content outside sections. So we can include a

for About Kalepa intro. Then headings for sections. Thus output:

About Kalepa: ...

then

About the role

with paragraph(s). Then

Responsibilities

with

. Then

Requirements

with
. Then

Qualifications

(for "As a plus:") with
. Then

Benefits

with
. Then

Pay

with

(maybe include base salary range). Also include location hybrid maybe in About the role paragraph. Check for duplication: The About the role paragraph includes "Base Salary: $180k–$220k*" and "Location: New York, NY (Hybrid)". But we said we will put Pay separate. However the About the role paragraph currently includes base salary and location. If we move base salary to Pay, we should not duplicate. So we need to decide: either keep base salary in About the role and not have Pay section, or move base salary to Pay and remove from About the role. The instruction: "include a section ONLY when the posting has real, specific content for it". Pay section: we have base salary range, so we should have Pay section. Then we should not duplicate base salary in About the role. So we should edit About the role paragraph to exclude base salary and location? Location could be part of About the role or maybe we could include location in About the role as it's not Pay or Schedule. The location is not covered by other headings. So we keep location in About the role. Thus About the role paragraph: "Kalepa is seeking a Lead Technical Recruiter to build the engine behind our next stage of growth. You will own full-cycle recruiting for Engineering, Product, and Design functions and shape the processes, tools, and brand that will define how Kalepa hires for years to come. Location: New York, NY (Hybrid)." That captures role description and location. Now Pay section: base salary range $180k–$220k* plus note about estimate varying etc. Also note "The salary range listed is an estimate and will vary based on a variety of factors. Final compensation will be determined during the offer stage based on relevant experience, performance during the interview process, and geographic location, and may therefore differ from the posted range." We'll include that as paragraph. Benefits: list from "What you'll get:" plus maybe other benefits mentioned earlier: "Excellent benefits: 100% covered medical, 100% covered vision and dental, and others." Also "20 days of PTO a year." "Global team offsites (2023 - Buenos Aires, 2024 - Lisbon, 2025 - Cartagena)" "Healthy living/gym stipend. Mobile phone bill stipend. Continuing education credits." Also "Significant equity options package." "401(k) plan with employer contribution (regardless of employee contribution)". Also "Competitive salary (based on experience level)" maybe duplicate with Pay but it's under benefits; we could include but might be redundant. However we should preserve all substantive information; we can include it but note it's about salary; but we already have Pay section. Might be okay to include as part of Benefits but could be considered duplication. The instruction: "Do NOT repeat the job title as a heading ... Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." It doesn't forbid duplicative content across sections, but better to avoid redundancy. However we must preserve all substantive information; if we omit "Competitive salary (based on experience level)" we might be losing info that is already covered by Pay section but it's still substantive. Since Pay section already covers salary range, we could consider this as redundant and maybe drop it. But to be safe, we could include it in Benefits as a bullet point, but it's about salary; might be okay. However the instruction says "Prefer a few substantive sections over many thin ones." Having both Pay and Benefits with salary might be thin. I'd include salary only in Pay section and not duplicate in Benefits. The "Competitive salary (based on experience level)" is essentially same as Pay; we can omit it as it's covered. The rest of benefits we keep. Now Requirements: from "About you:" list: - 5+ years of full life-cycle technical recruiting experience. - Track record hiring backend, infrastructure, full-stack, or ML/AI engineers. - Experience partnering directly with engineering leaders on intake and closing. - A strong, independent sourcer, not just an inbound processor. - Fluent in Greenhouse (or a comparable ATS) and modern sourcing tools such as Juicebox, Metaview, and Seekout. - Comfortable owning a full requisition load with minimal oversight. - Creative and energized by experimenting with new tools to identify and engage the highest quality engineers. - Able to critique your own work and be transparent in what's working and what's not. - Experience with nurturing pipelines over time and maintaining relationships with candidates beyond the first interaction. Qualifications (As a plus): - Experience recruiting for AI/ML or LLM-focused roles. - Experience building a recruiting function from an early stage. - Insurtech, fintech, or other regulated B2B SaaS recruiting experience. Now Responsibilities list: - Own full-cycle recruiting for Engineering roles: intake, sourcing, interviews, offer, and close. - Run intake with hiring managers to turn open roles into clear scorecards and search strategies. - Source and build pipelines for passive, hard-to-find technical and AI/ML talent. - Bring market and comp intelligence into hiring plans, and lead offer negotiation and closing. - Build and improve our interview process: kits, scorecards, structured debriefs. - Act as a strategic partner to company leaders and hiring managers, followed by strong execution, ensuring that all hiring goals are met in a timely manner with top-tier candidates. - Strengthen Kalepa's employer brand in the engineering and AI community. Now Benefits list: - Significant equity options package. - 401(k) plan with employer contribution (regardless of employee contribution). - Excellent benefits: 100% covered medical, 100% covered vision and dental, and others. - 20 days of PTO a year. - Global team offsites (2023 - Buenos Aires, 2024 - Lisbon, 2025 - Cartagena). - Healthy living/gym stipend. - Mobile phone bill stipend. - Continuing education credits. - Work with an ambitious, smart, global, and fun team to transform a $7T global industry. (maybe include as benefit) But that last sentence is more about work environment; could be included as benefit. We'll include as bullet. Now Pay section: base salary range $180k–$220k* and note about estimate. We'll output as

Base Salary: $180k–$220k*. The salary range listed is an estimate and will vary based on a variety of factors. Final compensation will be determined during the offer stage based on relevant experience, performance during the interview process, and geographic location, and may therefore differ from the posted range.

Now About Kalepa intro paragraph: include as

About Kalepa: Insurance is a $7T global industry built on professional labor: underwriting, claims, pricing, operations, and distribution. Kalepa is building AI that can perform that work. We create professional-grade AI systems for insurers: software that can read, reason, decide, and act inside real workflows and operate over long-time horizons. Kalepa begins by augmenting professionals with the tools to succeed at their jobs. That earns us the right to learn from real decisions, capture decision traces, and automate what can be automated successfully over time. Our products are already in production with leading insurers, driving measurable outcomes and expanding across functions. The opportunity is far broader than any single workflow: to build the AI operating system for decision-making across insurance. For people who want to work on AI that matters, in a sector where correctness, trust, and real-world impact count, Kalepa is just getting started. Kalepa is backed by leading investors such as IA Ventures and Inspired Capital, and our team brings experience from Facebook, Palantir, Google, Amazon, McKinsey, Mastercard, and Uber. Our Values (This is important): Many organizations have a dusty list of corporate values that no one ever follows. Kalepa is not one of those companies. Our values are designed to unlock the potential of our employees. Success at