Leasing Specialist -
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. There's no explicit application instructions. There's a line "#PNW Compensation Range". That's likely metadata; we can include compensation in a short
or drop? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Compensation is not minor metadata; it's substantive. So we need a Pay section if posting actually states them. It does: "Compensation Range $19—$21 USD". So we need a Pay section with that info. Should we use heading "Pay"? Yes, allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Pay heading.
Schedule: Not mentioned explicitly; there is "Flexible schedule that may include evenings and weekends." That's schedule info. So we can have Schedule heading.
Benefits: There's "Comprehensive Benefits – health, dental & vision, 401(k), personal time off, paid holidays and more!" Also later "Benefits Our organization’s diversity initiatives include..." That's more about diversity. But we can have Benefits heading with the list.
We need to avoid filler like "commensurate with experience". Not present.
We need to ensure we only include sections when there is real specific content.
Let's extract content:
Overview: Could be "About the role"? Actually Overview is about company. Could be "About the role"? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (maybe summarizing overview). But we must not repeat job title as heading. Overview is not job title. So we can have About the role with overview paragraph.
The Role: Could be Responsibilities? Actually The Role includes description of leasing specialist responsibilities. Could be Responsibilities.
Qualifications: Already a heading.
Key Accountabilities: Could be split into Responsibilities sub-sections? But we already have Responsibilities maybe. However we can treat Key Accountabilities as Responsibilities with sub-sections: Customer Service & Sales, Administrative, Resident Retention, Adherence to Property Management Rules, Regulations, and Guidelines.
Physical Demands & Working Conditions: Could be maybe a section? Not in allowed headings list but we could still include? 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)." Likely they expect only those headings. But we can still include other headings if needed? Safer to map content to allowed headings.
Physical Demands & Working Conditions could go under Responsibilities? Not ideal. Could be a separate section like "Working Conditions" but not in list. Might be okay to include as a heading? The instruction says use h3 for section headings (e.g. ...). It doesn't say you cannot use other headings, but they gave examples. Probably they want to limit to those. However Physical Demands is substantive; we could include it as a heading "Physical Demands". Might be acceptable.
How Avanath Supports You: Could be Benefits, Growth, Development, Diversity & Inclusion. Could be split into Benefits and maybe "Development". But we have Benefits heading allowed. We can put benefits there. Growth and Development could be under Benefits? Or maybe under "Skills"? Not exactly. Could be under "Benefits" as part of benefits. Diversity & Inclusion could be separate? Not in allowed headings but could be under Benefits as well.
We need to preserve all substantive info. Let's try to structure:
About the role
Overview paragraph about Avanath and the role purpose.
Responsibilities
The Leasing Specialist is responsible for leasing, marketing, and maintaining positive resident relations within the community....
Then we can have sub-sections? Could use - for lists of duties. The Key Accountabilities section includes many bullet-like sentences. We can convert each sentence into
- . Might be long but okay.
We need to avoid duplicating lines. Let's extract the responsibilities from "Key Accountabilities" and also from earlier "The Role" description.
Better: Use Responsibilities heading and then a
with items covering all duties.
Let's list duties from the text:
From The Role: "The Leasing Specialist is responsible for leasing, marketing, and maintaining positive resident relations within the community. The incumbent in this role must possess high professionalism and positive engagement for our residents and the workforce. An Aptitude for Connecting - Must possess a strong sense for creating a sense of community and the drive to go the extra mile to create a positive experience for all residents and staff. Your success and purpose are driven by the relationships that you build within your communities, including vendor partners and regulatory and social services partnerships. This includes adopting a collaborative approach to create consistently favorable circumstances that foster success and effectiveness for the Organization and the communities. An Authentic Attitude - Consistently demonstrate an open and professional attitude and approach when accessing and resolving resident and staff concerns. This includes, but is not limited to, seeking resources throughout the organization via the organization's support services and senior leadership. A positive and professional approach —Consistently demonstrate an active listening approach and understand that your participation and support are integral to Avanath's success. Ensure that each resident and staff member feels seen, heard, and valued as you and the staff work to resolve challenges."
That's a lot of prose; we could keep as but also break into list? The instruction: Use
- for any list of duties/requirements/benefits. So if we have a list, we should use ul. The responsibilities are not explicitly a list but we can treat each bullet as list item. However we risk losing nuance. Perhaps better to keep as
for prose and only use ul for explicit lists like qualifications, benefits, etc. The qualifications are listed as bullet-like sentences separated by periods. Could be turned into ul.
Let's decide: We'll keep Overview and Role description as
. Then Qualifications as
. Then Responsibilities (Key Accountabilities) as with items. Then Physical Demands & Working Conditions as maybe. Then How Avanath Supports You: we can have Benefits heading with
for benefits list, plus maybe separate headings for Growth, Development, Diversity & Inclusion? But we can combine under Benefits heading with multiple paragraphs.
Pay heading:
Compensation Range $19—$21 USD
Schedule heading: Flexible schedule that may include evenings and weekends.
Now we need to ensure we don't repeat content.
Let's extract qualifications:
"Passion for providing exceptional customer service.
2+ years of sales and/or customer relations experience
Low-Income Housing & Tax Credit experience is highly desired.
Bilingual (English & Spanish) highly desired.
Thrives in a fast-paced environment.
Flexible schedule that may include evenings and weekends.
Solid computer knowledge, Windows (Word, Excel), internet, and e-mail
Working knowledge of Yardi Voyager Property Management Software"
Note: Flexible schedule also appears in qualifications; but we also have schedule heading. Might duplicate. We could keep schedule heading separate and not repeat in qualifications list. But qualifications list includes flexible schedule as a qualification; we could keep it there and also have schedule heading? Might be duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep flexible schedule info somewhere. If we put it in schedule heading, we still need to keep it in qualifications? It's part of qualifications list. Could keep it there and not have separate schedule heading? But schedule heading is allowed and we have schedule info; we could keep schedule heading and remove from qualifications to avoid duplication. However the qualifications list originally includes it; removing would lose that detail from qualifications. But we could keep it in both places? That would be duplication, which we should avoid per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines". Duplicated lines should be removed. So we should not duplicate the same sentence. So we need to decide where to place flexible schedule info. It's both a qualification and schedule info. Perhaps we put it under Schedule heading and not repeat in qualifications. But then qualifications lose that item. However the qualifications list is about required skills/experience; flexible schedule is a requirement (availability). It's still a qualification. But we could still keep it under qualifications and not have separate schedule heading, but schedule heading is optional; we only include if posting actually states them. It does state flexible schedule, so we could include schedule heading. But then we would have duplication if we also keep it in qualifications. To avoid duplication, we could move flexible schedule to schedule heading and remove from qualifications list. However then we lose the qualification that they desire flexible schedule. But schedule heading conveys that info. Is that acceptable? The instruction: "Preserve ALL substantive information". If we move it, we still preserve it (just in a different place). That's okay as long as it's not lost. So we can place flexible schedule under Schedule heading and not duplicate in qualifications.
Thus qualifications list will exclude flexible schedule.
Now Benefits: "Comprehensive Benefits – health, dental & vision, 401(k), personal time off, paid holidays and more!" Also later "Benefits Our organization’s diversity initiatives include—but are not limited to—our practices and policies on recruitment and selection, compensation and benefits, professional development and training, promotions, transfers, and the ongoing development of a work environment built on the premise of gender and diversity equity that encourages and enforces: Respectful communication and cooperation between all employees. Teamwork and employee participation, permitting the representation of all groups and employee perspectives. Work/life balance through flexible work schedules to accommodate employees’ varying needs. Employer and employee contributions to the communities we serve promote a greater understanding and respect for diversity."
That's a lot. We could have Benefits heading with a for the concrete benefits list, and then maybe a for the diversity initiatives description. But diversity initiatives could be under a separate heading? Not in allowed list but we could still include as a
under Benefits heading.
Growth and Development: "Growth that is based on achievement and an emphasis on promoting from within our ranks versus just external candidates. Development – a commitment to creating opportunities to learn and expand your knowledge in the industry, from online training platforms to training classes to one-on-one coaching". Could be under Benefits heading as well, or maybe under Skills? Not exactly. Could be under a heading "Development"? Not in allowed list but we could still include as a
under Benefits.
Simplify: We'll have Benefits heading with a
for concrete benefits, and then a covering growth, development, diversity & inclusion.
Now Responsibilities: We'll take the Key Accountabilities bullet points and also the earlier role description maybe as a
preceding the list.
Let's list Key Accountabilities items:
Customer Service & Sales
- At all times, regardless, provides A+ customer service.
-
for prose. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. There's no explicit application instructions. There's a line "#PNW Compensation Range". That's likely metadata; we can include compensation in a short
or drop? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Compensation is not minor metadata; it's substantive. So we need a Pay section if posting actually states them. It does: "Compensation Range $19—$21 USD". So we need a Pay section with that info. Should we use heading "Pay"? Yes, allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Pay heading. Schedule: Not mentioned explicitly; there is "Flexible schedule that may include evenings and weekends." That's schedule info. So we can have Schedule heading. Benefits: There's "Comprehensive Benefits – health, dental & vision, 401(k), personal time off, paid holidays and more!" Also later "Benefits Our organization’s diversity initiatives include..." That's more about diversity. But we can have Benefits heading with the list. We need to avoid filler like "commensurate with experience". Not present. We need to ensure we only include sections when there is real specific content. Let's extract content: Overview: Could be "About the role"? Actually Overview is about company. Could be "About the role"? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (maybe summarizing overview). But we must not repeat job title as heading. Overview is not job title. So we can have About the role with overview paragraph. The Role: Could be Responsibilities? Actually The Role includes description of leasing specialist responsibilities. Could be Responsibilities. Qualifications: Already a heading. Key Accountabilities: Could be split into Responsibilities sub-sections? But we already have Responsibilities maybe. However we can treat Key Accountabilities as Responsibilities with sub-sections: Customer Service & Sales, Administrative, Resident Retention, Adherence to Property Management Rules, Regulations, and Guidelines. Physical Demands & Working Conditions: Could be maybe a section? Not in allowed headings list but we could still include? 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)." Likely they expect only those headings. But we can still include other headings if needed? Safer to map content to allowed headings.
Physical Demands & Working Conditions could go under Responsibilities? Not ideal. Could be a separate section like "Working Conditions" but not in list. Might be okay to include as a heading? The instruction says use h3 for section headings (e.g. ...). It doesn't say you cannot use other headings, but they gave examples. Probably they want to limit to those. However Physical Demands is substantive; we could include it as a heading "Physical Demands". Might be acceptable.
How Avanath Supports You: Could be Benefits, Growth, Development, Diversity & Inclusion. Could be split into Benefits and maybe "Development". But we have Benefits heading allowed. We can put benefits there. Growth and Development could be under Benefits? Or maybe under "Skills"? Not exactly. Could be under "Benefits" as part of benefits. Diversity & Inclusion could be separate? Not in allowed headings but could be under Benefits as well.
We need to preserve all substantive info. Let's try to structure:
About the role
Overview paragraph about Avanath and the role purpose.
Responsibilities
The Leasing Specialist is responsible for leasing, marketing, and maintaining positive resident relations within the community....
Then we can have sub-sections? Could use- for lists of duties. The Key Accountabilities section includes many bullet-like sentences. We can convert each sentence into
- . Might be long but okay.
We need to avoid duplicating lines. Let's extract the responsibilities from "Key Accountabilities" and also from earlier "The Role" description.
Better: Use Responsibilities heading and then a
- with items covering all duties.
Let's list duties from the text:
From The Role: "The Leasing Specialist is responsible for leasing, marketing, and maintaining positive resident relations within the community. The incumbent in this role must possess high professionalism and positive engagement for our residents and the workforce. An Aptitude for Connecting - Must possess a strong sense for creating a sense of community and the drive to go the extra mile to create a positive experience for all residents and staff. Your success and purpose are driven by the relationships that you build within your communities, including vendor partners and regulatory and social services partnerships. This includes adopting a collaborative approach to create consistently favorable circumstances that foster success and effectiveness for the Organization and the communities. An Authentic Attitude - Consistently demonstrate an open and professional attitude and approach when accessing and resolving resident and staff concerns. This includes, but is not limited to, seeking resources throughout the organization via the organization's support services and senior leadership. A positive and professional approach —Consistently demonstrate an active listening approach and understand that your participation and support are integral to Avanath's success. Ensure that each resident and staff member feels seen, heard, and valued as you and the staff work to resolve challenges."
That's a lot of prose; we could keep as
- for any list of duties/requirements/benefits. So if we have a list, we should use ul. The responsibilities are not explicitly a list but we can treat each bullet as list item. However we risk losing nuance. Perhaps better to keep as
for prose and only use ul for explicit lists like qualifications, benefits, etc. The qualifications are listed as bullet-like sentences separated by periods. Could be turned into ul. Let's decide: We'll keep Overview and Role description as
. Then Qualifications as
- . Then Responsibilities (Key Accountabilities) as
- with items. Then Physical Demands & Working Conditions as
maybe. Then How Avanath Supports You: we can have Benefits heading with
- for benefits list, plus maybe separate headings for Growth, Development, Diversity & Inclusion? But we can combine under Benefits heading with multiple
paragraphs. Pay heading:
Compensation Range $19—$21 USD
Schedule heading:Flexible schedule that may include evenings and weekends.
Now we need to ensure we don't repeat content. Let's extract qualifications: "Passion for providing exceptional customer service. 2+ years of sales and/or customer relations experience Low-Income Housing & Tax Credit experience is highly desired. Bilingual (English & Spanish) highly desired. Thrives in a fast-paced environment. Flexible schedule that may include evenings and weekends. Solid computer knowledge, Windows (Word, Excel), internet, and e-mail Working knowledge of Yardi Voyager Property Management Software" Note: Flexible schedule also appears in qualifications; but we also have schedule heading. Might duplicate. We could keep schedule heading separate and not repeat in qualifications list. But qualifications list includes flexible schedule as a qualification; we could keep it there and also have schedule heading? Might be duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep flexible schedule info somewhere. If we put it in schedule heading, we still need to keep it in qualifications? It's part of qualifications list. Could keep it there and not have separate schedule heading? But schedule heading is allowed and we have schedule info; we could keep schedule heading and remove from qualifications to avoid duplication. However the qualifications list originally includes it; removing would lose that detail from qualifications. But we could keep it in both places? That would be duplication, which we should avoid per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines". Duplicated lines should be removed. So we should not duplicate the same sentence. So we need to decide where to place flexible schedule info. It's both a qualification and schedule info. Perhaps we put it under Schedule heading and not repeat in qualifications. But then qualifications lose that item. However the qualifications list is about required skills/experience; flexible schedule is a requirement (availability). It's still a qualification. But we could still keep it under qualifications and not have separate schedule heading, but schedule heading is optional; we only include if posting actually states them. It does state flexible schedule, so we could include schedule heading. But then we would have duplication if we also keep it in qualifications. To avoid duplication, we could move flexible schedule to schedule heading and remove from qualifications list. However then we lose the qualification that they desire flexible schedule. But schedule heading conveys that info. Is that acceptable? The instruction: "Preserve ALL substantive information". If we move it, we still preserve it (just in a different place). That's okay as long as it's not lost. So we can place flexible schedule under Schedule heading and not duplicate in qualifications. Thus qualifications list will exclude flexible schedule. Now Benefits: "Comprehensive Benefits – health, dental & vision, 401(k), personal time off, paid holidays and more!" Also later "Benefits Our organization’s diversity initiatives include—but are not limited to—our practices and policies on recruitment and selection, compensation and benefits, professional development and training, promotions, transfers, and the ongoing development of a work environment built on the premise of gender and diversity equity that encourages and enforces: Respectful communication and cooperation between all employees. Teamwork and employee participation, permitting the representation of all groups and employee perspectives. Work/life balance through flexible work schedules to accommodate employees’ varying needs. Employer and employee contributions to the communities we serve promote a greater understanding and respect for diversity." That's a lot. We could have Benefits heading with a- for the concrete benefits list, and then maybe a
for the diversity initiatives description. But diversity initiatives could be under a separate heading? Not in allowed list but we could still include as a
under Benefits heading. Growth and Development: "Growth that is based on achievement and an emphasis on promoting from within our ranks versus just external candidates. Development – a commitment to creating opportunities to learn and expand your knowledge in the industry, from online training platforms to training classes to one-on-one coaching". Could be under Benefits heading as well, or maybe under Skills? Not exactly. Could be under a heading "Development"? Not in allowed list but we could still include as a
under Benefits. Simplify: We'll have Benefits heading with a
- for concrete benefits, and then a
covering growth, development, diversity & inclusion. Now Responsibilities: We'll take the Key Accountabilities bullet points and also the earlier role description maybe as a
preceding the list. Let's list Key Accountabilities items: Customer Service & Sales - At all times, regardless, provides A+ customer service. -
but also break into list? The instruction: Use
- for any list of duties/requirements/benefits. So if we have a list, we should use ul. The responsibilities are not explicitly a list but we can treat each bullet as list item. However we risk losing nuance. Perhaps better to keep as