Wastewater Business Development (SC, NC, GA)

We need to output only HTML fragment with sections for headings where content exists. We need to parse the job posting: It's about a Business Development role? The text includes "About Operators Unlimited" description, then "Our Purpose", "Our Mission", "Our Core Values", then "What you OWN (Responsible For)", then "Education/Experience", then "Physical Requirements", then "Our ideal Business Development candidate will have the following capabilities and skills:", then "What you need to SUCCEED (Core Competencies)", then "What WINNING looks like (Reviewed On)", then "Additional Information". We need to reformat into semantic HTML using

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading (none given). We must not put Job ID/requisition numbers as headings (none). We must preserve all substantive info; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. Not present. Remove duplicated lines. We need to include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. The posting does not mention Pay, Benefits, Schedule explicitly. There's mention of travel (75% travel) but not schedule. No pay or benefits. So we should not include Pay, Benefits, Schedule sections. We need sections like About the role? The posting includes "About Operators Unlimited" description; we could map that to "About the role" maybe? But the instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we can use those headings if appropriate. We need to map content to these headings. We have: - About the role: could be the company description and mission etc. Or maybe "About Operators Unlimited". We'll put that under

About the role

. - Responsibilities: from "What you OWN (Responsible For)" and maybe "What you need to SUCCEED (Core Competencies)"? Actually responsibilities are duties. The "What you OWN (Responsible For)" includes bullet points? It's a paragraph: "Are you ready to take part in our mission? Read more about what it takes to be part of our team! At Operators Unlimited, we equally weigh a person’s potential value and current strengths with their direct experience and track record of success." Then Education/Experience list. That seems more like qualifications. Responsibilities might be the bullet list under "What you need to SUCCEED (Core Competencies)" and "What WINNING looks like (Reviewed On)". Those are duties and performance metrics. - Requirements: could be Education/Experience and Physical Requirements. - Qualifications: maybe overlapping with Requirements. But we need to avoid duplication. Perhaps we can combine Education/Experience and Physical Requirements under Requirements. Qualifications could be the "Our ideal Business Development candidate will have the following capabilities and skills:" list. - Skills: maybe the core competencies list. We need to decide a clean structure that preserves all substantive info. We must not invent sections; we must only include sections where there is real content. So we need to decide which of the example headings we actually have content for. We definitely have content for: - About the role (company overview, mission, values) - Responsibilities (duties: lead generation, account strategies, prospecting, managing resources, executive relationships, multiple sales cycles, interpersonal skills, pipeline building, action oriented, business acumen, customer focus, timely decision quality, learning on fly, perseverance, plan accurately, living out core values, achieving sales goals, etc.) - Requirements (education/experience: BS/BA preferred, 15 years sales experience, knowledge selling solutions, consultative approach, book of business in SC/NC/GA, metal finishing background preferred, ability to sell to all levels, experience with entire sales cycle, CRM documentation, proven track record meeting goals, driven by high commission, forecasting, intermediate MS Office, problem solving, communication, organization, time management) - Physical Requirements (lift 50 pounds, 75% travel, stooping/bending/kneeling, ascend/descend ladders, walk through large facilities, work in environmental settings) - Qualifications/Skills: maybe combine "Our ideal Business Development candidate will have the following capabilities and skills:" list (representing company mission/values, staying abreast of technical applications, aligning solution to customer needs) plus core competencies list (which is essentially skills). Could treat core competencies as Skills. We need to avoid duplication: The core competencies list includes many items that overlap with responsibilities. But we must preserve all substantive info; we can't omit. We could put responsibilities as a

of duties, and core competencies as a
of skills/competencies. That's okay even if some overlap. We must not create Pay/Benefits/Schedule sections. Thus final HTML:

About the role

... company description ...

Responsibilities

• ... each duty ...

Requirements

• ... education/experience ...

Physical Requirements

• ... physical ...

Skills

• ... core competencies ...
But we also have "What you need to SUCCEED (Core Competencies)" and "What WINNING looks like (Reviewed On)" which are essentially responsibilities and performance metrics. We could merge them under Responsibilities. We also have "Our ideal Business Development candidate will have the following capabilities and skills:" which could be under Qualifications or Skills. Since we already have Skills, maybe put that under Qualifications. Let's decide: - About the role: company overview, mission, purpose, core values. - Responsibilities: the bullet list from "What you need to SUCCEED (Core Competencies)" and "What WINNING looks like (Reviewed On)" plus maybe the "representing company..." from ideal candidate list? Actually that is more of a qualification. - Requirements: Education/Experience list. - Qualifications: "Our ideal Business Development candidate will have the following capabilities and skills:" list. - Skills: core competencies list (maybe same as qualifications). But to avoid duplication, we could treat the ideal candidate list as Qualifications, and core competencies as Skills. But we need to ensure we don't create thin sections. Let's see the content volume. We'll produce:

About the role

Operators Unlimited was formed in 2001 to offer unsurpassed service to the water and wastewater industry. Located in Upstate South Carolina, Operators Unlimited has worked hard over the years to build a reputation of excellence in the wastewater community. ... (continue with purpose, mission, core values). We'll need to include all that descriptive text. We must preserve all substantive information; we cannot omit any detail. So we need to include the entire "About Operators Unlimited" paragraph, "Our Purpose", "Our Mission is Transformation", "Our Core Values" sections (Act with Agility, Own your Responsibility, Pursue Growth, Live with Thankfulness). Also the "Why?...because we believe in our mission." etc. We need to include all that as prose under About the role. Then Responsibilities: we need to list each duty from the "What you need to SUCCEED (Core Competencies)" and "What WINNING looks like (Reviewed On)" plus maybe the "representing company..." from ideal candidate? Actually that is more of a qualification but could be responsibility. We'll decide to put under Responsibilities the list of duties: develop strong prospect relationships, work collaboratively, follow lead generation strategy, be responsible for defined role in sales cycle, proactively manage resources, ability to establish/executive level customer relationships, ability to handle multiple complex sales cycles, strong interpersonal/communication skills, be a relentless hunter, travel to customer locations, be action oriented, have business acumen, be customer focused, possess timely decision quality, learning on the fly, perseverance, plan accurately, living out core values, you get your role etc., achieving sales goals/metrics, achieving quarterly rocks, following sales process, implementing solutions. We need to capture each bullet as

• . Then Requirements: Education/Experience list (the bullet points under Education/Experience). Also maybe include "Physical Requirements" as separate section. Physical Requirements: list bullet points. Qualifications: "Our ideal Business Development candidate will have the following capabilities and skills:" list (the bullet points after that). We'll put under

  Qualifications

  . Skills: maybe we can omit if we think Qualifications covers skills. But we need to avoid duplication. The core competencies list is extensive and could be considered Skills. However we already used many of those as Responsibilities. To avoid duplication, we could treat core competencies as Skills and not duplicate them under Responsibilities. But then we would lose the duty descriptions. However the duty descriptions are similar but not identical; many are phrased as responsibilities. The core competencies list includes items like "Develop strong prospect relationships during the lead generation process..." which is essentially a duty. So there is overlap. We need to preserve all substantive info; duplication is okay as long as we don't omit. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication. So we can include both sections even if overlapping. Thus we can have: - Responsibilities: list from "What you need to SUCCEED (Core Competencies)" and "What WINNING looks like (Reviewed On)" (maybe combined). - Skills: list from core competencies (the same list) - but that would be duplicate. Might be considered thin? But we have substantive content. Alternatively, we could merge them into one section called Responsibilities & Skills, but the instruction says use headings like Responsibilities, Skills etc. We could still have both. We need to avoid creating sections with filler/placeholder text. We have real content for both. Thus final HTML will have sections: About the role, Responsibilities, Requirements, Physical Requirements, Qualifications, Skills. We must not include Benefits, Pay, Schedule. Now we need to format the content. We need to extract the exact text from the posting, preserving details. Let's copy the relevant sections. About Operators Unlimited: "About Operators Unlimited Operators Unlimited was formed in 2001 to offer unsurpassed service to the water and wastewater industry. Located in Upstate South Carolina, Operators Unlimited has worked hard over the years to build a reputation of excellence in the wastewater community. Why?...because we believe in our mission. Our Purpose Operators Unlimited exists to glorify God by helping people have a better day. Our Mission is Transformation At Operators Unlimited, we clean dirty water with a refreshing approach to wastewater treatment. Transformation is why customers need us, people want to work for us, and the community continues to welcome us. By helping companies remove contaminants from water, we protect the lives of others and preserve our shared environment. Whether we are purifying water through our products, providing exceptional customer service with ouroperators, or encouraging the professional development of our team and industry, we strive to transform the environment through the lives we touch. We are determined to revolutionize the way people think about wastewater treatment. Through our actions, we seek to elevate the impersonal into relational, the replaceable into remarkable, and the transactional into transformative. Our Core Values Act with Agility Agility is our superpower: we fearlessly embrace challenges and strive for efficiency without ever sacrificing quality. We push ourselves to exceed the expectations of our customers and to think quickly on our feet. Flexibility is the key to our shared success. Own