Project Manager II

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules: 1. Use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) 2. Use

• for any list of duties/requirements/benefits, and

  for prose. 3. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. 4. Preserve ALL substantive information; do NOT invent or summarize away detail. 5. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. 6. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a 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 the posting actually states them. 7. Prefer a few substantive sections over many thin ones. 8. Output ONLY the HTML fragment — no /, no markdown code fences. Now, let's analyze the job posting content: - "Our Promise To You" section: This is about AdventHealth's mission and benefits. It includes benefits list: Benefits from Day One: Medical, Dental, Vision Insurance, Life Insurance, Disability Insurance; Paid Time Off from Day One; 403-B Retirement Plan; 4 Weeks 100% Paid Parental Leave; Career Development; Whole Person Well-being Resources; Mental Health Resources and Support; Pet Benefits. This is a Benefits section. - Schedule: "Full time Shift Day (United States of America)" - this is schedule info. - Address: "601 E ROLLINS ST City ORLANDO State Florida Postal Code 32803" - location metadata. - Job Description: "Responsible for independently scoping and leading the successful management and execution of strategic initiatives..." This is the role description. - Then a list of duties: "Manages and executes strategic initiatives. Conducts observations, develops actionable plans, and implements viable solutions to problems identified. Handles change management concerns and addresses political issues that may interfere with projects. Works closely with finance to develop Business Model Calculations as required. Other duties as assigned. Maintains accurate documentation and status of project timeline and keeps team stakeholders and executive leadership informed of project status. Facilitates cross-functional meetings and discussions to address roadblocks and ensure critical milestones and deliverables are completed in a timely manner. Travels between local locations as required for meetings and observations. Prioritizes and manages multiple competing projects, deadlines, and customer relationships. Manages project costs and schedule, and alerts stakeholders to deviations in budget/schedule and resulting potential impact." This is Responsibilities. - Knowledge, Skills, And Abilities: a list of required and preferred skills. This is Skills/Requirements. - Education: Bachelor's [Required], Master's [Preferred] - Education/Qualifications. - Work Experience: "3+ proven experience managing projects, preferably in a complex organizational environment [Required] Process Improvement Experience [Preferred]" - Experience. - Licenses And Certifications: "Certified Associate in Project Management (CAPM) [Preferred] Certified Scrum Master (CSM) [Preferred]" - Certifications. - Physical Requirements: link to physical requirements. Could be a note. - Pay Range: "$60,756.80 - $113,006.40" - Pay. - Background Screening Requirement: Florida Level 2 background screening. This is legal/boilerplate? Might be considered a requirement but it's a legal requirement. The instructions say remove EEO/equal-opportunity/scam-warning boilerplate. This is a background screening requirement specific to Florida law. Might be considered a requirement. But it's also legal boilerplate. I'll include it as a note maybe. - The facility is an equal opportunity employer... that's EEO boilerplate, remove. Now, I need to structure sections with h3 headings. The user gave examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should create sections only when there is real content. Potential sections: - About the role (or Job Description) - the prose description. - Responsibilities - the list of duties. - Skills (or Knowledge, Skills, and Abilities) - the list of skills. - Qualifications (or Education) - education and experience. - Certifications - licenses and certifications. - Benefits - the benefits list. - Schedule - full time, day shift. - Pay - pay range. - Location - address (maybe fold into a short p). But the instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." The address is minor metadata, maybe include as a short p at the top or in a Location section? The user didn't list Location as a heading example, but they said "e.g." so we can add if needed. However, they prefer a few substantive sections over many thin ones. So maybe fold location into a short p at the beginning. Also, the "Our Promise To You" is essentially the company's mission and benefits. Could be an "About the Company" or "Benefits" section. Since benefits are listed, I'll create a Benefits section. The schedule is given: "Full time Shift Day (United States of America)" - that's schedule info. Pay range is given. Physical requirements link - maybe include as a note in Requirements or a separate section? But it's a link, not detailed. Could be a short p. Background screening - maybe a note. Now, I need to output HTML fragment with h3 headings, ul/li for lists, p for prose. Let's plan the HTML structure: 1. Maybe a short introductory paragraph about the company promise? But the instruction says remove boilerplate. However, "Our Promise To You" is specific to this employer and includes benefits. I'll include a Benefits section with the list. 2. Job Description: The first paragraph "Responsible for independently scoping..." is prose. Then the bullet points are responsibilities. I'll create an "About the Role" section with the prose, then a "Responsibilities" section with the list. 3. Knowledge, Skills, and Abilities: list of skills. I'll create a "Skills" section. 4. Education: list. Could be part of "Qualifications" or separate "Education". I'll create a "Qualifications" section that includes Education, Experience, and Certifications? Or separate sections. The user examples include "Qualifications" and "Requirements". I'll combine Education, Experience, Certifications into a "Qualifications" section with sub-lists? But the instruction says use ul/li for any list. I can have multiple ul under the same h3. That's fine. 5. Benefits: list. 6. Schedule: short p. 7. Pay: short p. 8. Location: short p. 9. Physical Requirements: short p with link. 10. Background Screening: short p. But the instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." They are stated, so include. Now, I need to ensure I don't duplicate. The job title is not given in the text? The user didn't provide a job title. The posting starts with "Our Promise To You". There's no explicit job title. But the instruction says "Do NOT repeat the job title as a heading (the page already shows it)". Since we don't have a job title in the input, we don't need to worry. Now, let's write the HTML. I'll start with a short paragraph for location and schedule maybe. But the user wants sections with h3. I'll create sections in logical order. Possible order: - About the Role (prose) - Responsibilities (list) - Skills (list) - Qualifications (education, experience, certifications) - Benefits (list) - Schedule (p) - Pay (p) - Location (p) - Physical Requirements (p with link) - Background Screening (p) But that's many sections. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine some. For example, Schedule and Location could be combined into a "Job Details" section? But the user examples include Schedule as a heading. I'll keep Schedule separate if it's substantive. It's just one line. Could be a p under a "Schedule" h3. That's thin. But the posting has it, so include. Similarly, Pay is one line. Benefits is a list, substantive. Qualifications includes three sub-lists: Education, Experience, Certifications. That's substantive. Skills is a long list. Responsibilities is a long list. About the Role is prose. Physical Requirements and Background Screening are minor, maybe fold into a "Additional Requirements" section? But they are not exactly requirements. Physical requirements is a link, background screening is a legal note. Could be a "Notes" section. But the instruction says include a section ONLY when the posting has real, specific content. They have specific content: a link and a statement. I'll include them as a "Additional Information" section with two paragraphs. But the user examples don't include "Additional Information". However, they said "e.g." so we can add. I'll try to keep sections as per examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. In the posting, "Knowledge, Skills, And Abilities" is essentially Skills. "Education", "Work Experience", "Licenses And Certifications" are Qualifications/Requirements. I'll map: - About the Role: the initial job description paragraph. - Responsibilities: the bullet list of duties. - Skills: the Knowledge, Skills, and Abilities list. - Qualifications: Education, Work Experience, Licenses and Certifications (maybe as sub-lists under Qualifications). - Benefits: the benefits list. - Schedule: the schedule line. - Pay: the pay range. - Location: the address (maybe as a short p at top or under a "Location" heading? Not in examples, but I'll include as a short p before sections or under a "Job Details" heading? I'll include a short paragraph at the beginning with location and schedule? But schedule is separate. I'll include a "Job Details" section with location and schedule? But the user didn't list that. I'll just put location as a short p before the first heading? The instruction says output ONLY the HTML fragment. It can start with a p. That's fine. But the instruction: "use

  for section headings". It doesn't say we cannot have a p before any h3. So I can start with a p for location. However, the user might expect the fragment to start with a heading. But it's okay. Let's structure:

  Location: 601 E Rollins St, Orlando, FL 32803

  About the Role

  Responsible for independently scoping and leading the successful management and execution of strategic initiatives. This position requires a thorough understanding of project management concepts, principles, and theories. This role prioritizes and manages multiple competing projects, deadlines, and customer relationships while interacting effectively with stakeholders at all organizational levels. Additional expectations include translating clients' perceptions of problems into viable solutions and actionable items, maintaining oversight of cost, schedule, and quality.

  Responsibilities

  • Manages and executes strategic initiatives.
  • Conducts observations, develops actionable plans, and implements viable solutions to problems identified.
  • Handles change management concerns and addresses political issues that may interfere with projects.
  • Works closely with finance to develop Business Model Calculations as required.
  • Other duties as assigned.
  • Main