Affordable Housing Leasing Manager

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Must not create sections with filler like "commensurate with experience". Must not invent or summarize away detail. We need to parse the posting. Company Overview: description of Asset Living. That's about the company, not necessarily "About the role". Could be placed under "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections like About the role (maybe includes company overview and role summary). Responsibilities: list of duties. Requirements: maybe education/experience, physical requirements? Qualifications: maybe knowledge of Fair Housing, OSHA. Skills: maybe computer skills, etc. Benefits: mention benefits package. Pay: salary range. Schedule: maybe not given; we should not create Schedule unless present. The posting does not mention schedule specifics (full-time implied but not explicit schedule). So we should omit Schedule section. We must not include headings with filler. So we need to ensure each section has substantive content. Let's extract: Company Overview paragraph(s): "Asset Living is a third-party management firm...". That's about the company. Could be placed under About the role. Role summary: "Leasing Manager The Leasing Manager is responsible for overseeing all aspects of leasing and marketing at the property. The Leasing Manager works closely with the Community Manager to set leasing goals and develop a strategic marketing plan for achieving budgeted occupancy. The Leasing Manager is responsible for effectively leading the leasing team and accomplishing effective leasing, marketing, and positive resident relations." That's also about the role. Thus About the role can combine company overview and role summary. Responsibilities: list of duties under Essential Duties & Responsibilities with subcategories: Strategic Leasing Management, Marketing Management, Personnel Management, Administrative Management. We need to output as

• items. Should we preserve subheadings? Probably just list each duty as separate li. Could group but not required. We'll list each bullet. Responsibilities items: - Strategic Leasing Management: - Regular/daily onsite attendance is required - Ensure staff leasing techniques are effective in obtaining closure, follow-up procedures met, signing/documentation of leases, and reporting systems are accurate and up to date. - Audit all lease files to ensure adherence to policies and procedures - Deal with resident complaints, concerns, and requests to ensure resident satisfaction - Develop and implement resident retention programs (i.e., resident functions, special promotions, monthly newsletter, etc.) - Effectively show, lease, and move in prospective residents - Marketing Management: - Assist in developing the annual marketing plan and marketing budget - Implement all marketing efforts and outreach, developing campaigns and assisting with design to generate traffic - Monitor leasing/renewal progress, focusing on areas needing additional support - Supervise the planning, preparation, and implementation of all leasing and renewal events as approved by the Community Manager - Maintain thorough product knowledge of the property and competition as well as market conditions; complete weekly market survey report - Utilize established sales and marketing strategies to increase property traffic, maintain closing ratios, and achieve budgeted occupancy. - Personnel Management: - Assist the Community Manager in the use of consistent techniques & company directives to screen, hire, train, coach, and develop on-site staff. - Assist the Community Manager in ensuring the effectiveness of staff through ongoing training, coaching, counseling, and guidance in compliance with Asset training benchmarks. - Promote harmony and quality job performance of staff through support and effective leadership - Ensure staff compliance and consistency with Company policies and procedures - Administrative Management: - Manage excellent customer service and monitor service request turnaround and responsiveness of maintenance staff - Maintain property appearance and ensure repairs are noted and completed on a timely basis (this requires regular property inspections and tours) - Assist with supervision of all business functions related to operations - Plan for and utilize property resources, equipment, and supplies economically (i.e., obtaining bids/pricing from vendors, suppliers, contractors, dealing with inadequate service, etc.) We could keep subheadings as plain text inside li? Probably better to keep as separate li with the subheading bold? But we cannot add extra tags not specified? We can include inside li? Not prohibited. But to keep simple, we can just list each duty as separate li, maybe grouping with a leading dash? The instruction: Use
  • for any list of duties/requirements/benefits. So we can have nested lists? Probably okay to have a
    with
    • items, each item can contain a sentence. We'll just list each duty as separate li. Requirements: Education/experience: "High School Diploma or Equivalent; Bachelor’s degree preferred or one year’s experience in the housing industry; Ability to understand and perform all on-site software functions; basic computer skills required." Also "Must have basic knowledge of Fair Housing Laws and OSHA requirements." That could be qualifications. Physical Requirements: long list. Could be part of Requirements or Qualifications? Probably Requirements includes education/experience, physical requirements. Qualifications maybe skills? But we have separate Skills section. We need to avoid filler. So we need to decide which sections to include. We have: - About the role: company overview + role summary. - Responsibilities: list as above. - Requirements: education/experience + physical requirements? Might be too much but okay. - Qualifications: maybe knowledge of Fair Housing Laws and OSHA requirements. - Skills: basic computer skills, ability to understand software, maybe also "ability to understand and perform all on-site software functions; basic computer skills required." That's skill. But we already have education/experience includes basic computer skills. Could combine. Better to follow typical sections: Requirements (education/experience), Qualifications (knowledge/certifications), Skills (specific abilities). Benefits (benefits package). Pay (salary range). Schedule (omit). Let's extract: Education/experience: "High School Diploma or Equivalent; Bachelor’s degree preferred or one year’s experience in the housing industry; Ability to understand and perform all on-site software functions; basic computer skills required." Qualifications: "Must have basic knowledge of Fair Housing Laws and OSHA requirements." Skills: maybe "Ability to understand and perform all on-site software functions; basic computer skills required." But that's already in education/experience. Could also include "Ability to understand and perform all on-site software functions" as skill. But to avoid duplication, we could put skills as "Ability to understand and perform all on-site software functions; basic computer skills required." However that duplicates. Maybe we treat education/experience as just education and experience, and skills as computer skills, software proficiency. Let's parse: Education/experience: High School Diploma or Equivalent; Bachelor’s degree preferred or one year’s experience in the housing industry. Skills: Ability to understand and perform all on-site software functions; basic computer skills required. Qualifications: Must have basic knowledge of Fair Housing Laws and OSHA requirements. Physical Requirements: could be its own section? Not in the list of headings but we could include under Requirements or Qualifications? The instruction only gave examples but we can add other headings if needed? It says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Prefer a few substantive sections over many thin ones." So we could incorporate physical requirements into Requirements or Qualifications. Probably better to put under Requirements as part of job requirements. Thus Requirements will include education/experience and physical requirements. Let's craft Requirements

      with items: - High School Diploma or Equivalent; Bachelor’s degree preferred or one year’s experience in the housing industry. - Ability to understand and perform all on-site software functions; basic computer skills required. - Must have basic knowledge of Fair Housing Laws and OSHA requirements. - Physical requirements: while performing duties, employee regularly required to remain stationary, often standing or sitting for prolonged periods, communicate with others, repeat motions that may include wrists, hands, and/or fingers; frequently required to ascend/descend ladders, stairs, scaffolding, ramps, step stools, move about, operate motor vehicles and/or golf carts, assess accuracy, neatness, thoroughness of work, traverse flat and non-flat terrain; occasionally required to move self into different positions to accomplish tasks in various environments including tight and confined spaces, work in overhead position and reach, adjust or move objects up to 25 lbs in all directions, lift and place objects up to 25 lbs, operate machinery or power tools, identify and inspect objects, able to work overtime, weekends, night hours (emergencies), work in extremely low or high temperatures, work in outdoor environments such as precipitation and wind, work in small and/or enclosed spaces, be exposed to hazardous chemicals. That's a long sentence; we can break into multiple li for readability but it's okay as one. Benefits: "Our employment offer is accompanied by additional compensation associated with our comprehensive total rewards package, which includes benefits (medical, dental, vision, life, accidental, and disability insurance), 401K with employer matching, and commission and performance bonuses, when applicable. Full-time employees also receive paid sick days and company holidays." Pay: "Salary Range: $22 per hour to $24 per hour" Schedule: Not present, omit. Now we need to ensure we don't include boilerplate like "This job description should not be considered all-inclusive..." etc. Remove that. Also remove lines like "At Asset Living, a variety of factors are considered in making compensation decisions..." maybe part of Pay? Actually that's about compensation decisions; we could include in Pay section? But it's generic. Might be considered boilerplate? It's not a specific benefit or pay range; it's about how compensation determined. Could be omitted as it's not specific. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. That sentence is substantive? It's about compensation decisions but it's generic. Might be considered boilerplate but it's part of the posting. However we already have Pay section with salary range. The extra sentence about factors considered could be considered part of Pay but it's not specific numbers. Might be okay to include as a brief note in Pay section. But the instruction says prefer few substantive sections over many thin ones. Including that sentence may be okay. But also there is line: "When selecting the top candidate to hire for a position, the offer we extend is dependent on the facts associated with each specific individual’s relevant experience for the role." That's also generic. Could be omitted as boilerplate? It's about hiring process. Might be considered boilerplate. Safer to omit. Also line: "This is a safety-sensitive position and may be subject to additional compliance requirements." Could be omitted? It's substantive about safety-sensitive. Could be included maybe under Requirements? But not in given headings. Could be added as a note under Requirements? Might be considered substantive. However we have no specific heading for safety. Could add a line in Requirements about safety-sensitive. But we might omit to keep sections thin. Given instruction to preserve ALL substantive information, we should keep that line. But where to put? Could add a

      after Requirements maybe. But we must not create new headings unless we have content. Could add a

      under Requirements? Actually we can include a paragraph inside the Requirements section after the list? The instruction says use

      for prose. So we can have a

      after the

      inside the same section? But the section heading is

      then we can have

      and

      . That's fine. Thus Requirements section:

      Requirements

      then a

      for prose (maybe the safety-sensitive line) and a

      for the