Juvenile Justice Youth Development Specialist II, Shift Supervisor, Mariposa
Executive Office of Technology Services and Security · Boston, MA · 1 mo ago
OTHRPart-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invention. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes Shift: 3rd Shift (11:00PM - 9:00AM) with Sunday, Monday, and Tuesday off. Also mentions mandatory overtime. That's schedule info. So we can include a Schedule section. Benefits: posting mentions "Comprehensive Benefits" and says "Explore our Employee Benefits and Rewards!" but does not list specific benefits. It says "Comprehensive Benefits When you embark on a career with the Commonwealth, you are offered an outstanding suite of employee benefits..." That's generic but still mentions benefits. However rule: never create Benefits section unless posting actually states them. It does state there are benefits, but not specifics. Is that enough? It says "Comprehensive Benefits" heading in text. It mentions "Explore our Employee Benefits and Rewards!" but not details. The rule: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". Benefits section would be vague but not placeholder like that. It says "Comprehensive Benefits" and then description of benefits being offered but not enumerated. Might be considered substantive enough? It says "outstanding suite of employee benefits". That's still vague. Might be considered filler? The instruction: "Prefer a few substantive sections over many thin ones." Could include Benefits but maybe better to omit if not specific. However they explicitly mention "Comprehensive Benefits" and encourage to explore. Might be considered a section with content (though not detailed). I'd lean to include Benefits section with a paragraph summarizing that comprehensive benefits are offered, referencing the link? But we must not invent details. We can say "The position offers comprehensive employee benefits as part of the Commonwealth employment package." That's not invented, it's from text. That seems okay.
Pay: posting does not mention salary or pay specifics. It mentions "Salary placement is determined by a combination of factors..." but no numbers. That's vague. According to rule, never create Pay section unless posting actually states them. It does mention salary placement determined by factors, but no actual pay. That's still vague. Might be considered filler? It says "Salary placement is determined by a combination of factors..." Not a specific number or range. I'd avoid Pay section.
Schedule: we have shift details. So include Schedule section.
Responsibilities: we have duties and responsibilities list. So include Responsibilities.
Requirements: there is "Required Qualifications" and also "Minimum Entrance Requirements". Could combine into Requirements section. Also "Special Requirements" (age, physical, certifications). Could be part of Requirements.
Qualifications: there is "Preferred Qualifications". Could be Qualifications section.
Skills: maybe not separate; we could embed skills in qualifications.
About the role: there is introductory paragraph about role. Could be About the role.
Also "About The Department Of Youth Services" could be About the role? Actually that's about the department. Could be About the role or maybe a separate About the department but not in allowed headings. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put department info under About the role.
We must not include duplicated lines. Need to parse content and produce concise but preserve all substantive info. Not summarizing away detail; we must keep details but can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can rephrase? Probably we should keep the details as is, maybe bullet lists.
We need to output HTML fragment only.
Let's extract sections:
About the role: combine introductory paragraph and department description.
Intro: "The Department of Youth Services (DYS) is seeking a dynamic, positive, and service-minded individual to fill the role of Juvenile Justice Youth Development Specialist, Shift Administrator (JJYDS III). The selected candidate will work with juvenile justice-involved young people ages 12 – 20 years old (most of the youth served are 14 -18 years old) in DYS residential facilities. The selected candidate performs various care and security activities in connection with young people in the custody of the Department of Youth Services. They will observe the conduct and behavior of juveniles assigned to the facility and maintain liaison with staff members, law enforcement agencies, professional specialists, and others. They serve as a part of a team to provide guidance and direction to the JJYDS and JJYDS Shift Supervisors and supervise the operations of assigned shifts."
Department description: "As the Juvenile Justice agency for the Commonwealth of Massachusetts, the Department of Youth Services promotes positive change in the youth in our care and custody. Our mission is to make communities safer by improving the life outcomes for youth in our care. We achieve our mission through investing in highly qualified staff and a service continuum that engages youth, families, and communities in strategies that support positive youth development."
We can combine.
Responsibilities: list duties from "Duties and Responsibilities (these duties are a general summary and not all inclusive):" then bullet points. Need to preserve all details. We'll create