Apartment Community Assistant Manager

We need to output HTML fragment with sections: About Us? The instructions: Use

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

• for any list of duties/requirements/benefits, and

  for prose. 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. 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. We need to decide which sections to include based on content. The posting includes: - About Us: description of ESS. - Primary Responsibility: description. - Key Responsibilities: broken into Accounts Receivable, Business/Financial Responsibilities, General Duties. - Experience/Qualifications: sub-sections: Previous Work Experience, Education/Training, Communication/Skills/Schedules, Continuing Education. - Why Join ESS?: bullet points: Temporary to Permanent Opportunities, Flexible Scheduling, Weekly Pay, Skill Development, Referral Bonuses. - Also mention "We are an equal-opportunity employer..." which is boilerplate to remove. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have "About Us" which could map to "About the role"? Actually "About the role" is a heading for description of role. We have "Primary Responsibility" and "Key Responsibilities". Could combine into Responsibilities section. We have Experience/Qualifications which could be Requirements and Qualifications. We have Communication/Skills/Schedules which could be Skills. We have Why Join ESS? which includes Benefits (Flexible Scheduling, Weekly Pay, Skill Development, Referral Bonuses, Temporary to Permanent Opportunities). Also "Weekly Pay" is pay info, so we can include Pay section. "Flexible Scheduling" is schedule info, so we can include Schedule section. "Skill Development" maybe benefits. "Referral Bonuses" benefits. "Temporary to Permanent Opportunities" maybe benefits. Thus we can have sections: About the role (maybe using About Us content), Responsibilities (Primary Responsibility + Key Responsibilities), Requirements (Previous Work Experience, Education/Training), Qualifications (maybe combine with Requirements? But we need separate sections only if content exists. Could treat Requirements as experience/education, Qualifications as skills? But we also have Skills section for Communication/Skills/Schedules. Let's decide: - About the role: Use About Us paragraph. - Responsibilities: Combine Primary Responsibility and Key Responsibilities (Accounts Receivable, Business/Financial Responsibilities, General Duties) into a list. - Requirements: Previous Work Experience and Education/Training (maybe also Continuing Education? That's more like training after hire). Could put Continuing Education under Requirements or Qualifications. But we have Qualifications maybe for skills? Let's see. The posting has "Experience/Qualifications:" heading with subpoints: Previous Work Experience, Education/Training, Communication/Skills/Schedules, Continuing Education. So we could map: - Requirements: Previous Work Experience, Education/Training. - Qualifications: Communication/Skills/Schedules (maybe also Continuing Education? but that is more like training after hire). However we have a Skills section for skills; maybe Communication/Skills/Schedules fits Skills. - Benefits: Why Join ESS? points. - Pay: Weekly Pay. - Schedule: Flexible Scheduling. We need to avoid filler. Ensure we don't create sections with placeholder text. Let's extract substantive content. About Us: "Essential Staffing Solutions (ESS) is a leading staffing agency dedicated to providing top-tier service and staffing solutions. We pride ourselves on our supportive work environment, schedule flexibility, and opportunities for professional growth. Join our award-winning team today and start making a difference!" Primary Responsibility: "The Assistant Manager is a customer service specialist primarily responsible for collecting and posting rent, initiating follow-up actions on delinquent residents, processing purchase orders and invoices, and other duties as assigned by the Community Manager. The Assistant Manager should be fully capable of conducting the business operations of the Community in the absence of the Community Manager." Key Responsibilities: bullet-like paragraphs: Accounts Receivable: - Accept and accurately post rent and other payments in Yardi. - Ensure residents are correctly set up to use online, electronic, and WIPS payments. - Address late rent payments by closely following IPM policy, including distributing late notices and making personal calls and visits to delinquent residents. - Make bank deposits daily. - Inform residents of NSF checks within 24 hours of notification from accounting, and follow up within 48 hours. - File evictions and manage the eviction process, including attending court dates. - Conduct move-out inspections and manage the process in Yardi. - Turn over bad debts for collection and process SURE deposits within 72 hours of move-out. - Prepare month-end accounting reports as per Owner's requirements and Company procedures. Business/Financial Responsibilities: - Ensure purchase order policy is followed at all times, including monthly statement reconciliation. - Process invoices for payment as directed by the Community Manager. - Manage the vendor process to ensure all vendors are approved and using vendor café. - Weekly review of budget comparison to identify any budget variances. - Respond to all accounting inquiries timely and assist in monthly closeout. - Process SODA's and submit to Regional Manager within three business days of move-out. General Duties: - Utilize Yardi to post rent and produce accurate and timely reports. - Answer telephone with appropriate greeting. - Assist in leasing activities and resident relations. - Implement the monthly Renewal/Resident Retention Program. - Perform pre-inspection walks with the Service Manager. - Comply with Company policies and procedures. - Support the turnkey process and initiate make-ready dashboard in Yardi. - Monitor the leasing team to ensure accurate completion of leasing activity reports. - Complete the Utility Log and monitor usage. - Enter service requests in Yardi as received. - Serve as back-up to Community Manager, including reviewing reports and daily office tasks. Experience/Qualifications: Previous Work Experience: "1-2 years' experience in the multi-family apartment industry. Experience in dealing with customers or the public. Previous leasing/customer service and collection experience helpful. Previous management experience helpful." Education/Training: "High School Diploma or GED required. Business school, college, marketing, or other accredited courses in sales and marketing preferred. Proficient in MS Office Suite. Yardi experience is a plus." Communication/Skills/Schedules: "High energy with a positive, customer service-oriented attitude. Proven leadership capabilities. Energetic, enthusiastic, and creative. Social media knowledge is a plus. Effective communication skills, both telephone and written correspondence. Professional demeanor and team player. Flexibility to assist the Community Manager, which may include hours outside of published office hours." Continuing Education: "Successful completion of all in-house training programs as defined in the IPM Management Service Policies and Procedures manual." Why Join ESS?: - Temporary to Permanent Opportunities: Potential to transition into a permanent role. - Flexible Scheduling: Enjoy a balanced work schedule. - Weekly Pay: Get paid every week! - Skill Development: Grow your expertise in a supportive environment. - Referral Bonuses: Unlimited rewards for referring friends or family. We need to remove boilerplate: "We are an equal-opportunity employer and welcome diversity in our workforce." Also maybe "Apply Today to Join Our ESS Team!" is application instruction; remove. Now construct HTML. We need headings

  for each section we include. We need to decide which sections to include: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for: - About the role: About Us paragraph. - Responsibilities: combine Primary Responsibility and Key Responsibilities (maybe as a list). Could also include Primary Responsibility as a paragraph then list. - Requirements: Previous Work Experience and Education/Training (maybe also Continuing Education? but that's more like training after hire; could be under Qualifications? But we have Qualifications maybe for skills? Let's see. - Qualifications: maybe Communication/Skills/Schedules? But we also have Skills section for skills. Actually Communication/Skills/Schedules includes skills and schedule flexibility. But schedule we already have separate Schedule section. So we could put Communication/Skills/Schedules under Skills (excluding schedule part). But the schedule part is "Flexibility to assist the Community Manager, which may include hours outside of published office hours." That's schedule flexibility; we could move that to Schedule section. However the schedule section we already have from Why Join ESS? "Flexible Scheduling: Enjoy a balanced work schedule." That's a benefit. The schedule flexibility in Communication/Skills/Schedules is a requirement (need flexibility). Might be better to keep under Skills? But we have a separate Schedule section for schedule info from posting (like flexible scheduling benefit). The requirement of flexibility to work outside hours could be under Requirements or Qualifications. Let's treat it as part of Requirements (maybe under "Availability"). But we have limited headings; we can just put Communication/Skills/Schedules under Skills (since it's about skills and attitude). The schedule flexibility phrase can be kept there; we still have a Schedule section for benefit. Thus: - Skills: Communication/Skills/Schedules content (excluding maybe the schedule flexibility phrase? but we can keep it; it's still a skill/attribute). We'll keep as is. - Benefits: Why Join ESS? points (Temporary to Permanent Opportunities, Flexible Scheduling, Weekly Pay, Skill Development, Referral Bonuses). However Weekly Pay and Flexible Scheduling also map to Pay and Schedule sections. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Weekly Pay and Flexible Scheduling as benefits. So we could create Pay and Schedule sections for those specific items, and Benefits for the rest (Temporary to Permanent Opportunities, Skill Development, Referral Bonuses). Or we could put all under Benefits and not create separate Pay/Schedule sections. But we have the option to create Pay and Schedule sections if they exist. The instruction: "Prefer a few substantive sections over many thin ones." So maybe better to combine Pay and Schedule into Benefits? But they specifically mention Pay and Schedule as possible headings. Since we have explicit statements, we could create them. However that would create many thin sections (Pay, Schedule, Benefits). Might be better to have Benefits section that includes all, and not create separate Pay/Schedule. But the instruction says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does not forbid creating them if they exist; but we should prefer few substantive sections over many thin ones. So we need to decide: Is it better to have one Benefits section containing all (including weekly pay and flexible scheduling) or three sections? The instruction says prefer a few substantive sections over many thin ones. So one Benefits section is fewer sections. So we should not create separate Pay and Schedule sections; we should include those details within Benefits. However the instruction also says: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That list includes Pay and Schedule as examples, but not mandatory. So we can choose to not include them if we think it's