Community Assistant - The Hilltop (Student Living)
Greystar · Santa Cruz, CA · 1 mo ago
OTHR$16.9–$17.5/hrPart-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About Greystar" (company description) and "Job Description Summary" and "Job Description" details. We need to use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real, specific content. We must not repeat job title as heading. We must not put Job ID etc. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning). So we need to extract substantive info: company description (About Greystar) could be placed under "About the role"? Actually "About the role" heading is for role description, not company. But we have company description; maybe we can put under "About the role"? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must use those exact headings, just examples. It says "use
.
List items:
- Performs administrative tasks for the leasing office including but not limited to: copying documents, filing resident files, preparing notices, handling resident calls, and organizing rent payments and other collateral materials.
- Assists with sales and leasing activities to achieve the property’s revenue and occupancy goals by conducting virtual tours, responding to online inquiries, greeting and qualifying prospects, conducting property tours, and showing apartments.
- Assists with the lease preparation process by generating all required lease paperwork and organizing resident lease files.
- Assists with move in and move out process for residents; commits to working move-in and move-outs with the understanding that these events, along with “turn”, are mandatory work dates. Any time off during these dates will be considered an exception and must be requested and approved in writing by the Community Manager well in advance.
- Answers incoming calls and sets appointments for prospects to tour the property.
- Performs on-campus marketing outreach to generate Community awareness and qualified traffic.
- Assists with coordinating resident functions, including parties, birthday cards, unit visits, and other programs to achieve resident satisfaction goals.
- Schedules and conducts resident visits as directed and distributes notices such as flyers, newsletters, resident surveys, and late notices.
- Acts as an after-hours liaison between residents and property management; responds to after-hours emergencies within a required period of time. At least one on-call shift per week is expected; however, the schedule is determined at the site level.
- Responds quickly and courteously to resident concerns and questions and takes prompt action to solve problems and/or document and convey resident or other requests to the appropriate individual(s).
Physical Demands: multiple sentences. We'll treat as requirements.
Physical Demands paragraph:
"Physical Demands: Incumbents need to be able to stand, walk, and/or sit for extended periods of time and bend, stoop, climb ladders, reach, carry objects, and crawl in confined areas. Incumbents must be able to work inside and outside in all weather conditions (rain, snow, heat, hail, wind, sleet). Incumbents must be able to push, pull, lift, carry, or maneuver weights of up to twenty-five (25) pounds independently and fifty (50) pounds with assistance. Rare or regular travel may be required to assist other properties as needed, attend training classes, business meetings, or other situations necessary for the accomplishment of some or all of the daily responsibilities of this position. Incumbents must be able to work a flexible work schedule, which includes taking “call” during evenings, weekends and holidays."
We can split into requirements.
Pay: "The hourly range for this position is $16.90 - $17.50 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."
Benefits: "Benefits Offered for Part-time Team Members*: 401(k) with Company Match (eligibility required)Employee Assistance ProgramPaid sick timeFor 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."
We need to format benefits as list items.
Also note there is a footnote asterisk; we keep text.
Schedule: we already included flexible schedule in physical demands; but we could also have a Schedule section referencing flexible schedule, on-call shift per week, evenings, weekends, holidays. However we already have that in physical demands. To avoid duplication, we could put schedule info under Schedule section and keep physical demands under Requirements. Let's separate: Requirements: physical demands (stand, walk, lift, weather, travel). Schedule: flexible work schedule, on-call shift, evenings, weekends, holidays.
Thus:
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real, specific content. We must not repeat job title as heading. We must not put Job ID etc. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning). So we need to extract substantive info: company description (About Greystar) could be placed under "About the role"? Actually "About the role" heading is for role description, not company. But we have company description; maybe we can put under "About the role"? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which headings to include based on content. We have content about Greystar (company). Could be placed under "About the role"? Might be odd but acceptable. Alternatively we could omit that heading and just put company description as a
without heading? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must use those exact headings, just examples. It says "use for section headings". So we can create headings like "About Greystar" if we want, but they gave examples. Probably they expect to use those headings when applicable. We have content that fits "Responsibilities" (the list of duties). We have "Pay" (hourly range). We have "Benefits" (list). We have maybe "Schedule" (flexible schedule, on-call shift). We have "Qualifications"? Not explicit qualifications besides physical demands and ability to work flexible schedule. Could treat physical demands as "Requirements"? Might be "Requirements". There's no explicit education or experience. So we could have sections: About Greystar (maybe as a heading but not in list). But to follow instruction, maybe we create a heading "About the role" and put company description there? That seems odd but maybe acceptable. However they said "do NOT repeat the job title as a heading (the page already shows it)". They didn't forbid other headings.
Better: Use headings that match content: "About Greystar" (though not in examples) but still a heading. The instruction 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. So we can use other headings as needed. But to be safe, we could map company description to "About the role". However the role description is about the job, not company. But we could still put company description under "About the role" as context. Might be okay.
Alternatively we could omit company description entirely? But we must preserve ALL substantive information. So we need to include it somewhere.
Thus we will produce:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. So we can use other headings as needed. But to be safe, we could map company description to "About the role". However the role description is about the job, not company. But we could still put company description under "About the role" as context. Might be okay.
Alternatively we could omit company description entirely? But we must preserve ALL substantive information. So we need to include it somewhere.
Thus we will produce:
About the role
[Greystar description]
Then responsibilities:Responsibilities
- ...
Pay
The hourly range for this position is $16.90 - $17.50...
plus additional compensation details. Then "Benefits":Benefits
- ...
Requirements
- Ability to stand, walk, and/or sit for extended periods of time; bend, stoop, climb ladders, reach, carry objects, and crawl in confined areas.
- Ability to work inside and outside in all weather conditions (rain, snow, heat, hail, wind, sleet).
- Ability to push, pull, lift, carry, or maneuver weights of up to 25 pounds independently and 50 pounds with assistance.
- Rare or regular travel may be required to assist other properties, attend training, business meetings, etc.
Schedule
- Flexible work schedule, including taking “call” during evenings, weekends, and holidays.
- At least one on-call shift per week expected; schedule determined at site level.
before responsibilities. Could put under About the role after company description? Actually About the role could contain both company description and summary. But we already used About the role for company description; we could add summary after that. Let's structure:
About the role
[Greystar company description]
[Job Description Summary]
Then responsibilities list. Then Requirements. Then Schedule. Then Pay. Then Benefits. Check for any other substantive info: "Greystar will consider for employment qualified applicants with arrest and conviction records." That's EEO/boilerplate? It's a statement about considering applicants with arrest/conviction records. Might be considered EEO/legal boilerplate; but it's substantive? It's a hiring policy. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. This line is about considering applicants with arrest and conviction records, which is a type of EEO statement. Likely to be removed. Also "Greystar is an equal opportunity employer..." remove. Also "Important Notice: ..." remove. Thus we keep only the substantive content. Now produce HTML fragment. Make sure to use proper HTML:...
- ...
...
No extra