Systems Support Specialist

We need to output HTML fragment with sections: About the role? The posting includes a description includes intro about ScriptPro, job summary, reporting relationship, shift, scope of the role (list of duties), required qualifications, preferred qualifications, remote work requirements, benefits, employment conditions, working conditions, EEO etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Please visit www.scriptpro.com to learn more..." maybe considered boilerplate? It's not navigation but could be considered promotional; but it's not required. Probably we can keep it as part of About the role? But they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Please visit..." is not those; but it's like a call to action. Might be okay to keep but maybe it's considered boilerplate? Safer to drop it. We need sections only when there is real specific content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include. We have: - About the role: could be the introductory paragraph about ScriptPro and job summary. We'll put that as About the role. - Responsibilities: Scope of the Role list (duties). We'll put as Responsibilities. - Requirements: Required Qualifications. - Qualifications: maybe Preferred Qualifications? But they said use Qualifications as a heading; we could put Preferred Qualifications under Qualifications? Or we could have both Required and Preferred under Qualifications? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections for each of those if content exists. We have content for About the role, Responsibilities, Requirements (required qualifications), Qualifications (preferred qualifications), Skills (maybe we can extract skills from required/preferred?), Benefits, Pay (not mentioned), Schedule (shift info). Pay not mentioned, so we should NOT create Pay section. Schedule: we have shift info: General business hours Monday-Friday 8am-5pm CST, hybrid role, on-campus/remote. That's schedule info, so we can include Schedule section. Skills: we could extract skills like SQL Server, Windows OS, troubleshooting, etc. But those are already in qualifications. Might be redundant. Better to not create Skills if no distinct content beyond qualifications. But we could still create Skills with bullet list of technical skills. However instruction: Prefer a few substantive sections over many thin ones. So maybe combine Required and Preferred into Qualifications? But they gave separate headings Requirements and Qualifications. We could put Required under Requirements, Preferred under Qualifications. That seems appropriate. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. We must not repeat job title as heading. No Job ID. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting within those sections. We need to format lists with

• . For prose use

  . We need to remove boilerplate: EEO etc. 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 legal/boilerplate; but it's about employment conditions, security clearance, etc. Might be considered boilerplate? It's not EEO but it's still legal/compliance. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is legal boilerplate (background check, security clearance, cybersecurity training). So we should remove that entire block. Also remove "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." That's also somewhat boilerplate but maybe considered working conditions; not explicitly listed as a section heading we must include? We have Schedule but not Working Conditions. Could we include Working Conditions as a section? Not in the list of allowed headings; they gave examples but not exhaustive? They said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples; we could add other headings if needed, but they said prefer a few substantive sections over many thin ones. Working Conditions might be thin; we could incorporate into Schedule or About the role? Probably better to omit as it's somewhat generic. However we must preserve ALL substantive information; if we omit Working Conditions we lose detail about physical requirements. Is that substantive? It's about physical demands; maybe considered boilerplate but still substantive. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Working Conditions is not those categories. So we should keep it. But we don't have a heading for it; we could add a

  Working Conditions. The examples didn't forbid other headings; they just gave examples. So we can add Working Conditions section. Similarly, we have "Remote Work Requirements:" which could be part of Schedule or its own section. Could be under Schedule or Remote Work Requirements. Since Schedule already covers shift/hours, remote work requirements could be separate. But we can incorporate into Schedule as details about hybrid/remote. However Remote Work Requirements includes specific tech requirements (high-speed internet, hard-wired, distraction free workspace, camera on). That's substantive. We could add a section Remote Work Requirements. But not in examples; but we can add. We need to avoid too many sections. Perhaps combine Schedule and Remote Work Requirements into a single "Schedule & Remote Work" section. But we need to keep all info. Let's decide sections: - About the role (intro + job summary) - Responsibilities (scope of role duties) - Requirements (required qualifications) - Qualifications (preferred qualifications) - Benefits (benefits list) - Schedule & Remote Work (shift, hybrid, remote work requirements) - Working Conditions (physical demands, etc.) That's 7 sections. Might be okay. We must not create Pay section. Now we need to extract content precisely. Let's copy the relevant parts. About the role: The first paragraph: "Who is 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 across a range of products and systems, helping customers navigate technical challenges with confidence. This team operates in a fast-paced environment where problem-solving, adaptability, and continuous learning are key. Every interaction is an opportunity to make a direct impact by resolving issues, building customer trust, and playing a critical role in the overall customer experience. Job Summary: The Systems Support Specialist works directly with external customers to resolve issues in live production environments. The ideal candidate will be able to work with customers to provide system support focused on improving hardware and system performance, as well as overall customer satisfaction. Candidates will be measured by their ability to resolve complex hardware and software issues while delivering an exceptional customer experience. Candidates will achieve these objectives through a combination of hands-on involvement with customers and internal technical teams." We should keep all that as prose under About the role. Responsibilities: Scope of the Role list: - Maintain, analyze, troubleshoot, and repair ScriptPro systems, hardware, computer peripherals, applications, and configurations - Complete remote software configurations and upgrade support - Configure, build, and image workstation drives for fielded systems and mobile devices - Provide remote desktop support and network connectivity for field systems and mobile devices - Assess system needs and recommend technical solutions such as patches, upgrades or enhancements - Complete triage activities and troubleshoots complex problems - Provide server operating system administration and support for physical and virtual server environments - Support Windows Server updates, patching, and related maintenance activities - Service, customize, and deploy software packages as needed - Complete ticket documentation and tracking using Siebel with a high level of data quality - Perform other job duties as assigned We'll put each as

  . Requirements (Required Qualifications): - Associate's or Bachelor's degree in information technology, computer science, or a related technical field or equivalent - 2 years of related experience - 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 We'll list as

  . Qualifications (Preferred Qualifications): - 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 We'll list as

  . Benefits: The benefits paragraph: "At ScriptPro, we believe that our employees are our greatest asset. That’s why we are committed to fostering a workplace that prioritizes and enhances your personal health and well-being. Health: Medical, Dental, Vision, Short-Term Disability, Company Paid Life Insurance & Long-Term Disability, 24/7 on campus Gym, and Vitality Wellness Program that helps lower your premium costs Well-being: Paid Time Off (PTO), Parental Leave, nine (9) paid holidays, paid volunteer hours, Employee Assistance Program, company-sponsored events and team-building activities, 401(k) Retirement Plan with company match, financial investment services, employee discounts on products and services." We need to keep that as prose or maybe break into list? The instruction: Use

  • for any list of duties/requirements/benefits, and

    for prose. Benefits is a list; we could turn into

    • . But the benefits paragraph includes colon and commas. Safer to make a list: Health: Medical, Dental, Vision, Short-Term Disability, Company Paid Life Insurance & Long-Term Disability, 24/7 on campus Gym, and Vitality Wellness Program that helps lower your premium costs. Well-being: Paid Time Off (PTO), Parental Leave, nine (9) paid holidays, paid volunteer hours, Employee Assistance Program, company-sponsored events and team-building activities, 401(k) Retirement Plan with company match, financial investment services, employee discounts on products and services. We could split into two lists or one combined