Leasing Consultant
Eagle Rock Properties · Ambler, PA · 1 mo ago
On-siteSalesFull-time
Here's a thinking process:
1. **Analyze User Input:**
- **Company:** Eagle Rock Properties, headquartered in New York, full-service real estate firm
- **Services:** investment management, property management, construction management
- **Team:** 275+ professionals
- **Specialization:** rental apartment communities across Northeast & Mid-Atlantic US
- **Leadership:** executives with 30+ years experience
- **Role:** Leasing Consultant
- **Reporting:** under Community Manager
- **Goal:** maximize property occupancy, generate qualified traffic, network locally, schedule appointments, promote retention, provide/coordinate exceptional customer service
- **Level:** entry-level, willing to train
- **Responsibilities:** (list of 12 bullet points)
- **Qualifications:** (list of 8 bullet points)
- **EEO statement** at the end
2. **Identify Rules from Prompt:**
- Use `` for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule
- Use `
` for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule
- Use `- ` for lists of duties/requirements/benefits
- Use `
` 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
3. **Map Content to Sections:**
- The posting has: Company description, Role description, Responsibilities, Qualifications, EEO statement (to remove)
- I need to identify which sections have real content:
- "About the role" / company info: The posting starts with company description, but the rule says "do NOT repeat the job title as a heading (the page already shows it)". It also says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I need to decide how to handle the company/role intro. The prompt says "About the role" is a heading example. The company description is substantial. I could put it under a section or as prose before headings. But the rule says output ONLY HTML fragment with those headings. Let re-read carefully: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say I must use all of them, only include a section ONLY when the posting has real, specific content for it. Also "Do NOT repeat the job title as a heading (the page already shows it)". So I shouldn't have an Leasing Consultant
.
- Let's list potential sections and what content they'd have:
- About the role/company: The posting has company info and role description. I could make a section with that, or integrate it. The prompt says "About the role" is an example heading. I think I should include sections that have specific content. The company description is specific. The role responsibilities and qualifications are specific.
- Responsibilities: Yes, 12 items listed.
- Requirements/Qualifications: Yes, qualifications listed. The prompt says "Requirements" is a heading example. Qualifications section is there.
- Skills: The qualifications mention skills (Microsoft Office, communication, etc.). I could put that under Qualifications or Skills. The prompt lists "Skills" as a possible heading. I'll see if there's distinct skill content beyond qualifications. The qualifications already cover skills. I might merge or have a brief Skills section if there's notable specific skills not covered. But the rule says prefer few substantive sections over many thin ones. So maybe I skip Skills if it's redundant.
- Benefits: Not mentioned in posting. Rule: never create Benefits section unless posting actually states them. So skip.
- Pay/Schedule: Not mentioned. Rule: never create unless posting actually states them. So skip.
- EEO boilerplate: Must remove. The posting ends with "Eagle Rock Management provides equal employment opportunities (EEO) to all employees..." I need to remove this entirely per rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions."
- Now, structure decisions:
- I'll create sections that have real content:
- About the company/role (maybe combine company info and role summary into one section, or use "About the role" heading). The prompt says "About the role" is an example heading. The posting has company info + role summary. I'll use About the role
and put the prose there. But wait: "Do NOT repeat the job title as a heading (the page already shows it)". That refers to the job title "Leasing Consultant". So I shouldn't have Leasing Consultant
. I can have About the role
.
- Responsibilities: Responsibilities
with - items.
- Qualifications:
Qualifications
with - items. The prompt says "Requirements" is also a heading example, but "Qualifications" is listed too. The posting has "Qualifications:" section. I'll use
Qualifications
.
- Skills: The qualifications list skills. I could either put them under Qualifications or make a separate Skills section. Since the rule says "Prefer a few substantive sections over many thin ones", and skills are already in qualifications, I'll likely omit a separate Skills section to avoid thinness. But maybe I can extract the skill-specific items that are distinct from general qualifications. Looking at qualifications: "1-2 years of high-quality customer service experience", "Prior leasing & lease-up experience preferred", "Strong communication & marketing skills", "Professional and positive attitude", "College Degree preferred", "Proficient in Microsoft Office Suite, Outlook", "Must be able to work weekends and have a reliable way to get to work". These are a mix of experience, education, skills, and availability. I think putting them under Qualifications is fine, and I'll skip a separate Skills section.
- Actually, the prompt explicitly lists possible headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It uses "Requirements" and "Qualifications" separately in the example. The posting has "Qualifications:" as a heading. I could split into Requirements and Qualifications, but the content blurs that. I'll just use Qualifications since that's what the posting uses, and it contains both requirements and qualifications. To be safe, I could make two sections: "Requirements" and "Qualifications", but the rule says prefer few substantive sections over many thin ones. If I split, each might be thin. I'll stick with one Qualifications section containing all listed items.
- Let's re-read the prompt's heading examples: "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It's not exhaustive mandate, just examples. I'll include sections that have content. I'll do: About the role, Responsibilities, Qualifications. I'll skip Skills, Benefits, Pay, Schedule because either content is redundant or absent.
- Let's map the prose content:
* Company intro: "Eagle Rock Properties, headquartered in New York, is a full-service real estate firm offering investment management, property management, and construction management services. With a team of over 275 professionals, we specialize in rental apartment communities across the Northeast and Mid-Atlantic regions of the United States. Under the leadership of our executives, who have owned and managed properties for more than 30 years, Eagle Rock Properties has emerged as a pioneering force in the industry."
* Role summary: "The Leasing Consultant, under the direction of the Community Manager, is responsible for maximizing property occupancy by generating qualified traffic, networking within the local community, scheduling appointments, promoting resident retention and providing or coordinating exceptional customer service. The position is entry-level, but we would be willing to train the right candidate."
- I need to output HTML fragment with headings, - lists,
for prose. No job title heading. No EEO. No benefits/pay/schedule.
- Structure plan:
About the role
...prose combining company intro and role summary...>
Actually, the company intro is about the company, not just the role. Maybe I should have About Eagle Rock Properties
but the example says "About the role". I'll use "About the role" and include the company context as part of the role description, since it's relevant. Or I could split, but rule says prefer few sections. I'll put the company description and role summary together under "About the role".
Responsibilities
- Greeting prospective residents and provide them with property tours
- Process lease applications and qualify residents
- Coordinate with the marketing team to place online ads and ensure signage is correctly positioned
- Support the Community Manager with general office maintenance by answering phones and performing other administrative task
- Maintain an up-to-date market study of primary competitors
- Provide high quality customer service to residents and prospective residents
- Effectively showcase the features and benefits of the apartments and communities
- Identify strengths & weakness of alternative sales approach; overcome objections and create excitement
- Accurately prepare all lease-related documents
- Consistent and timely follow-up on all calls, emails, and site visits
Qualifications
- 1-2 years of high-quality customer service experience
- Prior leasing & lease-up experience preferred
- Strong communication & marketing skills
- Professional and positive attitude
- College Degree preferred
- Proficient in Microsoft Office Suite, Outlook
- Must be able to work weekends and have a reliable way to get to work
- Check rules:
- Use for section headings: yes.
- Use - for any list of duties/requirements/benefits: yes.
- Use
for prose: yes.
- Do NOT repeat the job title as a heading: I'm not using "Leasing Consultant" as a heading. I'm using "About the role", "Responsibilities", "Qualifications". Good.
- Do NOT put Job ID / requisition numbers as headings: none present.
- Preserve ALL substantive information: I'm including all responsibilities and qualifications items verbatim. Good.
- Remove EEO boilerplate: I'm not including the final EEO statement. Good.
- Remove cookie/navigation/legal/equal-op
` 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 3. **Map Content to Sections:** - The posting has: Company description, Role description, Responsibilities, Qualifications, EEO statement (to remove) - I need to identify which sections have real content: - "About the role" / company info: The posting starts with company description, but the rule says "do NOT repeat the job title as a heading (the page already shows it)". It also says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I need to decide how to handle the company/role intro. The prompt says "About the role" is a heading example. The company description is substantial. I could put it under a section or as prose before headings. But the rule says output ONLY HTML fragment with those headings. Let re-read carefully: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say I must use all of them, only include a section ONLY when the posting has real, specific content for it. Also "Do NOT repeat the job title as a heading (the page already shows it)". So I shouldn't have an Leasing Consultant
.
- Let's list potential sections and what content they'd have:
- About the role/company: The posting has company info and role description. I could make a section with that, or integrate it. The prompt says "About the role" is an example heading. I think I should include sections that have specific content. The company description is specific. The role responsibilities and qualifications are specific.
- Responsibilities: Yes, 12 items listed.
- Requirements/Qualifications: Yes, qualifications listed. The prompt says "Requirements" is a heading example. Qualifications section is there.
- Skills: The qualifications mention skills (Microsoft Office, communication, etc.). I could put that under Qualifications or Skills. The prompt lists "Skills" as a possible heading. I'll see if there's distinct skill content beyond qualifications. The qualifications already cover skills. I might merge or have a brief Skills section if there's notable specific skills not covered. But the rule says prefer few substantive sections over many thin ones. So maybe I skip Skills if it's redundant.
- Benefits: Not mentioned in posting. Rule: never create Benefits section unless posting actually states them. So skip.
- Pay/Schedule: Not mentioned. Rule: never create unless posting actually states them. So skip.
- EEO boilerplate: Must remove. The posting ends with "Eagle Rock Management provides equal employment opportunities (EEO) to all employees..." I need to remove this entirely per rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions."
- Now, structure decisions:
- I'll create sections that have real content:
- About the company/role (maybe combine company info and role summary into one section, or use "About the role" heading). The prompt says "About the role" is an example heading. The posting has company info + role summary. I'll use About the role
and put the prose there. But wait: "Do NOT repeat the job title as a heading (the page already shows it)". That refers to the job title "Leasing Consultant". So I shouldn't have Leasing Consultant
. I can have About the role
.
- Responsibilities: Responsibilities
with - items.
- Qualifications:
Qualifications
with - items. The prompt says "Requirements" is also a heading example, but "Qualifications" is listed too. The posting has "Qualifications:" section. I'll use
Qualifications
.
- Skills: The qualifications list skills. I could either put them under Qualifications or make a separate Skills section. Since the rule says "Prefer a few substantive sections over many thin ones", and skills are already in qualifications, I'll likely omit a separate Skills section to avoid thinness. But maybe I can extract the skill-specific items that are distinct from general qualifications. Looking at qualifications: "1-2 years of high-quality customer service experience", "Prior leasing & lease-up experience preferred", "Strong communication & marketing skills", "Professional and positive attitude", "College Degree preferred", "Proficient in Microsoft Office Suite, Outlook", "Must be able to work weekends and have a reliable way to get to work". These are a mix of experience, education, skills, and availability. I think putting them under Qualifications is fine, and I'll skip a separate Skills section.
- Actually, the prompt explicitly lists possible headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It uses "Requirements" and "Qualifications" separately in the example. The posting has "Qualifications:" as a heading. I could split into Requirements and Qualifications, but the content blurs that. I'll just use Qualifications since that's what the posting uses, and it contains both requirements and qualifications. To be safe, I could make two sections: "Requirements" and "Qualifications", but the rule says prefer few substantive sections over many thin ones. If I split, each might be thin. I'll stick with one Qualifications section containing all listed items.
- Let's re-read the prompt's heading examples: "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It's not exhaustive mandate, just examples. I'll include sections that have content. I'll do: About the role, Responsibilities, Qualifications. I'll skip Skills, Benefits, Pay, Schedule because either content is redundant or absent.
- Let's map the prose content:
* Company intro: "Eagle Rock Properties, headquartered in New York, is a full-service real estate firm offering investment management, property management, and construction management services. With a team of over 275 professionals, we specialize in rental apartment communities across the Northeast and Mid-Atlantic regions of the United States. Under the leadership of our executives, who have owned and managed properties for more than 30 years, Eagle Rock Properties has emerged as a pioneering force in the industry."
* Role summary: "The Leasing Consultant, under the direction of the Community Manager, is responsible for maximizing property occupancy by generating qualified traffic, networking within the local community, scheduling appointments, promoting resident retention and providing or coordinating exceptional customer service. The position is entry-level, but we would be willing to train the right candidate."
- I need to output HTML fragment with headings, - lists,
for prose. No job title heading. No EEO. No benefits/pay/schedule.
- Structure plan:
About the role
...prose combining company intro and role summary...>
Actually, the company intro is about the company, not just the role. Maybe I should have About Eagle Rock Properties
but the example says "About the role". I'll use "About the role" and include the company context as part of the role description, since it's relevant. Or I could split, but rule says prefer few sections. I'll put the company description and role summary together under "About the role".
Responsibilities
- Greeting prospective residents and provide them with property tours
- Process lease applications and qualify residents
- Coordinate with the marketing team to place online ads and ensure signage is correctly positioned
- Support the Community Manager with general office maintenance by answering phones and performing other administrative task
- Maintain an up-to-date market study of primary competitors
- Provide high quality customer service to residents and prospective residents
- Effectively showcase the features and benefits of the apartments and communities
- Identify strengths & weakness of alternative sales approach; overcome objections and create excitement
- Accurately prepare all lease-related documents
- Consistent and timely follow-up on all calls, emails, and site visits
Qualifications
- 1-2 years of high-quality customer service experience
- Prior leasing & lease-up experience preferred
- Strong communication & marketing skills
- Professional and positive attitude
- College Degree preferred
- Proficient in Microsoft Office Suite, Outlook
- Must be able to work weekends and have a reliable way to get to work
- Check rules:
- Use for section headings: yes.
- Use - for any list of duties/requirements/benefits: yes.
- Use
for prose: yes.
- Do NOT repeat the job title as a heading: I'm not using "Leasing Consultant" as a heading. I'm using "About the role", "Responsibilities", "Qualifications". Good.
- Do NOT put Job ID / requisition numbers as headings: none present.
- Preserve ALL substantive information: I'm including all responsibilities and qualifications items verbatim. Good.
- Remove EEO boilerplate: I'm not including the final EEO statement. Good.
- Remove cookie/navigation/legal/equal-op
Leasing Consultant
. - Let's list potential sections and what content they'd have: - About the role/company: The posting has company info and role description. I could make a section with that, or integrate it. The prompt says "About the role" is an example heading. I think I should include sections that have specific content. The company description is specific. The role responsibilities and qualifications are specific. - Responsibilities: Yes, 12 items listed. - Requirements/Qualifications: Yes, qualifications listed. The prompt says "Requirements" is a heading example. Qualifications section is there. - Skills: The qualifications mention skills (Microsoft Office, communication, etc.). I could put that under Qualifications or Skills. The prompt lists "Skills" as a possible heading. I'll see if there's distinct skill content beyond qualifications. The qualifications already cover skills. I might merge or have a brief Skills section if there's notable specific skills not covered. But the rule says prefer few substantive sections over many thin ones. So maybe I skip Skills if it's redundant. - Benefits: Not mentioned in posting. Rule: never create Benefits section unless posting actually states them. So skip. - Pay/Schedule: Not mentioned. Rule: never create unless posting actually states them. So skip. - EEO boilerplate: Must remove. The posting ends with "Eagle Rock Management provides equal employment opportunities (EEO) to all employees..." I need to remove this entirely per rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." - Now, structure decisions: - I'll create sections that have real content: - About the company/role (maybe combine company info and role summary into one section, or use "About the role" heading). The prompt says "About the role" is an example heading. The posting has company info + role summary. I'll useAbout the role
and put the prose there. But wait: "Do NOT repeat the job title as a heading (the page already shows it)". That refers to the job title "Leasing Consultant". So I shouldn't haveLeasing Consultant
. I can haveAbout the role
. - Responsibilities:Responsibilities
with- items.
- Qualifications:
Qualifications
with- items. The prompt says "Requirements" is also a heading example, but "Qualifications" is listed too. The posting has "Qualifications:" section. I'll use
Qualifications
. - Skills: The qualifications list skills. I could either put them under Qualifications or make a separate Skills section. Since the rule says "Prefer a few substantive sections over many thin ones", and skills are already in qualifications, I'll likely omit a separate Skills section to avoid thinness. But maybe I can extract the skill-specific items that are distinct from general qualifications. Looking at qualifications: "1-2 years of high-quality customer service experience", "Prior leasing & lease-up experience preferred", "Strong communication & marketing skills", "Professional and positive attitude", "College Degree preferred", "Proficient in Microsoft Office Suite, Outlook", "Must be able to work weekends and have a reliable way to get to work". These are a mix of experience, education, skills, and availability. I think putting them under Qualifications is fine, and I'll skip a separate Skills section. - Actually, the prompt explicitly lists possible headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It uses "Requirements" and "Qualifications" separately in the example. The posting has "Qualifications:" as a heading. I could split into Requirements and Qualifications, but the content blurs that. I'll just use Qualifications since that's what the posting uses, and it contains both requirements and qualifications. To be safe, I could make two sections: "Requirements" and "Qualifications", but the rule says prefer few substantive sections over many thin ones. If I split, each might be thin. I'll stick with one Qualifications section containing all listed items. - Let's re-read the prompt's heading examples: "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It's not exhaustive mandate, just examples. I'll include sections that have content. I'll do: About the role, Responsibilities, Qualifications. I'll skip Skills, Benefits, Pay, Schedule because either content is redundant or absent. - Let's map the prose content: * Company intro: "Eagle Rock Properties, headquartered in New York, is a full-service real estate firm offering investment management, property management, and construction management services. With a team of over 275 professionals, we specialize in rental apartment communities across the Northeast and Mid-Atlantic regions of the United States. Under the leadership of our executives, who have owned and managed properties for more than 30 years, Eagle Rock Properties has emerged as a pioneering force in the industry." * Role summary: "The Leasing Consultant, under the direction of the Community Manager, is responsible for maximizing property occupancy by generating qualified traffic, networking within the local community, scheduling appointments, promoting resident retention and providing or coordinating exceptional customer service. The position is entry-level, but we would be willing to train the right candidate." - I need to output HTML fragment withheadings,
- lists,
for prose. No job title heading. No EEO. No benefits/pay/schedule. - Structure plan:
About the role
...prose combining company intro and role summary...>
Actually, the company intro is about the company, not just the role. Maybe I should haveAbout Eagle Rock Properties
but the example says "About the role". I'll use "About the role" and include the company context as part of the role description, since it's relevant. Or I could split, but rule says prefer few sections. I'll put the company description and role summary together under "About the role".Responsibilities
- Greeting prospective residents and provide them with property tours
- Process lease applications and qualify residents
- Coordinate with the marketing team to place online ads and ensure signage is correctly positioned
- Support the Community Manager with general office maintenance by answering phones and performing other administrative task
- Maintain an up-to-date market study of primary competitors
- Provide high quality customer service to residents and prospective residents
- Effectively showcase the features and benefits of the apartments and communities
- Identify strengths & weakness of alternative sales approach; overcome objections and create excitement
- Accurately prepare all lease-related documents
- Consistent and timely follow-up on all calls, emails, and site visits
Qualifications
- 1-2 years of high-quality customer service experience
- Prior leasing & lease-up experience preferred
- Strong communication & marketing skills
- Professional and positive attitude
- College Degree preferred
- Proficient in Microsoft Office Suite, Outlook
- Must be able to work weekends and have a reliable way to get to work
for section headings: yes. - Use
- for any list of duties/requirements/benefits: yes.
- Use
for prose: yes. - Do NOT repeat the job title as a heading: I'm not using "Leasing Consultant" as a heading. I'm using "About the role", "Responsibilities", "Qualifications". Good. - Do NOT put Job ID / requisition numbers as headings: none present. - Preserve ALL substantive information: I'm including all responsibilities and qualifications items verbatim. Good. - Remove EEO boilerplate: I'm not including the final EEO statement. Good. - Remove cookie/navigation/legal/equal-op
- lists,
- items. The prompt says "Requirements" is also a heading example, but "Qualifications" is listed too. The posting has "Qualifications:" section. I'll use