Senior Technical Recruiter

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include boilerplate like EEO, legal, scam warning, etc. Must preserve all substantive info. Must not invent or summarize away detail. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes: "This position follows the Company’s hybrid schedule which currently requires employees to work in the office at one of the following locations a minimum of three days per week: Durham, NC or Emeryville, CA." So schedule info present. Pay: "The annual base salary range for this full-time position is $70,000 to $215,000." Also mentions equity awards and generous benefits package. Benefits: list of benefits: medical, dental and vision plan, family planning benefits, health savings account, flexible spending account, transportation savings account, 401(k) retirement savings plan with company match, life, accident and disability coverage, business travel accident insurance, employee assistance programs, disability insurance, and other well-being benefits. Also volunteer time off (VTO) 5 days. So Benefits section should include that. We need sections: About the role (maybe intro paragraph). Responsibilities (list of duties). Requirements (maybe "We’re Looking For Someone With ..."). Qualifications (maybe overlapping with requirements? The instruction says use sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills. We need to decide what content goes where. The posting includes: "What You’ll Do" list (responsibilities). "We’re Looking For Someone With" list (requirements/qualifications). Also "About Tanium" description (company overview) maybe not needed? Could be part of About the role? Probably not. The "About Tanium" is company description, not role-specific. Could be omitted? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep company description? It's substantive but not about role. However sections are limited to those headings; we could put company description under About the role? Might be okay. But "About the role" heading expects role description. The intro paragraph before "What You’ll Do" describes the role: "As our Senior Technical Recruiter, you'll own full-cycle recruiting..." That's about the role. So we can put that in About the role. Responsibilities: the bullet list under "What You’ll Do". Requirements: maybe the "We’re Looking For Someone With" list. Qualifications: maybe overlapping but we could split: Requirements = hard requirements (5+ years experience etc). Qualifications = preferred (7+ years, agency experience, etc). Skills: maybe sourcing skills, data-driven, communication, etc. But we can also combine. The instruction: Prefer a few substantive sections over many thin ones. So we might not need all sections; we can include only those with real content. Let's see what we have: - About the role: intro paragraph. - Responsibilities: bullet list under "What You’ll Do". - Requirements: "We’re Looking For Someone With" list (includes 5+ years experience, agency/in-house experience a plus, enterprise software recruiting experience preferred, thrives in fast-paced, strong sourcing skills, learning agility, track record advising senior stakeholders, comfort with autonomy, data-driven approach, experience with Greenhouse, comfort with AI-enabled tools, excellent communication). - Qualifications: maybe we could treat the same as Requirements; but to avoid thin sections, we could combine Requirements and Qualifications into one section? But headings are separate; we could omit Qualifications if not distinct. However we have "Preferred" items (7+ years preferred, agency and in-house experience a plus, enterprise software recruiting experience preferred). Those could be Qualifications. So we can split: Requirements = required (5+ years full-cycle technical recruiting experience). Qualifications = preferred items (7+ years preferred, agency/in-house experience a plus, enterprise software recruiting experience preferred, etc). Skills: maybe sourcing skills, learning agility, advising stakeholders, data-driven, communication. But those are already in the list. Could make Skills section for those soft skills. But we must not create sections with filler. If we split too thin, might be considered thin. However each will have substantive content. Let's decide sections: - About the role: intro paragraph. - Responsibilities: bullet list of duties. - Requirements: required experience (5+ years full-cycle technical recruiting). - Qualifications: preferred experience (7+ years preferred, agency/in-house experience a plus, enterprise software recruiting experience preferred). - Skills: sourcing skills, learning agility, advising senior stakeholders, comfort with autonomy, data-driven approach, experience with Greenhouse, comfort with AI-enabled tools, excellent written/verbal communication. - Benefits: list of benefits + VTO. - Pay: salary range. - Schedule: hybrid schedule requirement. We must not include boilerplate like EEO, legal, scam warning, accommodations, privacy policy, etc. Also remove duplicated lines. Also remove "About Tanium" company description? It's substantive but not role-specific; but we could include it under About the role? Might be okay but could be considered not about role. However instruction: preserve ALL substantive information. If we omit it, we lose substantive info about company. But maybe it's okay to omit because not required for role? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That suggests we should keep all info from posting, not just role-specific. So we need to include company description somewhere. Could add a section "About Tanium" but not in allowed headings. The allowed headings are limited to those list; we cannot add other headings. So we must fit it into one of those sections. Perhaps we can put it under About the role as a brief company overview. That would be acceptable. Thus About the role will contain both role description and company overview. Now we must ensure we don't include filler like "commensurate with experience". Not present. Now produce HTML fragment: use

for each section heading. Use

• for lists. Use

  for prose. We must not include or . Just output the fragment. Let's craft. About the role:

  As our Senior Technical Recruiter, you'll own full-cycle recruiting for some of our most competitive, highest-impact technical roles - backed by a best-in-class, AI-enabled stack (recruiting tools like Noon.AI and BrightHire, plus enterprise AI like Claude for everyday work) built to strip out busywork so you can spend your time on judgment calls, not admin. This role covers a variety of technical requisitions rather than one narrow lane, so it rewards curiosity and learning agility over deep specialization in any single domain. Our environment moves fast and priorities shift often. If that kind of ambiguity energizes you, you'll get broad exposure across teams and real room to build influence quickly. This position follows the Company’s hybrid schedule which currently requires employees to work in the office at one of the following locations a minimum of three days per week: Durham, NC or Emeryville, CA.

  But schedule is also its own section; we might move schedule info to Schedule section. However About the role currently includes schedule sentence; maybe better to keep schedule separate and remove from About the role. But we need to preserve all info; we can keep schedule in Schedule section and not duplicate. So About the role will not include schedule sentence. Let's adjust. About the role:

  As our Senior Technical Recruiter, you'll own full-cycle recruiting for some of our most competitive, highest-impact technical roles - backed by a best-in-class, AI-enabled stack (recruiting tools like Noon.AI and BrightHire, plus enterprise AI like Claude for everyday work) built to strip out busywork so you can spend your time on judgment calls, not admin. This role covers a variety of technical requisitions rather than one narrow lane, so it rewards curiosity and learning agility over deep specialization in any single domain. Our environment moves fast and priorities shift often. If that kind of ambiguity energizes you, you'll get broad exposure across teams and real room to build influence quickly.

  Now Responsibilities: list from "What You’ll Do". We'll convert each line to
• . Responsibilities list: - Own full-cycle recruiting (from intake through offer and close) across a variety of technical roles (engineering, product, AI research, IT, etc.) - Build and execute proactive sourcing strategies that go beyond inbound applicants: passive-candidate outreach, talent mapping, and creative channels for hard-to-find technical talent - Partner with hiring managers and TA leadership as a strategic advisor: run structured intakes, calibrate on requirements, and influence hiring decisions with market insight - Use recruiting data, funnel metrics, and our AI-enabled recruiting stack (Noon.AI, BrightHire) to work smarter, spot bottlenecks, and report progress - Deliver a high-touch, world-class candidate experience end to end, with fast follow-up at every stage - Evaluate candidates rigorously using structured/behavioral interviewing and deliver thorough, calibrated scorecards - Keep Greenhouse accurate and current: job postings, candidate records, and a weekly pipeline/status report for stakeholders - Run post-interview debrief meetings and prep hiring teams with clear, actionable materials - Build durable relationships across candidates, the TA team, and business partners, and act as an ambassador for Tanium's employer brand Now Requirements: required experience: "5+ years of full-cycle technical recruiting experience required". Could also include "including a track record of closing niche or competitive technical talent". That's part of requirements. Also maybe "Agency and in-house experience a plus; enterprise software recruiting experience preferred" is preferred, not required. So Requirements: 5+ years full-cycle technical recruiting experience, track record of closing niche or competitive technical talent. We'll put as
  . Qualifications: preferred items: "7+ preferred", "Agency and in-house experience a plus; enterprise software recruiting experience preferred", "Thrives in a fast-paced, outcome-oriented recruiting environment - driven by closing searches and hitting hiring goals, not just staying busy", "Strong sourcing skills: proven ability to find and engage candidates who aren't actively looking, not just screen inbound applicants", "Learning agility and genuine curiosity: comfortable ramping quickly across different technical domains rather than specializing in just one", "A track record of advising and influencing senior stakeholders, including director/VP-level hiring managers", "Comfort operating with autonomy in a fast-paced, ambiguous, frequently-shifting environment: you see that as opportunity, not friction", "Data-driven approach: comfortable tracking, interpreting, and acting on recruiting funnel metrics", "Experience with Greenhouse or a comparable modern ATS strongly preferred; comfort with AI-enabled recruiting tools (e.g., Noon.AI, BrightHire) a plus", "Excellent written and verbal communication skills, with the interpersonal skill to build trust quickly with candidates and hiring managers alike". We could split some into Skills section but we can keep Qualifications as all preferred items. Skills: maybe we can extract specific skills: sourcing skills, learning agility, advising stakeholders, data-driven, communication, experience with Greenhouse, comfort with AI-enabled tools. But those are already in Qualifications. To avoid thin sections, maybe we combine Qualifications and Skills into one section? But we need to follow headings list; we can omit Skills if not distinct. However we have a lot of content; we could keep Skills separate for things like "sourcing skills", "learning agility", "advising stakeholders", "data-driven", "communication", "Greenhouse", "AI-enabled tools". But that would be thin? Might be okay. Given instruction: Prefer a few substantive sections over many thin ones. So maybe better to have fewer sections: About the role, Responsibilities, Requirements (including both required and preferred), Benefits, Pay, Schedule. That's 6 sections. That seems reasonable. We can embed preferred items within Requirements section, labeling