Digital Recruiting Sourcing Specialist

We need to output HTML fragment with sections: About the role? Actually headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Only include sections where posting has real specific content. Must not repeat job title. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Key sections: - Overview: includes location, pay, schedule, location requirement. Pay: $19 per hour. Schedule: Monday - Friday. Location Requirement: Candidates must reside in MT or CT zones. Also Work Location: Chicago, IL 60606 (but location requirement overrides? We'll keep both maybe). Overview also includes "Job Type Regular". We'll include Pay and Schedule sections if present. Benefits: list of benefits: Paid weekly, Next day pay on-demand with DailyPay, Eligible for Medical, Dental, and Vision Benefits plus 401K matching, Paid time off, Paid holidays, $30 Mobile Reimbursement, Scholarship Opportunities, Employee Assistance Program. - About The Job: description paragraph. - What We're Looking For: bullet list of skills/qualities. - Job Description: list of duties (multiple sentences). Could be considered Responsibilities. - Qualifications: list. - What You Can Expect From 2020 Companies: inclusive environment statement. - 2020’s Commitment: EEO statement (should be removed as boilerplate? It's EEO/equal-opportunity boilerplate; we must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should drop that section. Also "What’s in it for you?" is Benefits. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /. Use

headings,

• for lists,

  for prose. We must not repeat job title as heading. So no heading for Recruiting Admin/Digital Sourcing Specialist. We need to decide sections: About the role (maybe "About The Job") corresponds to About the role heading. Responsibilities could be Job Description. Requirements could be Qualifications? Actually Requirements and Qualifications may overlap. We can combine? But we need to follow instruction: Use headings for those categories if content exists. We have content for About the role (About The Job). Responsibilities (Job Description). Requirements (maybe "What We're Looking For" includes skills). Qualifications (Qualifications). Skills maybe also covered. Benefits (What's in it for you?). Pay and Schedule. We must not create sections with placeholder text. All sections we include must have real content. Let's extract content: About the role (About The Job): paragraph(s). The text: "In partnership with recruiting leadership, the Sourcing Specialist serves as a key operational and strategic resource supporting sourcing initiatives, workforce planning, and recruitment marketing efforts. This role is responsible for managing and optimizing job board and digital sourcing strategies, maintaining critical recruiting data and reporting, and ensuring the effective allocation of sourcing resources and spend. The Sourcing Specialist analyzes sourcing performance, monitors budget utilization, identifies opportunities for cost savings and process improvements, and provides actionable insights to leadership through data analysis and reporting. This individual will maintain recruiting systems, dashboards, and spreadsheets, ensure compliance with job posting standards, and support the execution of sourcing campaigns across job boards, social media platforms, and other recruitment channels. Success in this role requires exceptional organizational skills, strong analytical abilities, attention to detail, and the ability to prioritize competing needs in a fast-paced environment. The ideal candidate is a proactive problem solver who enjoys working with data, identifying trends, and driving continuous improvement to support recruiting goals." We'll put that in

  . Responsibilities (Job Description): list of duties. The Job Description section includes multiple sentences each starting with a verb. Could be turned into

  • . Let's extract each bullet: - Implement staffing strategies to provide a qualified and diverse candidate pool - Responsible for sourcing qualified, diverse candidates through networking, internet postings, social media and referrals - Experience with applicant tracking system hiring and reporting functions - Review applicant data reporting to identify challenges in applicant flow - Advise Management team on strategy to improve applicant flow - Develop knowledge of client(s) and management to effectively target recruitment efforts in a cost effective and efficient manner - Maintain daily work trackers as assigned and assist with tracking recruiting metrics - Maintain and distribute Excel reports as requested - Coordinate and facilitate recruitment functions, including college, job and career fairs as required - Communicate recruiting information and provide feedback on successes on areas of improvement - Perform all other duties as assigned We'll make each a
  • . Requirements: maybe "What We're Looking For" list: Organized and able to manage competing priorities, Advanced Excel and Google Sheets skills, Adaptable, resourceful, and quick to learn, Strong analytical and research capabilities, Creative, out-of-the-box problem solver, Comfortable using social media as a sourcing and engagement tool, Self-starter with excellent attention to detail. We'll put as
    • . Qualifications: list: High School Diploma or equivalent required, 2 + years of recruiting with emphasis on self-sourcing, Prior high-volume recruiting experience a plus, Intermediate working knowledge of Outlook and Microsoft Office (Word, Excel, PowerPoint), Prior experience with Workday Recruit applicant tracking system a plus, Able to work autonomously with excellent time management skills, Problem solving and think outside the box mentality. We'll put as
      • . Skills: maybe not separate; but we could combine with Requirements. However we have both Requirements and Skills headings; we could put skills under Requirements or Skills. Since we have both headings, we need to decide if we have content for Skills separate. The posting doesn't have a distinct "Skills" section besides what we already have. Could treat "What We're Looking For" as Skills. But we already used that for Requirements. Might be better to map: Requirements = Qualifications, Skills = What We're Looking For. But the instruction says use headings for those categories if content exists. We have content for both. So we can assign: - Requirements: Qualifications list. - Skills: What We're Looking For list. But then we also have "What We're Looking For" which is more about skills/attributes. So yes. Thus: Requirements (

        Requirements

        ) -> list of qualifications. Skills (

        Skills

        ) -> list of attributes/skills. We need to avoid duplication. Ensure we don't repeat same content. Let's list: Qualifications (Requirements): - High School Diploma or equivalent required - 2 + years of recruiting with emphasis on self-sourcing - Prior high-volume recruiting experience a plus - Intermediate working knowledge of Outlook and Microsoft Office (Word, Excel, PowerPoint) - Prior experience with Workday Recruit applicant tracking system a plus - Able to work autonomously with excellent time management skills - Problem solving and think outside the box mentality Skills (What We're Looking For): - Organized and able to manage competing priorities - Advanced Excel and Google Sheets skills - Adaptable, resourceful, and quick to learn - Strong analytical and research capabilities - Creative, out-of-the-box problem solver - Comfortable using social media as a sourcing and engagement tool - Self-starter with excellent attention to detail Now Benefits: list as above. Pay: $19 per hour. Schedule: Monday - Friday. Location maybe not needed as heading; we can include in a short

        under Overview? But we have no heading for Overview; we could include location and location requirement in a

        after the job title? The instruction says do not put Job ID/requisition numbers as headings — fold minor metadata into a short

        or drop it. So we can include location and location requirement in a

        maybe under a generic "Overview" but we don't have heading for Overview unless we want to use About the role? Actually we already have About the role heading. Could we include location info in a

        before About the role? The instruction says use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. So we need to place location info somewhere, maybe as a

        before the first heading or after? It says "fold minor metadata into a short

        or drop it." So we can add a

        containing location and location requirement before the first heading. That seems okay. Thus output:

        Work Location: Chicago, IL 60606. Candidates must reside in the Mountain Time (MT) or Central Time (CT) zones.

        Then

        About the role

        ...paragraph...

        Then

        Responsibilities

        • ...
        Then

        Requirements

        • ...
        Then

        Skills

        • ...
        Then

        Benefits

        • ...
        Then

        Pay

        $19 per hour

        Then

        Schedule

        Monday - Friday

        We must not include any boilerplate like EEO etc. Check that we haven't missed any substantive info: The "What You Can Expect From 2020 Companies" paragraph about inclusive environment. That is substantive; should we include? It's not covered by any heading. Could be part of About the role? But it's more about company culture. Could be included as a separate section maybe "About the company"? Not in allowed headings. The allowed headings list does not include "About the company". However we could fold it into About the role? But that might be mixing. The instruction: "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive? It says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not add other headings. Where to put the inclusive environment paragraph? Could be part of About the role? It's not about the role but about company. Could be considered part of Benefits? Not really. Could be omitted? But we must preserve ALL substantive information. So we need to include it somewhere. Perhaps we can add a

        after Benefits before Pay, without a heading, as minor metadata? But it's not minor; it's substantive. However the instruction says "Prefer a few substantive sections over many thin ones." So we could incorporate that paragraph into Benefits? Not ideal. Maybe we can add a

        About the company

        but that's not in the list; risk of being considered not allowed. The instruction says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies those are examples, not an exhaustive list. So we could use other headings if appropriate, as long as they are descriptive. However they also say "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add a heading like "Company Culture" if there is content. The inclusive environment paragraph is substantive. So we could add a

        Company Culture

        with that paragraph. But the examples list didn't include Company Culture; but it's not prohibited. The instruction says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills,