Care and Operations Specialist
` 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 job title as a heading (already shown)
- Do NOT put Job ID / requisition numbers as headings - fold minor metadata into 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")
- Prefer a few substantive sections over many thin ones
- Output ONLY the HTML fragment — no `/`, no markdown code fences
2. **Analyze the Provided Job Posting Text:**
Let me copy and structure the input:
Unit: Student Affairs (Vice Provost)
MBU Department: Student Affairs Department
Summary: Navigating college can be a challenging experience. The mission for the Office of Student Advocacy is to champion the rights, welfare, and academic success of every student within our educational community. As the central hub for connecting students to resources and services, we are committed to fostering an inclusive and supportive environment where all students can thrive and reach their full potential.
Duties & Responsibilities The Care and Operations Specialist serves as a vital operational and student-facing member of the Office of Student Advocacy (OSA) team, balancing non-clinical, trauma-informed student support with high-level administrative coordination. This professional is the central point of contact for students navigating academic or personal concerns and utilizes an empathetic, student-centered approach, ensuring students are seamlessly connected to essential internal and external resources to foster their success and retention. Daily responsibilities include managing all intake processes, creating and assigning meticulous student case files, providing direct student support, providing programmatic support to special populations served by OSA, providing administrative support to all OSA staff, and tracking departmental key performance indicators and longitudinal student need trends. The Specialist also works closely with the Finance Team to procure goods and services and actively participates in professional development and university committees.
Qualifications Minimum Qualifications Bachelor’s degree in Social Work, Psychology, Education, Public Administration or related education, experience, certifications and/or training that demonstrates the knowledge, skills, and abilities required to perform the work. Empathetic and student-centered approach with a commitment to timely action and response. Strong organizational and multitasking abilities with meticulous attention to detail. Excellent verbal and written communication skills. Experience in case management, student services, or administrative support Ability to handle sensitive and confidential information with discretion and professionalism. Proficiency with Maxient case management software and Google Workspace. Ability to work both independently and collaboratively within a team. Demonstrated experience working in and fostering an environment of respect, professionalism and civility with a population of faculty, staff, and students from various backgrounds and experiences, or a commitment to do so as a staff member at VCU.
Preferred Qualifications Master's degree in Social Work, Psychology, Education, Public Administration or related education, experience, certifications and training that demonstrates the knowledge, skills, and abilities required to perform the work. Minimum 2 years experience in case management, student services, or administrative support, preferably in a higher education or advocacy setting. Knowledge of university policies and student support systems. Experience with conflict resolution or crisis intervention.
Salary Range: 46,000
Benefits: All full-time university staff are eligible for VCU’s robust benefits package that includes comprehensive health benefits, paid annual and holiday leave, generous tuition benefits, retirement planning and savings options, tax-deferred annuity and cash match programs, employee discounts, well-being resources, abundant opportunities for career development and advancement, and more.
FLSA Exemption Status: Exempt
Hours per Week: 40
Restricted Position: Yes
ORP Eligible: No
Flexible Work Arrangement
University Job Title: 35221N - Specialist SS 1
Contact Information Contact Name: Xavier Bey Contact Email: xbey@vcu.edu
Now, I need to parse this and decide what sections to include, following the rules.
Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule
Let's map the content:
- "About the role" / Summary: The first paragraph about mission, Office of Student Advocacy, connecting students to resources, inclusive environment. I'll use `
About the role
` or maybe just keep it as prose under a heading if needed. The rules say use `` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So I can use "About the role" for the summary paragraph.
- "Duties & Responsibilities": Clear section. I'll use `Responsibilities
` and list duties with `- `. The text has a paragraph plus specific duties. I'll structure it as a list, but also keep the introductory sentence maybe in `
` or integrate into list items. Rules: "Use `
- ` for any list of duties/requirements/benefits, and `
` for prose." So I'll make the daily responsibilities a list, and possibly keep the first sentence as `
` or incorporate naturally. I'll aim for clean semantic HTML.
- "Qualifications": The text has "Minimum Qualifications" and "Preferred Qualifications". I'll combine or separate? Rules say use headings like Requirements, Qualifications. I'll likely use `
Qualifications
` and sub-divide into minimum/preferred, or just list them. Since rules say "Include a section ONLY when the posting has real, specific content for it", and "never emit a heading followed by filler/placeholder text". I have real content, so I'll include it. I'll structure as `Qualifications
` with maybe two sub-lists or a combined list with labels. But to keep it simple and semantic, I'll use `Qualifications
` and then `` or `
- ` for the content. The rules say use `
- ` for lists of duties/requirements/benefits. Qualifications are requirements, so `
- ` is appropriate.
- "Skills": Not explicitly a separate section, but qualifications imply skills. The rules list "Skills" as a possible heading, but I should only include it if there's real specific content. I don't see a distinct "Skills" section separate from qualifications. I'll probably skip a standalone "Skills" section unless I can map meaningful content. The posting has skills embedded in qualifications. I'll likely not create a separate "Skills" section to avoid thin content.
- "Benefits": Clear section. "Salary Range: 46,000" and "Benefits:" paragraph. I'll use `
Benefits
` for the benefits paragraph. Pay/salary might go under "Pay" heading, but rules say "Prefer a few substantive sections over many thin ones" and "never create Pay/Schedule/Benefits sections unless the posting actually states them." Salary is stated: "Salary Range: 46,000". Benefits are stated. I'll include both "Pay" and "Benefits" if I can structure them properly. But rules also say: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". Salary is specific: 46,000. Benefits are specific. I'll include `Pay
` and `Benefits
`. However, rules also say: "Prefer a few substantive sections over many thin ones." I need to be careful not to create too many sections if they're thin. But both salary and benefits have substantial content. I'll include them.
- "Schedule": "Hours per Week: 40" and "FLSA Exemption Status: Exempt" and "Restricted Position: Yes" and "ORP Eligible: No" and "Flexible Work Arrangement". These are metadata. Rules: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short `` or drop it." "Hours per Week", "FLSA Status", etc. are minor metadata. I'll fold them into a short `
` perhaps under "About the role" or a separate "Schedule" heading only if there's meaningful content beyond just numbers/status. The rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It says "unless the posting actually states them" - they are stated, but are they substantive sections? The intent seems to be: don't create a "Schedule" section just saying "40 hours a week" if it's just boilerplate. But the posting does state "Hours per Week: 40", "FLSA Exemption Status: Exempt", etc. I need to decide. The rule: "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." This implies I should create Pay/Schedule/Benefits sections only if there's actual content, not placeholder. The posting states specific values, so I could create them, but I need to weigh against "Prefer a few substantive sections over many thin ones." Also, "fold minor metadata into a short `
` or drop it." I think "Hours per Week", "FLSA Status", etc. are minor metadata and should be folded into a `
`, not given their own `
` section. I'll avoid a "Schedule" heading. I'll maybe put them in a small `
` at the bottom or integrate.
- "About the role": The summary paragraph. I'll use `
About the role
`.
- "Responsibilities": `Responsibilities
`.
- "Qualifications": `Qualifications
`. I'll split into Minimum and Preferred, or just list them together with labels. To keep it clean, I'll use `- ` for each qualification list, maybe with `` for labels.
- "Skills": Not explicitly present as a separate section. I'll skip.
- "Pay": "Salary Range: 46,000". I'll use `
Pay
` and put the salary in `` or `
- `. Since it's a single line, `
` might be fine, but rules say use `
- ` for lists. I'll use `
` for the salary statement, or `
- Salary Range: 46,000
`. I think `` is okay for prose, but salary is a specific data point. I'll use `
Salary Range: 46,000
`.
- "Benefits": `Benefits
` with
` for prose - Do NOT repeat job title as a heading (already shown) - Do NOT put Job ID / requisition numbers as headings - fold minor metadata into 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") - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no `/`, no markdown code fences 2. **Analyze the Provided Job Posting Text:** Let me copy and structure the input: Unit: Student Affairs (Vice Provost) MBU Department: Student Affairs Department Summary: Navigating college can be a challenging experience. The mission for the Office of Student Advocacy is to champion the rights, welfare, and academic success of every student within our educational community. As the central hub for connecting students to resources and services, we are committed to fostering an inclusive and supportive environment where all students can thrive and reach their full potential. Duties & Responsibilities The Care and Operations Specialist serves as a vital operational and student-facing member of the Office of Student Advocacy (OSA) team, balancing non-clinical, trauma-informed student support with high-level administrative coordination. This professional is the central point of contact for students navigating academic or personal concerns and utilizes an empathetic, student-centered approach, ensuring students are seamlessly connected to essential internal and external resources to foster their success and retention. Daily responsibilities include managing all intake processes, creating and assigning meticulous student case files, providing direct student support, providing programmatic support to special populations served by OSA, providing administrative support to all OSA staff, and tracking departmental key performance indicators and longitudinal student need trends. The Specialist also works closely with the Finance Team to procure goods and services and actively participates in professional development and university committees. Qualifications Minimum Qualifications Bachelor’s degree in Social Work, Psychology, Education, Public Administration or related education, experience, certifications and/or training that demonstrates the knowledge, skills, and abilities required to perform the work. Empathetic and student-centered approach with a commitment to timely action and response. Strong organizational and multitasking abilities with meticulous attention to detail. Excellent verbal and written communication skills. Experience in case management, student services, or administrative support Ability to handle sensitive and confidential information with discretion and professionalism. Proficiency with Maxient case management software and Google Workspace. Ability to work both independently and collaboratively within a team. Demonstrated experience working in and fostering an environment of respect, professionalism and civility with a population of faculty, staff, and students from various backgrounds and experiences, or a commitment to do so as a staff member at VCU. Preferred Qualifications Master's degree in Social Work, Psychology, Education, Public Administration or related education, experience, certifications and training that demonstrates the knowledge, skills, and abilities required to perform the work. Minimum 2 years experience in case management, student services, or administrative support, preferably in a higher education or advocacy setting. Knowledge of university policies and student support systems. Experience with conflict resolution or crisis intervention. Salary Range: 46,000 Benefits: All full-time university staff are eligible for VCU’s robust benefits package that includes comprehensive health benefits, paid annual and holiday leave, generous tuition benefits, retirement planning and savings options, tax-deferred annuity and cash match programs, employee discounts, well-being resources, abundant opportunities for career development and advancement, and more. FLSA Exemption Status: Exempt Hours per Week: 40 Restricted Position: Yes ORP Eligible: No Flexible Work Arrangement University Job Title: 35221N - Specialist SS 1 Contact Information Contact Name: Xavier Bey Contact Email: xbey@vcu.edu Now, I need to parse this and decide what sections to include, following the rules. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule Let's map the content: - "About the role" / Summary: The first paragraph about mission, Office of Student Advocacy, connecting students to resources, inclusive environment. I'll use `
About the role
` or maybe just keep it as prose under a heading if needed. The rules say use `` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So I can use "About the role" for the summary paragraph.
- "Duties & Responsibilities": Clear section. I'll use `Responsibilities
` and list duties with `- `. The text has a paragraph plus specific duties. I'll structure it as a list, but also keep the introductory sentence maybe in `
` or integrate into list items. Rules: "Use `
- ` for any list of duties/requirements/benefits, and `
` for prose." So I'll make the daily responsibilities a list, and possibly keep the first sentence as `
` or incorporate naturally. I'll aim for clean semantic HTML.
- "Qualifications": The text has "Minimum Qualifications" and "Preferred Qualifications". I'll combine or separate? Rules say use headings like Requirements, Qualifications. I'll likely use `
Qualifications
` and sub-divide into minimum/preferred, or just list them. Since rules say "Include a section ONLY when the posting has real, specific content for it", and "never emit a heading followed by filler/placeholder text". I have real content, so I'll include it. I'll structure as `Qualifications
` with maybe two sub-lists or a combined list with labels. But to keep it simple and semantic, I'll use `Qualifications
` and then `` or `
- ` for the content. The rules say use `
- ` for lists of duties/requirements/benefits. Qualifications are requirements, so `
- ` is appropriate.
- "Skills": Not explicitly a separate section, but qualifications imply skills. The rules list "Skills" as a possible heading, but I should only include it if there's real specific content. I don't see a distinct "Skills" section separate from qualifications. I'll probably skip a standalone "Skills" section unless I can map meaningful content. The posting has skills embedded in qualifications. I'll likely not create a separate "Skills" section to avoid thin content.
- "Benefits": Clear section. "Salary Range: 46,000" and "Benefits:" paragraph. I'll use `
Benefits
` for the benefits paragraph. Pay/salary might go under "Pay" heading, but rules say "Prefer a few substantive sections over many thin ones" and "never create Pay/Schedule/Benefits sections unless the posting actually states them." Salary is stated: "Salary Range: 46,000". Benefits are stated. I'll include both "Pay" and "Benefits" if I can structure them properly. But rules also say: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". Salary is specific: 46,000. Benefits are specific. I'll include `Pay
` and `Benefits
`. However, rules also say: "Prefer a few substantive sections over many thin ones." I need to be careful not to create too many sections if they're thin. But both salary and benefits have substantial content. I'll include them.
- "Schedule": "Hours per Week: 40" and "FLSA Exemption Status: Exempt" and "Restricted Position: Yes" and "ORP Eligible: No" and "Flexible Work Arrangement". These are metadata. Rules: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short `` or drop it." "Hours per Week", "FLSA Status", etc. are minor metadata. I'll fold them into a short `
` perhaps under "About the role" or a separate "Schedule" heading only if there's meaningful content beyond just numbers/status. The rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It says "unless the posting actually states them" - they are stated, but are they substantive sections? The intent seems to be: don't create a "Schedule" section just saying "40 hours a week" if it's just boilerplate. But the posting does state "Hours per Week: 40", "FLSA Exemption Status: Exempt", etc. I need to decide. The rule: "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." This implies I should create Pay/Schedule/Benefits sections only if there's actual content, not placeholder. The posting states specific values, so I could create them, but I need to weigh against "Prefer a few substantive sections over many thin ones." Also, "fold minor metadata into a short `
` or drop it." I think "Hours per Week", "FLSA Status", etc. are minor metadata and should be folded into a `
`, not given their own `
` section. I'll avoid a "Schedule" heading. I'll maybe put them in a small `
` at the bottom or integrate.
- "About the role": The summary paragraph. I'll use `
About the role
`.
- "Responsibilities": `Responsibilities
`.
- "Qualifications": `Qualifications
`. I'll split into Minimum and Preferred, or just list them together with labels. To keep it clean, I'll use `- ` for each qualification list, maybe with `` for labels.
- "Skills": Not explicitly present as a separate section. I'll skip.
- "Pay": "Salary Range: 46,000". I'll use `
Pay
` and put the salary in `` or `
- `. Since it's a single line, `
` might be fine, but rules say use `
- ` for lists. I'll use `
` for the salary statement, or `
- Salary Range: 46,000
`. I think `` is okay for prose, but salary is a specific data point. I'll use `
Salary Range: 46,000
`.
- "Benefits": `Benefits
` with
` or integrate into list items. Rules: "Use `
- ` for any list of duties/requirements/benefits, and `
` for prose." So I'll make the daily responsibilities a list, and possibly keep the first sentence as `
` or incorporate naturally. I'll aim for clean semantic HTML. - "Qualifications": The text has "Minimum Qualifications" and "Preferred Qualifications". I'll combine or separate? Rules say use headings like Requirements, Qualifications. I'll likely use `
Qualifications
` and sub-divide into minimum/preferred, or just list them. Since rules say "Include a section ONLY when the posting has real, specific content for it", and "never emit a heading followed by filler/placeholder text". I have real content, so I'll include it. I'll structure as `Qualifications
` with maybe two sub-lists or a combined list with labels. But to keep it simple and semantic, I'll use `Qualifications
` and then `` or `
- ` for the content. The rules say use `
- ` for lists of duties/requirements/benefits. Qualifications are requirements, so `
- ` is appropriate.
- "Skills": Not explicitly a separate section, but qualifications imply skills. The rules list "Skills" as a possible heading, but I should only include it if there's real specific content. I don't see a distinct "Skills" section separate from qualifications. I'll probably skip a standalone "Skills" section unless I can map meaningful content. The posting has skills embedded in qualifications. I'll likely not create a separate "Skills" section to avoid thin content.
- "Benefits": Clear section. "Salary Range: 46,000" and "Benefits:" paragraph. I'll use `
Benefits
` for the benefits paragraph. Pay/salary might go under "Pay" heading, but rules say "Prefer a few substantive sections over many thin ones" and "never create Pay/Schedule/Benefits sections unless the posting actually states them." Salary is stated: "Salary Range: 46,000". Benefits are stated. I'll include both "Pay" and "Benefits" if I can structure them properly. But rules also say: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". Salary is specific: 46,000. Benefits are specific. I'll include `Pay
` and `Benefits
`. However, rules also say: "Prefer a few substantive sections over many thin ones." I need to be careful not to create too many sections if they're thin. But both salary and benefits have substantial content. I'll include them. - "Schedule": "Hours per Week: 40" and "FLSA Exemption Status: Exempt" and "Restricted Position: Yes" and "ORP Eligible: No" and "Flexible Work Arrangement". These are metadata. Rules: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short `` or drop it." "Hours per Week", "FLSA Status", etc. are minor metadata. I'll fold them into a short `
` perhaps under "About the role" or a separate "Schedule" heading only if there's meaningful content beyond just numbers/status. The rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It says "unless the posting actually states them" - they are stated, but are they substantive sections? The intent seems to be: don't create a "Schedule" section just saying "40 hours a week" if it's just boilerplate. But the posting does state "Hours per Week: 40", "FLSA Exemption Status: Exempt", etc. I need to decide. The rule: "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." This implies I should create Pay/Schedule/Benefits sections only if there's actual content, not placeholder. The posting states specific values, so I could create them, but I need to weigh against "Prefer a few substantive sections over many thin ones." Also, "fold minor metadata into a short `
` or drop it." I think "Hours per Week", "FLSA Status", etc. are minor metadata and should be folded into a `
`, not given their own `
` section. I'll avoid a "Schedule" heading. I'll maybe put them in a small `
` at the bottom or integrate. - "About the role": The summary paragraph. I'll use `
About the role
`. - "Responsibilities": `Responsibilities
`. - "Qualifications": `Qualifications
`. I'll split into Minimum and Preferred, or just list them together with labels. To keep it clean, I'll use `- ` for each qualification list, maybe with `` for labels.
- "Skills": Not explicitly present as a separate section. I'll skip.
- "Pay": "Salary Range: 46,000". I'll use `
Pay
` and put the salary in `` or `
- `. Since it's a single line, `
` might be fine, but rules say use `
- ` for lists. I'll use `
` for the salary statement, or `
- Salary Range: 46,000
` is okay for prose, but salary is a specific data point. I'll use `
Salary Range: 46,000
`. - "Benefits": `Benefits
` with
- ` for lists. I'll use `
- `. Since it's a single line, `
- ` for each qualification list, maybe with `` for labels.
- "Skills": Not explicitly present as a separate section. I'll skip.
- "Pay": "Salary Range: 46,000". I'll use `
- ` is appropriate.
- "Skills": Not explicitly a separate section, but qualifications imply skills. The rules list "Skills" as a possible heading, but I should only include it if there's real specific content. I don't see a distinct "Skills" section separate from qualifications. I'll probably skip a standalone "Skills" section unless I can map meaningful content. The posting has skills embedded in qualifications. I'll likely not create a separate "Skills" section to avoid thin content.
- "Benefits": Clear section. "Salary Range: 46,000" and "Benefits:" paragraph. I'll use `
- ` for lists of duties/requirements/benefits. Qualifications are requirements, so `
- ` for the content. The rules say use `