Senior Talent Recruiter

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Climb" then "Role Summary", "Key Responsibilities", "Required Qualifications", "Preferred Qualifications", "Who Thrives Here", "Why Climb", "What we offer". Also maybe "About Climb" is not a section heading per rules: we can use

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

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings? It says e.g., meaning examples. Probably we should use those headings where appropriate. We have content for About the role (maybe Role Summary), Responsibilities (Key Responsibilities), Requirements (Required Qualifications), Qualifications (Preferred Qualifications maybe?), Skills (maybe not explicit), Benefits (What we offer), Pay (maybe not explicit but we have Competitive base salary with performance-based bonuses), Schedule (maybe remote-first work environment). We need to include a section only when posting has real, specific content for it. So we need to decide which sections to include. We have: - About the role: Role Summary paragraph. - Responsibilities: Key Responsibilities bullet list. - Requirements: Required Qualifications bullet list. - Qualifications: Preferred Qualifications bullet list. - Skills: maybe not separate; could combine with qualifications? But we could omit Skills if no explicit skills list. - Benefits: What we offer bullet list (competitive base salary, MacBook, health insurance, 401k, holidays, PTO, remote-first, professional dev budget, spot bonuses, conference attendance, collaborative culture, access to leadership, opportunity to shape practice). Also maybe "Competitive base salary with performance-based bonuses" could be Pay. - Pay: Could extract salary info: "Competitive base salary with performance-based bonuses". That's specific enough? It's not a number but it's mention. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Competitive base salary with performance-based bonuses" is not filler; it's a statement. So we can include Pay section with that sentence. - Schedule: "Generous holidays, flexible PTO, and remote-first work environment" could be Schedule? Actually schedule is about work hours/remote. Could include remote-first work environment. Might be okay. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO statement at end should be removed. We must not include application instructions. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details from each bullet. We need to format lists with

• . For prose use

  . We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

  About the role

  ... role summary ...

  Responsibilities

  • Own full-cycle recruiting: sourcing, outreach, screening, interview loop coordination, offer negotiation, and keeping candidates warm through start date.
  ...
  Similarly for Requirements (Required Qualifications), Qualifications (Preferred Qualifications), Benefits (What we offer), Pay, Schedule. We need to ensure we don't create sections with filler. All have content. Let's extract details. About Climb paragraph: "About Climb Climb is a Data and AI consultancy that partners with enterprises to design, build, and operationalize modern data platforms and production AI systems. As a Databricks partner, we go deep on lakehouse architecture, machine learning, and applied AI, with a bias toward production over proof of concept. Our team brings deep technical expertise and a builder's mindset to every engagement, and we measure our work not just by what ships, but by the business impact it drives." But the instruction: "About the role" heading maybe should contain role summary not about company? However they gave example headings; we can use About the role for role summary. The "About Climb" could be considered company description; maybe we could include it under About the role or maybe we could add a separate section like "About Climb" but not in allowed headings. Safer to incorporate it into About the role paragraph? The role summary already includes some description of role; we could prepend the About Climb description to that paragraph. That preserves all info. Thus About the role paragraph: combine About Climb and Role Summary. Let's craft: "Climb is a Data and AI consultancy that partners with enterprises to design, build, and operationalize modern data platforms and production AI systems. As a Databricks partner, we go deep on lakehouse architecture, machine learning, and applied AI, with a bias toward production over proof of concept. Our team brings deep technical expertise and a builder's mindset to every engagement, and we measure our work not just by what ships, but by the business impact it drives. The Senior Talent Recruiter owns how Climb hires. You run full-cycle recruiting for a firm whose entire product is the caliber of its people: sourcing, screening, closing, and everything in between, for Forward Deployed Engineers, Data Engineers, Architects, and the leaders who run them. This is a closer's seat, not a coordinator's. The hard part of our hiring is not finding resumes. It is holding a senior engineer's attention through a process, understanding the technical work well enough to be credible about it, and being the reason they take our offer instead of the other one. You will work a small number of hard, specific reqs rather than a wide, shallow funnel. You are the first dedicated Talent hire at Climb. You inherit a published leveling ladder, defined comp bands, and written job descriptions, and you own the process that runs on top of them." That seems comprehensive. Now Responsibilities: list each bullet from Key Responsibilities. Key Responsibilities bullet list: - Own full-cycle recruiting: sourcing, outreach, screening, interview loop coordination, offer negotiation, and keeping candidates warm through start date. - Recruit against a credential-gated market: senior data and AI engineers, Databricks practitioners, and client-facing consultants who are usually employed and not looking. - Build and maintain a real pipeline rather than working req to req, so the practice can hire on demand instead of starting cold each time. - Run our applicant tracking system (Ashby) as a system of record: clean data, accurate stages, and reporting leadership can act on. - Partner with hiring managers to define the need, calibrate candidates against the level framework, and hold the bar when a search gets long. - Own the candidate experience end to end; every candidate, hired or not, should come away with a high opinion of Climb. - Assess candidates against published leveling criteria and flag when a candidate does not map cleanly to a level rather than stretching a title to fit. - Build the employer brand in the market: referral networks, community presence, and outbound that sounds like a person rather than a template. - Report on the funnel that matters: time to fill, offer acceptance, source of hire, and pipeline coverage against the hiring plan. - Manage recruiting tooling and external agency relationships where we use them, including cost and performance. Now Requirements (Required Qualifications) bullet list: - 5+ years of full-cycle technical recruiting, with meaningful time in an in-house or embedded seat rather than agency only. - Demonstrated ability to close senior technical candidates: specific examples of hires you personally sourced, ran, and landed. - Enough technical fluency to hold a credible conversation about data engineering, cloud platforms, and AI systems, and ability to differentiate strong engineers and architects. - Proven sourcing ability against passive, hard-to-reach candidate pools, not reliance on inbound applicants or job board volume. - Hands-on ownership of an applicant tracking system and the discipline to keep its data clean. - Comfort operating without a recruiting team around you: you set the process, you run it, and you are accountable for the outcome. - Clear, direct communication with hiring managers and executives, including the willingness to push back when a req or a level is wrong. Preferred Qualifications bullet list: - Experience recruiting for a consultancy, systems integrator, or professional services firm, where candidates must be both technical and client-facing with requisite soft skills and aptitude for consulting. - Experience hiring into the data and AI ecosystem (Databricks, Snowflake, or comparable credential-gated platforms). - Experience with Ashby, or strong fluency in a comparable modern ATS. - Experience building a recruiting function from an early stage rather than inheriting a mature one. - Familiarity with leveling frameworks, compensation bands, and offer governance. - Experience using AI-assisted tooling in sourcing and screening workflows. Who Thrives Here paragraph: we could maybe treat as a section like "Who thrives here" but not in allowed headings. Could incorporate into About the role? Might be better to create a section "Who thrives here" but not in allowed list; risk of violating instruction? 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 those for section headings. It might be okay to use other headings if needed, but better to stick to those. However we have substantive content for "Who Thrives Here" and "Why Climb" and "What we offer". We can map: - Who Thrives Here could go under "Skills"? Not really. Could be part of About the role? Might be okay to add a section "Who thrives here" as

  but not in list; risk. Perhaps we can treat it as part of About the role or as a separate section "About the role" already used. Better to incorporate into About the role? But that would be lengthy. Alternatively we could create sections: "Why Climb" and "What we offer" map to Benefits and maybe Pay/Schedule. "Who Thrives Here" could be considered "Skills"? Not exactly. Could be omitted? But we must preserve ALL substantive information. So we need to include it somewhere. We could create a section

  Who thrives here

  even if not in the example list; the instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say you cannot use other headings, just that you should use

  for section headings. So using

  for any section heading is fine. The examples are just examples. So we can use headings like "Who thrives here", "Why Climb", "What we offer". That seems acceptable. Thus we will have sections: - About the role - Responsibilities - Requirements - Qualifications - Who thrives here - Why Climb - What we offer (Benefits) - Pay - Schedule We also might need Skills section? Not present; we can omit. Now extract content for each. Who Thrives Here paragraph: "This role is designed for a recruiter who wants to own a function, not work a req queue. You are a closer. You know the difference between a candidate who is interested and a candidate who is going to sign. You would rather run six hard searches well than thirty easy ones. You tell a hiring manager the truth about their req, their process, or their band when it is the reason the search is stuck. You treat candidate experience as a reflection of the firm, including for the people you turn down." Why Climb paragraph(s): "Ground floor, real backing. You are joining early, with founders who have built and exited firms like this before. You help write the playbook rather than inherit one. Own the function. You are the first dedicated Talent hire. You set the process, choose the tooling, partner with hiring managers, and shape how Climb