Project Coordinator

We need to output HTML fragment with sections: About Us? Actually "About Us" is a section heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can include other headings if content exists. Must not repeat job title as heading. Must include sections only when posting has real specific content. We need to preserve all substantive information, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also remove "About Us" maybe? It's substantive about company mission. Could be a section "About Us". Not in examples but allowed? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow similar style. Probably include "About Us", "About The Role", "Requirements", "Skills", "Benefits". Also maybe "Additional Responsibilities"? Could be part of Responsibilities. But we have a big "Requirements You Will:" which is actually responsibilities/duties. The posting includes a "Requirements" section that actually lists duties. Then later "You Have Education..." etc. That's qualifications. Then "Skills", "Attributes". Also "Benefits". Also "Pay" is mentioned in Benefits: base pay $60,000-$70,000. So we should include a Pay section? The instruction: include Pay section only if posting actually states them. It does state base pay range. So we can have a Pay section with that info. Also Schedule: they mention "MET working hours are required (9am-6pm ET)". That's schedule. So include Schedule section. We must not include placeholder/filler like "commensurate with experience". Not present. We must remove duplicated lines, boilerplate like EEO statement, at-will employment, etc. Also remove "Join Softheon, and together..." etc. Also remove "Are you ready..." etc. Also remove "Employment with Softheon is at-will..." etc. Also remove "Please note that candidates applying for this position must reside within the United States Eligibility to Work in the U.S.: ..."? That's substantive about location and work authorization; maybe keep as part of Requirements? But it's more like eligibility. Could be part of Requirements or a separate "Eligibility". But instruction: only include sections when posting has real specific content. Could incorporate into Requirements or a separate "Eligibility". However they didn't list Eligibility as example but we could include a heading like "Eligibility". But safer to fold into Requirements or a short p. Since it's about location and work auth, we could include in Requirements as bullet? But it's not a requirement per se. Might be better to create a short p after Requirements. But instruction: output only HTML fragment, no extra text. We can include a

for prose. So we can add a paragraph after Requirements about location and work auth. We must not include navigation, cookie, legal, EEO, equal-opportunity, scam-warning boilerplate. The final paragraphs about diversity, equal opportunity, at-will employment are boilerplate; remove them. Also remove duplicated lines: there may be duplicates like "Join us in revolutionizing healthcare!" appears in About Us and later? Actually appears only once. But there is also "Join Softheon, and together, we'll shape the future of healthcare in America." That's promotional; maybe remove as boilerplate? It's not legal but could be considered fluff. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Promotional marketing sentences maybe not required to remove, but we should preserve substantive information. Those sentences are somewhat fluff but not boilerplate. Might keep them in About Us? However About Us already describes mission. The later promotional sentences repeat similar content; could be considered duplicated. Safer to remove them. Also remove "Please note that the base pay shown is a guideline, and individual total compensation will vary based on factors such as candidate location, qualifications, skill level, and competencies." That's substantive about pay variation; we could keep in Pay section as note. Also remove "Please note that candidates applying for this position must reside within the United States Eligibility to Work in the U.S.: We are unable to sponsor or assist with visa-related processes. Candidates must have valid work authorization to work in the U.S. without any current or future need for employer sponsorship." That's substantive about eligibility; we should keep. Now structure:

About Us

... mission description ...

About The Role

... description ...

Responsibilities

• ... list of duties from Requirements You Will: ...

But the posting has "Requirements You Will:" which actually lists duties. Could treat as Responsibilities. Then later "You Have Education..." etc is Qualifications/Skills/Attributes. We could split into Qualifications (Education, Experience, Certifications, Knowledge) and Skills (Skills, Attributes). But we need to avoid thin sections. Could combine Education, Experience, Certifications, Knowledge into a Qualifications section with subpoints? But we must use

• for any list of duties/requirements/benefits. For prose, use

  . So we could have a Qualifications section with

  summarizing? But we must preserve all substantive information; cannot summarize away detail. So we need to keep each bullet. Could have multiple

  under a heading? Probably okay: heading then multiple
  • groups? Might be okay but could be considered multiple lists. Better to have one
    with all items; but items are of different types (education, experience, certifications, knowledge, skills, attributes). Could still be one list but might be messy. Perhaps better to have separate headings: Qualifications, Skills, Attributes. But instruction: prefer a few substantive sections over many thin ones. However we have a lot of detail; we could have Qualifications (Education, Experience, Certifications, Knowledge) as one
    with items each maybe a sentence. Then Skills and Attributes as another
    . That's three sections plus About Us, About The Role, Responsibilities, Benefits, Pay, Schedule, Eligibility. That's many sections but each substantive. We need to ensure we don't create sections with filler. All have content. Let's extract content. About Us: "Join us in revolutionizing healthcare! We build software that simplifies the process of choosing the right health insurance for individuals. Our solutions help our health plan and government customers with the administration, reporting, and operational requirements of their plans. By tackling the complexities of enrollment, administration, renewal, billing, and more, we enable our customers and partners to concentrate on advancing their core missions. Our Company Culture Our culture is built on collaboration, innovation, and appreciation. We value each employee's unique talents and contributions and understand that every individual plays a critical role in our mission to transform healthcare. Every day, we celebrate our team's dedication, creativity, and expertise, which drive us closer to our goals. At Softheon, our mission is making healthcare more affordable, accessible, and plentiful for every American. Our vision is that everyone can access and choose the healthcare they need." We could split into two paragraphs: first about mission, second about culture. Keep as

    maybe two

    tags. About The Role: "We are looking for a Project Coordinator to join our Project Management team and support the successful delivery of client-facing and internal implementation projects. In this role, you will work closely with Project Managers, Lead Project Managers, cross-functional teams, clients, and external stakeholders to help coordinate project activities, maintain project documentation, track action items, support meeting preparation, and ensure project information stays organized and up to date. A successful Project Coordinator at Softheon is highly organized, detail-oriented, proactive, and comfortable working in a fast-paced environment. This role is ideal for someone who enjoys keeping teams aligned, following up on open items, maintaining accurate documentation, and helping project teams stay on track from initiation through closing. Success in this role means project artifacts are accurate, meetings are well-prepared, action items are clearly tracked, follow-ups are timely, and Project Managers have the coordination support needed to focus on delivery oversight, client engagement, risk management, and strategic project execution." Responsibilities: The "Requirements You Will:" bullet points. Let's extract each bullet as separate

    • . The text includes many sentences; we need to break into logical items. The original has headings like "Project Coordination and Administrative Support", then paragraphs. We could treat each heading as a group of items but we need
    • for each duty. Could break each sentence into
    • . But that may be too granular but preserves detail. However we must not invent or summarize away detail; splitting sentences is okay as long as we keep all info. Could keep each paragraph as a single
    • but that may be long but still preserves detail. Probably better to keep each heading as a
    • containing the paragraph. But then we lose granularity but still all info present. The instruction: Use
      • for any list of duties/requirements/benefits. It doesn't require each sentence separate. So we can make each heading a
      • with the paragraph text. Thus Responsibilities
        • Project Coordination and Administrative Support: ... (the paragraph)
        • Meeting Coordination and Follow-Up: ...
        • Project Monitoring and Reporting Support: ...
        • Stakeholder and Cross-Functional Coordination: ...
        • Documentation and Process Support: ...
        • Risk, Issue, and Escalation Support: ...
        • Talent Management: ...
        • Additional Responsibilities: ... (on-call duty, in-person attendance, travel, time zone, state list)
        Now Qualifications: Education, Experience, Certifications, Knowledge. Could make a section "Qualifications" with
        • each bullet. Education: "Bachelor's degree in Business Administration or a related field of study." Experience: "0-2 years of experience in project coordination, project administration, implementation support, operations coordination, client support, or a related role preferred. Internship or early career experience supporting project teams, client implementations, technology delivery, healthcare operations, or SaaS environments is a plus. Experience working with health plan, government, or healthcare technology clients is a plus. Experience working with cross-functional teams or supporting multiple priorities in a fast-paced environment is preferred." Certifications: "Must complete CAPM certification within 6 months of hire, if not already certified. SAFe Agile, Lean Six Sigma, CSM preferred. Other project management, Agile, or healthcare-related certifications are a plus." Knowledge: "Basic understanding of project management concepts, including milestones, dependencies, risks, issues, action items, and status reporting. Working knowledge of Microsoft Office tools, especially Excel, Word, PowerPoint, Outlook, and Teams. Familiarity with Microsoft Project, Azure DevOps, SharePoint, Smartsheet, Jira, or similar project tracking tools is a plus. Familiarity with the Software Development Life Cycle, SaaS technology, healthcare operations, or implementation projects is a plus." Skills: "Excellent organizational and time management skills. Strong written and verbal communication skills. High attention to detail and accuracy. Ability to track multiple items at once. Strong follow-up skills and ability to keep action items moving. Ability to organize information clearly for Project Managers and stakeholders. Comfortable asking clarifying questions and escalating when ownership, deadlines, or next steps are unclear. Ability to work collaboratively with internal teams. Self-motivated, proactive, and comfortable working in a remote-first environment." Attributes: "Detail-oriented and highly organized. Collaborative and team focused. Proactive and accountable. Com