Jobs · Information Technology · Massachusetts

RBT Site Manager

ServiceNet · Southampton, MA · 2 wk ago
On-siteInformation Technology$19.57–$24.93/hrFull-time
We need to output HTML fragment with sections: h3 headings for sections present: About the role? The posting includes description: "ServiceNet is seeking a compassionate and dedicated leader..." That's about the role. Could be "About the role". Also "Responsibilities" includes Site Manager Responsibilities and RBT Responsibilities. Could combine? Probably separate? The instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content. We have: - About the role: description paragraph about role, why you'll love it. - Responsibilities: includes Site Manager Responsibilities and RBT Responsibilities. Could be combined under Responsibilities. - Qualifications: Required and Preferred. - Benefits: listed. - Pay: compensation details. - Schedule: "Second Shift". We must not include sections with filler like "not specified". All have content. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, equal opportunity, etc. Also navigation, cookie, legal, scam-warning, duplicated lines, application instructions. Also remove "Learn More About ServiceNet" maybe? It's not boilerplate but maybe considered promotional; but it's substantive? It's a link to learn more; could be considered part of About ServiceNet. Might keep as paragraph? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Learn More About ServiceNet" link is not boilerplate; it's informational. Could keep as a paragraph under About ServiceNet? But we don't have a section for About ServiceNet; we could include under About the role or maybe a separate "About the organization". Not in list of allowed headings but we could still include? The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says prefer a few substantive sections over many thin ones. Probably better to keep to those headings. So we can incorporate ServiceNet description into About the role paragraph. We must preserve all substantive information; do not invent or summarize away detail. So we need to include details like responsibilities bullet points, qualifications, benefits, pay range, schedule. We must not include duplicated lines: there are duplicated "Benefits:" appears twice; we need to combine. We must not include "And much more" vague? That's filler; maybe we should omit that line as it's not specific. The instruction: 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. "And much more" is vague; better to omit. We need to format lists with
  • . For prose use

    . We need to output only HTML fragment, no /, no markdown. Let's craft:

    About the role

    ServiceNet is seeking a compassionate and dedicated leader to oversee a residential program for individuals with developmental disabilities or brain injuries. This role is more than just a job—it’s an opportunity to make a meaningful impact in the lives of others by helping them achieve personal goals, build connections, and find fulfillment. Why You’ll Love This Role: Make a Difference – Support individuals in living more independent and joyful lives. Lead with Purpose – Supervise and collaborate with a team to provide high-quality care. Grow Your Career – Gain valuable leadership experience and professional development.

    But note we should not lose the bullet points? The "Why You’ll Love This Role" includes bullet-like sentences separated by periods. Could keep as prose. Alternatively we could keep as
    • but not required. The instruction: Use
      • for any list of duties/requirements/benefits, and

        for prose. The "Why You’ll Love This Role" is not a list of duties/requirements/benefits; it's more like benefits but could be considered a list. However it's not explicitly a list; we can keep as

        . Now Responsibilities: we have Site Manager Responsibilities and RBT Responsibilities. Could combine under one Responsibilities section with two subheadings? But we cannot use headings other than h3? Could use

        maybe but not specified. Safer to just list all responsibilities as a single list. List items: - Support and Empower Residents – Assist with daily routines, recreational activities, and goal-setting while fostering a warm and inclusive environment. - Ensure Safety and Well-being – Administer medications (MAP training available), provide transportation to appointments and activities, and uphold health and safety protocols. - Lead and Collaborate – Supervise, train, and support staff while working closely with the Program Director to ensure smooth operations. - Stay Organized – Manage staff schedules, track important resident information, and complete necessary documentation. - Guide Behavioral Support & Training – Coach, train, and support program staff in behavior plan implementation, clinical protocols, and best practices, serving as a liaison with the clinical team and families. - Ensure Clinical Quality & Data Integrity – Collect, review, and maintain accurate behavioral data and clinical documentation while supporting staff in proper data-collection practices. - Support ISPs & Risk Management – Participate in ISP development, assist with assessments and crisis planning, and respond to behavioral incidents using approved interventions and reporting procedures. - Maintain Ethical & Regulatory Compliance – Adhere to RBT ethical standards, supervision and scope-of-practice requirements, and ensure program operations meet all clinical, regulatory, and documentation expectations. We need to ensure we didn't miss any. Now Qualifications: Required and Preferred. Required list: - High school diploma or GED. - RBT certification (or willingness to obtain within 30 days). - Ability to maintain RBT ethics and supervision requirements. - PABC, MAP, First Aid, and CPR (or willingness to obtain upon hire). - Strong communication, leadership, and problem-solving skills. - Valid driver’s license and reliable transportation. - Ability to pass CORI and background checks. Preferred list: - Associate’s or bachelor’s degree in a related field. - 2–3 years of experience supporting individuals with developmental disabilities or brain injuries. - Experience in residential or clinically intensive programs. - Familiarity with trauma-informed care and data-based decision-making. We could combine into one list but maybe better to separate with headings? Not allowed. Could just list all as one list, but we lose distinction. However instruction: preserve ALL substantive information; we can still preserve by including both required and preferred in same list but we need to indicate which are required vs preferred. Could add text like "Required:" then list, then "Preferred:" then list. That's still prose? Could be

        with bold? But we cannot add extra tags beyond

        ,

        • ,

          . We could embed required/preferred as inside

          ? Not allowed? The instruction only says use those tags for those purposes; but we could still use inside

          maybe? Safer to keep as

          with sentences. We could do:

          Qualifications

          Required: High school diploma or GED; RBT certification (or willingness to obtain within 30 days); ability to maintain RBT ethics and supervision requirements; PABC, MAP, First Aid, and CPR (or willingness to obtain upon hire); strong communication, leadership, and problem-solving skills; valid driver’s license and reliable transportation; ability to pass CORI and background checks.

          Preferred: Associate’s or bachelor’s degree in a related field; 2–3 years of experience supporting individuals with developmental disabilities or brain injuries; experience in residential or clinically intensive programs; familiarity with trauma-informed care and data-based decision-making.

          That uses

          and which is not prohibited. The instruction only mandates use of

          • for lists and

            for prose; using inside

            is okay as it's still prose. Should be fine. Now Benefits: we have list: - Generous PTO (time-off) package. - Comprehensive health and dental insurance plans. - Life insurance and long-term disability insurance. - 403(b) retirement plan. - Tuition remission for eligible classes. - Public Service Loan Forgiveness (PSLF) eligibility and tuition assistance. - Opportunities for career development and advancement. We should omit "And much more". Also note there was earlier mention of 401(k) matching etc but later benefits list includes 403(b). We need to preserve all substantive information; the earlier bullet list includes "401(k)401(k) matchingDental insuranceHealth insuranceOpportunity for advancementPaid time offTraining & developmentTuition assistanceVision insurance". That seems garbled due to formatting. The later benefits list is more detailed. We should combine both? The earlier list seems to be a duplicate but missing details. We should include all unique benefits: 401(k) matching, dental insurance, health insurance, opportunity for advancement, paid time off, training & development, tuition assistance, vision insurance, generous PTO package, comprehensive health and dental insurance plans, life insurance and long-term disability insurance, 403(b) retirement plan, tuition remission for eligible classes, PSLF eligibility and tuition assistance, opportunities for career development and advancement. But many overlap. We need to preserve all substantive information; we can combine into a list without duplicates. Let's enumerate unique benefits: - 401(k) matching - Dental insurance - Health insurance - Vision insurance - Opportunity for advancement - Paid time off (PTO) / Generous PTO (time-off) package - Training & development - Tuition assistance / Tuition remission for eligible classes - Public Service Loan Forgiveness (PSLF) eligibility - Life insurance - Long-term disability insurance - 403(b) retirement plan We could also include "Opportunity for advancement" already. We should not include vague "And much more". So list these. Now Pay: compensation details: "$19.57-24.93/hour $19.57-$20.53/hr base +$2.00 differential when MAP Certified + $2.40 differential RBT/Site differential". We need to preserve that exactly. Could phrase as

            Pay: $19.57‑24.93/hour ($19.57‑$20.53/hr base + $2.00 differential when MAP Certified + $2.40 differential RBT/Site differential)

            . Use en-dash? We'll keep hyphens. Now Schedule: "Second Shift". So

            Schedule: Second Shift

            . Now ensure we don't include any boilerplate like "ServiceNet is an equal opportunity employer." Remove. Also remove "Learn More About ServiceNet https://www.servicenet.org/" maybe considered navigation? It's a link; could be considered boilerplate? It's not navigation but it's a call to action; maybe remove as it's like application instruction? Not exactly. Safer to remove. Now produce HTML fragment. Let's craft:

            About the role

            ServiceNet is seeking a compassionate and dedicated leader to oversee a residential program for individuals with developmental disabilities or brain injuries. This role is more than just a job—it’s an opportunity to make a meaningful impact in the lives of others by helping them achieve personal goals, build connections, and find fulfillment. Why You’ll Love This Role: Make a Difference – Support individuals in living more independent and joyful lives. Lead with Purpose – Supervise and collaborate with a team to provide high-quality care. Grow Your Career – Gain valuable leadership experience and professional development.

            Responsibilities

            • Support and Empower Residents – Assist with daily routines,

Similar jobs

Site Manager

Lazer LogisticsOlathe, KS· 1 wk ago
Information Technologyapply on intelliapp.driverapponline.com

Site Manager

MPS GroupLouisville, KY· 1 wk ago
Information Technologyapply on recruitingbypaycor.com

Site Manager

Newbold ServicesSouth Bend, IN· 3 wk ago
Information Technologyapply on recruiting.ultipro.ca

Site Manager

Karman Space & DefenseWilsonville, OR· 4 mo ago
Information Technologyapply on workforcenow.adp.com

Site Manager

Take 5 Car WashJeffersonville, IN· 3 mo ago
Information Technologyapply on whistleexpresscarwash.wd108.myworkdayjobs.com

Site Manager

NAPA Auto PartsGlobe, AZ· 2 mo ago
Project Managementapply on genpt.wd1.myworkdayjobs.com