Project Manager & Communications Specialist

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use

• for lists of duties/requirements/benefits, and

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

  or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - 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") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no /, no markdown code fences Now, let's parse the job posting: 1. "Full-time" - this is schedule info, but it's just "Full-time". Could be a Schedule section, but it's minimal. Might fold into a short p or drop. The rules say never create Schedule section unless posting actually states them. It does state "Full-time". But it's just one word. Might include as a short p in a meta section? But we shouldn't create a Schedule section for just "Full-time". Could include in a brief introductory paragraph. 2. "Our Mission" - this is about the organization, not the role. Could be "About the role" or "About the organization". The rules mention "About the role" as a heading. But this is mission statement. Might include as a prologue paragraph. 3. "Before applying, it's very important that you read..." - this is application instruction/boilerplate. Should remove. 4. "Position Summary" - this is about the role. Could be "About the role" heading with prose. 5. "Key Responsibilities" - this is responsibilities. Should be a section with sub-sections: Project Management, Recruiting & Admissions Project Management, Communications & Messaging, Events & Communications, Family Loyalty & Engagement, Staff Engagement & Internal Communications, Collateral & Print Management. Each sub-section has bullet points. Should use

  • for each bullet. 6. "Qualifications & Skills" - this is requirements/qualifications. Should be a section with bullet points. 7. "Anticipated Salary" - this is pay info. Should be a Pay section with prose. 8. "Apply Now" - application instruction, remove. Also note: "Full-time" appears at top. Could be included in a brief meta paragraph. We need to output only HTML fragment. No markdown fences. Let's structure: - Maybe start with a

    for mission and full-time? But rules: use

    for section headings. Could have "About the role" heading with position summary. Then "Responsibilities" heading with sub-sections? But the rules say use

    for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we can have sub-headings. But we can use

    ? Not specified. The rules only mention

    for section headings. Could use

    for each major section, and within responsibilities, use

    for sub-sections? But the rules don't forbid other heading levels. However, they say "use

    for section headings". Might be okay to use

    for each major section, and for sub-sections use

    or just bold? But they want semantic HTML. Probably best to use

    for each major section, and for sub-sections within responsibilities, we can use

    or just ? The rules don't specify. But they said "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". That suggests those are the only sections we should have. But the posting has multiple responsibility categories. Could combine all responsibilities under one "Responsibilities" section with a list of bullet points, but they are grouped. Could keep the groupings as sub-lists with bold labels? But the rules say use

    • for any list of duties/requirements/benefits. Could make a single list with nested lists? That might be messy. Better: Use

      for "Responsibilities" and then for each sub-category, use a

      (though not specified) or a with a nested

      . Since the rules don't forbid

      , I think it's acceptable. But to be safe, maybe use

      for each sub-category? That would create many sections. The rules say "Prefer a few substantive sections over many thin ones." So maybe combine all responsibilities into one section with sub-headings using

      or just bold. I'll use

      for major sections: "About the role", "Responsibilities", "Qualifications", "Pay". For responsibilities, I'll use

      for each sub-category (Project Management, Recruiting & Admissions Project Management, etc.) and then

      • for each bullet. But the rules say "use

        for section headings". It doesn't say we cannot use other headings. I'll assume it's okay. Alternatively, we could make each sub-category a separate

        section, but that would be many thin sections. The rules say prefer a few substantive sections. So I'll keep one Responsibilities section with sub-headings. Let's draft: First, a brief intro paragraph about mission and full-time? The mission is part of the posting. Could include under "About the role" or separate "About the organization". The rules mention "About the role" as a heading. I'll create "About the role" with the mission and position summary. But the mission is about the organization, not the role. However, it's part of the posting. I'll include it as a paragraph before the position summary. Let's structure:

        About the role

        Full-time position. [Mission statement...]

        Position summary...

        But the mission is long. Could include as a paragraph. Then

        Responsibilities

        Project Management

        • ...

        Recruiting & Admissions Project Management

        • ...
        ... etc. Then

        Qualifications

        • ...
        Then

        Pay

        Anticipated salary: $53,000-$58,000 based on experience.

        We should remove "Apply Now" and the boilerplate about reading mission & values etc. Also note: "Full-time" is at the very top. Could be included in a meta paragraph. Might add a

        at top: "Full-time position." But the rules say do not put Job ID/requisition numbers as headings — fold minor metadata into a short

        or drop it. "Full-time" is schedule metadata. Could fold into a short

        at the beginning. I'll include a

        at the start: "Full-time position." Then the mission. But the mission is not about the role. However, it's part of the posting. I'll include it under "About the role" as context. Let's write the HTML. Be careful to preserve all substantive information. Don't summarize. Now, let's extract bullet points from each sub-section. From "Project Management": - Serve as Marketing’s Project Manager for work across all Hope departments; including: Development, Recruiting & Admissions, Academics / school-wide events - Process marketing project requests and clarify objectives, timelines and deliverables - Build and maintain project plans, timelines, task lists, and deliverables for assigned projects. - Use Basecamp or the department's designated project-management software. From "Recruiting & Admissions Project Management": - Serve as Marketing’s lead with Recruiting & Admissions department - Manage Recruiting-related projects, lead meetings, drive decisions, optimize marketing effectiveness and manage all Recruiting-related marketing projects; hold Recruiting team accountable to meet deadlines and deliverables - Support the Manager of Marketing, Design and Brand in keeping enrollment marketing initiatives aligned with broader marketing strategy. From "Communications & Messaging": - Plan, write, and coordinate clear, engaging and mission-aligned communications for Hope Academy, including: Hope Happenings, Family communications, Key all-staff communications, Event communications - Develop communication plans for major initiatives, determining appropriate audiences, messages, channels, timing, and frequency. - Work with school leaders and departments to gather information and translate it into clear, audience-appropriate communications. - Coordinate translation and multilingual communications as needed. - Maintain communication calendars and establish strategic communication rhythms. From "Events & Communications": - Provide project-management and communications support for Development and school-wide events and initiatives. - Coordinate marketing deliverables for events - Help establish and maintain a consistent process for Marketing's involvement in events. From "Family Loyalty & Engagement": - Help execute the family loyalty and engagement plan to strengthen families' connection to Hope Academy and increase their sense of belonging, trust, and investment in the school community. - Identify and write stories, moments, celebrations, student experiences, parent voices, and other content. From "Staff Engagement & Internal Communications": - Help execute the staff loyalty and engagement marketing plan focusing on content that reminds staff of the mission and impact of their work. - Cultivate and write stories of student impact, staff excellence, answered prayers, community impact, and other moments that inspire and encourage employees. - Help establish clear distinctions between information that staff need to know and content that helps staff feel connected, inspired, and invested. From "Collateral & Print Management": - Serve as the primary coordinator for collateral requests and production needs. - Maintain an organized inventory of current collateral and identify when materials need to be updated, reordered, or retired. - Coordinate with the Manager of Marketing, Design and Brand on creative direction, design, and brand standards. - Prepare final files and coordinate production with print vendors. - Manage print production timelines, proofs, quantities, shipping, and delivery. Qualifications & Skills: - Bachelor's degree with 2-4 years experience in communications, marketing, public relations, journalism, project management, or a related field preferred. - Demonstrated experience managing multiple projects with competing priorities and deadlines. - Strong organizational, writing, editing, and proofreading skills. - Excellent organizational and follow-through skills. - Strong interpersonal, communication and relationship-building skills. - Experience coordinating print production and working with vendors preferred. - Proficiency with Basecamp or another project-management platform is required. - Strong proficiency with Microsoft Office, Google Workspace, or comparable productivity tools. - Ability to learn and effectively use new technology and organizational systems. - Strong attention to detail without losing sight of the larger purpose and strategic objective. - Supportive of the school's mission to foster hope in God within the inner-city neighborhood of Minneapolis by providing youth with an outstanding, Christ-centered education. Anticipated Salary: The salary for this role is expected to be approximately $53,000-$58,000 based on experience. Now, produce HTML. I'll start with a

        for "Full-time position." Then maybe a

        for the mission statement? But the mission statement is long. Could include as a paragraph under "About the role". I'll create an "About the role" section with the mission and