Program Assistant, Butterfly House

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. The posting includes summary, essential duties, core competencies, qualifications and experience, education, communication and language skills, mathematical skills, reasoning ability, computer skills, certificates, physical demands, work environment, work interactions, supervisor. Also mentions full-time position, must have ability to work evenings and weekends (schedule). No explicit pay or benefits. So we should not create Pay or Benefits sections. Schedule: we have "Must have the ability to work evenings and weekends." That's schedule info. So we can include a Schedule section with that. We need About the role: maybe summary? The summary: "The Butterfly House Program Assistant provides administrative support for the overall business operations of the Butterfly House, including acting as the registrar for visitor services, education, and events." That's about the role. Responsibilities: essential duties and responsibilities list. Requirements: maybe qualifications and experience? Could treat as Requirements. But we also have Qualifications and Experience section. We could combine? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we can have both Requirements and Qualifications if content distinct. But we can choose to have Qualifications and maybe Skills separate. The posting includes Core Competencies (skills). So we can have Skills section for core competencies. Qualifications and Experience for qualifications. Requirements maybe for minimum experience etc. But we have qualifications already includes experience. Could treat Requirements as "Must have ability to work evenings and weekends" but that's schedule. Might be better to have Requirements: Minimum of two (2) years office support or related experience required; scheduling, reservation or guest services experience preferred; prior experience with Tessitura or other CRM a plus; experience with bookkeeping/accounting system preferred; ability to complete multiple projects; ability to communicate effectively; etc. That's a lot overlapping with qualifications. But we can separate: Requirements = mandatory experience/skills; Qualifications = education, preferred etc. However the instruction: Prefer a few substantive sections over many thin ones. So maybe combine into Qualifications and Experience and Skills. Let's decide sections: - About the role (summary) - Responsibilities (essential duties) - Qualifications (education, experience, certificates) - Skills (core competencies, computer skills, communication, math, reasoning) - Schedule (ability to work evenings and weekends) - Physical Demands & Work Environment maybe combine? Could be a section "Working Conditions" but not in list. The allowed headings are limited to those examples; but we can still use other headings? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we could use others but better to stick to those. We have Physical Demands and Work Environment not in list; maybe we can omit or fold into Qualifications? Probably better to include as a section "Working Conditions" but not in allowed list; risk. Safer to omit those details? But we must preserve ALL substantive information; cannot omit. So we need to include them somewhere. Could incorporate into Qualifications or Skills? Not ideal. Could create a section "Requirements" and include physical demands there? Might be okay. We have also Work Interactions and Supervisor info; could be part of About the role or Responsibilities. We need to avoid boilerplate like EEO etc. Already removed. We need to output only HTML fragment. Let's craft:

About the role

The Butterfly House Program Assistant provides administrative support for the overall business operations of the Butterfly House, including acting as the registrar for visitor services, education, and events. This is a full‑time position requiring the ability to work evenings and weekends.

Responsibilities

• Serve as the Tessitura (CRM) administrator to schedule events, classes, program bookings, and internal meetings for the Butterfly House Team.
• Respond by phone or email to visitor requests for ticketing, education classes, events, and other programs.
• Provide guest inquiries about the Butterfly House’s offerings (program/event content, pricing, availability) in a timely manner.
• Handle communication with the public by answering all incoming phone calls directed to the operator in a professional manner; provide general information or direct callers to appropriate department extensions.
• Communicate with program and event participants through online confirmations and pre‑visit materials as necessary.
• Assist in recruiting volunteers and interns by posting opportunities online (VolunteerMatch, STLVolunteer, Handshake, etc.) and support coordination through the Garden’s volunteer management software.
• Communicate thematic changes, daily programs, and departmental announcements to staff, volunteers, and interns via bulletin boards and eNewsletters.
• Support processing of purchase orders, check requests, and invoices.
• Update the Butterfly House website to ensure information is accurate and current; collaborate with the Garden Communication Department for larger website changes as needed.
• Sort and distribute incoming mail; order general office supplies and monitor janitorial supplies.
• Support use of cloud‑based platforms including Typeform, Prospect2, Donate2, and Guide by Cell to gather information from Garden constituents and/or deliver electronic communications.
• Attend various meetings, record and distribute meeting notes; perform other department administrative tasks.
• Support departments with daily tasks such as volunteer breaks, admissions support, group check‑ins, and special event assistance.
• Follow and adhere to established policies and procedures (Employee Handbook, Garden Safety Guidelines, Department Policies).
• Behave and communicate in a manner that promotes teamwork, cooperation, and respect within the division and throughout the Garden with employees, supervisors/managers, volunteers, visitors, and others.
• Perform other duties as assigned.

Qualifications

• Minimum of two (2) years office support or related experience required.
• Scheduling, reservation, or guest services experience preferred; prior experience with Tessitura or other CRM a plus.
• Experience with bookkeeping and/or accounting system preferred.
• Ability to complete multiple projects or tasks in a timely manner.
• Ability to communicate effectively at all levels; must enjoy and feel comfortable interacting and working in close proximity to the general public in a safe and friendly manner.
• Demonstrates highest level of professional and ethical conduct; knowledge and understanding of organizational policies, procedures, and systems.
• Prior experience preferred with emphasis on working with the general public in an educational/learning setting.
• Demonstrated experience working with databases and performing record‑keeping tasks.
• Experience working in a cultural institution preferred.
• Prior experience working collaboratively with internal team members and external organizations to create commitment to common goals, prioritize, minimize obstacles, and execute realistic priorities in a professional environment.
• Ability to work independently with little instruction; coordinate and prioritize multiple tasks, set deadlines, and complete projects in a timely manner.
• Strong organizational skills; attention to detail.
• Education: High school diploma or equivalent required; Bachelor’s degree in business, education, or a related field preferred. An equivalent combination of skills, education, and experience may be considered.
• Certificates, Licenses, Registrations: Tessitura Career Accelerator Program Certificate (or ability to obtain within the first year of employment), or previous experience in Tessitura and proficiency at a Super User level.

Skills

• Communication – Listens to others and asks questions for clarification; writes clearly and presents information accurately; speaks professionally and responds well to questions; supports positive visitor relations.
• Collaboration – Demonstrates teamwork and promotes respect in the workplace; engages in problem solving and group initiatives; cooperates in implementing procedures and process improvements; strives for positive visitor experiences.
• Accountability – Demonstrates commitment to responsibilities and adaptable to changes; effectively prioritizes, troubleshoots and takes appropriate actions; follows policies and procedures, meets deadlines, quality, and safety standards; strives to proactively address visitor and internal colleagues’ concerns.
• Problem Solving – Identifies and resolves problems; includes supervisor before taking action as necessary; recommends solutions, demonstrates creativity and resourcefulness; exhibits sound and accurate judgment in decision making process; includes appropriate people in making decisions.
• Stewardship – Promotes and adheres to sustainability, safety and security protocols; fosters a culture of respect, diversity and inclusion; demonstrates effective and prudent use of Garden resources; maximizes contributions during work hours.
• Communication and Language Skills: Ability to communicate effectively in English (oral/written).
• Mathematical Skills: Basic addition, subtraction, multiplication and division; able to calculate percentages and use decimals.
• Reasoning Ability: Ability to exercise independent and reasonable problem resolution with a wide range of possible internal/external issues related to public programming with schools; ability to exercise independent and reasonable problem resolution with a wide range of visitors’ requests.
• Computer Skills: Ability to utilize computer keyboard (typing); proficiency in navigating the Internet and various PC applications including Microsoft Office Suite (PowerPoint, Excel, Word, Access, Outlook) required; experience in database management; demonstrated technical aptitude and experience, including troubleshooting, utilizing a variety of cloud‑based software platforms to support program registration and organizational capacity; ability and willingness to learn and use Tessitura (CRM) effectively, attaining a Super User level status; ability to supervise and direct others to input data; ability to analyze and troubleshoot problems in software and work with IT and other system administrators to reach a solution.

Schedule

Must have the ability to work evenings and weekends.

We might also need to include Physical Demands and Work Environment. Could add a section "Working Conditions" but not in allowed headings. Perhaps we can add a

Requirements

and include physical demands there. But we already used Requirements? Not yet. We could rename Qualifications to Requirements and keep Qualifications for education? Hmm. We have not used "Requirements" heading. We could use Requirements for mandatory experience and physical demands, and keep Qualifications for education and certificates. But we already put experience in Qualifications. Might be okay to have both Requirements and Qualifications. Let's restructure: - About the role - Responsibilities - Requirements (minimum experience, ability to work evenings/weekends, physical demands, work environment) - Qualifications (education, preferred experience, certificates) - Skills (core competencies, computer, communication, math, reasoning) - Schedule (maybe redundant if we put ability to work evenings/weekends in Requirements). But we can keep Schedule separate. We need to avoid duplication. Let's decide to put schedule in Requirements? Actually schedule is a requirement. So we can put schedule in Requirements and not have separate Schedule section. But the instruction says we can include Schedule section only if posting states it. It does state it. So we could have Schedule section. But we can also include it in Requirements; duplication not allowed. Better to have Schedule section and not repeat in Requirements. Thus Requirements will include minimum experience, physical demands, work environment. Qualifications includes education, preferred experience, certificates. Skills as before. Schedule separate. Let's extract physical demands and work environment from posting: Physical Demands: - Ability to lift up to 20 lbs. - Ability to utilize computer keyboard (typing); principally operates standard office equipment to include computers, copiers, files, fax machines. - Ability to sit for extended periods throughout work day (may sit up to 50% of work day). - May be required to perform tasks at varying heights (i.e., climb step stools, etc