Recruiter
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting.
Content:
Title: Talent Acquisition Specialist (Engineering, Product & IT)
Then paragraph: "Are you passionate about connecting great talent with exciting career opportunities? We're looking for a Talent Acquisition Specialist to join our growing team and play a key role in attracting, hiring, and retaining top talent across our Engineering, Product Management, and Information Technology organizations. In this role, you'll partner closely with hiring leaders, build strong talent pipelines, and guide candidates through a best-in-class recruitment experience from first conversation through onboarding. If you thrive in a fast-paced environment, enjoy building relationships, and have a knack for finding exceptional talent, we'd love to hear from you."
Then "What You'll Do" list of duties (multiple sentences each starting with verb). Should be a list.
Then "What We're Looking For" list of requirements/qualifications.
Then "Why Join Us?" list of benefits? Actually it's reasons to join: opportunity to make impact, collaborative team, exposure, ability to build strategic partnerships. That's more like benefits or selling points. Could be a section "Why Join Us?" but not in allowed headings list? The allowed headings list includes Benefits, Pay, Schedule, etc. "Why Join Us?" is not in list but we could treat as Benefits? However instruction: Use headings from the list (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exhaustive? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should stick to those headings. So we need to map content to those.
We have:
- About the role: overview paragraph.
- Responsibilities: the "What You'll Do" list.
- Requirements: maybe "What We're Looking For" includes experience, skills, etc. Could be Requirements.
- Qualifications: maybe Bachelor's degree preferred; equivalent experience.
- Skills: maybe strong sourcing capabilities, interviewing, etc. Could be separate.
But we should avoid thin sections. Prefer few substantive sections. Could combine Requirements and Qualifications into one? But we need to follow instruction: include a section ONLY when posting has real, specific content for it. We can decide to have sections: About the role, Responsibilities, Requirements (including qualifications and skills), Benefits, Pay, Schedule? Let's see.
Pay: The posting includes "Pay And Benefits" with pay range $28.00 - $31.00/hr. Also mentions benefits list. So we need Pay and Benefits sections.
Schedule: The posting includes "Workplace Type This is a hybrid position in Davidson,NC." Also maybe schedule not specified. There's no explicit schedule like full-time, part-time, etc. It says Contract to Hire position based out of Davidson, NC. Workplace type hybrid. No explicit schedule like full-time, part-time, shift. So we should not create Schedule section unless posting actually states them. It does not state schedule specifics, so we omit Schedule.
Benefits: The posting lists benefits under Pay And Benefits: Medical, dental & vision, Critical Illness, Accident, and Hospital, 401(k) Retirement Plan, Pre-tax and Roth post-tax contributions available, Life Insurance (Voluntary Life & AD&D for the employee and dependents), Short and long-term disability, Health Spending Account (HSA), Transportation benefits, Employee Assistance Program, Time Off/Leave (PTO, Vacation or Sick Leave). So we need Benefits section with list.
Pay: Provide pay range.
Now About the role: overview paragraph.
Responsibilities: list of duties from "What You'll Do".
Requirements: Could combine "What We're Looking For" and "Bachelor's degree preferred; equivalent professional experience will also be considered." Also maybe "2+ years of full-cycle recruiting experience." etc.
Skills: Could be separate but we might combine into Requirements to avoid thin sections. However we have "Strong sourcing capabilities and experience identifying passive candidates." etc. Those are skills. Could be separate Skills section. But we prefer few substantive sections. Could have Requirements (including experience, education) and Skills (specific abilities). That's two sections plus About, Responsibilities, Pay, Benefits. That's 5 sections. Might be okay.
But we need to ensure we don't create thin sections with filler. Each should have substantive content.
Let's extract content precisely.
About the role paragraph: "Are you passionate about connecting great talent with exciting career opportunities? We're looking for a Talent Acquisition Specialist to join our growing team and play a key role in attracting, hiring, and retaining top talent across our Engineering, Product Management, and Information Technology organizations. In this role, you'll partner closely with hiring leaders, build strong talent pipelines, and guide candidates through a best-in-class recruitment experience from first conversation through onboarding. If you thrive in a fast-paced environment, enjoy building relationships, and have a knack for finding exceptional talent, we'd love to hear from you."
That's prose.
Responsibilities list items (each starts with a verb):
- Lead full-cycle recruitment efforts from sourcing and screening through offer acceptance and onboarding.
- Partner with hiring managers and HR teams to understand workforce needs, create hiring strategies, and set recruiting expectations.
- Proactively identify and engage top talent through referrals, networking, social media, industry events, and other innovative sourcing methods.
- Conduct candidate screenings and assessments to evaluate skills, experience, and overall fit.
- Present qualified candidates to hiring teams and facilitate interview coordination, feedback discussions, and hiring decisions.
- Build and maintain talent pipelines for current and future hiring needs, with a focus on technical and professional talent.
- Collaborate with HR and Compensation teams throughout the offer process, including approvals, negotiations, and onboarding activities.
- Deliver an exceptional candidate experience through consistent communication and relationship management.
- Identify opportunities to improve recruiting processes, enhance efficiencies, and contribute to Talent Acquisition best practices.
That's 9 items.
Requirements: from "What We're Looking For":
- 2+ years of full-cycle recruiting experience.
- Experience recruiting professional-level talent, ideally within Engineering, Product Management, IT, or other technical disciplines.
- Strong sourcing capabilities and experience identifying passive candidates.
- Excellent interviewing, candidate assessment, and relationship-building skills.
- Ability to influence and partner effectively with hiring managers, HR partners, and key stakeholders.
- Strong communication, organization, and problem-solving skills.
- A continuous improvement mindset with a passion for optimizing recruiting processes.
- Bachelor's degree preferred; equivalent professional experience will also be considered.
We could split: Requirements (experience, education) and Skills (sourcing, interviewing, influencing, communication, continuous improvement). But the list includes skills as well. However we can make a Requirements section that includes experience and education, and a Skills section for the rest. Let's see.
Requirements section content:
- 2+ years of full-cycle recruiting experience.
- Experience recruiting professional-level talent, ideally within Engineering, Product Management, IT, or other technical disciplines.
- Bachelor's degree preferred; equivalent professional experience will also be considered.
Skills section content:
- Strong sourcing capabilities and experience identifying passive candidates.
- Excellent interviewing, candidate assessment, and relationship-building skills.
- Ability to influence and partner effectively with hiring managers, HR partners, and key stakeholders.
- Strong communication, organization, and problem-solving skills.
- A continuous improvement mindset with a passion for optimizing recruiting processes.
That seems reasonable.
Now Benefits: list as above.
Pay: The pay range: "$28.00 - $31.00/hr." Also note that individual compensation depends on many factors. We should include that prose? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include the sentence about individual compensation depending on many factors. That's part of Pay section. So Pay section could have a
with that sentence, plus maybe the range as
or
? The range is a single value; we can put in . The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So for Pay, we have prose (the sentence about individual compensation). The range could be considered prose as well. We'll just put both in a
maybe separated by a space or line break. Could also put range in
and then another
for the factors. But we can combine.
Benefits: list of items.
Now we need to remove boilerplate: The sections about Aston Carter description, equal opportunity, accommodation, San Francisco Fair Chance, Massachusetts Lie Detector, Use of AI, etc. Those are legal/EEO boilerplate; remove.
Also remove "Job Type & Location This is a Contract to Hire position based out of Davidson, NC." and "Workplace Type This is a hybrid position in Davidson,NC." and "Application Deadline This position is anticipated to close on Oct 12, 2026." Those are minor metadata; we should fold into a short
or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include a short paragraph at the end maybe under a generic "Details" but not a heading. Since we are not to create headings for minor metadata, we could just drop them or include them in a
without heading. The instruction says fold minor metadata into a short
or drop it. Probably we can include a short
after the sections containing location, job type, deadline. But we must not create a heading for it. So we can add a
at the end: "This is a Contract to Hire position based out of Davidson, NC. Workplace type is hybrid. Application deadline: Oct 12, 2026." That preserves info.
Now ensure we don't repeat the job title as a heading. We'll not.
Now produce HTML fragment.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Pay
The pay range for this position is $28.00 - $31.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors.
Benefits
- Medical, dental & vision
- Critical Illness, Accident, and Hospital
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Content: Title: Talent Acquisition Specialist (Engineering, Product & IT) Then paragraph: "Are you passionate about connecting great talent with exciting career opportunities? We're looking for a Talent Acquisition Specialist to join our growing team and play a key role in attracting, hiring, and retaining top talent across our Engineering, Product Management, and Information Technology organizations. In this role, you'll partner closely with hiring leaders, build strong talent pipelines, and guide candidates through a best-in-class recruitment experience from first conversation through onboarding. If you thrive in a fast-paced environment, enjoy building relationships, and have a knack for finding exceptional talent, we'd love to hear from you." Then "What You'll Do" list of duties (multiple sentences each starting with verb). Should be a list. Then "What We're Looking For" list of requirements/qualifications. Then "Why Join Us?" list of benefits? Actually it's reasons to join: opportunity to make impact, collaborative team, exposure, ability to build strategic partnerships. That's more like benefits or selling points. Could be a section "Why Join Us?" but not in allowed headings list? The allowed headings list includes Benefits, Pay, Schedule, etc. "Why Join Us?" is not in list but we could treat as Benefits? However instruction: Use headings from the list (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exhaustive? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should stick to those headings. So we need to map content to those. We have: - About the role: overview paragraph. - Responsibilities: the "What You'll Do" list. - Requirements: maybe "What We're Looking For" includes experience, skills, etc. Could be Requirements. - Qualifications: maybe Bachelor's degree preferred; equivalent experience. - Skills: maybe strong sourcing capabilities, interviewing, etc. Could be separate. But we should avoid thin sections. Prefer few substantive sections. Could combine Requirements and Qualifications into one? But we need to follow instruction: include a section ONLY when posting has real, specific content for it. We can decide to have sections: About the role, Responsibilities, Requirements (including qualifications and skills), Benefits, Pay, Schedule? Let's see. Pay: The posting includes "Pay And Benefits" with pay range $28.00 - $31.00/hr. Also mentions benefits list. So we need Pay and Benefits sections. Schedule: The posting includes "Workplace Type This is a hybrid position in Davidson,NC." Also maybe schedule not specified. There's no explicit schedule like full-time, part-time, etc. It says Contract to Hire position based out of Davidson, NC. Workplace type hybrid. No explicit schedule like full-time, part-time, shift. So we should not create Schedule section unless posting actually states them. It does not state schedule specifics, so we omit Schedule. Benefits: The posting lists benefits under Pay And Benefits: Medical, dental & vision, Critical Illness, Accident, and Hospital, 401(k) Retirement Plan, Pre-tax and Roth post-tax contributions available, Life Insurance (Voluntary Life & AD&D for the employee and dependents), Short and long-term disability, Health Spending Account (HSA), Transportation benefits, Employee Assistance Program, Time Off/Leave (PTO, Vacation or Sick Leave). So we need Benefits section with list. Pay: Provide pay range. Now About the role: overview paragraph. Responsibilities: list of duties from "What You'll Do". Requirements: Could combine "What We're Looking For" and "Bachelor's degree preferred; equivalent professional experience will also be considered." Also maybe "2+ years of full-cycle recruiting experience." etc. Skills: Could be separate but we might combine into Requirements to avoid thin sections. However we have "Strong sourcing capabilities and experience identifying passive candidates." etc. Those are skills. Could be separate Skills section. But we prefer few substantive sections. Could have Requirements (including experience, education) and Skills (specific abilities). That's two sections plus About, Responsibilities, Pay, Benefits. That's 5 sections. Might be okay. But we need to ensure we don't create thin sections with filler. Each should have substantive content. Let's extract content precisely. About the role paragraph: "Are you passionate about connecting great talent with exciting career opportunities? We're looking for a Talent Acquisition Specialist to join our growing team and play a key role in attracting, hiring, and retaining top talent across our Engineering, Product Management, and Information Technology organizations. In this role, you'll partner closely with hiring leaders, build strong talent pipelines, and guide candidates through a best-in-class recruitment experience from first conversation through onboarding. If you thrive in a fast-paced environment, enjoy building relationships, and have a knack for finding exceptional talent, we'd love to hear from you." That's prose. Responsibilities list items (each starts with a verb): - Lead full-cycle recruitment efforts from sourcing and screening through offer acceptance and onboarding. - Partner with hiring managers and HR teams to understand workforce needs, create hiring strategies, and set recruiting expectations. - Proactively identify and engage top talent through referrals, networking, social media, industry events, and other innovative sourcing methods. - Conduct candidate screenings and assessments to evaluate skills, experience, and overall fit. - Present qualified candidates to hiring teams and facilitate interview coordination, feedback discussions, and hiring decisions. - Build and maintain talent pipelines for current and future hiring needs, with a focus on technical and professional talent. - Collaborate with HR and Compensation teams throughout the offer process, including approvals, negotiations, and onboarding activities. - Deliver an exceptional candidate experience through consistent communication and relationship management. - Identify opportunities to improve recruiting processes, enhance efficiencies, and contribute to Talent Acquisition best practices. That's 9 items. Requirements: from "What We're Looking For": - 2+ years of full-cycle recruiting experience. - Experience recruiting professional-level talent, ideally within Engineering, Product Management, IT, or other technical disciplines. - Strong sourcing capabilities and experience identifying passive candidates. - Excellent interviewing, candidate assessment, and relationship-building skills. - Ability to influence and partner effectively with hiring managers, HR partners, and key stakeholders. - Strong communication, organization, and problem-solving skills. - A continuous improvement mindset with a passion for optimizing recruiting processes. - Bachelor's degree preferred; equivalent professional experience will also be considered. We could split: Requirements (experience, education) and Skills (sourcing, interviewing, influencing, communication, continuous improvement). But the list includes skills as well. However we can make a Requirements section that includes experience and education, and a Skills section for the rest. Let's see. Requirements section content: - 2+ years of full-cycle recruiting experience. - Experience recruiting professional-level talent, ideally within Engineering, Product Management, IT, or other technical disciplines. - Bachelor's degree preferred; equivalent professional experience will also be considered. Skills section content: - Strong sourcing capabilities and experience identifying passive candidates. - Excellent interviewing, candidate assessment, and relationship-building skills. - Ability to influence and partner effectively with hiring managers, HR partners, and key stakeholders. - Strong communication, organization, and problem-solving skills. - A continuous improvement mindset with a passion for optimizing recruiting processes. That seems reasonable. Now Benefits: list as above. Pay: The pay range: "$28.00 - $31.00/hr." Also note that individual compensation depends on many factors. We should include that prose? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include the sentence about individual compensation depending on many factors. That's part of Pay section. So Pay section could have a
with that sentence, plus maybe the range as
or
- ? The range is a single value; we can put in
- for any list of duties/requirements/benefits, and
for prose. So for Pay, we have prose (the sentence about individual compensation). The range could be considered prose as well. We'll just put both in a
maybe separated by a space or line break. Could also put range in
and then another
for the factors. But we can combine. Benefits: list of items. Now we need to remove boilerplate: The sections about Aston Carter description, equal opportunity, accommodation, San Francisco Fair Chance, Massachusetts Lie Detector, Use of AI, etc. Those are legal/EEO boilerplate; remove. Also remove "Job Type & Location This is a Contract to Hire position based out of Davidson, NC." and "Workplace Type This is a hybrid position in Davidson,NC." and "Application Deadline This position is anticipated to close on Oct 12, 2026." Those are minor metadata; we should fold into a short
or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include a short paragraph at the end maybe under a generic "Details" but not a heading. Since we are not to create headings for minor metadata, we could just drop them or include them in a
without heading. The instruction says fold minor metadata into a short
or drop it. Probably we can include a short
after the sections containing location, job type, deadline. But we must not create a heading for it. So we can add a
at the end: "This is a Contract to Hire position based out of Davidson, NC. Workplace type is hybrid. Application deadline: Oct 12, 2026." That preserves info. Now ensure we don't repeat the job title as a heading. We'll not. Now produce HTML fragment. Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Pay
The pay range for this position is $28.00 - $31.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors.
Benefits
- Medical, dental & vision
- Critical Illness, Accident, and Hospital
. The instruction: Use