Application Administrator

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 if posting has real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Also we must not repeat job title as heading (already shown). No Job ID/requisition numbers as headings. We need to parse the posting. Let's extract content: Company description: SS&C is a leading provider... (maybe not needed? It's part of job description but could be considered boilerplate? It's about company, not role. Might be considered generic but it's substantive? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company overview maybe not boilerplate but could be considered part of job description. However we need to preserve ALL substantive information. The company description is substantive about SS&C. Should we keep? Probably yes as part of description. But we need to format into sections. The sections we can have: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. From posting: - Job Title: Application Administrator - Locations: 100% Remote – East Coast Only - Hours: 4:00pm – 12:00am EST - About The Role: paragraph: "This is an exciting opportunity for a skilled individual to work in a fast-paced environment with leading-edge technology and be part of a dynamic team supporting SS&C’s SaaS offerings. The Application Administrator will use his/her creativity and technical expertise to coordinate and execute all activities related to Production environments, including scripting automation, monitoring, response, and troubleshooting." - Why Join SS&C: paragraph about SS&C combines proprietary technology... (maybe could be part of About the role or separate? Not a standard heading; we could treat as About the role? But we have About The Role heading already. Could incorporate that paragraph into About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have those headings only if content exists. We have About The Role content. We could also have Responsibilities (list of duties). We have many duty bullet-like sentences under "Required Experience" and later list. Let's extract duties/responsibilities: Under "Required Experience" (though it's mislabelled) we have: - Note the required hours of this role are Monday through Friday from 4 PM to 12 AM Eastern Time. Occasional weekend coverage for maintenance activities (typically during the morning) is required as well - Provide first level technical support for various SS&C hosted applications to ensure uptime and service level objectives are met - Ensure SS&C’s operations, such as application job scheduling and server operations work properly and meet business and client expectations - In the event of an incident or failure, participating in repair and restoration of processing and systems availability in coordination with other departments to achieve a normal operational status - Lead or assist root cause analysis efforts and work with others to prevent future recurrences - Excellent understanding and working knowledge of Windows and/or Linux operating systems - Working knowledge of Encryption tools such as PGP, GPG, and GNU SFTP server configuration and troubleshooting - Knowledge of scripting technologies and/or willingness to learn - Monitor application availability and performance - Work with peers and customers to troubleshoot infrastructure, application, database, and network related issues - Coordinate/communicate with various teams on tasks and escalations using Agile methodologies - Participate in 24x7 escalation/rotation support as part of the larger team - Support new virtual and cloud solutions that improve SS&C service offerings - Ensure change management procedures are followed in a timely manner - Participates in the creation and maintenance of relevant documentation - Participates in Disaster Recovery validation scenarios Then after that: "We’d like to meet you if you:" list of soft skills. Then "What Sets You Apart": list of qualifications/preferred. Then benefits paragraph near end: "SS&C Technologies offers a comprehensive total rewards package designed to support your wellbeing, growth, and future. Our benefits include medical, dental, and vision coverage; a 401(k) plan with company match; paid time off, holidays, and parental leave; and professional development reimbursement opportunity." Also earlier: "Hours: 4:00pm – 12:00am EST" and location. We need to decide sections: - About the role: combine the About The Role paragraph and maybe Why Join SS&C? Could be separate but we only have headings list; we could put Why Join SS&C under About the role as additional prose. - Responsibilities: list of duties (the bullet list under Required Experience). Could be

• . - Requirements: maybe the hard requirements: hours, remote east coast only, etc. Could be under Requirements. - Qualifications: education/degree, experience, etc. Could be under Qualifications. - Skills: technical skills list (Windows/Linux, encryption, scripting, etc.) Could be under Skills. - Benefits: benefits paragraph. - Pay: not specified; we should not create Pay section if not stated. The posting does not mention pay/salary. So omit. - Schedule: we have hours info; could be under Schedule. But we also have hours in Requirements maybe. The instruction: include a section ONLY when posting has real, specific content for it. Hours are specific: Monday through Friday 4 PM to 12 AM EST, occasional weekend coverage. So we could have Schedule section with that info. However we also have location remote east coast only. That could be under Requirements or maybe under About the role? But we could put location under Requirements or maybe a separate section? Not in list. Could fold location into Requirements as a short p. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment. Let's structure:

  About the role

  ... (combine About The Role paragraph and Why Join SS&C paragraph?)

  Responsibilities

  • Provide first level technical support for various SS&C hosted applications to ensure uptime and service level objectives are met
  • Ensure SS&C’s operations, such as application job scheduling and server operations work properly and meet business and client expectations
  • In the event of an incident or failure, participating in repair and restoration of processing and systems availability in coordination with other departments to achieve a normal operational status
  • Lead or assist root cause analysis efforts and work with others to prevent future recurrences
  • Excellent understanding and working knowledge of Windows and/or Linux operating systems
  • Working knowledge of Encryption tools such as PGP, GPG, and GNU SFTP server configuration and troubleshooting
  • Knowledge of scripting technologies and/or willingness to learn
  • Monitor application availability and performance
  • Work with peers and customers to troubleshoot infrastructure, application, database, and network related issues
  • Coordinate/communicate with various teams on tasks and escalations using Agile methodologies
  • Participate in 24x7 escalation/rotation support as part of the larger team
  • Support new virtual and cloud solutions that improve SS&C service offerings
  • Ensure change management procedures are followed in a timely manner
  • Participates in the creation and maintenance of relevant documentation
  • Participates in Disaster Recovery validation scenarios
  But note some items like "Excellent understanding..." are more skills/requirements; but they appear in the responsibilities list. Might be okay.

  Requirements

  Location: 100% Remote – East Coast Only

  Hours: Monday through Friday, 4:00 PM – 12:00 AM EST; occasional weekend coverage for maintenance activities (typically during the morning) required.

  Qualifications

  • BS or MS Degree in Computer Science or similar degree
  • Some professional experience or a prior internship
  • Team player - Recognizes the bigger picture and understands the value of teamwork
  • Excellent communication skills, written and verbal
  • Any knowledge of the VAX VMS Operating Systems is a major plus
  • Any knowledge of Kubernetes and/or Container technologies is a major plus
  • Experience supporting complex internal and client facing environments is a major plus
  • Experience with troubleshooting Microsoft products and protocols is a plus
  • Experience working with enterprise applications is a plus
  But we also have "We’d like to meet you if you:" list of soft skills: self-starter, strong problem-solving skills, highly dependable, consistently follow through, maintain positive attitude, professional, excellent interpersonal and written communication skills, want to work with cloud computing, passionate about technology, desire and ability to learn new things fast, ability to think on your feet, want to be part of an efficient and effective team. These could be under Skills or Qualifications. Since we already have Qualifications, maybe we put those under Skills. Let's decide: - Skills: technical and soft skills. We have technical skills list from responsibilities (Windows/Linux, encryption, scripting, etc.) but we could move them to Skills. Better: Separate: Responsibilities: core duties (support, monitoring, incident response, RCA, change management, documentation, DR, etc.) Skills: technical skills (Windows/Linux, encryption, scripting, monitoring, troubleshooting, Agile, cloud/virtual, etc.) plus soft skills (self-starter, problem-solving, dependable, communication, etc.) Qualifications: education, experience, team player, communication, VAX VMS plus, Kubernetes plus, etc. But we have overlapping. Let's try to produce a clean structure:

  About the role

  This is an exciting opportunity for a skilled individual to work in a fast-paced environment with leading‑edge technology and be part of a dynamic team supporting SS&C’s SaaS offerings. The Application Administrator will use his/her creativity and technical expertise to coordinate and execute all activities related to Production environments, including scripting automation, monitoring, response, and troubleshooting. SS&C combines proprietary technology with deep industry expertise to support complex financial and health care operations. Our teams design, implement, and operate solutions that help clients manage data, automate processes, and scale their businesses with confidence. You will work with industry experts, modern platforms, and evolving technologies, gaining exposure to real‑world operational challenges and large‑scale enterprise environments.

  Responsibilities

  • Provide first‑level technical support for various SS&C hosted applications to ensure uptime and service level objectives are met
  • Ensure SS&C’s operations, such as application job scheduling and server operations, work properly and meet business and client expectations
  • Participate in incident response: repair and restoration of processing and systems availability in coordination with other departments to restore normal operational status
  • Lead or assist root‑cause analysis efforts and work with others to prevent future recurrences
  • Monitor application availability and performance
  • Work with peers and customers to troubleshoot infrastructure, application, database, and network‑related issues
  • Coordinate and communicate with various teams on tasks and escalations using Agile methodologies
  • Participate in 24×7 escalation/rotation support as part of the larger team
  • Support new virtual and cloud solutions that improve SS&C service offerings
  • Ensure change‑management procedures are followed in a timely manner
  • Participate