Site Associate, Lighthouse

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We have: - About Us (but not required heading; we can maybe treat as About the role? Actually "About Us" is about organization; but we have "About The Role". So we can use

About the role

and put the paragraph. - Responsibilities: we have "What You’ll Do" list. So we can make

Responsibilities

with

• items. - Requirements: we have "WHAT YOU’LL NEED:" list. So

  Requirements

  with list. - Qualifications: maybe same as Requirements? But we can treat Requirements as qualifications. However we need to decide if we need separate Qualifications section. The instruction says use headings for those categories if content exists. We have content for Requirements; we could also have Qualifications (maybe overlapping). But we should avoid thin sections. Probably combine into Requirements. - Skills: we have communication, organizational, etc. Could be part of Requirements. Might be separate Skills section if we want. But we can include within Requirements. - Benefits: we have "Benefits & Perks" paragraph. So

  Benefits

  with paragraph. - Pay: we have SALARY RANGE: $22.00/hr. So

  Pay

  with paragraph. - Schedule: we have SCHEDULE: Monday-Friday (3:00pm-11:30pm). Also occasional evening and weekend hours may be required. So

  Schedule

  with paragraph. We also have location, status, driver position, etc. Those are minor metadata; we can fold into a short

  maybe after the role heading? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include a short paragraph after the role heading containing location, status, driver position, etc. We must not include boilerplate like EEO, legal, etc. Remove those. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, but we can rephrase? It says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the details but can reformat. Likely we can copy sentences. We need to ensure we don't omit any substantive info: About Us paragraph, About The Role paragraph, What You’ll Do list items, Requirements list items, Work Environment And Physical Requirements (including prolonged sitting, changes in environment, physical effort/lifting, SPECIAL CONDITIONS: Mandated Reporting Requirements, COVID-19 Vaccination Requirements, Driver Positions Applicants..., NOTE about introductory period, at-will, etc). Also Benefits & Perks paragraph. Also EEO statement (but we must remove EEO/legal/equal-opportunity/scam-warning boilerplate). So we must remove EEO statement. Also remove "Please include references in your application" (application instructions). Also remove "Subject to criminal and driving background checks."? That's part of Requirements; we keep. We must also keep "Bilingual Spanish/English a plus." etc. We must keep "Proficient in Microsoft Office and Google Drive". Keep. We must keep "Ability to work nights/weekends". Keep. We must keep "Other duties as assigned to support the mission of the organization." Keep. We must keep "Drive SPY vehicles to transport residents to services and community activities". Keep. We must keep "Work within established legal and ethical guidelines". Keep. We must keep "A commitment to and passion for the mission, vision, values and culture of SPY". Keep. We must keep "Self-starter who is prepared to drive innovative solutions within the organization". Keep. We must keep "Must possess great communication and organizational skills". Keep. We must keep "An ability to work in a fast paced environment that requires effective collaboration with a variety of organizations and individuals". Keep. We must keep "Valid California driver’s license, auto insurance, and the ability to transport clients seeking housing and other services is required." Keep. We must keep "Bilingual Spanish/English a plus." Keep. We must keep "Subject to criminal and driving background checks." Keep. We must keep "Proficient in Microsoft Office and Google Drive". Keep. We must keep "Work Environment And Physical Requirements" details: prolonged periods of sitting at a desk and working on a computer; changes in the environment, such as the office or outdoors; physical effort/lifting, such as sedentary- up to 15-20 pounds at times. Keep. We must keep "SPECIAL CONDITIONS: Mandated Reporting Requirements: All SPY employees are mandated reporters and are legally required to report any reasonable suspicion of child, elder, or dependent adult abuse or neglect." Keep. We must keep "COVID-19 Vaccination Requirements Effective August 9, 2021, the State Health Officer has mandated that all workers, paid or unpaid, in homeless services organizations must provide proof of vaccination. If eligible for a booster shot, proof of booster is also required. Please submit proof of vaccination to HR@safeplaceforyouth.org. To request a reasonable accommodation or exemption, please get in touch with HR at the same email address. It's important to note that these accommodations are not guaranteed." Keep. We must keep "Driver Positions Applicants are required to provide a copy of their driving record from the Department of Motor Vehicles, along with a copy of their valid driver’s license and proof of insurance. Job offers are contingent upon a satisfactory driving record. For driver positions, driving is an essential job function and cannot be reasonably accommodated, employment may be discontinued." Keep. We must keep "NOTE: All staff members will be considered introductory employees for the first three months of employment and will not be considered regular employees until the conclusion of this period. SPY reserves the right to extend an employee’s introductory period. In no way does the expiration of this introductory period change the fact that all employees are at-will. Employees continue to have the right to terminate their employment/business relationship at any time, with or without cause or notice, and SPY has the same right. The organization, in its sole discretion, may change the job duties, responsibilities and assignments of any position, at any time." Keep. We must keep "Benefits & Perks Safe Place for Youth offers a competitive benefit package including comprehensive health coverage, 403b with agency contribution, and ample paid time off. We also offer unique perks including professional development opportunities that are tailored to your individual career growth." Keep. We must keep "About Us" paragraph. We must keep "About The Role" paragraph. We must keep "What You’ll Do" list items. We must keep "Requirements" list items. We must keep "Work Environment And Physical Requirements" etc. We must keep location, schedule, status, driver position, salary range. We must not include EEO statement, application instructions, references request. We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Now we need to output HTML fragment with headings

  for sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly also "About Us"? Not in list but could be considered "About the role"? Actually "About Us" is about organization; we could include as a

  after the role heading or as a separate section like "About the organization". But the instruction only lists those headings; we can add other headings if needed? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. We can add other headings if needed, but better to stick to those. We can put About Us content under About the role? Might be odd. Better to add a heading "About the organization" but not in list; maybe we can just include 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 forbid other headings, but suggests those are typical. Safer to include a heading "About the organization" maybe as

  About the organization

  . However the instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but we should follow the pattern. I'd include a heading "About the organization" as

  About the organization

  . It's not in the list but seems reasonable. Alternatively we could fold About Us into a

  after the role heading without a heading. The instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must use headings for every section, but we should use them for sections. I'd include a heading for About the organization. Now we need to ensure we don't repeat the job title as a heading. The job title is "Site Associate, Lighthouse". We must not put that as a heading. So we will not have

  Site Associate, Lighthouse

  . Good. We must not put Job ID/requisition numbers as headings; none present. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft:

  About the organization

  Safe Place for Youth (SPY) is the leading service provider for youth experiencing or at-risk of homelessness in West Los Angeles. Founded in 2011, our agency offers trauma-informed, low barrier programs that support young people in exiting the streets and achieving stability. Our robust continuum of care includes street outreach, drop-in services, health and wellness programming, case management, education and employment services, and housing programs. SPY is a unique social impact agency that values community collaboration, and a deep commitment to the wellbeing of youth.

  About the role

  The Site Associate is responsible for the general oversight of the property, including maintaining cleanliness, supporting site safety, responding to crises, and assisting with conflict resolution. This position reports directly to the Site Supervisor, Lighthouse and plays an important role in supporting a safe and stable living environment for residents. Occasional evening and weekend hours may be required.

  Responsibilities

  • Daily house and property inspection to maintain curb appeal and resident safety
  • Maintain adequate inventory and storage of program supplies, including snacks, materials for activities, cleaning supplies, laundry soaps, office supplies, etc.
  • Assist with program intakes and exits, including preparing intake packets, documentation of requirements, and conducting exit service evaluations.
  • Coordinate and assist with food and meal supports in the program, including Food Pantry donations.
  • Report all issues concerning resident health and safety, maintenance or other areas of concern to appropriate managers/point persons within SPY’s Maintenance Department in a timely manner, and track outcomes
  • Interact with and build relationships with program residents, demonstrating the ability to support resident success, solve problems and enforce house rules, and provide crisis response and conflict resolution with and among residents.
  • Communicate emerging and outstanding issues to the Housing Programs Manager in a timely manner; work closely with case managers to resolve issues.
  • Coordinate volunteers providing services on site.
  • Create and make available resource lists and other information to support residents in accessing needed amenities in the neighborhood.
  • In coordination with SPY