University Recruiter II

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Posting text: "University Recruiter II – N Reading, MA Are you seeking new challenges in your career? Embark on a new chapter and unleash your potential with Search Wizards, a leading global provider of talent solutions. If you have a passion for overcoming complex challenges and making a lasting impact on the organizations you work with, then this is the place for you. With a proven track record of matching your talent with the most sought-after companies across all industries , Search Wizards believe s in the power of connecting top talent with meaningful career opportunities. Start your journey with us today and take the first step towards a challenging and fulfilling career where opportunities for growth and professional development are endless. Excited yet? Us too! We currently have a very exciting opportunity available with our client for a University Recruiter II in N Reading, MA . This will begin as a 5 -month contract with the possibility of extension ." Then "Responsibilities" list. Then "Required Qualifications" list. Then "Pay Range" line. Then "Search Wizards is an equal opportunity employer." etc. Then "Search Wizards is known for its pioneering efforts and niche focus on Talent Solutions. We offer competitive rates, an excellent benefits package (healthcare and 401k), ongoing education, and more." Then "Consumer Privacy Notice Job ID: KB906034399" We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove "Search Wizards is an equal opportunity employer." Also remove "Consumer Privacy Notice Job ID: ..." maybe keep Job ID? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short

with Job ID maybe, but it's minor metadata. Could drop it. Probably drop it. We need to preserve all substantive information. So we need sections: About the role (intro paragraph), Responsibilities (list), Requirements/Qualifications (maybe combine? The posting has "Required Qualifications". Could treat as Qualifications. Also there is "Required Qualifications" includes experience, education, etc. Also there is "Skills" maybe not explicit. Could combine qualifications and skills? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include a section only when posting has real specific content for it. So we need to decide which sections we have content for. We have: - About the role: The introductory paragraph describing the role, company, contract length, location. That's substantive. - Responsibilities: bullet list of duties. - Requirements: maybe we have "Required Qualifications" which includes experience, etc. Could map to Requirements or Qualifications. The instruction says we can have both Requirements and Qualifications sections if content exists. But we need to avoid thin sections. The posting includes qualifications like years of experience, specific experience, education, ability to work onsite, etc. That's qualifications. Could also include skills like project management, communication, attention to detail. Those could go under Skills. But we could combine qualifications and skills into one Qualifications section. However we have to follow instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section called Qualifications (or Requirements). But we need to use heading exactly as given: e.g., Requirements, Qualifications. We could choose to use Qualifications heading and put all qualification-related content there. Or we could use Requirements heading for experience/education and Skills heading for soft skills. But that might be thin. Better: Use Qualifications heading for all qualification-related content (experience, education, skills). Then we don't need separate Requirements or Skills. Pay: we have pay range: $47.47 to 52.47 per hour. So we can include Pay section. Benefits: we have "excellent benefits package (healthcare and 401k), ongoing education, and more." Also "competitive rates". So we have benefits content. Schedule: we have "Ability to work onsite in North Reading, MA, five days per week." That's schedule info (onsite, 5 days/week). Also contract length 5-month with possible extension. That could be schedule? Could be schedule or maybe not. The posting mentions contract length; schedule could be work schedule (onsite 5 days/week). We'll include Schedule section with that info. We also have location: N Reading, MA. Already in About the role. We need to remove duplicated lines, boilerplate. Now construct HTML:

About the role

...

Then

Responsibilities

• ...

Then

Qualifications

• ...

(or

for prose? The instruction: Use

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

  for prose. So if we have a list, use ul/li. For qualifications we have a list of items; we can use ul/li. Then

  Benefits

  • ...
  (benefits list) Then

  Pay

  Pay range: $47.47 to $52.47 per hour.

  Then

  Schedule

  Onsite work in North Reading, MA, five days per week. Initial 5‑month contract with possibility of extension.

  We need to ensure we preserve all substantive information from responsibilities list, qualifications list, benefits, etc. Let's extract responsibilities list exactly as posted: "Lead sourcing and recruiting efforts for highly specialized early-career technical roles. Recruit top talent across areas including Artificial Intelligence, Machine Learning, Robotics, Software Engineering, Hardware Engineering, Silicon/Chip Design, Quantum Computing, and Science. Manage full-cycle recruiting activities from sourcing and candidate engagement through interview coordination and selection. Lead end-to-end recruiting programs with high-level business visibility. Develop and execute campus recruiting strategies and initiatives. Support internship, co-op, new graduate, and university talent pipeline programs. Build, manage, and maintain strong candidate pipelines to meet hiring goals and recruiting targets. Partner with internal recruiting teams and stakeholders to develop and execute recruiting strategies. Track, analyze, and report recruiting metrics, candidate activity, and program performance. Use data and performance metrics to identify trends, monitor progress, and support recruiting decisions. Lead recruiting projects from planning through execution, ensuring deadlines and deliverables are met. Coordinate campus recruiting events and initiatives, including strategy, execution, and follow-up. Conduct data reconciliation and maintain accurate recruiting and candidate information. Research and provide competitive intelligence related to technical and university talent markets. Manage multiple priorities and recruiting programs while maintaining a high level of quality and attention to detail. Collaborate effectively with a distributed team across multiple locations and time zones. Demonstrate strong ownership, judgment, and bias for action in a fast-paced technical recruiting environment." We need to put each as
• . Qualifications list: extract from "Required Qualifications" paragraph: "5-8 + years of recruiting and/or sourcing experience, preferably within the technology industry. Demonstrated experience recruiting for highly specialized technical roles. Experience recruiting Software Development Engineers (SDEs), Hardware Development Engineers (HDEs), Scientists, or similarly specialized technical professionals. Proven experience with sourcing and/or full-cycle recruiting within specialized technology domains. Experience supporting or leading recruiting programs with multiple stakeholders and competing priorities. Demonstrated ability to independently manage projects from planning through execution and completion. Strong experience tracking, analyzing, and reporting recruiting data and performance metrics. Experience developing or executing campus, university, early-career, or high-volume recruiting programs is preferred. Previous experience recruiting within a major technology company or similarly technical environment is preferred. Strong project management, organizational, and prioritization skills. Excellent written and verbal communication skills with the ability to collaborate across teams and time zones. Strong attention to detail and ability to maintain accurate candidate, recruiting, and program data. Bachelor's degree in a relevant field may be required, along with 5–8+ years of relevant experience. Ability to work onsite in North Reading, MA, five days per week. Candidates without demonstrated technical recruiting experience will not be considered." Note: The last two items about onsite and experience are also schedule/qualification. We'll keep them in qualifications list; but we also have schedule section. Might duplicate. Better to move onsite and schedule to Schedule section, and keep qualifications list without those. However we need to preserve all substantive information; we can keep them in qualifications but also mention schedule separately? Might duplicate. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplicate lines should be removed. So we should not duplicate the same info in two places. So we need to decide where to place each piece. The onsite ability and five days per week is schedule info; also it's a qualification (ability to work onsite). Could be placed under Schedule, and we can omit from qualifications list to avoid duplication. Similarly, the contract length (5-month) is schedule info; we can put under Schedule. Thus qualifications list will exclude those two items. Now benefits list: from "Search Wizards is known for its pioneering efforts and niche focus on Talent Solutions. We offer competitive rates, an excellent benefits package (healthcare and 401k), ongoing education, and more." We can extract benefits: competitive rates, excellent benefits package (healthcare and 401k), ongoing education, and more. Could list as items: Competitive rates; Excellent benefits package (healthcare and 401k); Ongoing education; Other benefits (more). But we should not invent details. We can keep as a prose paragraph? The instruction: Use
  • for any list of duties/requirements/benefits. So we need to make a list. We can break into items: Competitive rates; Excellent benefits package (healthcare and 401k); Ongoing education; Other benefits (as mentioned "and more"). However "and more" is vague; maybe we keep as a single item "Other benefits". But we should not invent. Could keep as a paragraph

    but instruction says use list for benefits. We'll make a list with the three concrete items: Competitive rates; Excellent benefits package (healthcare and 401k); Ongoing education. The "and more" is extra but we could include as "Additional benefits". Might be okay. Now About the role paragraph: combine the intro sentences before responsibilities. Let's extract: "University Recruiter II – N Reading, MA Are you seeking new challenges in your career? Embark on a new chapter and unleash your potential with Search Wizards, a leading global provider of talent solutions. If you have a passion for overcoming complex challenges and making a lasting impact on the organizations you work with, then this is the place for you. With a proven track record of matching your talent with the most sought-after companies across all industries , Search Wizards believe s in the power of connecting top talent with meaningful career opportunities. Start your journey with us today and take the first step towards a challenging and fulfilling career where opportunities for growth and professional development are endless. Excited yet? Us too! We currently have a very exciting opportunity available with our client for a University Recruiter II in N Reading, MA . This will begin as a 5 -month contract with the possibility of extension ." We need to clean up formatting: remove extra spaces, fix punctuation. Keep the substance. We'll produce a paragraph. Now Pay: we have "Pay range Pay range for this position will be $ 47.47 to 52.47 per hour . Compensation will vary depending