LGBTQ+ Program Coordinator
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: EEO, legal, etc. Also remove navigation, cookie, etc. Must preserve all substantive info.
We need to parse the posting.
Given description:
JOB TITLE: LGBTQ+ Program Coordinator
REPORTS TO: Sr. Director of Community Programs
SCHEDULE: Monday-Friday 9:00am-5:30pm
LOCATION: Venice, CA, Access Center, On-site
STATUS: Full-Time, 40 hrs/wk, Non-Exempt
DRIVER POSITION: Yes [If yes, please reference driving policy]
SALARY RANGE: $26.00-$28.85/hr
About Us: paragraph.
About The Role: paragraph.
What You’ll Do: list of duties (many bullet-like sentences). We'll need to put them in - .
Requirements: "WHAT YOU’LL NEED:" then list of requirements.
Work Environment And Physical Requirements: paragraph.
Special Conditions: includes Mandated Reporting, COVID-19 Vaccination Requirements, Driver Positions, etc. Some of these are boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Special Conditions includes Mandated Reporting Requirements (legal), COVID-19 Vaccination Requirements (legal), Driver Positions (specific to role). Should we keep driver position info? It's specific to role (driver position). The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." For driver position, it's a condition; maybe we can include in a short paragraph under something like "Additional Information" but we only have allowed headings list. We could include driver requirement under Requirements or Skills? It's a requirement: valid CA driver's license, auto insurance, ability to transport youth. That's already in Requirements. The special conditions about providing copy of driving record etc is more procedural; could be omitted as application instruction? It's somewhat like application instruction. Probably we can drop it.
Benefits & Perks: paragraph about benefits.
EEO Statement: remove.
We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content for About the role (the "About The Role" paragraph). Responsibilities: the "What You’ll Do" list. Requirements: the "WHAT YOU’LL NEED:" list. Qualifications: maybe overlapping with Requirements; but we can treat Requirements as qualifications? The instruction says prefer few substantive sections over many thin ones. We could combine Requirements and Qualifications into one section? But we have to use headings exactly as listed if we include them. We could include only those sections that have real content. Let's see:
- About the role: yes.
- Responsibilities: yes (What You’ll Do).
- Requirements: yes (WHAT YOU’LL NEED:).
- Qualifications: maybe we could treat the education/experience as qualifications; but we already have Requirements covering that. Could we omit Qualifications to avoid thin duplication? Probably better to omit Qualifications if content is same as Requirements. But we need to ensure we don't lose any substantive info. The Requirements list includes education, experience, knowledge, skills, driver license, etc. That covers qualifications and skills. So we could have Requirements section and maybe Skills section separate? But we have skills listed within Requirements (Strong communication, facilitation, organizational skills, ability to collaborate, etc.). Could split into Skills section. However instruction: prefer few substantive sections over many thin ones. So maybe combine Requirements and Skills into one section called Requirements (or Qualifications). But we must use headings exactly as given if we include them. We could include only Requirements and omit Skills, Qualifications, Benefits, Pay, Schedule if they have content? Benefits has content. Pay has content (salary range). Schedule has content (Monday-Friday 9:00am-5:30pm). So we need Benefits, Pay, Schedule sections.
Thus we will have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule.
We must not include Qualifications or Skills if we don't have separate content; but we could still include them if we split content. However to avoid thin sections, we can put skills inside Requirements.
Now we need to format.
We need to wrap each section:
About the role
then ...
for prose. For lists: - ...
.
We must preserve all substantive information. Let's extract.
About Us paragraph: "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. If you have the skills, passion, and collaborative spirit, join our growing team."
But "About Us" is not a section heading we need to include; we only need About the role. However the About Us paragraph is substantive info about the organization; should we include it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The About Us is substantive. Where to put it? Could be part of About the role section? The About the role section currently is the paragraph after "About The Role". We could prepend the About Us paragraph to that section, as it's still about the organization and role context. That would preserve info. The instruction about sections: use headings for section headings (About the role, Responsibilities, etc). It doesn't forbid adding extra paragraphs under those headings. So we can include About Us content under About the role heading.
Thus About the role section will have two paragraphs: first About Us, second About The Role.
Now Responsibilities: the "What You’ll Do" list. We need to convert each sentence into a - . Let's list them:
- Facilitate weekly Queer Joy group sessions (5–15 youth per session) focusing on identity exploration, self-care, sexual health, and navigating internalized homophobia and transphobia.
- Integrate creative, youth-centered activities such as zine-making, queer trivia, playlist-building, and DIY self-care kits.
- Create a safe, affirming environment where LGBTQ youth can build confidence, belonging, and community.
- Distribute gender-affirming products.
- Develop and maintain LGBTQ-specific resource lists.
- Provide individualized referrals for gender-affirming healthcare and legal services, including name/gender marker changes.
- Support SPY staff and partners in strengthening cultural competency and trauma-informed practices in daily interactions with LGBTQ youth.
- Partner with LA Pride, Promote, and other local organizations to host youth-centered events and outreach opportunities.
- Collaborate with the Los Angeles LGBT Center to provide mentorship opportunities for LGBTQ youth.
- Co-host workshops with AMAAD Institute on topics such as coming out, intersectionality, and identity development.
- Advocate for LGBTQ-inclusive organizational policies and practices within SPY and across partner systems.
- Collect data and feedback from participants to inform program improvements and broader advocacy efforts.
- Collaborate with SPY’s Access Center and Clinical Teams to support day-to-day program operations and youth engagement, ensuring LGBTQ+ youth are connected across all service areas.
- Implement culturally responsive outreach strategies to engage LGBTQ+ youth and allies in SPY’s case management and wellness services.
- Plan and facilitate site-wide community-building events (e.g. field trips, social gatherings, creative workshops) that foster belonging among LGBTQ youth and their peers, as part of SPY’s broader commitment to inclusive, affirming programming for all.
- Support wraparound resource navigation for LGBTQ+ youth, including warm referrals for housing, mental health, benefits, education, parenting resources, and employment.
- Contribute to multidisciplinary care coordination by participating in case conferencing and team-based service planning.
- Provide ongoing feedback to internal teams on how to improve site-wide LGBTQ+ inclusion and cultural responsiveness.
- Other duties as assigned to support the mission of the organization.
Now Requirements: "WHAT YOU’LL NEED:" list. Let's extract each bullet:
- Bachelor’s degree in social science or related field preferred.
- Related work or lived experience will be strongly considered in place of or in addition to a degree.
- 1-2 years of experience working with LGBTQ+ individuals in a social services, education, community based, or related setting required.
- Demonstrated knowledge of LGBTQ+ affirming practices, resources, and culturally responsive approaches to supporting LGBTQ+ youth
- 1–2 years of experience providing direct services to high-risk transitional-age youth required.
- 1–2 years of experience utilizing a trauma-informed care model required.
- Working knowledge of child and adolescent social, emotional, and cognitive development, and trauma-informed care service models.
- Ability to work within legal and ethical guidelines when serving LGBTQ youth.
- Flexibility in scheduling based on program needs (including evenings and weekends for events/workshops).
- Commitment and passion for the mission, vision, values, and culture of SPY.
- A self-starter who can drive innovative, affirming programming.
- Strong communication, facilitation, and organizational skills.
- Ability to collaborate effectively in a fast-paced environment.
- A valid California driver’s license, auto insurance, and the ability to transport youth.
- Proficiency in Microsoft Office and Google Drive.
- Deep cultural humility and commitment to LGBTQ equity.
Note there is a line break after "Demonstrated knowledge of LGBTQ+ affirming practices, resources, and culturally responsive approaches to supporting LGBTQ+ youth" (no period). We'll keep as is.
Now 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."
We'll put that as
under Benefits heading.
Pay: Salary range: $26.00-$28.85/hr. We'll put as
under Pay heading.
Schedule: Monday-Friday 9:00am-5:30pm. We'll put as
under Schedule heading.
We also have location, reports to, status, driver position etc. Those are metadata; we could fold into a short paragraph under About the role or maybe under a separate "Details" but not allowed headings. We could include them in a short paragraph after About the role content, maybe as a
with details. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include location, reports to, status, driver position etc in a short paragraph.
Thus after About the role content we can add a
with: "Reports to: Sr. Director of Community Programs. Location: Venice, CA, Access Center, On-site. Status: Full-Time, 40 hrs/wk, Non-Exempt. Driver position: Yes (valid CA driver’s license, auto insurance, and ability to transport youth required)." But note driver position info already in Requirements; we can still mention.
We must not repeat job title as heading.
Now ensure we don't include boilerplate: remove EEO statement, special conditions (mandated reporting, COVID vaccination, driver position details about providing copy of driving record etc). We already omitted those.
Now produce HTML fragment.
Structure:
About the role
About Us paragraph.
About The Role paragraph.
Metadata paragraph (
or drop it." For driver position, it's a condition; maybe we can include in a short paragraph under something like "Additional Information" but we only have allowed headings list. We could include driver requirement under Requirements or Skills? It's a requirement: valid CA driver's license, auto insurance, ability to transport youth. That's already in Requirements. The special conditions about providing copy of driving record etc is more procedural; could be omitted as application instruction? It's somewhat like application instruction. Probably we can drop it. Benefits & Perks: paragraph about benefits. EEO Statement: remove. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (the "About The Role" paragraph). Responsibilities: the "What You’ll Do" list. Requirements: the "WHAT YOU’LL NEED:" list. Qualifications: maybe overlapping with Requirements; but we can treat Requirements as qualifications? The instruction says prefer few substantive sections over many thin ones. We could combine Requirements and Qualifications into one section? But we have to use headings exactly as listed if we include them. We could include only those sections that have real content. Let's see: - About the role: yes. - Responsibilities: yes (What You’ll Do). - Requirements: yes (WHAT YOU’LL NEED:). - Qualifications: maybe we could treat the education/experience as qualifications; but we already have Requirements covering that. Could we omit Qualifications to avoid thin duplication? Probably better to omit Qualifications if content is same as Requirements. But we need to ensure we don't lose any substantive info. The Requirements list includes education, experience, knowledge, skills, driver license, etc. That covers qualifications and skills. So we could have Requirements section and maybe Skills section separate? But we have skills listed within Requirements (Strong communication, facilitation, organizational skills, ability to collaborate, etc.). Could split into Skills section. However instruction: prefer few substantive sections over many thin ones. So maybe combine Requirements and Skills into one section called Requirements (or Qualifications). But we must use headings exactly as given if we include them. We could include only Requirements and omit Skills, Qualifications, Benefits, Pay, Schedule if they have content? Benefits has content. Pay has content (salary range). Schedule has content (Monday-Friday 9:00am-5:30pm). So we need Benefits, Pay, Schedule sections. Thus we will have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. We must not include Qualifications or Skills if we don't have separate content; but we could still include them if we split content. However to avoid thin sections, we can put skills inside Requirements. Now we need to format. We need to wrap each section:
About the role
then...
for prose. For lists:- ...
under Benefits heading. Pay: Salary range: $26.00-$28.85/hr. We'll put as
under Pay heading. Schedule: Monday-Friday 9:00am-5:30pm. We'll put as
under Schedule heading. We also have location, reports to, status, driver position etc. Those are metadata; we could fold into a short paragraph under About the role or maybe under a separate "Details" but not allowed headings. We could include them in a short paragraph after About the role content, maybe as a
with details. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include location, reports to, status, driver position etc in a short paragraph. Thus after About the role content we can add a
with: "Reports to: Sr. Director of Community Programs. Location: Venice, CA, Access Center, On-site. Status: Full-Time, 40 hrs/wk, Non-Exempt. Driver position: Yes (valid CA driver’s license, auto insurance, and ability to transport youth required)." But note driver position info already in Requirements; we can still mention. We must not repeat job title as heading. Now ensure we don't include boilerplate: remove EEO statement, special conditions (mandated reporting, COVID vaccination, driver position details about providing copy of driving record etc). We already omitted those. Now produce HTML fragment. Structure:
About the role
About Us paragraph.
About The Role paragraph.
Metadata paragraph (