Jobs · OTHR

Mental Health Outreach Coordinator

Ellie Mental Health-Capital Region NY · New Providence, NJ · 1 mo ago
HybridOTHR$25–$30/hrFull-time
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use
  • for any list of duties/requirements/benefits, and

    for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. 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. Include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Content: - Benefits: "Health insurance Paid time off 401(k) Dental insurance Flexible schedule". Also later: "Benefits package for full-time team members". Also "Flexible work from home options available." Also "Compensation: $20.00 - $30.00 per hour". Also earlier: "Full-time, $25 to $30 per hour based on experience". So pay info: $25-$30 per hour based on experience; also compensation $20-$30 per hour (maybe contradictory). We need to preserve all substantive info; we can include both statements. - About Ellie: description of Ellie Mental Health. - About The Role: description. - What You'll Do: list of duties. - What We're Looking For: list of requirements/qualifications. - Why Ellie: includes full-time, pay, benefits package, culture, impact, flexible work from home options. - Employee Experience: description of culture, values, growth paths. - Company Structure: description. We need to decide sections: Likely we will have: - About Ellie (maybe as

    About Ellie) but the instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those standard headings. But we can also include other headings if needed? The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we can use other headings but they should be

    . Probably safe to use those headings where applicable. We need to avoid repeating job title as heading. No job title given explicitly; but we can ignore. We need to remove boilerplate: EEO, equal opportunity, scam warning, etc. There's a line: "Ellie Mental Health is an equal opportunity employer. Come as you are." That's EEO boilerplate; remove. Also "Flexible work from home options available." is not boilerplate; keep. Also "Seeking creative & collaborative humans..." is motivational; keep? It's not boilerplate; it's part of why Ellie? Might be okay. We need to preserve all substantive info; do not invent or summarize away detail. We need to output only HTML fragment, no /, no markdown fences. We need to decide which sections to include. We have: - About Ellie: description. - About The Role: description. - Responsibilities: "What You'll Do" list. - Requirements/Qualifications: "What We're Looking For" list (includes experience, skills, education). Could split into Requirements and Qualifications but we can combine. - Benefits: list of benefits. - Pay: compensation info. - Schedule: maybe flexible schedule mentioned; also "Flexible schedule" in benefits list; also "Full-time". Could include Schedule section if there is specific schedule info. There's "Flexible schedule" in benefits; also "Full-time". Not explicit schedule like "Monday-Friday 9-5". Might be okay to include Schedule section with "Full-time, flexible schedule". But we need to avoid filler placeholder text. If we have actual content, we can include. - Skills: maybe not explicit separate list; but we could include under Requirements. We need to avoid thin sections; prefer few substantive sections. Could combine Benefits and Pay into one section? But instruction says use headings for Benefits, Pay, Schedule separately if they exist. We have benefits list, pay info, schedule info (flexible schedule, full-time). So we could have three sections: Benefits, Pay, Schedule. But we also have About Ellie and About The Role and Responsibilities and Requirements. That's many sections. However instruction says "Prefer a few substantive sections over many thin ones." So we might combine some. We could have: - About Ellie (description) - About the Role (description) - Responsibilities (list) - Qualifications (list) - Benefits (list) - Pay (info) - Schedule (info) That's 7 sections; maybe okay if each has substantive content. But we need to ensure we don't create sections with filler like "commensurate with experience". We have actual content. Let's extract substantive content. **About Ellie**: "Ellie Mental Health is outpatient therapy done differently. No cookie-cutter care, no stuffy waiting rooms, and a team that actually goes to therapy too. Our three New Jersey clinics (Cranford, Wall Township, and New Providence) serve kids, teens, adults, couples, and families, in person and online, and we're in-network with most major insurance. We believe caring for your mental health is a strength, and we want every town we're in to know it." **About The Role**: "We're looking for someone who loves being out in the community and is good at turning a handshake into a real relationship. You'll be the face of Ellie to the people who refer clients to us: pediatricians, primary care practices, psychiatrists, schools, municipal alliances, coalitions, and local organizations. Your job is to make Ellie the trusted therapy resource in each of our towns, one conversation at a time. This is a value-first role. We lead with what we can offer a community (clinician-led workshops, event staffing, an expert voice for local press), not with a pitch." **What You'll Do** (Responsibilities): - Build and maintain relationships with referral partners across Union and Monmouth counties: medical practices, psychiatrists and prescribers, schools, and community organizations - Represent Ellie at community events, health fairs, coalition meetings, and municipal alliance meetings - Plan and coordinate clinician-led workshops, presentations, and awareness-month activities (Suicide Prevention Awareness Month, World Mental Health Day, Mental Health Awareness Month) - Keep a clean outreach pipeline: track contacts, touchpoints, and referral activity, and report on what's working - Work with the clinic director and our marketing efforts so outreach, ads, and website messaging tell one consistent story - Coordinate local press and publicity opportunities - Keep partners up to date on our availability, services, and insurance so referring to us stays easy **What We're Looking For** (Requirements/Qualifications): - 2+ years in community outreach, business development, provider relations, or a similar relationship-driven role (healthcare or behavioral health a plus) - Comfortable walking into a room of strangers and leaving with three new contacts - Organized and self-directed; you can run your own calendar and pipeline without hand-holding - Clear, warm communicator in person, on the phone, and in writing - Genuine interest in mental health and reducing the stigma around getting help - Reliable transportation and a valid driver's license; this role involves regular travel between Cranford, Wall Township, New Providence, and surrounding towns - Bachelor's degree in marketing, communications, public health, social work, or a related field preferred, but relevant experience counts **Why Ellie** (maybe includes Pay, Benefits, Culture): - Full-time, $25 to $30 per hour based on experience - Benefits package for full-time team members - A culture that runs on creativity, authenticity, humor, compassion, acceptance, and determination - Real impact: every partner you bring on is another door for someone in our community to get help - Flexible work from home options available. - Compensation: $20.00 - $30.00 per hour (maybe duplicate) - Also "Seeking creative & collaborative humans with a passion for changing mental health care in fun and meaningful ways." (maybe part of culture) - Also "Don’t meet EVERY requirement? ..." (EEO-ish but it's about encouraging applications; not boilerplate? Might be considered motivational; we can keep as part of culture but it's a bit long. Might be considered boilerplate? It's about encouraging applications; not EEO but still generic. Might be okay to keep but could be considered filler. Safer to remove? It's not EEO but it's a generic encouragement; could be considered boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not exactly EEO but it's encouraging underrepresented groups; could be considered EEO-related. Safer to remove. - "Employee Experience" section: description about investing in financial future, wages, caseload, happy employees, etc. That's substantive. - "Company Structure": description about for-profit socially responsible model. We need to decide whether to include Employee Experience and Company Structure as sections. They are substantive; could be included as separate sections like "Employee Experience" and "Company Structure". But instruction only gave examples of headings; we can still use

    for any section heading. So we could include those. But we need to avoid too many thin sections. Employee Experience and Company Structure each have multiple paragraphs; they are substantive. Thus final sections could be: - About Ellie - About the Role - Responsibilities - Qualifications - Benefits - Pay - Schedule - Employee Experience - Company Structure That's many sections; maybe we can combine some. We could combine About Ellie and About the Role into a single "About Ellie and the Role" but that might lose nuance. However instruction says prefer few substantive sections over many thin ones. So we should aim for maybe 4-5 sections. Potential grouping: - About Ellie (includes description of company) - The Role (includes role description and responsibilities) - Qualifications (includes requirements) - Benefits & Pay (includes benefits, pay, schedule) - Culture & Employee Experience (includes culture, employee experience, company structure) But we need to follow heading examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could stick to those headings and put content accordingly. Thus:

    About the role

    - combine About Ellie and About The Role? Actually "About the role" heading expects role description. Could put the role description there. About Ellie could be maybe omitted or placed under a different heading like "About Ellie" but not in list. But we could put About Ellie under "About the role" as introductory? Might be okay. Better: Use "About the role" for role description (the paragraph about looking for someone...). Use "Responsibilities" for What You'll Do list. Use "Requirements" for What We're Looking For list. Use "Benefits" for benefits list. Use "Pay" for compensation info. Use "Schedule" for schedule info (full-time, flexible schedule, flexible work from home). Then we could optionally add a section for "Employee Experience" and "Company Structure" if we want, but they are not in the examples; but we could still use

    for them. However instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but the examples are those. To be safe, we could incorporate Employee Experience and Company Structure into existing sections like Benefits/Pay or maybe under a "

Similar jobs