Operations Associate

About the role

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 - 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 - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no /, no markdown code fences 2. **Analyze the Job Posting:** Let me extract the meaningful content, structure it, and identify sections. Key parts: - Organization: The League of Credit Unions & Affiliates (The League) - Role: full-time Operations Associate - Summary/Intro: seeking dependable, service-oriented professional, fast-paced, welcoming workplace, ideal candidate traits - Role description: Operations Associate, support CUHVA, building maintenance, tenant experience, workplace readiness, cross-functional support - Responsibilities (bullet points): * Workplace Operations and Facility Support: maintain clean/safe/welcoming, routine walkthroughs, identify maintenance needs, coordinate service requests/work orders/vendor support, daily readiness (opening/closing, shared spaces, conference rooms, common areas), receive/sort/distribute mail/packages * Tenant, Employee And Visitor Experience: friendly/responsive point of contact, exceptional customer service, support room reservations/meetings/training/sessions/events, assist with tenant onboarding (access, orientation, procedures) * Operational & Administrative Support: partner with Operations team/departments, support day-to-day initiatives, coordinate vendors (cleaning, maintenance, utilities), order/stock/maintain workplace supplies, keep basic operational records/service schedules * Event & Meeting Coordination: coordinate room layouts/logistics for meetings/trainings/special events, set up/break down tables/chairs/equipment/event spaces, coordinate catering/food orders for internal meetings/employee events/org gatherings - Qualifications/Requirements: * High school diploma or equivalent required * 1-3 years experience in facilities support, workplace operations, tenant services, or related role preferred * Work Schedule: based onsite in downtown Richmond, VA; occasional travel required; flexibility to work occasional evenings/outside regular hours; valid driver's license; ability to travel by automobile and airline - How To Apply: brief online application () Now, map to required sections per rules: - Allowed heading tags:

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Must NOT create section if no real content - Must NOT repeat job title as heading - Must NOT put Job ID/requisition as headings - Preserve ALL substantive info - Remove boilerplate: EEO, equal-opportunity, scam-warning, navigation, cookie, application instructions (but "How To Apply" has substantive steps, but rule says "Remove... application instructions". Wait: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So I should remove application instructions. But the "How To Apply" section has specific steps. I'll remove it per rule.) - Pay/Schedule/Benefits sections ONLY if posting actually states them. It does state schedule details and benefits. But rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule and benefits. However, rule also: "Prefer a few substantive sections over many thin ones." and "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The benefits and schedule have specific content, so I can include them. But I need to be careful about "Skills" section - the posting doesn't explicitly have a "Skills" section, but has qualifications/requirements. I'll map appropriately. Let's identify which sections to include based on actual content: - "About the role" / introductory summary: yes, there's substantive content - "Responsibilities": yes, multiple bullet points - "Requirements" / "Qualifications": yes, high school diploma, experience preferred - "Skills": not explicitly a separate section; the qualifications imply skills. I could fold into Requirements or omit. Rule: prefer few substantive sections. I'll maybe combine qualifications and skills, or just have Requirements. The allowed headings list includes "Skills", but if there's no explicit skills section, I shouldn't invent one. I'll check if there are skill descriptions. The posting says "ideal candidate is highly organized, detail-oriented, and proactive, with the ability to manage multiple priorities, provide exceptional service, and support the day-to-day operations". That could go under Qualifications or a brief Skills section, but I'll be cautious. I'll include a Qualifications section that covers the requirements, and maybe fold the "ideal candidate" traits into it. Or I can create a "Qualifications" section with the listed requirements, and not a separate "Skills" section unless it's substantial. I'll see. - "Benefits": yes, comprehensive list with specific items - "Schedule": yes, work schedule details are specific - "Pay": not mentioned. Rule: never create Pay section unless posting actually states it. So I will NOT include a Pay section. - "About the role": the posting has a role description summary. I'll use that. Now, map the content to HTML structure: Allowed headings:

for: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule I need to decide which to use. I'll use: - About the role (intro/summary) - Responsibilities - Requirements (or Qualifications; the posting has "What You Need To Be Qualified For This Job" which lists diploma and experience) - Benefits - Schedule I'll skip Skills as a separate heading if not explicit. I'll fold the "ideal candidate" traits into Requirements or Responsibilities description. Actually, the posting has a section "What You Need To Be Qualified For This Job" - that's Requirements/Qualifications. I'll use

Requirements

or

Qualifications

. The rules list both; I'll pick one. I think "Requirements" fits the content. But the rule example says "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule" - these are examples. I can use either. I'll use

Requirements

for the diploma/experience part, and maybe combine the "ideal candidate" traits there. Let's structure:

About the role

...prose from intro and role description...

Responsibilities

• ...each bullet from "The Operations Associate Will Be Responsible For..." and sub-bullets...

Requirements

• High school diploma or equivalent required.
• 1-3 years of experience in facilities support, workplace operations, tenant services, or a related role preferred.

But wait, the schedule and "ideal candidate" traits: the schedule has specific details. I'll create a

Schedule

section with the work schedule details. And maybe fold the "Why Work at The League?" and benefits into

Benefits

. The posting also has "How To Apply" but rule says remove application instructions. So I'll drop that entirely. Let's re-read the rules carefully: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So I remove "Job Posted by ApplicantPro", the EEO statement at the end, the equal opportunity language, the drug-free workplace policy? It says "Remove... equal-opportunity boilerplate". The drug-free policy might be considered part of benefits or equal opportunity. I'll keep only the substantive benefits list, and remove the EEO/equal opportunity/drug-free boilerplate unless it has specific content. The posting says: "At The League, we prioritize a strong workplace culture, work-life balance, and meaningful team member engagement while staying dedicated to our mission of supporting credit unions and the communities they serve. The League enforces a drug-free workplace policy and employment offers are contingent on drug-screen and background check." This is mixed. I'll include the benefits package list, and maybe fold the culture/mission into About the role or Benefits narrative. But rule: "never emit a heading followed by filler/placeholder text". I need to be careful. I'll include Benefits section with the listed insurance, PTO, 401k, etc. I'll omit the EEO/drug-free text or fold it minimally if it's substantive. Actually, the benefits list is very specific and substantial. I'll make a Benefits section with those items. The culture/mission can go in About the role or a short paragraph, but I won't create a separate "Culture" heading unless it's needed. The rules say: "Prefer a few substantive sections over many thin ones." Let's list all sections I'll include: 1. About the role (intro + role description) 2. Responsibilities 3. Requirements (qualifications) 4. Schedule (work schedule details) 5. Benefits (benefits package) I'll skip Pay (not stated). I'll skip Skills (not explicit section). I'll skip How To Apply (removed per rule). I'll skip EEO/equal opportunity boilerplate. Now, construct the HTML fragment carefully. Let extract exact prose: "About the role" section content: I'll combine the first paragraph and the role description. The posting starts: "The League of Credit