Employment Coordinator

We need to output HTML fragment with sections: About the role (maybe "About the role" heading), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: "Essential Duties And Responsibilities" (list). "Qualification Requirements" (list). "WORK ENVIRONMENT" (some details). "WHY SEABOARD FOODS?" (benefits list). No explicit Pay or Schedule details (just "The hours and days of work are established by departmental needs and at the discretion of management. After-hours, weekends, and overnight travel as requested." That's schedule info but vague; we should not include Schedule unless specific. It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits are stated: medical, vision & dental benefits upon hire, 401K with company match, Paid Time Off & Company Holidays, Wellness Program, Tuition reimbursement, Employee pork purchase program. So we can include Benefits. Pay not stated, so omit. Schedule not specific enough (just generic), so omit. Also we have "About Us" which could be "About the role"? Actually "About Us" is company description; we could put under "About the role" maybe? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. We have content for About the role? Could use the introductory paragraph "YOUR OPPORTUNITY ..." as about the role. We'll put that under About the role. Responsibilities: essential duties list. Requirements: maybe qualification requirements? They have "Qualification Requirements". Could map to Requirements. Qualifications: maybe "Core Competencies"? Actually they have "CORE COMPETENCIES FOR SUCCESS IN ALL ROLES:" which could be Skills. We'll treat that as Skills. Requirements could be the qualification requirements (education, experience, bilingual). Qualifications maybe could be the same? But we need to avoid duplication. We could put Qualification Requirements under Requirements, and Core Competencies under Skills. Qualifications maybe we could omit if not distinct. But we need to include sections only when posting has real specific content. We have content for Requirements (qualification requirements). We have content for Skills (core competencies). We have Benefits. We have About the role (intro). We have Responsibilities. So we will output those sections. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, etc. Also remove navigation, cookie, legal, duplicated lines. Also remove application instructions (none). Remove "Seaboard Foods is an equal opportunity employer..." etc. We need to preserve all substantive information. So we need to include the details from each section. Let's extract: About the role (intro): "We’re excited to announce an opening for an Employment Coordinator at our Guymon, OK Employment Center! We’re looking for a friendly, organized, and customer‑focused team member to serve as the first point of contact for applicants and visitors. In this role, you’ll greet candidates, manage calls, coordinate interviews, and guide applicants through key steps of the hiring and onboarding process. You’ll help maintain accurate calendars and applicant records, support staffing and employment activities, and ensure all hiring paperwork runs smoothly. This role plays a vital role in keeping our operations running strong by helping ensure our teams have the support and talent our operations need." About Us (company description) maybe could be part of About the role? But we could include as part of About the role? The instruction says About the role heading; we could include both the opportunity and About Us as description. But maybe better to keep About the role as the intro; About Us could be omitted? It's substantive about company; but not strictly about the role. However we could include it under About the role as additional context. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine About the role and About Us into About the role section. That seems fine. Responsibilities list: - Serve as the first point of contact by answering phones, greeting visitors, directing calls, screening mail, and handling routine employment inquiries. - Review applications for accuracy and completeness, verify rehire eligibility, and update applicant information in databases and spreadsheets. - Coordinate interviews, pre‑employment requirements, new‑hire paperwork, orientation schedules, and start dates with applicants and internal teams. - Maintain calendars and communicate interview, physical, and application status updates to prospective employees. - Collect required information, prepare routine reports, and ensure data accuracy and completeness. - Maintain strict confidentiality of all applicants, employment, and HR records. - Build effective working relationships while providing excellent customer service, multitasking, prioritizing tasks, and assisting with related duties, including occasional overtime or weekend work. Requirements (Qualification Requirements): - Required Associate degree is preferred in a related field. - One year or more of experience in human resources, business administration, recruiting, employment, or a related area. - Comfortable working in a high‑volume, fast‑paced hiring environment with the ability to manage multiple priorities. - At least one year of customer service experience, demonstrating strong communication and relationship‑building skills. - Bilingual in English and Spanish (required) to effectively support a diverse applicant and employee population. Also note "Reasonable accommodation may be made..." but that's boilerplate; we can keep? It's generic; maybe we can keep as part of requirements but it's not specific. Might be considered boilerplate; but it's about accommodation. Could keep but it's generic. The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Reasonable accommodation is not exactly EEO but could be considered legal boilerplate. Safer to omit. Skills (Core Competencies): - instills trust - communicates effectively - action-oriented - ensures accountability - drives results Benefits (WHY SEABOARD FOODS?): - Medical, vision & dental benefits upon hire - 401K with company match - Paid Time Off & Company Holidays - Wellness Program - Tuition reimbursement - Employee pork purchase program Also note "For a complete list of our benefits please visit our career site: https://www.seaboardfoods.com/careers/why-sbf/" That's a link; we could keep as part of benefits? It's a reference; but it's not substantive detail; maybe we can keep as a sentence? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The link is substantive? It's a reference; we could include as a

with the link. But it's not a benefit itself; it's a pointer. Could include as a note. We also have WORK ENVIRONMENT details; we didn't include a section for that. Could we include under Requirements? Not exactly. Could we add a section "Work Environment"? Not in the allowed headings list; but we could maybe include under Requirements? The instruction says use headings from list; but we could also add other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should stick to those. So we should not add Work Environment heading. However we could incorporate work environment details into Requirements or About the role? Might be a stretch. Better to omit? But we must preserve ALL substantive information. If we omit work environment details, we lose info. However maybe we can fold into Requirements as "Work environment: ..." but that's not a qualification. Could we add a section "Requirements" and include both qualification requirements and work environment? The heading Requirements could encompass both. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid adding other content under those headings. So we can put work environment details under Requirements as a paragraph. Similarly, we could put "Core Competencies" under Skills. Thus we will have sections: About the role, Responsibilities, Requirements, Skills, Benefits. We need to ensure we don't create empty sections. Now format: Use

for each heading. Then content:

for prose,

• for lists. We need to avoid repeating job title as heading. Not needed. We must not include markdown code fences. Just raw HTML. Let's craft. About the role: combine intro and About Us. Paragraphs: maybe two

  elements. Responsibilities:

  with each duty. Requirements: include qualification requirements as
  and also work environment as

  maybe. Skills:

  with core competencies. Benefits:
  with benefits list, plus maybe a

  with link. Let's write. Check for any boilerplate: remove EEO statement, remove "Reasonable accommodation may be made..." etc. Also remove "The hours and days of work are established by departmental needs..." (schedule) as we omitted Schedule section. Could we include that under Requirements? It's schedule info; but we decided not to create Schedule section. Could we include it under Requirements as a note? It's not a requirement but a condition. Might be okay to include under Requirements as additional info. But we already have a lot; maybe we can add a

  under Requirements about schedule. However the instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It doesn't forbid mentioning schedule info elsewhere. So we can include schedule details in Requirements or About the role. But it's generic; maybe we can include as a short paragraph under Requirements. Let's include schedule: "The hours and days of work are established by departmental needs and at the discretion of management. After-hours, weekends, and overnight travel as requested." Now ensure we don't repeat any duplicated lines. Now produce HTML. Let's write:

  About the role

  We’re excited to announce an opening for an Employment Coordinator at our Guymon, OK Employment Center! We’re looking for a friendly, organized, and customer‑focused team member to serve as the first point of contact for applicants and visitors. In this role, you’ll greet candidates, manage calls, coordinate interviews, and guide applicants through key steps of the hiring and onboarding process. You’ll help maintain accurate calendars and applicant records, support staffing and employment activities, and ensure all hiring paperwork runs smoothly. This role plays a vital role in keeping our operations running strong by helping ensure our teams have the support and talent our operations need.

  At Seaboard Foods, we create the most sought‑after pork. A top U.S. pork processor and leading exporter to 30+ countries, we are committed to bringing excellence to the table, seeking a better way to produce wholesome pork, and connecting every step between our farms and family tables. More than 5,400 employees in five states work on our farms, feed mills, and processing plant to produce Prairie Fresh® pork, ensuring the well‑being of our animals, the environment, our employees, and the communities we call home. Our commitment to sustainability is reflected in our renewable gas projects on our farms creating renewable energy. Owned by Seaboard Corporation, a Fortune 500 company, and nominated as one of the “Best Places to Work” by Kansas City’s Business Journal, we have a dynamic culture where our employees can contribute and understand why they matter.

  Responsibilities

  • Serve as the first point of contact by answering phones, greeting visitors, directing calls, screening mail, and handling routine employment inquiries.
  • Review applications for accuracy and completeness, verify rehire eligibility, and update applicant information in databases and spreadsheets.
  • Coordinate interviews, pre‑employment requirements, new‑hire paperwork, orientation schedules, and start dates with applicants and internal teams.