Talent Acquisition Intern

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. Content: - "What We're Looking For" intro: description about internship. - Location: Atlanta, GA - Number of positions available: 1 - Schedule: Summer 2027 - "You Will Be Involved In Daily Tasks And Projects With The Opportunity To Be Exposed To Many Different Aspects Of Talent Acquisition." Then bullet list of typical projects (list items). Let's extract. List: - Assisting with Talent Acquisition, coordinating interviews or onboarding processes - Supporting the deployment of learning and development activities - Deployment of leadership development tools and management support - Supporting the HR Director with special projects - Communication across various levels and locations - Supporting business professionals in completing daily business operations - Collaborating with team members on new ideas/innovations - Education & Experience Qualifications (maybe heading) Then "Education & Experience Qualifications" bullet list: - Using Microsoft Suite programs, LinkedIn, Cornerstone ATS, and ADP - Must be pursuing a bachelor’s degree or master’s degree from an accredited university - Major: Human Resources or related field - Preference will be given to students that do not require sponsorship - Current GPA of 3.0 or higher - You must be at least 18 years of age. Additional Details: - This is a paid internship working full-time hours (40) per week. - This is an in-person work opportunity. "Why join us?" paragraph about company. Then core values etc. We need to remove boilerplate: Equal Opportunity Employer etc. Also remove "Equal Opportunity Employer/Veterans/Disabled Agency Submissions No unsolicited agency submissions..." etc. We need to keep substantive info. We need sections: maybe About the role (intro), Responsibilities (list of tasks), Requirements (education/experience), Qualifications (maybe same as requirements?), Skills (maybe using Microsoft Suite etc), Benefits (paid internship full-time hours, in-person), Schedule (Summer 2027), Pay? Not explicitly stated salary amount, only "paid internship". The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It says paid internship but no amount. Is "paid internship" enough to create Pay section? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "paid internship". That is a statement about pay (that it's paid). However they also say "Prefer a few substantive sections over many thin ones." Might still include Pay section with statement that it's paid (no amount). But they said never create Pay/Schedule/Benefits sections unless posting actually states them. It does state it's paid, so we could include Pay section with that statement. However they also said never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Paid internship" is not filler; it's specific. So we can include Pay section with that sentence. Schedule: they gave "Schedule: Summer 2027". That's specific, so include Schedule section. Benefits: they gave "This is a paid internship working full-time hours (40) per week. This is an in-person work opportunity." That's more about schedule and benefits? Could be Benefits section: paid, full-time, in-person. But we already have Pay and Schedule sections; maybe Benefits could be other benefits like company description? But they didn't list benefits like health insurance etc. So maybe we skip Benefits section to avoid thin sections. However we have Pay and Schedule already; we could combine Pay and Schedule into one? But rule: Prefer a few substantive sections over many thin ones. Having Pay and Schedule separate may be thin but each has specific content. Could combine into "Details" but headings are prescribed: we should use those headings only if we have content. Could we omit Pay and Schedule and instead put that info in About the role or Responsibilities? The rule says use those headings for sections; but we can omit sections if not needed. However we have specific info about pay and schedule; better to include them. Thus sections: About the role (intro), Responsibilities (list of tasks), Requirements (education/experience), Skills (maybe using Microsoft Suite etc), Pay (paid internship), Schedule (Summer 2027). Possibly also Qualifications? Might be redundant with Requirements. We'll decide. Let's extract content for each. About the role: The introductory paragraph: "What We're Looking For Are you a hard-working and dedicated college student who is looking to gain valuable work experience in your field? Do you want to gain experience while learning from great mentors and leaders? Barge Design Solutions is looking for someone like you to intern with us next summer." Also location and number of positions maybe could be included here. But location and number of positions are metadata; we could 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." Location and number of positions are minor metadata; we can include them in a short paragraph under About the role or separate paragraph. Probably include them in About the role paragraph. Thus About the role

includes: "What We're Looking For Are you a hard-working and dedicated college student who is looking to gain valuable work experience in your field? Do you want to gain experience while learning from great mentors and leaders? Barge Design Solutions is looking for someone like you to intern with us next summer. Location: Atlanta, GA. Number of positions available: 1." But we should avoid repeating "What We're Looking For" as heading; we already have

About the role

. So inside we put that prose. Responsibilities: list of tasks from "You Will Be Involved In Daily Tasks And Projects..." bullet list. We'll output

• each. Requirements: education & experience qualifications: Must be pursuing bachelor's or master's degree, major HR or related, GPA 3.0+, at least 18, no sponsorship preference, using Microsoft Suite etc? Actually those are skills. We'll separate. Skills: Using Microsoft Suite programs, LinkedIn, Cornerstone ATS, and ADP. Requirements: degree pursuit, major, GPA, age, sponsorship preference. Pay: "This is a paid internship." Schedule: "Summer 2027" and also full-time hours (40) per week maybe belongs to Schedule? Actually schedule includes both timing and hours. Could put both: "Summer 2027, full-time (40 hours per week)". But we have Pay separate. We could also include in-person work opportunity maybe as Benefits? But we already have Pay and Schedule; maybe we add Benefits section for "in-person work opportunity". However that's not a benefit per se; it's work arrangement. Could be considered a benefit? Might be thin. Better to include in Schedule or About the role? Could add to Schedule: "in-person work opportunity". But schedule is about timing; location is separate. Could add a short paragraph under About the role for in-person. Given the instruction to prefer few substantive sections, maybe we combine Pay and Schedule into one section called "Details"? But headings are prescribed; we cannot create custom headings. We must use those headings if we create a section. If we want to avoid many thin sections, we could omit Pay and Schedule sections and instead include that info in About the role or Responsibilities. However the rule says: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must use all; we can choose which to include based on content. So we can include About the role, Responsibilities, Requirements, Skills. For pay and schedule we could embed in About the role or Responsibilities? Probably About the role is fine: we can mention it's a paid internship, full-time, summer 2027, in-person. Thus we avoid thin Pay and Schedule sections. Thus final sections: About the role (intro + location + number of positions + pay + schedule + in-person), Responsibilities (list), Requirements (education/experience/age/GPA/sponsorship), Skills (software/tools). Let's craft. About the role

  : "What We're Looking For Are you a hard-working and dedicated college student who is looking to gain valuable work experience in your field? Do you want to gain experience while learning from great mentors and leaders? Barge Design Solutions is looking for someone like you to intern with us next summer. Location: Atlanta, GA. Number of positions available: 1. This is a paid internship working full-time hours (40) per week. This is an in-person work opportunity." Check for duplication: we included location and number of positions. Good. Responsibilities

  with the list items. List items exactly as in posting: - Assisting with Talent Acquisition, coordinating interviews or onboarding processes - Supporting the deployment of learning and development activities - Deployment of leadership development tools and management support - Supporting the HR Director with special projects - Communication across various levels and locations - Supporting business professionals in completing daily business operations - Collaborating with team members on new ideas/innovations Make sure each is a
  • . Requirements
    : - Must be pursuing a bachelor’s degree or master’s degree from an accredited university - Major: Human Resources or related field - Preference will be given to students that do not require sponsorship - Current GPA of 3.0 or higher - You must be at least 18 years of age. Skills
    : - Using Microsoft Suite programs, LinkedIn, Cornerstone ATS, and ADP We could also include "Education & Experience Qualifications" heading but we used Requirements. Check for any other substantive content: The "Why join us?" paragraph about company description, core values, purpose. That's substantive but not fitting into prescribed headings. Could be About the role? Already used. Could be a separate section like "About the company" but not in list. The instruction: use those headings for sections; we could add a section like "About the company" but not allowed headings? The list includes examples but not exhaustive? It says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples; we could use other headings if appropriate? But better to stick to those. The company description could be considered "About the role"? Not really. Could be "About the company" but not in list. However we could incorporate that into About the role as extra prose. That would make About the role longer but still okay. Thus we can append company description to About the role paragraph after the basics. Add: "Barge Design Solutions, Inc., is an engineering and architecture firm with diverse in-house multidisciplinary practice areas. The employee-owned company is more than 650+ people strong and serves clients nationwide from multiple U.S. locations. Barge is ranked on Engineering News-Record (ENR)’s Top 500 Design Firms and Architectural Record’s Top 300 Architecture Firms and is a certified Great Place To Work®. Our Primary Purpose For Being In Business Is Ultimately To Create a Better Life By Unleashing The Potential Of Our People, Clients And Communities. This Purpose Is Supported By Our Company’s Core Values Because At The End Of The Day, Barge CARES Collaborate – Help and expect help. Teamwork is essential in what we do. Authentic – Honesty, integrity and trust are at the heart of everything we do. We are who we say we are. Responsible – We are accountable for our work, our attitude, and our actions. We make Barge better. Excellence – We go