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 need to parse the posting. The posting includes: - Onsite only note: "This position is onsite only. Applications for remote employment will not be considered." This is metadata; we can fold into a short

maybe. - Tagline: “COME JOIN MID-CONTINENT! “Where your work is valued—above-market pay, real work-life balance, and a team that feels like home.”” - THE POSITION… description: As a Technical Recruiter, you will be responsible for identifying, attracting, and hiring top technical talent. You’ll partner with hiring managers to understand the technical requirements, build talent pipelines, and engage with passive and active candidates using professional networks, social media, and niche platforms. To be successful in this role, you will need strong sourcing skills and a deep understanding of the technology hiring landscape. - THIS POSITION MAY BE FOR YOU IF… list of qualifications/experience: bullet list. - WE WOULD REALLY LIKE IT IF… (but it’s not a deal breaker) list of nice-to-haves. - WHAT YOU CAN EXPECT FROM ONE DAY TO THE NEXT… list of duties/responsibilities. - WE ARE ONE OF THE BEST PLACES TO WORK… description of benefits, pay, environment, perks. - WHO WE ARE… company description. - Then note about job description not exhaustive, compensation determined etc. We need to produce sections: maybe About the role (summary), Responsibilities (duties), Requirements (must-have), Qualifications (maybe education?), Skills (maybe?), Benefits, Pay, Schedule. We need to decide which sections have content. We have: - About the role: could be the THE POSITION… paragraph. - Responsibilities: WHAT YOU CAN EXPECT FROM ONE DAY TO THE NEXT… list of duties. - Requirements: THIS POSITION MAY BE FOR YOU IF… list (must-haves). Also maybe include education (bachelor's degree) and experience etc. - Qualifications: maybe the WE WOULD REALLY LIKE IT IF… (nice-to-have) could be Qualifications or Preferred Qualifications. But we have a section Qualifications; we could put nice-to-haves there. - Skills: maybe we could extract skills from requirements: strong sourcing skills, understanding technology hiring landscape, interviewing, relationship-building, Microsoft Office, attention to detail, organized, problem-solver, critical thinking, prioritization, communication. Could be a Skills section. - Benefits: WE ARE ONE OF THE BEST PLACES TO WORK… includes above-market pay, comprehensive benefits package, work-life balance, facility details, events, food drive, food truck fest, fruit/donut day, luncheons, wellness challenges, ticket raffles, small company feel. - Pay: The posting mentions "above-market pay" but not specific numbers. According to rule: do NOT create Pay section unless posting actually states them (specific). It says "above-market pay" but not a number or range. The rule: 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. "above-market pay" is somewhat vague but it's a statement about pay. Is that considered stating them? It's not a specific number but it's a statement about pay level. The rule says "unless the posting actually states them." It does state "above-market pay". That is a statement about pay, albeit not specific. I'd argue it's enough to include a Pay section with that statement. However, they also say "Prefer a few substantive sections over many thin ones." Might combine Pay and Benefits? But we have separate headings for Pay and Benefits. Could we put pay info inside Benefits? The rule says we should not create Pay section unless posting actually states them. It does state "above-market pay". So we could include a Pay section with that sentence. - Schedule: The posting says "This position is onsite only." That's schedule/location. Could be Schedule section: Onsite only. That's a statement about schedule. So we can include Schedule section with that. - Also we have a note about remote not considered. Thus we can have sections: About the role, Responsibilities, Requirements, Qualifications (nice-to-have), Skills, Benefits, Pay, Schedule. We need to ensure we don't repeat job title as heading. Not include Job ID etc. We need to use

for section headings. Use

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

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as given (maybe rephrase? but must preserve). We should not omit any bullet. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's none obvious except maybe the final sentence about job description not exhaustive and compensation determined etc. That's not boilerplate? It's part of job description but maybe we should keep? It's substantive? It's a disclaimer. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The final note is not exactly those; it's a generic disclaimer about job description. Might be considered legal boilerplate? It's about job description not exhaustive. Could be considered legal. Safer to remove? The instruction says remove legal boilerplate. That line is legal. So we should drop it. Also we need to drop duplicated lines: none. Now we need to decide how to structure content. Let's extract: About the role: The paragraph after THE POSITION…: "As a Technical Recruiter, you will be responsible for identifying, attracting, and hiring top technical talent. You’ll partner with hiring managers to understand the technical requirements, build talent pipelines, and engage with passive and active candidates using professional networks, social media, and niche platforms. To be successful in this role, you will need strong sourcing skills and a deep understanding of the technology hiring landscape." That's prose; put in

  . Responsibilities: The list under WHAT YOU CAN EXPECT FROM ONE DAY TO THE NEXT…: bullet points: - Partner with engineering and IT managers to understand technical staffing needs and job requirements - Source candidates through job boards, social media, professional networks, employee referrals, external recruiting firms, and other recruiting channels - Screen resumes and conduct interviews to assess technical and cultural fit - Coordinate interviews between candidates, external recruiting firms, and hiring teams - Manage candidate communication throughout the recruiting process and ensure a positive candidate experience - Coordinate technical internship programs - Build and maintain talent pipelines for current and future hiring needs - Represent company at college career fairs and other similar venues - Track recruiting metrics and provide regular hiring updates to key stakeholders - Stay current on industry trends, market conditions, and competitive hiring practices We need to preserve each bullet exactly. Requirements: THIS POSITION MAY BE FOR YOU IF… list: - You have a bachelor’s degree in human resources or related field. - You have a minimum of 2 years of experience in technical recruitment. - You have familiarity with applicant tracking system (ATS) and sourcing platforms. - You have strong interviewing and relationship-building skills. - You are proficient with Microsoft Office. - You have strong attention to detail. - You are organized, focused, and results oriented. - You are a problem-solver with critical thinking and prioritization skills. - You have excellent verbal, written, and interpersonal communication skills. We need to keep each bullet. Qualifications (nice-to-have): WE WOULD REALLY LIKE IT IF… (but it’s not a deal breaker) list: - You have professional certifications in recruiting or human resources. - You have company-level recruiting experience in the manufacturing industry. We need to keep each bullet. Skills: Could combine some of the requirements that are skills: strong sourcing skills, deep understanding of technology hiring landscape, interviewing and relationship-building, Microsoft Office, attention to detail, organized, problem-solver, critical thinking, prioritization, communication. But we already have those in requirements. Might be redundant. Perhaps we can create a Skills section that extracts skill-based items from requirements and responsibilities, but we must not invent or summarize away detail. If we create Skills section, we need to list skills; we could take from the requirements and responsibilities but we must not duplicate content? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but better to avoid duplication? Not explicitly prohibited. However, we might just not include Skills section if it would be thin or duplicate. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we skip Skills section and incorporate skills into Requirements or Responsibilities. But we have a heading Skills in the list of allowed headings; we can choose to include only if we have real specific content. We could create Skills section with list of skills extracted from the posting that are not already covered elsewhere? But that would be summarizing/inventing? Might be okay to list skills as they appear in the posting (like "strong sourcing skills", "deep understanding of the technology hiring landscape", "strong interviewing and relationship-building skills", "proficient with Microsoft Office", "strong attention to detail", "organized, focused, and results oriented", "problem-solver with critical thinking and prioritization skills", "excellent verbal, written, and interpersonal communication skills"). Those are already in the requirements list. If we put them in Skills, we would be duplicating. Might be okay but maybe better to not include Skills to avoid duplication and keep few sections. Benefits: WE ARE ONE OF THE BEST PLACES TO WORK… paragraph: "We provide above-market pay and a comprehensive benefits package. We promote an environment where you can excel in your career while maintaining a healthy work-life balance. Our facility is climate controlled, clean, organized, and safe. We operate in a professional, light manufacturing environment. We believe anything worth doing is worth doing right – every time. We have frequent events to keep work interesting. Our food drive is super impressive, we enjoy an annual food truck fest appreciation day, monthly fruit/donut day, employee luncheons throughout the year, wellness challenges with incentives, and frequent ticket raffles for local sporting and cultural events. We have a small company feel – even though we’re doing big things!" We need to preserve all that. Could be a

  or we could break into

  • for list of benefits? The rule: Use
    • for any list of duties/requirements/benefits, and

      for prose. Benefits section includes a list of specific perks (food drive, food truck fest, fruit/donut day, luncheons, wellness challenges, ticket raffles). Could treat as list. But also includes prose sentences. We could split: first sentences as

      , then a

      • for the specific perks. However, the rule says use
        • for any list of duties/requirements/benefits. So we should put the benefits list as
          • . The other sentences can be

            . Let's extract list: - Our food drive is super impressive - we enjoy an annual food truck fest appreciation day - monthly fruit/donut day - employee luncheons throughout the year - wellness challenges with incentives - frequent ticket raffles for local sporting and cultural events But note the original text: "Our food drive is super impressive, we enjoy an annual food truck fest appreciation day, monthly fruit/donut day, employee luncheons throughout the year, wellness challenges with incentives, and frequent ticket raffles for local sporting and cultural events." It's a sentence with commas. We could break into list items preserving the meaning. Might be okay to keep as a single