Technical Recruiter

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting: It includes sections: About Agile Defense (intro), Why This Role Exists, Performance Objectives — What Success Requires (list of objectives), What Success Looks Like (timeline), Your Scope & Environment, What You Bring (requirements/qualifications), Clearance, Location & Travel, Our Core Values (maybe not needed?), plus maybe Benefits? Not explicit benefits listed. Pay? Not mentioned. Schedule? Not mentioned. So we should not create Pay/Benefits/Schedule sections because no specific content. We need to decide headings: About the role (maybe "About the role" corresponds to "Why This Role Exists"? Actually "About the role" could be description of role. We have "Why This Role Exists". Could map to "About the role". Also "Responsibilities" could be Performance Objectives? Those are outcomes, not duties. But we can treat them as responsibilities. "Requirements" could be "What You Bring". "Qualifications" maybe similar. "Skills" maybe also part of What You Bring. We need to avoid duplication. Better to have sections: About the role (Why This Role Exists), Responsibilities (Performance Objectives), Qualifications (What You Bring), maybe Clearance, Location & Travel as separate? Not in list of allowed headings but we could incorporate into Qualifications or a separate section like "Clearance, Location & Travel" but not allowed heading. Allowed headings are limited to those list. We could put clearance location under Qualifications or maybe as a

within Qualifications. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. We can include multiple of them if content exists. We need to decide which sections have content. - About the role: we have description why role exists. Good. - Responsibilities: we have Performance Objectives (list of outcomes). Could treat as responsibilities. - Requirements: maybe we have "What You Bring" which includes track record, knowledge, etc. That's qualifications/requirements. - Qualifications: maybe similar to Requirements; but we could split: Requirements = hard requirements (clearance, location, travel). Qualifications = soft skills/experience. But we have limited headings; we could combine. - Skills: maybe we could list specific skills like sourcing, screening, interviewing, negotiating, closing, AI usage, stakeholder management, project leadership, compliance, clearance fluency. Could be derived from posting. - Benefits: none. - Pay: none. - Schedule: none. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills. Possibly also include a short paragraph for metadata like location etc within Qualifications or Requirements. We must not include filler like "commensurate with experience". Avoid. We need to preserve all substantive information: we must not lose details. So we need to embed the content from the posting into these sections. Let's extract content: About the role (Why This Role Exists): Paragraph: "Technical Recruiter is the seat where a recruiter proves they can run the entire tactical recruiting process — sourcing, screening, interviewing, and closing — across the full range of technical and cleared requisitions, no matter the complexity. Agile Defense needs recruiters who can be handed anything in the caseload and deliver, while they build the judgment, stakeholder trust, and process ownership that portfolio-level seniority requires. This is a developmental seat on the way to Senior Technical Recruiter: you can do the work — all of it — but you're not yet accountable for a full portfolio of senior stakeholders or for mentoring others. That comes next." We can put that as

. Responsibilities (Performance Objectives — What Success Requires): List of objectives (bullet points). We'll convert to

• . List: - 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 We need to keep the content exactly; no summarizing. What Success Looks Like (timeline) could be considered part of responsibilities? But we could incorporate into Responsibilities as additional bullet points? However it's more about outcomes timeline. Could be placed under Responsibilities as well. But we might create a separate section? Not allowed headings besides those. Could incorporate into Responsibilities as additional bullet list. But we must preserve all substantive info. So we need to include the timeline details. We could add a subsection under Responsibilities: maybe a

  summarizing timeline then bullet list? But we must not invent headings. We can just add a

  after the heading Responsibilities that contains the timeline description, then the bullet list of objectives. Let's extract timeline: 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 We'll put that as a

  maybe. Now Requirements: maybe include Clearance, Location & Travel, and maybe "What You Bring" items that are mandatory? The posting says: "We're not screening for years of experience or a specific past title. We're looking for evidence that you can deliver the objectives above. That typically looks like:" then list bullet points of evidence. Thus Requirements could be those bullet points (evidence). Qualifications could be the core values? Not needed. Skills could be specific competencies. But we need to avoid duplication. Let's decide: - Requirements: the bullet list under "What You Bring" (evidence). That includes: * 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 - Qualifications: maybe the "Clearance, Location & Travel" section: Must be clearable for a U.S. Secret security clearance (minimum); 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 We could put that as Qualifications. - Skills: maybe we can list specific skills like sourcing, screening, interviewing, negotiating, closing, stakeholder management, project leadership, compliance, AI usage, clearance fluency, pipeline diversification. But we might be duplicating. However we can still create a Skills section summarizing these. But we must not invent content not in posting. We can derive skills from the posting: sourcing, screening, interviewing, negotiating, closing, stakeholder relationship building, project leadership, compliance handling, AI-assisted efficiency, clearance process explanation, pipeline widening/diversifying. Those are all mentioned. So we can list them. We must ensure we don't include filler like "not specified". All content is specific. Now we need to output HTML fragment only, no extra tags. Structure:

  About the role

  ...

  Responsibilities

  What Success Looks Like timeline...

  • ...
  ...
  But we need to ensure we don't have empty sections. Let's craft. About the role paragraph: combine the Why This Role Exists paragraph. Responsibilities: first a

  containing the timeline (What Success Looks Like). Then a

  • for each Performance Objective. Requirements:
    • for each bullet under What You Bring. Qualifications: maybe a

      containing Clearance, Location & Travel details. Skills:

      • for each skill. Check for any duplication: The skills list may overlap with responsibilities bullet points (like sourcing, screening, etc). But it's okay. Now ensure we preserve all substantive info: Did we miss anything? The "Our Core Values" section is not required; we can drop as it's boilerplate? It's not EEO but it's cultural values. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Core values might be considered cultural but not boilerplate; however it's not a required heading. Could we include it under Qualifications? Might be considered extra but not required. Safer to omit as not under allowed headings and not essential to role specifics? It's somewhat generic. I'd omit. Also the paragraph about AI tools usage in hiring process (the disclaimer) is legal/boilerplate; remove. Now produce HTML. Let's write. About the role paragraph: "Technical Recruiter is the seat where a recruiter proves they can run the entire tactical recruiting process — sourcing, screening, interviewing, and closing — across the full range of technical and cleared requisitions, no matter the complexity. Agile Defense needs recruiters who can be handed anything in the caseload and deliver, while they build the judgment, stakeholder trust, and process ownership that portfolio-level seniority requires. This is a developmental seat on the way to Senior Technical Recruiter: you can do the work — all of it — but you're not yet accountable for a full portfolio of senior stakeholders or for mentoring others. That comes next." Responsibilities timeline paragraph: "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