Human Services Specialist

Here's a thinking process: 1. **Analyze the Request:** - User wants me to reformat a job posting into clean, well-structured semantic HTML. - Rules: - Use `

` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use `

• ` for lists of duties/requirements/benefits - Use `

  ` for prose - Do NOT repeat the job title as a heading (page already shows it) - 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 2. **Analyze the Input Job Posting:** Let me extract the content carefully. The posting text is: "Our client is a local government entity committed to delivering essential public services and fostering community development. The Human Services Specialist will provide short-term case management and support to connect older adults and individuals with disabilities to long-term services and supports, ensuring they can age in place with dignity and access to critical resources. This is a full-time, contract position based in Arlington, VA, paying $24.00 per hour. Responsibilities: Conduct intake by phone, email, or in-person walk-ins seeking long-term services, emergency assistance, or support for older adults and persons with disabilities. Complete initial assessments and annual reassessments using the Virginia statewide assessment tool, recording information accurately in the system. Utilize assessment data to determine clients' needs for resources and design activities accordingly. Perform short-term case management to connect clients to requested services, completing all referral documentation and processes. Document all interactions and maintain the progress records in the No Wrong Door System of Record (Peer Place). Collaborate with team members and consult with clinical staff for complex cases. Support other ADSD teams with phone screening/triage and assist in planning and implementing aging programs like Home-Delivered Meals, Transportation, and Caregiver Supports. Required Qualifications: Bachelor's Degree in Social Work, Sociology, Psychology, Mental Health, or Counseling. One-year experience in human services/social services program delivery, including behavioral management, counseling, or making social service referrals. Preferred qualification Master’s Degree in Social Work, Sociology, Psychology, Mental Health, or Counseling. Experience working in an Aging and Disability Resource Center. Support and social work services experience with older adults and persons with disabilities. Documenting client encounters in electronic record-keeping systems, particularly No Wrong Door systems or Peer Place. Experience working with diverse cultural and ethnic backgrounds. Bilingual in Spanish, Korean, Amharic, or Vietnamese. Technical skills or certifications Ability to conduct assessments and record data accurately in electronic systems. Strong interpersonal, problem-solving, and coordination skills. What We Offer 401K retirement plan Medical and dental benefits for qualifying professionals Flex spending account Volunteer opportunities Worker Advantage discount program membership Sick Leave available where mandated by law Voluntary Supplemental Insurance Our Equal Employment Opportunity Policy: Employment Enterprises, Inc. is an equal employment opportunity employer. We recruit, employ, assign, train, compensate and promote without regard to race, color, sex, age, disability, religion, national origin, marital status, sexual orientation, ancestry, U.S. Veteran status, or any other protected category under applicable law. Employment Enterprises, Inc. is the parent company of Temporary Solutions, Inc. Temporary Solutions is a workforce solutions company based out of 10550 Linden Lake Plaza, Suite 200, Manassas, VA 20109. You can reach our recruiters about this job and more at 703-361-2220 or email recruiters@eeihr.com." Now, I need to follow the rules strictly. - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. - The EEO policy at the end needs to be removed per rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." - Also the last paragraph about Temporary Solutions, Inc. and contact info is likely application instructions or boilerplate. I'll remove it. - The EEO policy line is explicitly mentioned to remove. - Preserve ALL substantive information; do NOT invent or summarize away detail. - I need to keep all the responsibilities, qualifications, benefits, pay info, etc., exactly as stated. - Use `

  ` for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. - Note: The rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This gives examples of allowed headings. I should use these or similar, but only include sections that have real content. - "Do NOT repeat the job title as a heading (the page already shows it)" - so no `

  Human Services Specialist

  `. - "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." - The posting doesn't have a job ID explicitly, but has location, pay rate, etc. I'll fold pay and location into appropriate sections or a short paragraph. - "Preserve ALL substantive information; do NOT invent or summarize away detail." - Keep all duty lines, qualification lines, etc. - "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." - The posting states Pay: "$24.00 per hour". So I can have a Pay section. - It states "full-time, contract position based in Arlington, VA". So Schedule could be inferred as full-time, but the rule says never create Schedule section unless the posting actually states them. It says "full-time", so maybe Schedule can have content. But let's see: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Pay is stated. Schedule: "full-time" is stated, but is that enough? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "full-time, contract position". I think I can include Schedule with "Full-time, contract" but I need to be careful. Actually, the rule prefers "a few substantive sections over many thin ones." I'll include Pay since it's explicitly "$24.00 per hour". For Schedule, I could fold it into a short paragraph or include it if there's meaningful content. The posting says "This is a full-time, contract position based in Arlington, VA, paying $24.00 per hour." I'll probably put employment type in a brief intro or

  . - Benefits: The posting has "What We Offer" section with specific benefits: 401K, medical/dental, FSA, volunteer opportunities, discount program, sick leave (where mandated), voluntary supplemental insurance. So Benefits section is warranted. - Section headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. - Let's map the content: - "About the role": The first paragraph describes the role: "Our client is a local government entity committed to delivering essential public services and fostering community development. The Human Services Specialist will provide short-term case management and support to connect older adults and individuals with disabilities to long-term services and supports, ensuring they can age in place with dignity and access to critical resources." This is substantive. I'll use

  About the role

  . - "Responsibilities": List of 7 bullet points. Use
  • . - "Requirements": The posting has "Required Qualifications" and "Preferred qualification". The rules list "Requirements" as a heading example. I need to decide how to handle. The posting separates "Required Qualifications" and "Preferred qualification". I could have two sub-sections or combine under "Requirements". The rule says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It lists both "Requirements" and "Qualifications" as separate examples. I think I should have "Requirements" for the required qualifications, and maybe "Qualifications" for preferred? Or combine. Let's see the exact text: "Required Qualifications:" then list, then "Preferred qualification" then list. I'll create "Requirements" heading and include both required and preferred, or maybe "Qualifications" and list required first, then preferred. To be safe, I'll use "Requirements" as the heading, and include both required and preferred qualifications under it, clearly marked. Or I could do two headings: "Requirements" and "Preferred Qualifications". But the rule says "include a section ONLY when the posting has real, specific content for it". Both have content. I'll use "Requirements" and under it list required, then preferred. Or follow the examples: the examples list "Requirements" and "Qualifications" as separate. I'll likely use "Requirements" for the mandatory ones, and maybe "Qualifications" for the preferred? Actually, the rule says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say I must use all, and I should only include when there's content. I'll use "Requirements" to cover both required and preferred, as is common. Or I can use "Qualifications" for the degree/experience part, and "Skills" for the soft skills/technical. Let's map properly: Looking at the posting structure: - Responsibilities (bullet list) - Required Qualifications (bullet list) - Preferred qualification (bullet list, but labeled "Preferred qualification") - What We Offer (bullet list of benefits) The rule's heading examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I think best mapping: - "About the role" → the first paragraph - "Responsibilities" → the duty list - "Requirements" → the Required Qualifications + Preferred qualification (I'll combine or separate clearly) - "Qualifications" might be redundant. I'll probably use "Requirements" for the qualification lists. - "Skills" → the technical skills/interpersonal skills listed under "Technical skills or certifications" and "Strong interpersonal, problem-solving, and coordination skills." I could put those under "Skills". - "Benefits" → the "What We Offer" list - "Pay" → "$24.00 per hour" - "Schedule" → "full-time, contract" but I need to check if I should create a Schedule section. The rule says "never create Pay/Schedule/B