Assistant Community Manager - Murrieta, CA
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 parse the job posting.
First part: About Greystar (company description). That's not about the role; it's company overview. Should we include? The instruction says we reformat a job posting into clean HTML. Likely we include sections like About the role (maybe summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content.
Let's extract:
Job Description Summary: This role supports and assists the Community Manager in overseeing and managing the financial and operational facets of the community by completing accounting and bookkeeping tasks, preparing monthly close-out and financial reports, processing invoices for payment, collecting rent, fees, and other payments, completing bank deposits, dispositions, and account reconciliations, and using the property management software to record, track, and report on all financial workings of the community.
That's a summary; could be "About the role" or "Job Description Summary". We'll treat as "About the role".
Then "Job Description" heading with details: Property Type: Lease Up Unit Count: 322 Schedule: Monday - Friday, *Subject to change based on property needs. Experience requirements: 2+ years of Assistant Community Manager experience required. Lease up experience required. Then bullet-like paragraphs: Completes the daily transactions..., Operates the property management software..., Reviews resident files..., Reviews and submits invoices..., Follows the Company’s established procedures..., Processes resident move-outs..., Promotes resident satisfaction..., Acts as the on-site supervisor..., Assists in managing the client/owner relationship..., May assist and/or support leasing and marketing efforts..., For California Only: The Assistant Community Manager or Leasing Manager must review all completed move in files prior to submission to the Community Manager for review and approval.
These are responsibilities/duties. Could be "Responsibilities".
Then "BASIC KNOWLEDGE & QUALIFICATIONS:" with bullet-like sentences: Bachelor’s degree in Business Management, Communications, or related field from an accredited college or university is preferred. 1-3 years minimum of relevant experience in residence life and/or property management that demonstrates the application of community management, sales, marketing, and customer service background sufficient to assist in managing the day-to-day operations of an apartment community, resolve customer complaints and issues, complete financial records, documents, and reports, increase sales revenues, and coordinate the work of a team. Understanding of lease terms and lease enforcement, including collections. Excellent written and verbal communication skills. Detail-oriented and self-motivated with the ability to work independently and as a collaborative member of a team.
That's qualifications/requirements.
Then "SPECIALIZED SKILLS:" with bullet-like sentences: Incumbents must have all licenses and/or certifications as required by State and Local jurisdictions. Incumbents must have valid driver’s license to drive a golf cart on property. Demonstrated proficiency in Internet, word processing, spreadsheet, and database management programs in order to complete required reports and documents. Strong proficiency in using property management software (Yardi, OneSite, Entrata, etc.).
That's skills.
Then "TRAVEL / PHYSICAL DEMANDS:" with bullet-like sentences: Team members work in an office environment but also may have frequent exposure to outside elements where temperature, weather, odors, and/or landscape may be unpleasant and/or hazardous. Incumbents must be able to physically access all exterior and interior parts of the property and amenities. Incumbents must be able to physically access all exterior and interior parts of the community and amenities. Incumbents must be able to push, pull, lift, carry, or maneuver weights of up to twenty (20) pounds independently and fifty (50) pounds with assistance. Routine local travel may be required to make bank deposits, attend training classes, or other situations necessary for the accomplishment of some or all of the daily responsibilities of this position. Rare or occasional travel may be required to attend business meetings, training programs, or other situations necessary for the accomplishment of some or all of the daily responsibilities of this position.
That could be "Physical Demands" or "Travel". Not in list of headings but we could include as a section maybe "Travel & Physical Demands". But instruction says use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But they say "Prefer a few substantive sections over many thin ones." We could combine travel/physical demands into maybe "Requirements" or "Qualifications". However they are not exactly requirements but physical demands. Could be part of "Requirements". We'll include them under a "Requirements" section maybe.
Then "The hourly pay range for this position is $27-$30/hour. (Murrieta, CA)" That's pay. So we need a Pay section.
Then "Additional Compensation: Many factors go into determining employee pay within the posted range including business requirements, prior experience, current skills and geographical location. Corporate Positions: In addition to the base salary, this role may be eligible to participate in a quarterly or annual bonus program based on individual and company performance. Onsite Property Positions: In addition to the base salary, this role may be eligible to participate in weekly, monthly, and/or quarterly bonus programs." That's also compensation details; could be part of Pay section.
Then "Robust Benefits Offered*: Competitive Medical, Dental, Vision, and Disability & Life insurance benefits. Low (free basic) employee Medical costs for employee-only coverage; costs discounted after 3 and 5 years of service. Generous Paid Time off. All new hires start with 15 days of vacation, 4 personal days, 10 sick days, and 11 paid holidays. Plus your birthday off after 1 year of service! Additional vacation accrued with tenure. For onsite team members, onsite housing discount at Greystar-managed communities are available subject to discount and unit availability. 6-Week Paid Sabbatical after 10 years of service (and every 5 years thereafter). 401(k) with Company Match up to 6% of pay after 6 months of service. Paid Parental Leave and lifetime Fertility Benefit reimbursement up to $10,000 (includes adoption or surrogacy). Employee Assistance Program. Critical Illness, Accident, Hospital Indemnity, Pet Insurance and Legal Plans. Charitable giving program and benefits. Benefits offered for full-time employees. For Union and Prevailing Wage roles, compensation and benefits may vary from the listed information above due to Collective Bargaining Agreements and/or local governing authority." That's benefits.
Then "Greystar will consider for employment qualified applicants with arrest and conviction records. Greystar is an equal opportunity employer..." That's EEO boilerplate; we should remove.
Then "Important Notice: Greystar will never request your banking details..." That's scam-warning boilerplate; remove.
Thus we need sections: About the role (summary), Responsibilities (duties), Requirements (maybe combine experience requirements and basic knowledge?), Qualifications (maybe basic knowledge & qualifications?), Skills (specialized skills), Benefits, Pay, Schedule (we have schedule mentioned: Monday - Friday, *Subject to change based on property needs). That's schedule info.
We must not create sections with filler. All have content.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide what to put in lists vs paragraphs.
For Responsibilities: we have many duty sentences. Could make a
with each duty as - . Similarly for Requirements/Qualifications/Skills/Benefits.
But we need to avoid duplication. Let's extract each piece.
First, About the role: The summary paragraph. We'll put in
.
Second, Responsibilities: list of duties from "Completes the daily transactions..." through "May assist and/or support leasing and marketing efforts..." plus the California-only note. We'll make each a list item.
Third, Requirements: Could include experience requirements: "2+ years of Assistant Community Manager experience required. Lease up experience required." Also maybe "Property Type: Lease Up Unit Count: 322" is not a requirement but property details. Could be metadata; maybe we drop or put in a short
. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So property type and unit count could be minor metadata; we could include in a short
under About the role or separate. But we could also drop. However we need to preserve ALL substantive information; property type and unit count is substantive? It's about the job; maybe we keep as a short paragraph.
Schedule: "Monday - Friday, *Subject to change based on property needs." That's schedule; we need a Schedule section.
Pay: "$27-$30/hour. (Murrieta, CA)" plus additional compensation details.
Benefits: the robust benefits offered.
Now, we also have "BASIC KNOWLEDGE & QUALIFICATIONS:" and "SPECIALIZED SKILLS:" and "TRAVEL / PHYSICAL DEMANDS:".
We could treat BASIC KNOWLEDGE & QUALIFICATIONS as "Qualifications". SPECIALIZED SKILLS as "Skills". TRAVEL / PHYSICAL DEMANDS could be part of "Requirements" or its own section but not in list; maybe we incorporate into Requirements.
We need to avoid too many thin sections. Let's aim for sections: About the role, Responsibilities, Requirements (includes experience, basic knowledge, travel/physical demands), Qualifications (maybe we merge with Requirements?), Skills, Benefits, Pay, Schedule.
But we have both Requirements and Qualifications; they may overlap. Could combine into one "Requirements & Qualifications". But instruction says prefer few substantive sections over many thin ones. So maybe we combine Basic Knowledge & Qualifications and Specialized Skills into a single "Requirements" section? However they are distinct: qualifications vs skills. Could still be separate but we risk many sections.
Let's think: The typical job posting sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. That's 8 sections. That's okay if each has substantive content. We have content for each.
Let's assign:
- About the role: summary paragraph.
- Responsibilities: list of duties.
- Requirements: maybe the experience requirements (2+ years Assistant Community Manager, lease up experience) plus property type/unit count? Actually property type is not a requirement. Could be under About the role. We'll
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 parse the job posting. First part: About Greystar (company description). That's not about the role; it's company overview. Should we include? The instruction says we reformat a job posting into clean HTML. Likely we include sections like About the role (maybe summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. Let's extract: Job Description Summary: This role supports and assists the Community Manager in overseeing and managing the financial and operational facets of the community by completing accounting and bookkeeping tasks, preparing monthly close-out and financial reports, processing invoices for payment, collecting rent, fees, and other payments, completing bank deposits, dispositions, and account reconciliations, and using the property management software to record, track, and report on all financial workings of the community. That's a summary; could be "About the role" or "Job Description Summary". We'll treat as "About the role". Then "Job Description" heading with details: Property Type: Lease Up Unit Count: 322 Schedule: Monday - Friday, *Subject to change based on property needs. Experience requirements: 2+ years of Assistant Community Manager experience required. Lease up experience required. Then bullet-like paragraphs: Completes the daily transactions..., Operates the property management software..., Reviews resident files..., Reviews and submits invoices..., Follows the Company’s established procedures..., Processes resident move-outs..., Promotes resident satisfaction..., Acts as the on-site supervisor..., Assists in managing the client/owner relationship..., May assist and/or support leasing and marketing efforts..., For California Only: The Assistant Community Manager or Leasing Manager must review all completed move in files prior to submission to the Community Manager for review and approval. These are responsibilities/duties. Could be "Responsibilities". Then "BASIC KNOWLEDGE & QUALIFICATIONS:" with bullet-like sentences: Bachelor’s degree in Business Management, Communications, or related field from an accredited college or university is preferred. 1-3 years minimum of relevant experience in residence life and/or property management that demonstrates the application of community management, sales, marketing, and customer service background sufficient to assist in managing the day-to-day operations of an apartment community, resolve customer complaints and issues, complete financial records, documents, and reports, increase sales revenues, and coordinate the work of a team. Understanding of lease terms and lease enforcement, including collections. Excellent written and verbal communication skills. Detail-oriented and self-motivated with the ability to work independently and as a collaborative member of a team. That's qualifications/requirements. Then "SPECIALIZED SKILLS:" with bullet-like sentences: Incumbents must have all licenses and/or certifications as required by State and Local jurisdictions. Incumbents must have valid driver’s license to drive a golf cart on property. Demonstrated proficiency in Internet, word processing, spreadsheet, and database management programs in order to complete required reports and documents. Strong proficiency in using property management software (Yardi, OneSite, Entrata, etc.). That's skills. Then "TRAVEL / PHYSICAL DEMANDS:" with bullet-like sentences: Team members work in an office environment but also may have frequent exposure to outside elements where temperature, weather, odors, and/or landscape may be unpleasant and/or hazardous. Incumbents must be able to physically access all exterior and interior parts of the property and amenities. Incumbents must be able to physically access all exterior and interior parts of the community and amenities. Incumbents must be able to push, pull, lift, carry, or maneuver weights of up to twenty (20) pounds independently and fifty (50) pounds with assistance. Routine local travel may be required to make bank deposits, attend training classes, or other situations necessary for the accomplishment of some or all of the daily responsibilities of this position. Rare or occasional travel may be required to attend business meetings, training programs, or other situations necessary for the accomplishment of some or all of the daily responsibilities of this position. That could be "Physical Demands" or "Travel". Not in list of headings but we could include as a section maybe "Travel & Physical Demands". But instruction says use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But they say "Prefer a few substantive sections over many thin ones." We could combine travel/physical demands into maybe "Requirements" or "Qualifications". However they are not exactly requirements but physical demands. Could be part of "Requirements". We'll include them under a "Requirements" section maybe.
Then "The hourly pay range for this position is $27-$30/hour. (Murrieta, CA)" That's pay. So we need a Pay section.
Then "Additional Compensation: Many factors go into determining employee pay within the posted range including business requirements, prior experience, current skills and geographical location. Corporate Positions: In addition to the base salary, this role may be eligible to participate in a quarterly or annual bonus program based on individual and company performance. Onsite Property Positions: In addition to the base salary, this role may be eligible to participate in weekly, monthly, and/or quarterly bonus programs." That's also compensation details; could be part of Pay section.
Then "Robust Benefits Offered*: Competitive Medical, Dental, Vision, and Disability & Life insurance benefits. Low (free basic) employee Medical costs for employee-only coverage; costs discounted after 3 and 5 years of service. Generous Paid Time off. All new hires start with 15 days of vacation, 4 personal days, 10 sick days, and 11 paid holidays. Plus your birthday off after 1 year of service! Additional vacation accrued with tenure. For onsite team members, onsite housing discount at Greystar-managed communities are available subject to discount and unit availability. 6-Week Paid Sabbatical after 10 years of service (and every 5 years thereafter). 401(k) with Company Match up to 6% of pay after 6 months of service. Paid Parental Leave and lifetime Fertility Benefit reimbursement up to $10,000 (includes adoption or surrogacy). Employee Assistance Program. Critical Illness, Accident, Hospital Indemnity, Pet Insurance and Legal Plans. Charitable giving program and benefits. Benefits offered for full-time employees. For Union and Prevailing Wage roles, compensation and benefits may vary from the listed information above due to Collective Bargaining Agreements and/or local governing authority." That's benefits.
Then "Greystar will consider for employment qualified applicants with arrest and conviction records. Greystar is an equal opportunity employer..." That's EEO boilerplate; we should remove.
Then "Important Notice: Greystar will never request your banking details..." That's scam-warning boilerplate; remove.
Thus we need sections: About the role (summary), Responsibilities (duties), Requirements (maybe combine experience requirements and basic knowledge?), Qualifications (maybe basic knowledge & qualifications?), Skills (specialized skills), Benefits, Pay, Schedule (we have schedule mentioned: Monday - Friday, *Subject to change based on property needs). That's schedule info.
We must not create sections with filler. All have content.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide what to put in lists vs paragraphs.
For Responsibilities: we have many duty sentences. Could make a
with each duty as - . Similarly for Requirements/Qualifications/Skills/Benefits.
But we need to avoid duplication. Let's extract each piece.
First, About the role: The summary paragraph. We'll put in
.
Second, Responsibilities: list of duties from "Completes the daily transactions..." through "May assist and/or support leasing and marketing efforts..." plus the California-only note. We'll make each a list item.
Third, Requirements: Could include experience requirements: "2+ years of Assistant Community Manager experience required. Lease up experience required." Also maybe "Property Type: Lease Up Unit Count: 322" is not a requirement but property details. Could be metadata; maybe we drop or put in a short
. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So property type and unit count could be minor metadata; we could include in a short
under About the role or separate. But we could also drop. However we need to preserve ALL substantive information; property type and unit count is substantive? It's about the job; maybe we keep as a short paragraph.
Schedule: "Monday - Friday, *Subject to change based on property needs." That's schedule; we need a Schedule section.
Pay: "$27-$30/hour. (Murrieta, CA)" plus additional compensation details.
Benefits: the robust benefits offered.
Now, we also have "BASIC KNOWLEDGE & QUALIFICATIONS:" and "SPECIALIZED SKILLS:" and "TRAVEL / PHYSICAL DEMANDS:".
We could treat BASIC KNOWLEDGE & QUALIFICATIONS as "Qualifications". SPECIALIZED SKILLS as "Skills". TRAVEL / PHYSICAL DEMANDS could be part of "Requirements" or its own section but not in list; maybe we incorporate into Requirements.
We need to avoid too many thin sections. Let's aim for sections: About the role, Responsibilities, Requirements (includes experience, basic knowledge, travel/physical demands), Qualifications (maybe we merge with Requirements?), Skills, Benefits, Pay, Schedule.
But we have both Requirements and Qualifications; they may overlap. Could combine into one "Requirements & Qualifications". But instruction says prefer few substantive sections over many thin ones. So maybe we combine Basic Knowledge & Qualifications and Specialized Skills into a single "Requirements" section? However they are distinct: qualifications vs skills. Could still be separate but we risk many sections.
Let's think: The typical job posting sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. That's 8 sections. That's okay if each has substantive content. We have content for each.
Let's assign:
- About the role: summary paragraph.
- Responsibilities: list of duties.
- Requirements: maybe the experience requirements (2+ years Assistant Community Manager, lease up experience) plus property type/unit count? Actually property type is not a requirement. Could be under About the role. We'll
- for any list of duties/requirements/benefits. Use
for prose. We need to decide what to put in lists vs paragraphs. For Responsibilities: we have many duty sentences. Could make a
- with each duty as
- . Similarly for Requirements/Qualifications/Skills/Benefits.
But we need to avoid duplication. Let's extract each piece.
First, About the role: The summary paragraph. We'll put in
. Second, Responsibilities: list of duties from "Completes the daily transactions..." through "May assist and/or support leasing and marketing efforts..." plus the California-only note. We'll make each a list item. Third, Requirements: Could include experience requirements: "2+ years of Assistant Community Manager experience required. Lease up experience required." Also maybe "Property Type: Lease Up Unit Count: 322" is not a requirement but property details. Could be metadata; maybe we drop or put in a short
. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So property type and unit count could be minor metadata; we could include in a short
under About the role or separate. But we could also drop. However we need to preserve ALL substantive information; property type and unit count is substantive? It's about the job; maybe we keep as a short paragraph. Schedule: "Monday - Friday, *Subject to change based on property needs." That's schedule; we need a Schedule section. Pay: "$27-$30/hour. (Murrieta, CA)" plus additional compensation details. Benefits: the robust benefits offered. Now, we also have "BASIC KNOWLEDGE & QUALIFICATIONS:" and "SPECIALIZED SKILLS:" and "TRAVEL / PHYSICAL DEMANDS:". We could treat BASIC KNOWLEDGE & QUALIFICATIONS as "Qualifications". SPECIALIZED SKILLS as "Skills". TRAVEL / PHYSICAL DEMANDS could be part of "Requirements" or its own section but not in list; maybe we incorporate into Requirements. We need to avoid too many thin sections. Let's aim for sections: About the role, Responsibilities, Requirements (includes experience, basic knowledge, travel/physical demands), Qualifications (maybe we merge with Requirements?), Skills, Benefits, Pay, Schedule. But we have both Requirements and Qualifications; they may overlap. Could combine into one "Requirements & Qualifications". But instruction says prefer few substantive sections over many thin ones. So maybe we combine Basic Knowledge & Qualifications and Specialized Skills into a single "Requirements" section? However they are distinct: qualifications vs skills. Could still be separate but we risk many sections. Let's think: The typical job posting sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. That's 8 sections. That's okay if each has substantive content. We have content for each. Let's assign: - About the role: summary paragraph. - Responsibilities: list of duties. - Requirements: maybe the experience requirements (2+ years Assistant Community Manager, lease up experience) plus property type/unit count? Actually property type is not a requirement. Could be under About the role. We'll
- . Similarly for Requirements/Qualifications/Skills/Benefits.
But we need to avoid duplication. Let's extract each piece.
First, About the role: The summary paragraph. We'll put in