Project Manager

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content. We must not repeat job title. Remove boilerplate like EEO, legal, application instructions, etc. Must preserve all substantive info. We need to parse the description. Let's extract sections: - "Who we are:" paragraph about Levata. That's about the company, maybe "About the role"? Actually "Who we are" is about company. Could be "About the role"? The instructions: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have: Description: Who we are: At Levata, we believe... (company description). Then "What You'll Do:" list of responsibilities. Then "What You'll Need:" list of requirements/qualifications/skills. Then "Who You Are" values. Then "Who We Are" again (company values). Then "What We Offer" benefits. We need to decide which sections to include. We have responsibilities: many bullet-like sentences under "What You'll Do:". We have requirements: "What You'll Need:" includes experience, skills, abilities, degree, travel. We have skills: maybe overlapping with requirements; but we can combine. We have benefits: "What We Offer" includes compensation and benefits. Pay: Not explicitly stated; only "Competitive compensation". That's vague; we should not create Pay section unless posting actually states them. It says "Competitive compensation coupled with a comprehensive benefits package". That's not a specific number; but it's still mention of compensation. The rule: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Competitive compensation" is somewhat vague but not exactly placeholder? It's still vague. Might be considered filler? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation (competitive) and benefits. So we can include Benefits section with details. Pay maybe not specific enough; we could omit Pay section because not specific numeric. Safer to omit Pay. Schedule: Not mentioned. Thus sections: About the role (maybe combine Who we are and Who we are values?), Responsibilities, Requirements (or Qualifications), Skills, Benefits. We need to avoid duplication. Let's extract substantive content: About the role / company: "Who we are: At Levata, we believe in making your journey with us seamless, impactful, and filled with opportunities to elevate your potential. As we think big, we enable what's next by leveraging our knowledge of what's possible today. Join a team where complexity doesn't mean confusion but rather a deep dive into understanding, surfacing with clear options and recommendations." Also later "Who We Are Welcome to Levata, a hub of innovation and a community that thrives on values that set us apart. At Levata, we're not just about business; we're about accelerating success, prioritizing quality, and advancing excellence inside out. Dive into a world where action is a way of life. At Levata, we believe in taking decisive steps to propel business success. We are doers, creators, and innovators inspired by challenge and change. Our commitment to building trust is unwavering, and we see your potential as our priority. Apply now and become part of a community that understands that great outcomes are the product of great collaboration. As partners in transformation, we work closely with our customers and teams to deliver extraordinary results. Everything we build, we build together." We should combine these into About the role (or About the company). Since heading "About the role" is expected, we can put that. Responsibilities: list from "What You'll Do:" includes many items. We'll turn each sentence into

. Let's extract them: - Managing complete lifecycles of complex projects including Initiation, Planning, Design, Execution, and Close. - Executing projects using the BCI PMO Methodology. - Managing multiple projects (internal and external) simultaneously. - Providing mentoring and guidance to others in the organization as it pertains to project management. - Quoting PM engagement and presenting PMO capabilities. - Review and Understand Scopes of Work (SOW) - Management of multiple complex projects, simultaneously (external and/or internal) - Running and managing customer and internal project kickoff and cadence calls - Gathering and understanding detailed customer project requirements - Creation and management of Project Workbook, including RAID log, Project Timeline, and schedule and the overall project plan - Management of project budget - Produce and manage all project-related templates and documents in accordance with the BCI PMO Methodology - Track time against projects/project tasks - Management of project issues and root cause analysis (RCA) process - Risk Management - Management of project escalations - Perform data analysis for projects, as needed - Solve problems that arise throughout a project - Prepare project status reports, internal and external, including Executive status reports, when applicable - Provide backup for other Project Managers, as needed - Provides backup to the PMO Director, as needed - Building out of the project, specific workflows - Identify and management of changes i.e., change requests - Conduct project close and reconciliations - Provide reporting and tracking, applicable to customer projects and based on the scope - Quoting project management engagements - Presenting PMO capabilities and methodology to internal and external customers - Provides support and guidance to Project Managers and Coordinators Note some duplicates: "Managing multiple projects (internal and external) simultaneously." appears twice; we can keep one. Also "Quoting PM engagement and presenting PMO capabilities." and later "Quoting project management engagements" and "Presenting PMO capabilities and methodology to internal and external customers" similar but we keep both as they are distinct. We'll deduplicate obvious exact duplicates. Now Requirements/Qualifications/Skills: "What You'll Need:" includes: - Five years of relevant experience required - Exceptional verbal, written, and presentation skills - Ability to problem solve - Ability to work effectively both independently and as part of a team - Competency in Microsoft applications including Project, Word, Excel, and Outlook - Ability to work on tight deadlines - Ability to multi-task and manage team workflow - Excellent organizational skills - Process-oriented with analytical and problem-solving abilities - Attention to detail - Bachelor's degree preferred, but not required - Ability to travel (minimal travel) in support of projects Also "Who You Are" values: take action, build trust, think BIG, make it easy, win together. Those could be considered "Skills" or "Qualifications". We could put them under Skills. We need sections: Requirements, Qualifications, Skills. We can decide to put experience, degree, travel under Requirements; skills like verbal, presentation, problem solving, teamwork, Microsoft apps, deadlines, multitask, organizational, process-oriented, analytical, attention to detail under Skills; and values under maybe "Qualifications"? But we can combine. Better: Use Requirements for mandatory experience/education; Skills for abilities and competencies; Qualifications maybe not needed. But we must only include sections with real content. We can include Requirements and Skills. Possibly also Qualifications if we have content like "Bachelor's degree preferred". That's a qualification. Let's make: - Requirements: Five years of relevant experience required; Ability to travel (minimal travel) in support of projects; Bachelor's degree preferred, but not required. - Skills: Exceptional verbal, written, and presentation skills; Ability to problem solve; Ability to work effectively both independently and as part of a team; Competency in Microsoft applications including Project, Word, Excel, and Outlook; Ability to work on tight deadlines; Ability to multi-task and manage team workflow; Excellent organizational skills; Process-oriented with analytical and problem-solving abilities; Attention to detail. - Qualifications: maybe the values? But values are more like "Who You Are". Could be considered "Qualifications". However the heading list includes Qualifications. We could put the values under Qualifications. But we need to avoid filler. The values are substantive: take action, build trust, think BIG, make it easy, win together. We'll include them as list items under Qualifications. Benefits: "What We Offer Competitive compensation coupled with a comprehensive benefits package including medical, dental, vision, life, flexible spending, 401k, holiday and paid time off, parental leave and a pre-tax transit program." We'll put that as

• items. We should not include EEO etc. Now produce HTML fragment with

  headings and

  • for lists,

    for prose. We need to decide which content is prose vs list. About the role: we have two paragraphs; we can combine into a single

    maybe. Responsibilities: list. Requirements: list. Skills: list. Qualifications: list (values). Benefits: list. We must not repeat job title. Let's craft. Check for any duplicate content: Ensure we didn't include boilerplate like "Apply now" etc. In About the role we have "Apply now and become part of a community..." that's from the second Who We Are paragraph. That is basically a call to action; might be considered boilerplate? It's not EEO/legal but it's an invitation to apply. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." "Apply now" is an application instruction. So we should remove that sentence. Also "Apply now and become part of a community..." is an application instruction. So we should exclude that. Also "Please see EEO is the Law." etc removed. Thus in About the role we should keep only the descriptive parts, not the call to action. Let's extract About the role content without calls: First paragraph: "Who we are: At Levata, we believe in making your journey with us seamless, impactful, and filled with opportunities to elevate your potential. As we think big, we enable what's next by leveraging our knowledge of what's possible today. Join a team where complexity doesn't mean confusion but rather a deep dive into understanding, surfacing with clear options and recommendations." Second paragraph (Who We Are) after that: "Welcome to Levata, a hub of innovation and a community that thrives on values that set us apart. At Levata, we're not just about business; we're about accelerating success, prioritizing quality, and advancing excellence inside out. Dive into a world where action is a way of life. At Levata, we believe in taking decisive steps to propel business success. We are doers, creators, and innovators inspired by challenge and change. Our commitment to building trust is unwavering, and we see your potential as our priority. As partners in transformation, we work closely with our customers and teams to deliver extraordinary results. Everything we build, we build together." We should remove any "Apply now" etc. There's none in that paragraph besides maybe "Dive into a world where action is a way of life." That's fine. Thus About the role can be two paragraphs combined into one

    maybe. Now Responsibilities list: we need to ensure we keep all substantive items, no duplication. Let's list unique items: 1. Managing complete lifecycles of complex projects including Initiation, Planning, Design, Execution, and Close. 2. Executing projects using the BCI PMO Methodology. 3. Managing multiple projects (internal and external) simultaneously. 4. Providing mentoring and guidance to others in the organization as it pertains to project management. 5. Quoting PM engagement and presenting PMO capabilities. 6. Review and Understand Scopes of Work (SOW) 7. Running and managing customer and internal project kickoff and cadence calls 8. Gathering and understanding detailed customer project requirements 9. Creation and management of Project Workbook, including