Senior Technical Recruiter & Portfolio Owner

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 need to parse the job posting. First, there is a description about Agile Defense (company overview) – maybe not needed? The instruction: "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." So we can include a short paragraph about the company? Possibly not needed but we can include as prose under maybe "About the role"? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content. Let's extract content. The posting includes: - About Agile Defense (company description) – could be "About the role"? Actually "About the role" would be description of the role. The posting includes "Why This Role Exists" and details about role. So we can put that under "About the role". - Performance Objectives – What Success Requires – these are outcomes. Could be under "Responsibilities" or "Requirements"? Might be considered responsibilities. We'll treat as responsibilities. - What Success Looks Like (first 90 days, 6 months, 12 months) – also responsibilities or expectations. - Your Scope & Environment – description of scope. - What You Bring – qualifications/requirements. - Clearance, Location & Travel – location, clearance, travel. - Our Core Values – maybe not needed; could be omitted as boilerplate? It's values, maybe not required but could be included under "About the role"? Might be considered fluff but it's specific content. However instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Core values not boilerplate but maybe not needed. Could be omitted. - Equal Opportunity Employer... – that's EEO boilerplate, remove. - AI usage statement – maybe not needed. Thus we need to produce sections:

About the role

– include description: Why This Role Exists, maybe also company overview? We'll include the role description: "Senior Technical Recruiter is where portfolio ownership becomes the job..." plus details.

Responsibilities

– include performance objectives, success looks like, scope & environment.

Requirements

– include What You Bring (track record, coaching, stakeholder management, process improvement, AI interest, diverse slates, federal contract cycles knowledge).

Qualifications

– maybe clearance, location, travel? Could be separate but we can combine into Requirements? The instruction allows Qualifications section. We'll put clearance, location, travel there.

Skills

– maybe not explicit; we could omit if no specific skill list. Could include "AI-assisted recruiting", "process improvement", "stakeholder management", "coaching". But we might not have a dedicated skills list; we could skip Skills section if no specific content. Better to omit.

Benefits

– not mentioned; omit.

Pay

– not mentioned; omit.

Schedule

– not mentioned; omit. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications. Now we need to preserve all substantive information, not invent or summarize away detail. Must not omit details. We need to include all details from the posting within those sections. We must be careful not to leave out any detail. Let's extract details: Company overview (About Agile Defense) – maybe not needed for role but could be included under About the role as context. It's substantive. We'll include. Why This Role Exists paragraph: "Senior Technical Recruiter is where portfolio ownership becomes the job. Agile Defense needs experienced recruiters who can own a full portfolio of technical, cleared requisitions and the senior stakeholders behind them — Program Managers, Directors, Capture leads — end-to-end, while coaching and raising the floor for the Recruiter I's and II's around them. This is the senior individual-contributor delivery seat on the team: the recruiter other people's hardest searches get routed to, and the proving ground for anyone interested in the operational or people-leadership track that follows — Recruiting Lead or Recruiting Manager." Performance Objectives – What Success Requires bullet list (actually paragraphs). We need to preserve each bullet as list items. List: - Own a full portfolio of senior stakeholders. Within 90 days, take full ownership of a portfolio of technical, cleared requisitions spanning multiple senior stakeholders (Program Managers, Directors, Capture leads), and become a trusted authority on hiring cleared technical talent up through TS/SCI with polygraph - Mentor and coach junior recruiters. On an ongoing basis, mentor Recruiter I and II team members, with at least one showing a measurable improvement in independent req ownership, compliance accuracy, or candidate-experience feedback within two quarters of your coaching - Recommend and contribute to process improvement. Identify at least one process or workflow gap per year and bring a concrete, well-reasoned recommendation to your Recruiting Lead or Manager — with the credibility and data to make the case - Deliver consistently on the hardest searches. Be a recruiter your Recruiting Lead routes complex or sensitive requisitions to, and deliver strong outcomes on them without needing close oversight - Model AI-enabled, human-led recruiting. Maintain and refine your own AI-assisted practices, and actively share them with Recruiter I and II teammates — always in service of a better human experience, not a replacement for it - Champion diverse, qualified slates. Each quarter, partner with at least one senior hiring team to build and present a deliberate strategy for a more diverse, representative finalist slate — without lowering the bar for cleared, technical qualification What Success Looks Like: First 90 Days: You've absorbed your portfolio, built credibility with senior stakeholders, and are operating independently across the full complexity range, including TS/SCI and polygraph searches First 6 Months: At least one recruiter you're coaching is noticeably more capable than when you started, and you've brought at least one credible process recommendation forward First 12 Months: You're a recruiter your Recruiting Lead or Manager routes the hardest, most senior, or most sensitive reqs to — and you're ready to consider whether your next step is deeper portfolio ownership, a Recruiting Lead track leading a program or workstream beyond delivery, or people management Your Scope & Environment: You'll report to the VP of Talent Acquisition and own a full portfolio — typically 15-20+ concurrent requisitions — for mid-to-senior technical and programmatic roles, working alongside the Recruiter I/II teammates you help develop and partnering closely with HR, Security/Facility Security Officers (FSO), compensation, and contracts staff. Expect real ownership of the relationships that matter most to a program's success, and real influence over how the team works — without yet carrying the org-wide program-building, prioritization, or escalation responsibilities that define a Recruiting Lead. What You Bring: 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: - A demonstrated track record independently owning full-cycle recruiting for technical, cleared positions up through TS/SCI with polygraph - A track record of informally or formally coaching other recruiters and genuinely wanting to see them grow - Confidence managing multiple senior stakeholders at once, including the ability to push back, advise, and influence a hiring decision when the data says you should - Experience building or meaningfully improving a process, tool, or workflow, and partnering with hiring managers to make it stick - A genuine, demonstrable personal interest in applying AI to recruiting work, paired with a firm point of view on where automation belongs and where it doesn't - A real, lived belief that diverse slates and diverse interview panels produce better hiring outcomes, evidenced by specific outcomes you've driven - Working knowledge of how federal contract cycles — recompetes, awards, labor categories, staffing plans — shape hiring urgency and timing Clearance, Location & Travel: Location: 100% Remote (U.S.) | Travel: Minimal / occasional (client sites in the US or Reston, VA / McLean, VA & the DMV region) Other ideal locations would include Greater Tampa, FL region or Ft. Huachuca, AZ Clearance: Must be clearable for a U.S. Secret security clearance (minimum) Our Core Values: maybe we can omit as not required but it's substantive. However it's not a section heading we have; we could include under About the role? Might be too much. But we can include as a short paragraph under About the role? The instruction: "Prefer a few substantive sections over many thin ones." So we could include core values as part of About the role? But it's not about the role. Might be better to omit because not requested sections. The instruction says we should include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid including other content outside those headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. Any other content should be placed under those headings as prose or lists. So we need to fit all content under those four headings. Thus we need to decide where to put core values. Could be under About the role as a brief description of company culture. That seems acceptable. Now we need to ensure we don't miss any detail. Let's craft HTML. We'll start with

About the role

Under it, we can have a

containing company overview and why role exists. We need to preserve all details: company overview paragraph, why role exists paragraph. We'll combine them maybe as two

elements. Then

Responsibilities

Under it, we need to include performance objectives, what success looks like, scope & environment. We can structure as

• for each bullet. Performance objectives are six items. What Success Looks Like: three items (first 90 days, 6 months, 12 months). Could be list as well. Scope & Environment: a paragraph. We'll put all as list items under responsibilities? Might be mixing different types. But we can still use
  • for each responsibility item. For scope & environment, we can put a

    . Thus:

    Responsibilities

    • Own a full portfolio of senior stakeholders. Within 90 days, take full ownership of a portfolio of technical, cleared requisitions spanning multiple senior stakeholders (Program Managers, Directors, Capture leads), and become a trusted authority on hiring cleared technical talent up through TS/SCI with polygraph
    • Mentor and coach junior recruiters. On an ongoing basis, mentor Recruiter I and II team members, with at least one showing a measurable improvement in independent req ownership, compliance accuracy, or candidate-experience feedback within two quarters of your coaching
    • Recommend and contribute to process improvement. Identify at least one process or workflow gap per year and bring a concrete, well-reasoned recommendation to your Recruiting Lead or Manager — with the credibility and data to make the case
    • Deliver consistently on the hardest searches. Be a recruiter your Recruiting Lead routes complex or sensitive requisitions to, and deliver strong outcomes on them without needing close oversight
    • Model AI-enabled, human-led recruiting. Maintain and refine your own AI-assisted practices, and actively