Jobs · OTHR · California

Journey Home Case Manager (Part-Time)

GLIDEsf · San Francisco, CA · 1 mo ago
On-siteOTHR$31–$35/hrPart-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About Glide" description, then Position Summary, then Key Qualities, Essential Duties And Responsibilities, Minimum Qualifications, Required Licenses And/or Certifications, Physical Requirement, Pay, Schedule, Work Environment maybe. We must use

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. Thus we need to decide which sections to include based on content. We have: - About Glide: description of organization. Could be "About the role"? Actually "About Glide" is about organization, not role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map content accordingly. We have Position Summary: description of role duties. Could be "Responsibilities" or maybe "About the role". The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings. We have Key Qualities To Ensure Success In This Role: list of qualities (professional manner, emotional intelligence, attendance, certification). Could be "Qualifications" or "Skills". Might be "Qualifications". Essential Duties And Responsibilities: list of duties. Could be "Responsibilities". Minimum Qualifications: list of qualifications. Could be "Requirements" or "Qualifications". Might be "Requirements". Required Licenses And/or Certifications: list. Could be "Qualifications" or "Requirements". Physical Requirement: description. Could be "Skills"? Not exactly. Might be omitted if not a standard heading; but we could include as "Requirements"? However instruction says prefer a few substantive sections over many thin ones. We could combine some. Pay: "$31 - $35 an hour". That's specific, so we should include Pay section. Schedule: "Sunday–Monday, 10:30 PM–7:30 AM | 16 hours/week". Also mention 8-hour shifts etc. So we should include Schedule. Work Environment: description of location, open door policy, CBA, AI note. Could be omitted? It's substantive but not a standard heading. Could be included as maybe "About the role"? But we already have that. Could be omitted to keep few sections. However we need to preserve ALL substantive information. If we omit Work Environment, we lose that info. But we could incorporate into "About the role" or "Responsibilities"? Probably better to include a section like "Work Environment" but not in the list of allowed headings? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we should map content to those headings. If a piece doesn't fit, we could incorporate into nearest. Thus we need to produce sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay, Schedule. Possibly Benefits if present (none). We'll omit Benefits. We need to avoid filler like "commensurate with experience". Not present. We need to use
    • for any list of duties/requirements/benefits. So for lists we use
      • . For prose we use

        . We need to preserve all substantive information. Let's extract content. About Glide paragraph: "GLIDE is a nationally recognized center for social justice, dedicated to fighting systemic injustices, creating pathways out of poverty and crisis, and transforming lives. Through its integrated comprehensive services, advocacy initiatives, and inclusive community, GLIDE empowers individuals, families, and children to achieve stability and to thrive. GLIDE is on the forefront of addressing some of society’s most pressing issues, including poverty, housing and homelessness, and racial and social justice. GLIDE’s mission is to create a radically inclusive, just, and loving community mobilized to alleviate suffering and break the cycles of poverty and marginalization." That's about the organization. Could be placed under "About the role"? Might be better as "About the role" but it's about organization. However we can still put it there. Position Summary: "Journey Home Case Managers spearhead mobile and on-premises client outreach, intake, assessment, and low-threshold to intensive case management: develop and manage individualized care plans, coordinate resources and wrap-around services, transport clients to appointments, connect clients with shelter and housing, facilitate health, mental health, and substance use disorder treatment, arrange travel and transportation, and help clients reunite with family, support networks, and careers for long-term well-being and housing stabilization. In this role, you will create, develop, and steward a caseload of approximately 20-25 clients at various stages of their journey toward housing stabilization and help approximately 3-5 people per month progress from homelessness toward housing stability. Journey home case managers are assigned a regular shift ( such as AM, PM or Graveyard) . You must be flexible and available to work outside of their regular shift when assigne d. A nd must be available to work special events or serve as emergency workers when required by community need . Shifts may be reassigned or rotated (within the parameters of the CBA) as the business needs of the operations change. Schedule: Sunday–Monday, 10:30 PM–7:30 AM | 16 hours/week" We can split: Position Summary is responsibilities. The schedule line also appears; we will handle schedule separately. Key Qualities To Ensure Success In This Role: list: "Must be able to conduct oneself in a professional manner, model emotional intelligence and self-regulation. Consistent attendance and on-time arrival (for all assigned shifts) are crucial. Must successfully complete the California Peer-to-Peer Support Specialist certification within 60 days upon hire." That's more like qualifications/skills. Essential Duties And Responsibilities: a long list of duties (bullet-like sentences). We'll turn into

        • . Minimum Qualifications: list of qualifications (Bachelor's degree etc). We'll turn into
          • . Required Licenses And/or Certifications: list (valid CA driver's license, auto insurance, clean DMV, ability to drive van, CA Peer-to-Peer Support Specialist certification within 60 days, CA Community Health Worker Certification preferred). We'll turn into
            • . Physical Requirement: paragraph describing abilities. Could be under "Skills" or "Requirements". We'll treat as "Skills". Pay: "$31 - $35 an hour". Also note part-time 16 hours/week, Non-Exempt. We'll include in Pay section. Schedule: "Sunday–Monday, 10:30pm-7:30am". Also mention 8-hour shifts etc. We'll include. Work Environment: description of location, open door policy, CBA, AI note. Could be under "About the role" or maybe a separate section but not in allowed headings. Could incorporate into "About the role". We'll add a paragraph after About Glide. We must not repeat job title as heading. No Job ID. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. There's no explicit application instructions besides maybe "If you would like more information about how your data is processed, please contact us." That's maybe legal/boilerplate; we should remove. Also the AI note about hiring process maybe considered boilerplate? It's about hiring process; could be considered legal? Might be okay to keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The AI note is about hiring process; not exactly those categories but could be considered legal? Safer to remove it. Also the line "We may use artificial intelligence (AI) tools to support parts of the hiring process..." is likely boilerplate; remove. Also "Final hiring decisions are ultimately made by humans." remove. Also "If you would like more information about how your data is processed, please contact us." remove. Also "This role is covered by the collective bargaining agreement." That's substantive? Might be considered work environment; we can keep. Now we need to output HTML fragment with

              headings and content. We'll decide sections: - About the role: combine About Glide description + Work Environment (location, open door policy, CBA). Could be two paragraphs. - Responsibilities: combine Position Summary + Essential Duties And Responsibilities (maybe as list). But we need to avoid duplication. Position Summary already includes some duties; Essential Duties list more details. We'll combine into a single Responsibilities section with list items (maybe some prose). We'll include the Position Summary as prose then list of duties. - Requirements: Minimum Qualifications (education/experience) plus maybe Required Licenses And/or Certifications? Could be separate Qualifications section. But we have both Requirements and Qualifications headings allowed. We'll use Requirements for minimum qualifications (education/experience, skills). Qualifications for licenses/certifications and maybe key qualities? Actually Key Qualities could be Skills. Let's map: - Requirements: Minimum Qualifications (education/experience, experience, abilities). We'll list as
              • . - Qualifications: Required Licenses And/or Certifications (driver's license, insurance, certification, preferred CHW). Also maybe Key Qualities (professional manner, emotional intelligence, attendance, certification). But certification already mentioned. We'll keep Key Qualities under Skills maybe. - Skills: Key Qualities (professional manner, emotional intelligence, self-regulation, attendance, ability to complete certification within 60 days) plus Physical Requirement (ability to work on computer, hear, communicate, finger dexterity, sit/stand, navigate, etc.) plus maybe communication skills etc. - Pay: "$31 - $35 an hour; part-time 16 hours/week; Non-Exempt." - Schedule: "Sunday–Monday, 10:30 PM–7:30 AM; 8-hour shifts; 16 hours/week." We must avoid filler like "commensurate with experience". Not present. Now we need to ensure we don't create sections with filler. All sections have real content. Now produce HTML. We'll start with

                About the role

                then

                ... about Glide ...

                then maybe another

                for work environment. Then

                Responsibilities

                then maybe a

                for position summary prose then

                • for essential duties. Then

                  Requirements

                  then
                  • for minimum qualifications. Then

                    Qualifications

                    then

Similar jobs