Systems Administrator - Newport, RI
Serco · Newport, RI · 1 mo ago
Full-time
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 not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, legal, application instructions, etc. Must preserve all substantive info.
We need to parse the posting: It's a long description. We need to extract sections.
Let's identify content:
- Position Description & Qualifications: description of role, responsibilities.
- "As the System Administrator, you will be responsible for setting up and maintaining a system or specific components of a system (e.g. installing, configuring, and updating hardware and software; establishing and managing user accounts; overseeing or conducting backup and recovery tasks; implementing operational and technical security controls; and adhering to organizational security policies and procedures)."
- Then description of Serco support etc.
- Then "In This Role, You Will" list of many duties.
- Then "To Be Successful In This Role, You Will Have" list of qualifications.
- Then "Additional Desired Experience And Skills" list.
- Then "If you are interested..." that's application encouragement, maybe we drop as boilerplate? It's not EEO but it's encouraging to apply; but instructions say remove application instructions. This line is encouraging to apply; likely considered application instruction, drop.
- Then "Company Overview" - that's about Serco, maybe we can include as "About the role"? Actually "About the role" is about the job; company overview maybe not needed but could be considered "About the role"? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" for general description of role and maybe company overview. But we need to decide.
- Then benefits section: "Pay Transparency Our Total Rewards package includes competitive pay..." then details about benefits, salary range, etc. This includes Pay and Benefits info. We need to include Pay and Benefits sections only if posting actually states them. It does state salary range: "Salary range: The range for this position can be found at the top of this posting." That's not a specific number; it's a placeholder. The instruction says: 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. Here they say salary range can be found at top of posting (not provided). That's placeholder. So we should not create Pay section. Benefits: they list benefits: "Medical, dental, and vision insuranceRobust vacation and sick leave benefits, and flexible work arrangements where permitted by role or contract401(k) plan that includes employer matching fundsTuition reimbursement programLife insurance and disability coverageOptional coverages that can be purchased, including pet insurance, home and auto insurance, additional life and accident insurance, critical illness insurance, group legal, ID theft protectionBirth, adoption, parental leave benefitsEmployee Assistance Plan". That's substantive benefits. So we can include Benefits section.
- Schedule: not mentioned. So no Schedule.
- Skills: we have many skills listed in qualifications and desired experience. Could create Skills section.
- Requirements: maybe combine qualifications and requirements. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which to use. We have responsibilities (duties). We have qualifications (education, certifications, experience). We have skills (technical skills). We have benefits. We could also have About the role (overview). We should not duplicate content.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all duties, qualifications, desired experience, etc. We can structure as:
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, legal, application instructions, etc. Must preserve all substantive info.
We need to parse the posting: It's a long description. We need to extract sections.
Let's identify content:
- Position Description & Qualifications: description of role, responsibilities.
- "As the System Administrator, you will be responsible for setting up and maintaining a system or specific components of a system (e.g. installing, configuring, and updating hardware and software; establishing and managing user accounts; overseeing or conducting backup and recovery tasks; implementing operational and technical security controls; and adhering to organizational security policies and procedures)."
- Then description of Serco support etc.
- Then "In This Role, You Will" list of many duties.
- Then "To Be Successful In This Role, You Will Have" list of qualifications.
- Then "Additional Desired Experience And Skills" list.
- Then "If you are interested..." that's application encouragement, maybe we drop as boilerplate? It's not EEO but it's encouraging to apply; but instructions say remove application instructions. This line is encouraging to apply; likely considered application instruction, drop.
- Then "Company Overview" - that's about Serco, maybe we can include as "About the role"? Actually "About the role" is about the job; company overview maybe not needed but could be considered "About the role"? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" for general description of role and maybe company overview. But we need to decide.
- Then benefits section: "Pay Transparency Our Total Rewards package includes competitive pay..." then details about benefits, salary range, etc. This includes Pay and Benefits info. We need to include Pay and Benefits sections only if posting actually states them. It does state salary range: "Salary range: The range for this position can be found at the top of this posting." That's not a specific number; it's a placeholder. The instruction says: 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. Here they say salary range can be found at top of posting (not provided). That's placeholder. So we should not create Pay section. Benefits: they list benefits: "Medical, dental, and vision insuranceRobust vacation and sick leave benefits, and flexible work arrangements where permitted by role or contract401(k) plan that includes employer matching fundsTuition reimbursement programLife insurance and disability coverageOptional coverages that can be purchased, including pet insurance, home and auto insurance, additional life and accident insurance, critical illness insurance, group legal, ID theft protectionBirth, adoption, parental leave benefitsEmployee Assistance Plan". That's substantive benefits. So we can include Benefits section.
- Schedule: not mentioned. So no Schedule.
- Skills: we have many skills listed in qualifications and desired experience. Could create Skills section.
- Requirements: maybe combine qualifications and requirements. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which to use. We have responsibilities (duties). We have qualifications (education, certifications, experience). We have skills (technical skills). We have benefits. We could also have About the role (overview). We should not duplicate content.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all duties, qualifications, desired experience, etc. We can structure as:
About the role
... overview of role, mission, etc.
Responsibilities
- ... each duty
Qualifications
- ... required qualifications
Skills
- ... technical skills, desired experience
Benefits
- ... benefits
,
,
- . No extra tags.
We'll produce:
About the role
Seeking a Systems Administrator who is engaging in high profile and challenging projects supporting the U.S. Navy. Serco has a great opportunity with the Naval Undersea Warfare Center (NUWC) Division for Autonomous Underwater Vehicles and associated lab for our customer in the Newport, Rhode Island area. As the System Administrator, you will be responsible for setting up and maintaining a system or specific components of a system (e.g. installing, configuring, and updating hardware and software; establishing and managing user accounts; overseeing or conducting backup and recovery tasks; implementing operational and technical security controls; and adhering to organizational security policies and procedures). Serco supports NUWC by providing technical oversight for the implementation, integration, testing, operational support, training, integrated logistics engineering, and sustainment within the U.S Navy platforms for submarines, surface ships, aircraft, and facilities ashore. The mission and activities include overall research, development, and design oversight of Navy protected Autonomous Underwater Vehicles and Torpedo Electronics Lab.
Responsibilities
- Conduct functional and connectivity testing to ensure continuing operability.
- Develop and document systems administration standard operating procedures (SOP).
- Maintain baseline system security according to organizational policies.
- Manage accounts, network rights, and access to systems and equipment.
- Plan, execute and verify data redundancy and system recovery procedures.
- Install, update, and troubleshoot systems/servers.
- Evaluate and install patches and resolve software related problems.
- Perform system backups and recovery.
- Comply with organization systems administration standard operating procedure.
- Implement and enforce local network usage policies and procedures.
- Manage system/server resources including performance, capacity, availability, serviceability, and recoverability.
- Monitor and maintain system/server configuration.
- Perform repairs on faulty system/server hardware.
- Troubleshoot hardware/software interface and interoperability problems.
- Maintain data files and monitor system configuration to ensure data integrity.
- Provide critical preventive and corrective maintenance, information assurance, asset management, technical systems updates, service call resolution, and configuration management for C4I systems worldwide.
- Design group policies and access control lists to ensure compatibility with organization standards, business rules, and needs.
- Provide ongoing