Lease-Up Leasing Consultant

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Description (some intro), About Us, What’s In It For You? (benefits), What You’ll Do (responsibilities), Requirements (what you’ll need), What’ll Set You Apart (maybe qualifications/skills), Physical Activities and Work Environment (maybe not a standard heading). Also there is mention of competitive pay but no specific amount; we should not create Pay section unless posting actually states them. It says "In addition to competitive pay" but no specific number, so we should not create Pay section. Schedule: mentions flexible schedule, must be willing to work Saturdays. That's schedule info. So we can include a Schedule section with that info. Benefits: we have list: Bonus potential, 30% rental discount, Paid time off and company holidays, 401k plus 4% company match, Wellness plans, flexible spending accounts, dependent care, Participation in professional development programming, including a designated Mentor from day one. So Benefits section. About the role: we have description about role: "ECI Group is currently hiring an experienced Lease-Up Leasing Consultant to oversee leasing results and strategy. The Lease-Up Leasing Consultant is a critical member of our onsite community team, marketing and leasing apartments to prospective residents while providing fantastic customer service throughout the entire lease process and on an ongoing basis to residents..." That's about the role. Could be About the role section. Responsibilities: "What You’ll Do" list. Requirements: "What You’ll Need" list. Qualifications/Skills: "What’ll Set You Apart" plus maybe "Requirements" includes some qualifications. We could combine Qualifications and Skills. But we need to decide headings. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include multiple of those as appropriate. We have content for About the role, Responsibilities, Requirements, Benefits, Schedule. Also we have "What’ll Set You Apart" which could be Qualifications or Skills. We could put that under Qualifications (preferred experience, etc.) and maybe Skills under that? But we should not create thin sections. Could combine Qualifications and Skills into one section? But we have separate headings allowed. We could make Qualifications section for "What’ll Set You Apart" (prior lease-up experience, customer service). Skills could be maybe from Requirements: interpersonal communication, Microsoft Office, multitasking, etc. But those are already in Requirements. Might be redundant. Better to have Requirements include both hard requirements and skills. Then we could omit Qualifications and Skills sections if they'd be thin. However we have "What’ll Set You Apart" which is additional preferred qualifications; we could put that under Qualifications as a subsection? But we need to follow instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So if we put Qualifications heading, we need to put specific content under it. We have content: "Prior lease-up experience strongly preferred. Prior customer service experience is also a plus." That's specific. So we can have Qualifications section with that content. Skills: we could extract skills from Requirements: Excellent interpersonal communication skills, ability to influence and motivate, knowledge of Fair Housing/ADA, proficiency in Microsoft Office, able to multitask, meet deadlines, flexible schedule, reliable transportation, ability to tour community (walking, stairs). Those are skills. But many are already in Requirements. To avoid duplication, we could keep Requirements as the list of mandatory requirements, and Skills as a separate list of desired skills (maybe from "What’ll Set You Apart" plus some). However the instruction says preserve ALL substantive information; do not invent or summarize away detail. We can split the Requirements list into two: mandatory requirements (high school diploma, driver's license, 1 year experience, etc.) and preferred qualifications (lease-up experience, customer service). But the posting already separates "What You’ll Need" (requirements) and "What’ll Set You Apart" (preferred). So we can map: Requirements = What You’ll Need. Qualifications = What’ll Set You Apart. Skills maybe not needed separately; we could omit Skills section to avoid thin content. But we have interpersonal communication etc. inside Requirements; they are part of requirements. So we can keep them there. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. Check each for specific content: - About the role: we have description paragraph(s). Good. - Responsibilities: "What You’ll Do" bullet list. - Requirements: "What You’ll Need" list. - Qualifications: "What’ll Set You Apart" list (two items). - Benefits: "What’s In It For You?" list. - Schedule: mention flexible schedule, must be willing to work Saturdays. Also maybe "must be able to work a flexible schedule as needed". That's schedule. We should not include Pay section because no specific pay. We should not include sections like "Physical Activities and Work Environment" because not in allowed headings; but we could incorporate that info into Requirements or Schedule? It's not a standard heading; we could drop it? But instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info somewhere. We could add it under Requirements as a bullet (or under a separate section like "Work Environment" but not allowed heading). Since allowed headings are limited, we could incorporate into Requirements or maybe under a generic section? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies we should use those headings for sections; but we could also add other headings if needed? Probably better to stick to those. We can place physical activities info under Requirements as a bullet: "Requires frequently being on your feet; may regularly climbing stairs to access upper floor apartments. Requires working indoors (majority of time); may require working outside in various weather conditions." That's substantive. Also EEO boilerplate should be removed. Now craft HTML. Structure:

About the role

ECI Group is currently hiring an experienced Lease-Up Leasing Consultant to oversee leasing results and strategy. The Lease-Up Leasing Consultant is a critical member of our onsite community team, marketing and leasing apartments to prospective residents while providing fantastic customer service throughout the entire lease process and on an ongoing basis to residents. Our Leasing Consultants make a big impact in many small ways - a friendly smile, a welcoming handshake, taking a genuine interest in our residents and prospective residents. Our Leasing Consultants create a positive and lasting influence on visitors, prospects, and residents, and understand the importance of every interaction. As a Leasing Consultant, you manage your own success by attaining leasing goals, such as occupancy and rent growth, and by building rapport with prospects and residents. We are looking for an enthusiastic person who enjoys being hands-on, helping customers and motivating team members.

Responsibilities

• Drive the sale by highlighting the quality of the community and the lifestyle of an apartment home.
• Follow established policies and procedures to aide prospects in the qualification, screening and acceptance of applications for residency.
• Ensure apartments are prepared for move-in including inspection, keys, remote and parking permit
• Deliver unmatched service to residents to exceed their expectations, while maintaining resident retention.
• Manage and track marketing strategies metrics, including advertising, promotions and publications.
• Review aged vacancies, market-ready apartments and models.
• Participate in resident functions and other ECI Group sponsored resident activities after hours and/or on weekends.
• Consistently meet individual rental and renewal goals.
• Assist in the performance of the turn process and walk vacant units.
• Visit other locations when assigned by Community Manager, Assistant Manager or Leasing Manager.
• Respond to resident requests and help to minimize and resolve resident problems.
• Respond to internet leads and other inquiries by prospective residents.

Requirements

• High school diploma or GED along with a valid driver’s license.
• Bachelor’s degree is preferred.
• A minimum of 1 year of related leasing experience.
• Excellent interpersonal communication skills, including the ability to influence and motivate clients and colleagues.
• Knowledge and experience with Compliance to Fair Housing and ADA regulations.
• Proficiency in Microsoft Office (Word, Excel).
• Able to multitask and meet deadlines in a timely and organized manner.
• Must be able to work a flexible schedule as needed, must be willing to work on Saturdays.
• Maintain regular and predictable attendance in accordance with company policy to meet business and operational needs.
• Must have access to reliable transportation.
• Must be able to tour the community with clients, which includes walking the property and climbing stairs.
• Requires frequently being on your feet; may regularly climbing stairs to access upper floor apartments.
• Requires working indoors (majority of time); may require working outside in various weather conditions.

Qualifications

• Prior lease-up experience strongly preferred.
• Prior customer service experience is also a plus.

Benefits

• Bonus potential
• 30% rental discount at ECI properties
• Paid time off and company holidays
• 401k plus 4% company match
• Wellness plans, flexible spending accounts, and dependent care
• Participation in professional development programming, including a designated Mentor from day one

Schedule

Must be able to work a flexible schedule as needed, including willingness to work on Saturdays.

We have duplicated flexible schedule mention; we already have it in Requirements. But we can keep schedule section short; it's okay to repeat? The instruction says preserve ALL substantive information; not to invent or summarize away detail. Duplication is okay if it's already present elsewhere? Might be considered duplication but not invented. Could remove from Requirements to avoid duplication, but then we lose that info from Requirements. However schedule info is also a requirement; we could keep it only under Schedule and remove from Requirements. But Requirements also includes "Must be able to work a flexible schedule as needed, must be willing to work on Saturdays." That's a requirement. If we move it to Schedule, we still preserve it. We should avoid duplicate content? Not explicitly forbidden, but better to avoid redundancy. Let's keep schedule info only under Schedule, and remove from Requirements. However Requirements also includes "Must be able to work a flexible schedule as needed, must be willing to work on Saturdays." We'll delete that line from Requirements. Also we have "Must be able to tour the community with clients, which includes walking the property and climbing stairs." That's a requirement; keep. Now adjust Requirements list accordingly. Also we have "Maintain regular and predictable attendance..." keep. Now final HTML. Check no extra headings like About Us etc. We omitted About Us description (company overview) as not needed per headings; but is that substantive? It's about company, not role. The instruction says we should not repeat job title as heading; but we can include About Us? Not in allowed headings list. Could we include it under About the role