Associate, Development Operations

The user wants me to convert this job posting into clean semantic HTML following specific rules. Let me analyze the content and structure it appropriately. First, I need to identify the sections: 1. Position Summary (prose) 2. Essential Job Duties and Responsibilities (list with percentages) 3. Core Competencies (list) 4. Required Skills/Abilities (subsections: Interpersonal, Technical, Subject Matter Knowledge, Work Habits/Attributes) 5. Required Qualifications (list) 6. Preferred Qualifications (list) 7. Physical Demands (prose) 8. Benefits (list) 9. Additional info about PPGNY (prose - but this seems like boilerplate/org description) 10. EEO/AI disclaimer (boilerplate - should remove) Rules: - Use

for section headings - Use

• for lists - Use

  for prose - Don't repeat job title as heading - Don't put Job ID/requisition as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no html/body, no markdown fences Looking at the content: - Position Summary: detailed prose - Essential Job Duties: list with percentages - Core Competencies: bullet list - Required Skills/Abilities: categorized bullet lists - Required Qualifications: bullet list - Preferred Qualifications: bullet list - Physical Demands: prose - Benefits: list (explicitly stated) - PPGNY description: this is organizational boilerplate, but it's substantive info about the employer. However, the rules say remove EEO/equal-opportunity boilerplate. The PPGNY description includes mission, diversity statement, etc. This might be considered boilerplate. But it's not exactly EEO - it's about the organization. The rules say "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". The PPGNY description includes "PPGNY is committed to diversity, equity, and inclusion..." which is EEO-like. Also the AI disclaimer at the end is boilerplate. I should probably remove the organizational description and AI disclaimer as they are not specific to the job posting content. The benefits are explicitly listed, so keep that. The posting doesn't have explicit Pay or Schedule sections, so don't create them. Now structure:

  About the role

  - for Position Summary

  Responsibilities

  - for Essential Job Duties

  Competencies

  - for Core Competencies

  Requirements

  - for Required Skills/Abilities and Required Qualifications? But they are separate. Could combine under Requirements with subsections? The rules say use

  for section headings like "Requirements". Could have subsections using

  ? But rules only mention

  for section headings. Might keep as separate

  sections: "Required Skills", "Required Qualifications", "Preferred Qualifications". But "Required Skills/Abilities" has subcategories. Could make them nested lists under one "Requirements" heading. However, the rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So "Requirements" and "Qualifications" are separate example headings. I'll do: - About the role (Position Summary) - Responsibilities (Essential Job Duties) - Competencies (Core Competencies) - Skills (Required Skills/Abilities) - with sub-lists - Qualifications (Required Qualifications) - Preferred Qualifications - Physical Demands - Benefits But "Skills" and "Qualifications" are separate. The posting has "REQUIRED SKILLS/ABILITIES" and "REQUIRED QUALIFICATIONS". I'll treat "Skills" as a section and "Qualifications" as another. Also "Core Competencies" is separate. Let's map: 1. About the role: Position Summary prose 2. Responsibilities: Essential Job Duties list 3. Competencies: Core Competencies list 4. Skills: Required Skills/Abilities (with subcategories) 5. Qualifications: Required Qualifications list 6. Preferred Qualifications: Preferred Qualifications list 7. Physical Demands: prose 8. Benefits: list Now, for Skills, there are four subcategories: Interpersonal, Technical, Subject Matter Knowledge, Work Habits/Attributes. I'll make them nested lists under Skills heading. For Responsibilities, the list has percentages. Keep as list items. For Benefits, the list is given as bullet points. Now, ensure no filler. All content is substantive. Now write HTML. Note: The user said "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Associate, Development Operations". Not in the provided text? Actually the first line is "POSITION SUMMARY The Associate, Development Operations (“Associate”)...". So job title appears in summary. Not as a separate heading. So fine. Also "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." No Job ID present. Now produce HTML fragment. I'll write:

  About the role

  ...position summary text...

  Responsibilities

  • Gift processing (25%)
  • Data entry and maintenance (25%)
  • Administrative support (25%)
  • Customer Service and Donor Relations (15%)
  • Special Projects (10%)

  Competencies

  • A demonstrated commitment to PPGNY’s mission related to bodily autonomy, health equity, and gender and racial justice.
  • A demonstrated commitment to learning about and enhancing practices related to racial equity and its impact on healthcare systems.
  • Strong relationship building and communication skills, including an ability to work and build trust across cultural differences related to race, class, age, gender, gender identity and expression, sexual orientation, religion, ethnicity, national origin or ability; and to reflect on one’s personal identity with humility.

  Skills

  • Interpersonal
    • Excellent customer service and communication skills
    • Excellent interpersonal and verbal skills
    • Superior oral and written communication skills
    • Ability to develop and maintain effective, professional relationships with internal and external stakeholders
    • Ability to work effectively as part of team
    • Ability to remain focused and calm in stressful situations
  • Technical
    • Proficient in Microsoft Office Suite or similar software
    • Familiarity with donor databases, such as Raiser’s Edge
    • Familiarity with online fundraising platforms, such as EveryAction
    • Familiarity with credit card processing gateways, such as USPay
  • Subject Matter Knowledge
    • Familiarity with the principles of data entry, data health, and data management
    • Familiarity with principles of financial reporting and reconciliation for a high-volume development department
  • Work Habits/Attributes
    • Keen attention to detail
    • Excellent organizational skills
    • Outstanding time management skills, including the ability to work under deadline
    • Ability to produce high-quality work in a fast-paced environment with changing and/or competing priorities
    • Ability to exercise discretion in the handling of confidential information
    • Ability to work a flexible or extended schedule, including evenings and weekends, as operational demands require

  Qualifications

  • Minimum education: high school diploma/GED
  • Minimum work experience: none required
  • Licensures/Certifications: none required

  Preferred Qualifications

  • 1-2 years of experience providing comprehensive operations administrative support to a high-volume nonprofit Development Department

  Physical Demands

  Requires sitting for long periods of time. Periodic standing, walking, bending. Requires lifting of up to 15 pounds. Visual acuity sufficient to perform frequent work on a computer screen and review printed reports and other materials. This role routinely uses standard office equipment such as computers, phones, photocopiers, and filing cabinets. Requires the ability to hear and to communicate orally with others.

  Benefits

  • Generous PTO and holiday schedule
  • Medical, dental and vision coverage options for you and eligible dependents
  • FSA, HSA, Commuter pre-tax reimbursement funds
  • Short- and Long-Term Disability, Free Basic Life and AD&D
  • 401(k) Retirement Plan with Safe Harbor contributions after 1 year of employment
  I should also include the immunization requirement? That's in the benefits section? Actually it's after benefits: "All positions at PPGNY require: Proof of immunization..." That's a requirement, not a benefit. Could be under Qualifications or a separate note. But it's a condition of employment. Might add as a paragraph under Qualifications or separate. Since it's not a typical qualification, maybe add as a note after Benefits? But rules: include section ONLY when real specific content. This is specific. Could add a

  Requirements

  but we already have Qualifications. Could add a paragraph under Qualifications or a new section "Additional Requirements". However, the posting lists it after benefits. I'll include it as a paragraph after Benefits or under a new heading "Employment Requirements". But the rules say prefer few substantive sections. Might just add as a paragraph under Qualifications? But Qualifications already has list. Could add a

  after Qualifications list. But the heading "Qualifications" is for required qualifications. The immunization is a requirement for all positions. I'll add a separate

  Employment Requirements

  with a paragraph. But that might be too many sections. Alternatively, fold into a

  under Qualifications. Since the rules say "fold minor metadata into a short

  or drop it." This is not minor metadata; it's a requirement. But it's not a qualification per se. I'll include it as a paragraph after Benefits? Actually the benefits section ends with the list, then there's "All positions at PPGNY require: Proof of immunization..." then the PPGNY description. I'll include the immunization requirement as a paragraph under a heading "Employment Conditions" or similar. But the rules say never create sections unless posting actually states them. The posting doesn't have a heading for that. However, it's substantive info. I think it's okay to include as a paragraph under "Qualifications" or "Additional Information". But to keep clean, I'll add a

  Additional Requirements

  with a paragraph. But the rules say "Prefer a few substantive sections over many thin ones." This is a thin section. Maybe just include as a paragraph after Benefits without a heading? But the rules say use

  for section headings. Prose can be

  without heading? The example shows sections with headings. The position summary has heading "About