Community Resource Specialist I
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We need to parse the posting. Key info: - Title: Community Resource Specialist I (but we must not repeat job title as heading; page already shows it, so we don't output heading for title.) - About the role: The posting includes "Make an Impact" paragraph describing Trillium, mission, etc. Also "Why Work for Us?" paragraph. Also "What We’re Looking For" paragraph describing role. So we can have an "About the role" section summarizing the role description. Must preserve all substantive info, not invent or summarize away detail. We need to include the content as paragraphs (
) possibly multiple. - Responsibilities: The bullet list under "On a Typical Day, You Might ..." includes several duties. Those are list items. So we can have a
Responsibilities
with- each duty.
- Requirements: There's "Required Qualifications" section with bullet points? Actually it's paragraph: "High school diploma or GED and one (1) year experience in a Health or Human Services field, including experience working the BH/SU/IDD population, including experience with public speaking, training and/or teaching; OR Equivalent combination of education and experience. Must have a valid driver’s license. Must reside within Trillium’s South-Central Region, which includes the following counties: Carteret, Craven, Duplin, Jones, Lenoir, Onslow, Pender, Sampson, and Wayne. Must be able to travel within catchment as required."
Also "Preferred Lived experience, community development experience, and/or experience with community-based organizations and/or community partners centered around housing, food insecurity, transportation, education & employment, interpersonal violence/toxic stress and/or social integration and inclusion"
Thus we can have a Requirements section (maybe split into Required Qualifications and Preferred Qualifications). But we can combine into one Requirements section with subpoints? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have separate headings for Requirements and Qualifications if needed. But we need to avoid thin sections. We have both Required and Preferred qualifications; we could put them under Requirements heading with two sub-lists? But we must use only
headings, not subheadings. Could we have two sections: Requirements (for required) and Qualifications (for preferred)? Might be okay. However we need to ensure we don't create sections with filler. Both have content. - Benefits: The posting lists "Employee Benefits" with bullet list: Typical working hours, flexible schedules, work-from-home options, Health Insurance with no premium for employee coverage, Flexible Spending Accounts, 24 days PTO plus 12 paid holidays, NC Local Government Retirement Pension, 401k with 5% employer match immediate vesting, Public Service Loan Forgiveness qualifying employer, Quarterly stipend for remote work supplies. So we can have Benefits section. - Pay: The posting includes "Posting Salary Range: $42,682- $54,205". That's specific pay range. So we should include Pay section with that info. - Schedule: The posting includes "Typical working hours: 8:30 am – 5:00 pm; flexible work schedules with some roles with management approval." That's schedule info. So we can include Schedule section. We must not include boilerplate like EEO, application instructions, etc. Also remove duplicated lines, cookie/navigation/legal etc. Also remove "How To Apply" etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to include the exact text? Probably we can paraphrase but must preserve meaning. Safer to copy the sentences as is. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:
About the role
Trillium Health Resources is a Tailored Plan and Managed Care Organization (MCO) serving 46 counties across North Carolina. We manage services for individuals with serious mental health needs, substance use disorders, traumatic brain injuries, and intellectual/development (IDD) disabilities. Our mission is to help individuals and families build strong foundations for healthy, fulfilling lives.
Trillium believes that empowering others begins with supporting our team. We offer our employees: A collaborative, mission-driven work environment Competitive benefits and work-from-home options for most positions Opportunities for professional growth in a diverse inclusive culture Every day, our work changes lives – from children thriving through early intervention and school-based therapies, to adults with severe mental illness living independently and contributing to their communities. If you are looking for a unique opportunity to make a tangible impact on the lives of others, apply today!
The Community Resource Specialist I supports access to community-based resources that address social drivers of health. The role connects individuals to services, tracks referral outcomes, and supports timely resource navigation through coordination with community partners.
Responsibilities
- Receive and respond to referrals related to unmet health related resource needs, including housing, food, transportation, and employment.
- Connect individuals to community-based organizations and public programs to address identified needs.
- Maintain working knowledge of available community resources and service eligibility requirements.
- Coordinate referral follow-up to confirm connection to services and identify unresolved needs.
- Document referral activities, interactions, and outcomes accurately and within established time frames.
Requirements
High school diploma or GED and one (1) year experience in a Health or Human Services field, including experience working the BH/SU/IDD population, including experience with public speaking, training and/or teaching; OR Equivalent combination of education and experience. Must have a valid driver’s license. Must reside within Trillium’s South-Central Region, which includes the following counties: Carteret, Craven, Duplin, Jones, Lenoir, Onslow, Pender, Sampson, and Wayne. Must be able to travel within catchment as required.
Qualifications
Preferred: Lived experience, community development experience, and/or experience with community-based organizations and/or community partners centered around housing, food insecurity, transportation, education & employment, interpersonal violence/toxic stress and/or social integration and inclusion.
Benefits
- Typical working hours: 8:30 am – 5:00 pm; flexible work schedules with some roles with management approval.
- Work-from-home options available for most positions
- Health Insurance with no premium for employee coverage
- Flexible Spending Accounts
- 24 days of Paid Time Off (PTO) plus 12 paid holidays in your first year
- NC Local Government Retirement Pension (defined-benefit plan)
- 401k with 5% employer match and immediate vesting
- Public Service Loan Forgiveness (PSLF) qualifying employer
- Quarterly stipend for remote work supplies
Pay
Posting Salary Range: $42,682- $54,205
Schedule
Typical working hours: 8:30 am – 5:00 pm; flexible work schedules with some roles with management approval.
But note we duplicated typical working hours in Benefits and Schedule. The Benefits section already includes typical working hours as a bullet. The Schedule section could just be the same info; but we might avoid duplication. However the instruction says preserve ALL substantive information; we can keep it in both sections if it's present in both places. But we might consider moving the typical working hours to Schedule only and remove from Benefits bullet to avoid duplication. However the Benefits bullet list includes that as a bullet; if we remove it, we lose that info from Benefits section. But we could keep it in Benefits and also have Schedule section with same info; duplication is okay? The instruction says remove duplicated lines. That likely refers to duplicated lines in the source, not our output. Duplicating the same info in two sections might be considered duplication but not from source. Safer to avoid duplication: we can put typical working hours only under Schedule, and keep other benefits under Benefits without that line. However the Benefits bullet list originally includes "Typical working hours: 8:30 am – 5:00 pm; flexible work schedules with some roles with management approval." That is a benefit. If we remove it, we are omitting that substantive info from Benefits section. But we could keep it under Benefits and not have a separate Schedule section, but the instruction says we should include Schedule section only if posting actually states them. It does state typical working hours, so we need a Schedule section. We could keep the typical working hours info in both sections; it's not a duplicated line from source, it's just repeating. The instruction about duplicated lines likely refers to the source having duplicated lines (like repeated boilerplate). So repeating in our output is okay. Thus we keep both. Now check we didn't include any boilerplate: we omitted EEO, drug-free workplace, application instructions, deadline, How To Apply, etc. Also omitted "Posting Details" heading etc. Also omitted "Make an Impact" heading (we turned into About the role). Also omitted "Why Work for Us?" (we incorporated into About the role). Also omitted "What We’re Looking For" (we incorporated). Also omitted "Employee Benefits" heading (we turned into Benefits). Also omitted "Required Qualifications" and "Preferred" (we turned into Requirements and Qualifications). Also omitted "Deadline for Application". Also omitted "#Innovation #Technology #Careers #NorthCarolina #BehavioralHealth". Also omitted "Join our Talent Community..." etc. Now ensure we didn't miss any substantive info: The "Office Location: Remote within Trillium’s South-Central Region (See requirements section for included counties)" - we included the counties in Requirements. Also mention remote within region. Should we include that? It's substantive. We could add a sentence in Requirements about remote work location. The Requirements section currently mentions must reside within region and counties. Could also mention remote work. Let's add: "This is a remote position within Trillium’s South-Central Region." We'll incorporate. Also the "Posting Salary Range: $42,682- $54,205" we have. Also the "FLSA Status: Non-Exempt" maybe not needed as not a section heading; but it's substantive metadata. The instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a shortor drop it. FLSA status is minor metadata; we could fold into a short p maybe under About the role or a separate metadata paragraph. But we could drop it as minor? The instruction says fold minor metadata into a short
or drop it. It's up to us. Safer to include a short p somewhere, maybe after About the role: "
FLSA Status: Non-Exempt
" but that's a heading-like line. Better to include as a short paragraph without heading. We'll add a small paragraph under About the role maybe. Also "Position Number: 72056" is minor metadata; we can drop. Also "Pay Plan Title: Community Resource Specialist I Working Title: Community Resource Specialist I" - redundant with title; we can drop. Also "Office Location: Remote within Trillium’s South-Central Region (See requirements section for included counties)" - we captured remote and region. Now check we didn't include any "cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". Good.