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. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove EEO statement etc. Also remove "Equal Opportunity Employer/Protected Veterans/Individuals with Disabilities" and AI usage note? That is maybe considered boilerplate? It's about AI usage in hiring process, maybe not needed. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI usage note is maybe legal? Might be considered boilerplate but it's about process; but it's not EEO. Might keep? Safer to remove it as it's not substantive about role. Also remove "Our Core Values" maybe not needed? It's substantive about culture; could be part of About the role? Might be considered part of About the role. The instruction: Prefer a few substantive sections over many thin ones. So we can combine. We need sections: About the role (maybe includes description of role, why exists, performance objectives, scope & environment). Responsibilities (maybe performance objectives). Requirements (clearance, location, travel). Qualifications (what you bring). Skills (maybe AI, clearance fluency, stakeholder relationships). Benefits (none given). Pay (none). Schedule (none). So we will only include sections that have content: About the role, Responsibilities, Requirements, Qualifications, Skills. Possibly Benefits if none then omit. We must not create Pay/Schedule/Benefits unless posting actually states them. It does not state pay or schedule specifics, only location remote, travel minimal. So we omit Pay, Schedule, Benefits. Now we need to extract substantive info. Let's parse the posting. Sections: - About Agile Defense (company description). Could be part of About the role? Might be separate but we can include in About the role. - Why This Role Exists: description of Technical Recruiter role. - Performance Objectives — What Success Requires: list of outcomes (these are results measured). Could be Responsibilities. - What Success Looks Like (first 90 days, 6 months, 12 months): could be part of Responsibilities or expectations. - Your Scope & Environment: reporting, caseload, etc. - What You Bring: qualifications. - Clearance, Location & Travel: location remote, travel minimal, ideal locations, clearance must be clearable for US Secret. - Our Core Values: values list. - Equal Opportunity Employer... (remove). - AI usage note (maybe remove). We need to preserve all substantive info, not invent or summarize away detail. So we need to keep details like caseload 12-18 concurrent requisitions, reporting to VP of Talent Acquisition, work with Lead Recruiter, etc. Also performance objectives list. We must not repeat job title as heading. So no heading "Technical Recruiter". Use

for section headings. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We must not include filler like "commensurate with experience". Not present. Now craft HTML. We'll have sections:

  About the role

  ... combine company description and role purpose.

  Maybe separate company description and role purpose into paragraphs. Then

  Responsibilities

  • ... list of performance objectives and success looks like items.
  But we need to ensure we don't lose detail. Let's extract bullet points. Performance Objectives — What Success Requires: - Independently run the full recruiting toolkit. Within 90 days, manage a caseload of full-cycle requisitions across the full range of technical and cleared complexity — sourcing, screening, interviewing, negotiating, and closing — with only light oversight from a Senior Technical Recruiter or Recruiting Lead - Build real clearance fluency, including your first higher-tier searches. Within 6 months, be fully fluent explaining the clearance process - Own stakeholder relationships on your reqs. Build direct, trusted working relationships with the hiring managers on your caseload — providing market feedback, pipeline updates, and honest guidance without needing a more senior recruiter to translate for you - Take ownership of a small project. Lead at least one defined project or initiative beyond your own req load per year — for example, piloting a new sourcing channel, refining a screening guide, or improving one piece of the intake process — from proposal through completion - Maintain compliance accuracy independently. Handle all compliance requirements (EEO/OFCCP, clearance documentation, interview documentation) on your reqs with consistent accuracy and minimal correction needed - Make AI part of your daily practice, and widen your pipelines. Identify and adopt at least one recurring AI-assisted efficiency in your own workflow, and be able to describe how it's changed your day-to-day work — while applying deliberate sourcing practices that widen and diversify your candidate pipelines, with specific actions you can point to What Success Looks Like: - First 90 Days: You're running full-cycle reqs independently across the full range of complexity, with only light check-ins - First 6 Months: Hiring managers trust you directly, and you've identified and proposed the small project you'll own for the year - First 12 Months: You're a fully independent, reliable recruiter who can be handed anything in the tactical req workload — and you're ready for the portfolio ownership, mentoring, and senior-stakeholder responsibility that defines Senior Technical Recruiter Your Scope & Environment: - You'll report to the VP of Talent Acquisition, work with a Lead Recruiter around prioritization, and carry a caseload across the full range of technical/cleared complexity — typically 12 to 18 concurrent requisitions — as part of a broader team recruiting across DoD, Fed Civ, Homeland Security, Combatant Command, and Fourth Estate customers. - You're trusted with the full tactical req load, but your accountability stops at your own caseload and your one owned project — portfolio-level ownership, senior stakeholder relationships, and coaching responsibility are the next step, not yet the expectation here. What You Bring: - A demonstrated track record independently running full-cycle recruiting across the full range of technical, cleared complexity — you're not intimidated by a hard req - Working knowledge of the federal clearance process up through Top Secret/SCI and polygraph-level searches - A track record of hiring managers trusting your judgment on their reqs — you're seen as a partner, not just a processor - Experience proposing or improving something beyond your own req load, even in a small way - Personal habits or practices around using AI tools to work more efficiently, paired with the judgment to know where automation helps and where it shouldn't touch the candidate experience - A genuine, active interest in building more diverse candidate pipelines, with specific examples of actions you've taken, not just good intentions Clearance, Location & Travel: - Location: 100% Remote (U.S.) | Travel: Minimal / occasional (client sites in the US or Reston, VA / McLean, VA & the DMV region) - Ideal locations outside of the DMV: Greater Tampa, FL region, Ft Huachuca, AZ - Clearance: Must be clearable for a U.S. Secret security clearance (minimum) Our Core Values (maybe include as part of About the role or separate section? Could be a section "Our Values" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add a custom heading like "Our Values". We could incorporate into About the role or Skills? Probably About the role includes culture. We'll embed values in About the role paragraph. Now we need to map to allowed sections. About the role: include company description, why role exists, scope & environment maybe? But scope & environment could be part of About the role or Responsibilities. We'll put scope & environment in About the role. Responsibilities: performance objectives and success looks like. Requirements: clearance, location, travel (maybe also ideal locations). Could also include clearance requirement. Qualifications: what you bring (track record, knowledge, trust, improvement experience, AI habits, diversity interest). Skills: maybe AI, clearance fluency, stakeholder relationships, project ownership, compliance, sourcing, etc. But we might combine some into Qualifications. However we need to avoid thin sections. Perhaps we can have About the role, Responsibilities, Requirements, Qualifications. Skills could be omitted if not distinct. But we need to follow instruction: Prefer a few substantive sections over many thin ones. So we can combine skills into Qualifications or Responsibilities. But we have allowed headings; we can omit Skills if not needed. The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not that we must include all. So we can include only those with real content. Thus we will have About the role, Responsibilities, Requirements, Qualifications. Now we need to ensure we don't repeat job title as heading. Good. Now we need to format. Let's craft About the role paragraph(s). Could be multiple

  tags. We'll include: - Company description: At Agile Defense we know that action defines the outcome and new challenges require new solutions... (the paragraph about vision). - Why This Role Exists: Technical Recruiter is the seat where a recruiter proves they can run the entire tactical recruiting process... (the paragraph). - Scope & Environment: You'll report to the VP of Talent Acquisition... (the paragraph about reporting, caseload, etc.) - Core Values: maybe embed as a paragraph. We'll keep as separate

  for readability. Now Responsibilities:

  • each bullet from performance objectives and success looks like. We'll combine them. We need to preserve all substantive info; we should not lose any detail. So each bullet should be a
  • with the full sentence. Let's list them: 1. Independently run the full recruiting toolkit. Within 90 days, manage a caseload of full-cycle requisitions across the full range of technical and cleared complexity — sourcing, screening, interviewing, negotiating, and closing — with only light oversight from a Senior Technical Recruiter or Recruiting Lead 2. Build real clearance fluency, including your first higher-tier searches. Within 6 months, be fully fluent explaining the clearance process 3. Own stakeholder relationships on your reqs. Build direct, trusted working relationships with the hiring managers on your caseload — providing market feedback, pipeline updates, and honest guidance without needing a more senior recruiter to translate for you 4. Take ownership of a small project. Lead at least one defined project or initiative beyond your own req load per year — for example, piloting a new sourcing channel, refining a screening guide, or improving one piece of the intake process — from proposal through completion 5. Maintain compliance accuracy independently. Handle all compliance requirements (EEO/OFCCP, clearance documentation, interview documentation) on your reqs with consistent accuracy and minimal correction needed 6. Make AI part of your daily practice, and widen your pipelines. Identify and adopt at least one recurring AI-assisted efficiency in your own workflow, and be able to describe how it's changed your day-to-day work — while applying deliberate sourcing practices that widen and diversify your candidate pipelines, with specific actions you can point to 7. First 90 Days: You're running full-cycle reqs independently across the full range of complexity, with only light check-ins 8. First 6 Months: Hiring managers trust you directly, and you've identified and proposed the small project you'll own for the year 9. First 12 Months: You