Operations Manager

We need to output HTML fragment with sections: About the role? Actually we have sections: About WMCAT (mission), Position Summary, Essential Duties + Responsibilities (with sub-sections: Operations, Technology, Facilities, Human Resources, Accounting), WMCAT Mission + Organizational Expectations, Requirements Preferred Experiences + Skills, Physical Demands, Additional Details (maybe not needed?), WMCAT's Values, Transportation, Benefits Pay. We must use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can adapt headings to match content. Must not repeat job title as heading. Must not include Job ID etc. Must not include boilerplate like EEO etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Resume and cover letter are required for application..." etc. Also remove "Prepared Date: September, 2026" maybe minor metadata can be folded into short

or drop it. The instruction: "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." So we can include a short

for Prepared Date maybe. We must preserve all substantive information. Must not invent or summarize away detail. Must not emit a heading followed by filler/placeholder text. Must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes Benefits and Pay: "Benefits Pay: Compensation within the listed hiring range is based on experience and nonprofit industry standards. Competitive benefits package provided, including: ..." So we need a Benefits section (maybe also Pay). The instruction says: "Prefer a few substantive sections over many thin ones." So we can combine Pay and Benefits into one Benefits section? But they said use headings like Benefits, Pay, Schedule. We can have a Benefits heading and include both pay range and benefits list. Or separate Pay and Benefits headings if both have content. The posting includes hiring range ($44,000 - $47,000) and benefits list. So we can have a Pay section with the range, and a Benefits section with the list. Or combine. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we need to ensure each heading has content. We also have Schedule: The posting includes "Status: Salary, Exempt, Full-Time, 40 hours" and "WMCAT's regular office hours are Monday - Friday, 8 a.m. - 5 p.m." Also "Transportation: Consistent personal transportation will be necessary. In-person, full-time at WMCAT: This position is in Grand Rapids, Michigan. The candidate should be comfortable working in-person as responsibilities necessitate, with flexibility for remote work at other times." So we have schedule info: full-time, 40 hours, Monday-Friday 8-5. So we can create a Schedule section. We also have Requirements: "Preferred Experiences + Skills" list. That's like Requirements/Skills. We'll create a Requirements section with

• . Also maybe Qualifications? Not separate. We have Physical Demands section: we can include as a separate section maybe "Physical Demands". Not in the list of headings but we can still use

  for any section heading; the instruction gave examples but not exclusive. So we can add Physical Demands. We have Additional Details about diversity etc. That's substantive; we could include as a section "Equal Opportunity" but that's EEO boilerplate; but the instruction says remove EEO/equal-opportunity/scam-warning boilerplate. However the Additional Details includes a statement about diversity and non-discrimination. That is essentially EEO statement. The instruction says remove EEO/equal-opportunity/... boilerplate. So we should drop that. Also the Values section is substantive; we should keep. We have Transportation section: we can include as a separate heading "Transportation". Or maybe incorporate into Schedule or Additional Details. But we have specific content: "Consistent personal transportation will be necessary. In-person, full-time at WMCAT: This position is in Grand Rapids, Michigan. The candidate should be comfortable working in-person as responsibilities necessitate, with flexibility for remote work at other times." So we can make a Transportation section. We have Benefits and Pay sections. We have About WMCAT (mission) maybe as "About the organization" but we can use "About WMCAT". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also use other headings if needed. However they said "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are examples; we can use those headings where appropriate. For About WMCAT we could use "About the organization" but not in list. Might be okay to use "About WMCAT". The instruction didn't forbid other headings; just gave examples. We'll use headings that reflect content. We must not include application instructions like "Resume and cover letter are required for application..." etc. So drop that. We must not duplicate lines. Now produce HTML fragment. Structure:

  About WMCAT

  ... mission description ...

  Position Summary

  ... summary ...

  Responsibilities

  Maybe we can have subheadings inside? But we can just list responsibilities as
  • with sub-items? The instruction: Use
    • for any list of duties/requirements/benefits. So we can have a
      for responsibilities. However responsibilities are grouped into categories (Operations, Technology, Facilities, Human Resources, Accounting). We could either keep categories as headings inside responsibilities or just list all duties as items. To preserve structure, maybe we keep categories as

      ? But they only said use

      for section headings. Could use

      for sub-sections? Not prohibited. Safer to keep categories as

      inside responsibilities section. Or we could make each category its own

      section. The instruction: "include a section ONLY when the posting has real, specific content for it". So we could make each category a separate

      section (Operations, Technology, Facilities, Human Resources, Accounting). That would be many sections but each has content. They said prefer a few substantive sections over many thin ones. So better to have one Responsibilities section with subheadings maybe

      . But they didn't forbid

      . We'll do:

      Responsibilities

      Operations

      • ...
      ...

      Technology

      ...
      ... etc. That seems okay. Then

      Mission + Organizational Expectations

      ...

      Requirements

      ... (list of preferred experiences/skills)

      Physical Demands

      ...

      Values

      ... list of values maybe as

      with line breaks? Could use
      • each value. But they are descriptive. We'll keep as

        with each value separated by
        or just as paragraphs. Simpler: keep as

        with each value sentence.

        Transportation

        ...

        Pay

        Hiring range: $44,000 - $47,000 (based on experience and nonprofit industry standards).

        Benefits

        • 15 days of PTO
        ... etc.
        We also have "Prepared Date: September, 2026" maybe as a short

        meta at top. We must not include boilerplate like EEO etc. Already removed. Check for duplicated lines: Ensure not repeating. Now craft content precisely. Let's extract each piece. About WMCAT: "The West Michigan Center for Arts + Technology (WMCAT) provides a culture of opportunity for people to make social and economic progress in their lives and community. We fulfill our mission through visual arts and tech engagement and workforce development." Position Summary: "The Operations Manager is an integral member of the team, leveraging systems and cross-organizational coordination to advance WMCAT's mission-based programming and community-facing work. This position manages WMCAT's internal operations — technology liaison and asset management, facilities, financial support (data entry, and trained backup payroll processing), and human resources support — while providing backup front-desk coverage for the Administrative Associate. The ideal candidate brings curiosity, initiative, and a systems mindset to our operations, and thrives in a collaborative environment that advances WMCAT's mission of providing equitable access to opportunity." Responsibilities: Operations: - Coordinate daily administrative and operational activities across departments, supporting program teams with logistics, reporting, and compliance needs. - Develop and implement systems to improve workflows and cross-organizational communication. - Manage relationships with vendors and contractors - Create and maintain a welcoming environment for students, families, guests, and staff. - Provide backup to the Administrative Associate by covering times away from the front desk. Technology: - Serve as the primary point of contact for technology needs experienced by students and staff, managing the relationship with WMCAT's external IT partner (troubleshoot basic issues internally and escalate more complex needs as appropriate). - Order, inventory, and maintain hardware and software across the organization, including documentation of IT assets and user access credentials - Ensure systems remain updated and secure, including antivirus protection and software patches. - Collaborate with President + CEO to operationalize AI at WMCAT, including use-case identification, ethical and human-centered guardrails, and platform standards. Facilities: - Serve as an escalation point for facility needs beyond the Administrative Associate's day-to-day scope. - Manage facilities-related vendor relationships, contracts and standards. Human Resources: - Support the hiring process, including posting positions in the talent management software, scheduling candidate interviews, and providing structure and support to hiring managers throughout onboarding and offboarding. - Coordinate timeline and process for the performance review cycle in collaboration with the President + CEO. - Administer employee benefits, including facilitating open enrollment. - Foster a positive and inclusive workplace culture in partnership with the President + CEO. - Ensure compliance with employment laws and nonprofit standards. Accounting: - Serve as a trained backup for data entry and payroll processing, when primary coverage is unavailable. - Support annual audit and coordinate with WMCAT's financial partners. Mission + Organizational Expectations: - Maintain a commitment to the mission and vision of WMCAT. - Demonstrate a willingness and desire to grow professionally, learn new skills, and contribute to a culture of inclusivity and equity. - Represent WMCAT at occasional designated events throughout the year, which may occur outside of standard scheduled hours - Desire to align with WMCAT's values (listed below). Requirements (Preferred Experiences + Skills): - Experience managing relationships with vendors or contractors. - Basic technology troubleshooting skills and comfort supporting others with tech issues. - Experience with HR functions such as recruitment, onboarding, or benefits administration. - Comfort with, or willingness to be trained in, payroll processing procedures. - Strong proficiency in working with computers and various software systems, including but not limited to Microsoft Office suite and QuickBooks Online. - Comfort working both independently and collaboratively in a mission-driven environment. - Strong organizational skills, with the ability to prioritize multiple tasks and maximize efficiency. - Strong written and verbal communication skills to connect with a diverse group of people