Systems Support Specialist

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID etc. Remove boilerplate. We need to parse the posting. Content: - Intro about ScriptPro: "Imagine working at a place where innovation meets impact..." etc. That's about the company, could be "About the role"? Actually "About the role" is typical heading for job summary. The job summary: "Job Summary: The Systems Support Specialist works directly with external customers to resolve issues in live production environments..." etc. We need sections: About the role (maybe job summary), Responsibilities (Scope of the Role bullet list), Requirements (Required Qualifications), Qualifications (Preferred Qualifications), Skills (maybe combine required/preferred? but we can list skills under Requirements? The instruction: Use headings 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: could be the introductory paragraph about ScriptPro and the role? The job summary is more like "About the role". We'll put that under

About the role

with paragraphs. - Responsibilities: Scope of the Role list (maintain, analyze, troubleshoot...). That's a list. - Requirements: Required Qualifications list. - Qualifications: Preferred Qualifications list. - Skills: maybe we can extract skills from Required Qualifications (e.g., SQL Server, Windows OS, etc.) but those are already in Requirements. Could also list "Excellent customer service skills..." etc. But we might combine skills under Requirements? However we need to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must include all; only include when posting has real specific content. So we can include Skills if we have specific skill list not covered elsewhere. The posting includes many skill items in Required Qualifications (e.g., Basic SQL Server..., Advanced Windows OS Knowledge..., Working knowledge..., Experience with..., Basic understanding..., Experience with remote support tool..., Demonstrated ability..., Demonstrate proficiency..., Excellent analytical..., Excellent customer service..., Excellent verbal..., Ability to multitask...). Those could be considered skills. But they are already in Required Qualifications. To avoid duplication, we could put skills under Requirements and not have separate Skills section. But we need to decide. Better: Use Requirements for required qualifications (education, experience, certifications). Use Skills for technical and soft skills list. Qualifications for preferred qualifications. Thus: - Requirements: education (Associate's or Bachelor's degree...), 2 years related experience. - Skills: list of technical skills: Basic SQL Server 2000/2008/2012/MDSE administration skills; Advanced Windows OS Knowledge (Win 7/8/10); Working knowledge of desktop, mobile devices, and peripheral troubleshooting; Experience with Windows Patch Management, Desktop Updates, and Anti-virus tools; Basic understanding of connectivity and networking best practices; Experience with a remote support tool (BOMGAR, Windows Remote Desktop, etc.); Demonstrated ability to work with minimal supervision to set and prioritize work with a high level of detail; Demonstrate proficiency supporting proprietary software applications; Strong analytical and critical thinking skills with the ability to assess complex problems and identify root causes; Excellent customer service skills with a commitment to delivering high-quality support and positive outcomes; Excellent verbal and written communication skills, with the ability to tailor messaging to diverse audiences and stakeholders; Ability to multitask with varying priorities and attention to detail. - Qualifications (Preferred): CompTIA A+, Network+, Security+, Microsoft (MCSA/MCSE), or equivalent IT certifications; Knowledge of the pharmaceutical industry, particularly outpatient pharmacy operations; Multilingual skills in Spanish, Arabic, or French. - Benefits: list as given. - Pay: not specified; we should not include Pay section because no specific content. - Schedule: shift info: "General business hours are Monday through Friday 8 am to 5 pm CST. This hybrid role requires a combination of weekly on-campus and remote work with specific days varying based on departmental policy and business need. Generally, all positions may be fully performed on-campus in Mission, KS. Regular, punctual, and predictable attendance is an essential function of every job at ScriptPro." That's schedule info. So we can include Schedule section. - About the role: we can include the introductory paragraphs about ScriptPro and job summary. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. At end there is EEO statement, etc. Remove that. Also remove "Employment Conditions: It is ScriptPro's policy to run a comprehensive background check post job offer and you must be able to obtain Department of Defense security clearance after date of hire. See Standard Form 85 to preview requirements. This position includes responsibilities for ensuring compliance with cybersecurity and privacy policies to support the safeguarding sensitive data, including personally identifiable information (PII) and Protected Health Information (PHI). Completion of annual cybersecurity and privacy awareness training is required, as the role aligns with the organization’s security posture and risk management practices. All duties are defined in accordance with standardizations to ensure consistency and accountability of the policies." This is somewhat boilerplate but maybe relevant? It's about employment conditions, not specifically requested sections. Could be omitted as not part of headings. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is legal/employment conditions; maybe we should remove as it's not requested. However it's not exactly EEO but still legal. Safer to remove. Also "Working Conditions: Requires routine use of standard equipment and extended computer use. Employee must be able to sit, use hands and fingers, and occasionally lift, squat, stoop, bend, and reach. Problem-solving, practical learning, and instruction interpretation skills are essential." This could be considered part of Responsibilities or Requirements? Might be omitted as not under headings. But we could incorporate into Responsibilities? Probably better to omit as not requested. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must keep the substantive info from the posting that fits under headings. The employment conditions and working conditions are substantive but not under any of the headings list. However we could maybe put them under Responsibilities? But they are not duties. The instruction says to use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections. It doesn't say we cannot have other headings, but likely they want only those. Safer to stick to those headings and put relevant content under them. If some content doesn't fit, we might need to omit? But instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep all substantive info. If we omit employment conditions, we lose info. However maybe those are considered boilerplate legal? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Employment conditions could be considered legal. So we can remove them. Similarly Working Conditions maybe also considered boilerplate? Not sure. But it's substantive about physical requirements. Might be considered part of Responsibilities? Could be placed under Responsibilities as a bullet? But it's not a duty. However we could still include under Responsibilities as a note about physical demands. Might be okay. But to be safe, we could include a section "Working Conditions" but not in the list of allowed headings. 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, but the examples are those. It might be okay to add other headings if needed. However they said "Prefer a few substantive sections over many thin ones." So adding many sections is discouraged. Better to fit into existing sections. We can put physical demands under Responsibilities as a bullet: "Employee must be able to sit, use hands and fingers, and occasionally lift, squat, stoop, bend, and reach." That is a responsibility? Not exactly but could be considered job requirement. Could also go under Requirements as a bullet. But we already have Required Qualifications list; we could add a bullet about physical ability. Might be okay. Similarly employment conditions about background check, security clearance, cybersecurity training could go under Requirements as well (maybe as "Employment Conditions" but we can incorporate). However they are not qualifications but conditions. Could be placed under Requirements as additional notes. Given the instruction to preserve all substantive info, we should include them somewhere. Let's add them under Requirements as additional bullet points (maybe separate list). Or we could create a separate section "Employment Conditions" but that adds another heading. Might be okay but they said prefer few sections. I'd rather incorporate into Requirements. Thus: Requirements: education, experience, plus background check, security clearance, cybersecurity training, physical demands. But the posting also mentions "Employment Conditions: It is ScriptPro's policy to run a comprehensive background check post job offer and you must be able to obtain Department of Defense security clearance after date of hire. See Standard Form 85 to preview requirements. This position includes responsibilities for ensuring compliance with cybersecurity and privacy policies to support the safeguarding sensitive data, including personally identifiable information (PII) and Protected Health Information (PHI). Completion of annual cybersecurity and privacy awareness training is required, as the role aligns with the organization’s security posture and risk management practices. All duties are defined in accordance with standardizations to ensure consistency and accountability of the policies." We can summarize as bullet points: Must pass background check; Must be able to obtain DoD security clearance after hire; Must ensure compliance with cybersecurity and privacy policies; Must complete annual cybersecurity and privacy awareness training. Physical demands: "Requires routine use of standard equipment and extended computer use. Employee must be able to sit, use hands and fingers, and occasionally lift, squat, stoop, bend, and reach. Problem-solving, practical learning, and instruction interpretation skills are essential." We could add those as bullet under Requirements or maybe under Responsibilities. I'll put under Requirements as additional bullets. Now Benefits: we have list. Schedule: we have details. Now we need to output HTML fragment only. Structure:

About the role

... (intro paragraphs + job summary)

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Skills

• ...
...

Benefits

• ...
...

Schedule

... (maybe also bullet? but schedule info is prose)

We must not include Pay section. Now we need to extract exact text. Let's copy relevant sections. Intro about ScriptPro: "Imagine working at a place where innovation meets impact, and every day brings new opportunities to revolutionize the pharmacy industry! At ScriptPro, you’ll be part of a dynamic team that’s at the cutting edge of technology, creating solutions that make a real difference in people’s lives. ScriptPro develops, sells, and supports state of the art robotics and services in thousands of pharmacy settings around the United States and Canada. ScriptPro’s Customer Service department delivers high-quality support