Technical Recruiting Manager

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 Job ID etc. Must remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Must preserve all substantive info. We need to parse the posting. Key sections: - Intro: Build a Safer World... description of company. Could be "About the role" maybe? Actually "About the role" is a heading we can use for description of role. The posting includes: "As Technical Recruiting Manager, you will lead the team responsible for finding and closing some of the hardest-to-source technical talent..." That's role description. - Impact You’ll Have Here: bullet list of responsibilities. - What We’re Looking For: list of qualifications/experience. - About The Team: description of team. - Learn About TRM Speed In This Position: details about speed expectations (maybe could be part of responsibilities or separate? Could be "Responsibilities" or "Expectations". Might be considered part of responsibilities. - The following represents the expected range of compensation for this role: The estimated base salary range for this role is $200,000-$220,000. Additionally, this role may be eligible to participate in TRM’s equity plan. Please note – we factor in the different costs for geographies outside the United States. Thus we have Pay section. - Benefits: Not explicitly listed. There's mention of equity plan but that's part of compensation. No explicit benefits like health, etc. So we should not create Benefits section unless posting actually states them. It does not list benefits. So omit Benefits. - Schedule: Not mentioned. There's mention of remote, async, 4+ hour overlap with PST, preferred SF Bay Area-based; in office up to 2x per week as needed. That's schedule/location info. Could be considered Schedule? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could put schedule info under Schedule heading if present. The posting says: "Our Talent team is fully remote, embracing async collaboration via Slack, documentation, and proactive updates. We meet weekly for hiring syncs, sourcing jams, and team huddles to support shared momentum and alignment. The team is known for rigor, humility, and craft obsession—we continuously refine systems and raise our own bar. Most team members operate with a 4+ hour overlap with PST; we value flexibility and autonomy with accountability. Preferred SF Bay Area-based; in office up to 2x per week as needed". That's schedule/location info. So we can include Schedule section. - Skills: Not explicitly listed separate from qualifications. Could combine with Requirements/Qualifications. But we need to decide sections: We have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include only those with real content. We have About the role (role description). Responsibilities (Impact You’ll Have Here). Requirements/Qualifications: "What We’re Looking For" includes experience requirements. Could be Requirements. Also "About The Team" maybe not needed as separate heading; could be part of About the role? But we have no separate heading for team; we could omit or include as part of About the role. The instruction: Prefer a few substantive sections over many thin ones. So we could combine team description into About the role or Responsibilities? Probably About the role includes role description and team context. But we have separate "About The Team" which is substantive. Could we make a section "About the Team"? Not in the list of allowed headings. The allowed headings are those enumerated. So we must map content to those headings. "About The Team" could go under "About the role" or maybe "Responsibilities"? Not ideal. Could we create a section "About the role" that includes both role description and team info. That's acceptable. Skills: Not explicitly separate; we could omit Skills section if no specific skills listed beyond qualifications. The posting mentions "technical recruiting experience", "coaching recruiters", "strategic thinker", "operationally excellent", "clear communicator". Those are skills/qualifications. Could be placed under Requirements or Qualifications. We'll decide to have Requirements (experience) and Qualifications (skills). But we need to avoid duplication. Let's extract: About the role: description of TRM, mission, role as Technical Recruiting Manager, leading team, building technical recruiting function. Responsibilities (Impact You’ll Have Here): - Manage and coach a team of technical recruiters, raising the bar on sourcing strategy, candidate experience, and closing excellence. - Oversee delivery of high-priority engineering and technical roles; step in on complex searches as needed. - Partner closely with executives and hiring managers to calibrate, forecast, and course-correct hiring plans. - Build and scale technical recruiting capacity ahead of need: forecast hiring demand across R&D, translate it into your team's staffing plan. - Optimize tools, processes, and systems to drive speed, precision, and data hygiene across the recruiting funnel. - Build a culture of excellence, feedback, and continuous improvement within the recruiting team. Requirements (What We’re Looking For): - 10+ years of technical recruiting experience, including 4+ years managing high growth teams - Proven ability to hire for complex technical roles in high-growth environments - Demonstrated success coaching recruiters and raising execution quality across a team - Strategic thinker with strong instincts for prioritization, stakeholder alignment, and problem-solving - Operationally excellent with experience managing recruiting tools, dashboards, and workflows - Clear, concise communicator comfortable working with execs and distributed teams Qualifications: maybe not needed separate; but we could treat the above as Qualifications. However we need both Requirements and Qualifications sections if we have distinct content. The posting does not separate them clearly; it's a list of "What We’re Looking For". Could be considered Requirements. We could put that under Requirements and omit Qualifications. Or we could split: Requirements = years of experience, proven ability, etc. Qualifications = strategic thinker, operationally excellent, communicator. But that's arbitrary. Given instruction to prefer few substantive sections, we could combine into one section called "Requirements" (or "Qualifications") and omit the other. Which heading is more appropriate? The list includes experience and skills; both are requirements. I'd choose "Requirements". Then we omit Qualifications. Skills: Not needed. Benefits: Not present. Pay: base salary range $200k-$220k, equity plan eligibility, note about geography cost adjustment. Schedule: remote, async, weekly meetings, 4+ hour overlap with PST, flexibility, preferred SF Bay Area, in office up to 2x per week. We also have "Learn About TRM Speed In This Position" which details speed expectations. Could be part of Responsibilities or maybe a separate section like "Expectations". Not in allowed headings. Could be included under Responsibilities as additional bullet points. Let's incorporate those as responsibilities: "Within 72 hours of receiving a new headcount request, the Recruiting Manager ensures an intake meeting is scheduled and reviews sample profiles with recruiters. Within 48 hours of initial candidate feedback, partners with recruiters to synthesize insights and evolve search strategy; expects A/B tested outreach to be in-market within 24 hours. Within the first week of launching a new search, team has surfaced and messaged 100+ targeted candidates and flagged key conversion levers by channel or source." These are expectations/responsibilities. Thus Responsibilities section will include both the Impact bullet list and the speed expectations. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We must not include markdown code fences. We must not include any boilerplate like privacy policy, application instructions, interview process, life at TRM, leadership principles, etc. Remove all that. We must preserve all substantive information; we have removed many sections like interview process, life at TRM, leadership principles, privacy policy, etc. That's okay as per instruction to remove boilerplate/legal/EEO etc. However we must ensure we didn't remove substantive info that is not boilerplate. The removed sections include: "Learn About TRM Speed In This Position" (we kept), "Life at TRM", "Interview Process", "Leadership Principles", "Join our Mission", "Learn more: Company Values | Interviewing | FAQs", "Privacy Policy And Additional Information", etc. Those are considered boilerplate or not required. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not explicitly say to remove "Life at TRM" or "Leadership Principles". However those are more about culture; could be considered substantive? The instruction says "Prefer a few substantive sections over many thin ones." It doesn't forbid including culture sections, but we have limited headings. We could include them under About the role maybe. But we already have a lot. However 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 including culture info. But we must output only HTML fragment; we can choose to omit them if we deem them not essential. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must preserve all substantive information. Are "Life at TRM" and "Leadership Principles" substantive? They describe culture, values, expectations. Could be considered substantive. But we have no heading for culture; we could fold into About the role or Responsibilities. However that would be a lot of text; but we can include as prose under About the role maybe. Similarly "Learn About TRM Speed In This Position" we already incorporated. "AI Fluency at TRM" and "Leadership Principles" are also substantive about expectations. We could incorporate them under About the role or Responsibilities as well. But we must be careful not to create too many thin sections. We could have About the role (includes mission, role description, team description, culture, AI fluency, leadership principles). Responsibilities (impact + speed expectations). Requirements (experience & skills). Pay. Schedule. That seems reasonable. Let's extract substantive content from those sections: - About TRM mission: "Build a Safer World. TRM Labs provides AI-powered intelligence solutions that help public and private sector agencies investigate and disrupt crime. TRM's platforms enable investigators to trace illicit activity, build cases, and construct operating pictures of threat networks. Leading agencies and businesses worldwide rely on TRM to make the world safer and more secure." - Ability to identify, hire, retain exceptional talent is foundational. - Talent team description: seasoned professionals, experience hiring world-class Engineering, Data Science, GTM, People teams for notable startups in Silicon Valley. - As Technical Recruiting Manager, you will lead the team responsible for finding and closing some of the hardest-to-source technical talent in the market: engineers, data scientists, security researchers, and applied AI talent who can build at the pace TRM moves. - This is not a role for someone who wants to run an existing playbook; it's for someone who wants to build a world-class technical recruiting function and raise the bar on every hire that comes through it. - About The Team: fully remote, async collaboration via Slack, documentation, proactive updates. Meet weekly for hiring syncs, sourcing jams, team huddles. Known for rigor, humility, craft obsession—continuously refine systems and raise own bar. Most team members operate with a 4+ hour overlap with PST; we value flexibility and autonomy with accountability. Preferred SF Bay Area-based; in office up to 2x per week as needed. - Learn About TRM Speed In This Position: details as