Advanced Systems Administration Specialist

for prose. We need to preserve all substantive info, remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Company Overview" maybe? It's not a required heading but could be a section if it has content. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can include sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to map content. The posting includes: - Basic Qualifications Education Requirements: Bachelor’s degree in Computer Science, a related field or equivalent experience is required plus a minimum of 5 years of relevant experience; or Master's degree plus 3 years of relevant experience. - Clearance Requirements: Ability to obtain a Department of Defense Secret security clearance is required at time of hire. Applicants selected will be subject to a U.S. Government security investigation and must meet eligibility requirements for access to classified information. Due to the nature of work performed within our facilities, U.S. citizenship is required. - Responsibilities For This Position: ... (some narrative) - Responsibilities for this Position: (list of duties) - What you bring to our team: (list of qualifications/skills) - What sets you apart: (list of additional skills) - What else you should know: (clearance again, certification requirements) - NOTE: This position is ON SITE at our Pittsfield, MA Location. - Target salary range: USD $111,881.00/Yr. - USD $121,059.00/Yr. - This job posting will remain open until the position is filled. (maybe we drop as application instruction? It's not instruction but could be considered boilerplate; but it's about posting duration; maybe we keep? The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, application instructions. This line is not exactly application instruction but could be considered boilerplate; but it's not EEO. Might keep? Safer to drop? It's not substantive about role. I'd drop it. - Company Overview: (some prose) Could be considered "About the company" but not required heading; we could include as a section maybe "About the company" but not in list of allowed headings? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Company Overview not in list; but we could still include if we think it's substantive? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. So we could add other headings if appropriate. But better to stick to those. We need to decide which sections to include. We have: - Responsibilities: we have a paragraph describing role and then a list of duties. So we can have

Responsibilities

for the introductory paragraph, then

• for each duty. - Requirements / Qualifications: we have Basic Qualifications Education Requirements and Clearance Requirements, plus "What you bring to our team" (skills/qualifications) and "What sets you apart" (additional skills). Also "What else you should know" includes clearance again and certification requirements. We could combine into Requirements (education, experience, clearance, citizenship) and Qualifications (skills). Or we could have Requirements and Qualifications separate. Given the instruction: prefer a few substantive sections over many thin ones. So maybe we have: - Responsibilities - Requirements (education, experience, clearance, citizenship) - Qualifications (skills, knowledge, certifications) - Pay (salary range) - Location (maybe as part of Requirements? Could be a separate section like "Location" but not in list; we could embed in a paragraph under Requirements or as a note.) - Benefits: not mentioned explicitly; we have company overview mentions benefits but not specific. So we should not create Benefits section unless posting actually states them. It says "We offer highly competitive benefits" but not specific. That's vague; maybe we should not create Benefits section because it's not specific. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Pay (salary range). It does not state specific benefits. So we skip Benefits. - Schedule: not stated. So skip. Thus sections: Responsibilities, Requirements, Qualifications, Pay, Location (maybe as part of Requirements or separate). Could also include "About the role" as a summary paragraph before responsibilities? The posting has a paragraph: "At General Dynamics Mission Systems, we create the technologies..." That's more about company/mission. Could be considered "About the role". But we already have Responsibilities. Might combine. Better to have:

  Responsibilities

  Intro paragraph about role and mission.

  • ...

  Requirements

  Education and experience: Bachelor’s degree in Computer Science, a related field or equivalent experience is required plus a minimum of 5 years of relevant experience; or Master's degree plus 3 years of relevant experience.

  Clearance: Ability to obtain a Department of Defense Secret security clearance is required at time of hire. Applicants selected will be subject to a U.S. Government security investigation and must meet eligibility requirements for access to classified information. U.S. citizenship is required.

  Location: This position is ON SITE at our Pittsfield, MA Location.

  Qualifications

  What you bring to our team:

  • ...

  What sets you apart:

  • ...

  What else you should know:

  • Applicant must meet DoD 8570.1 certification requirements for IAT-II or higher. You must complete CompTIA Security+ certification minimum within 6 months of hire.

  Pay

  Target salary range: USD $111,881.00/Yr. - USD $121,059.00/Yr. This estimate represents the typical salary range for this position based on experience and other factors (geographic location, etc.). Actual pay may vary.

  We need to ensure we don't duplicate content. The clearance appears twice; we can mention once. We need to preserve all substantive info: include the list of duties from "Responsibilities for this Position:" and the list from "What you bring to our team:" and "What sets you apart:" and "What else you should know:" (certification). Also include the introductory paragraph about role and mission. We must not include boilerplate like "Equal Opportunity Employer / Individuals with Disabilities / Protected Veterans". Remove. Also remove "Company Overview" paragraph? It's substantive but not required heading; we could include as a paragraph under maybe "About the company" but not in allowed headings. Could we include as a

  without heading? The instruction: Output ONLY the HTML fragment. It didn't forbid stray paragraphs without heading. But they said use

  for section headings (e.g...). It didn't say every paragraph must be under a heading. However they said "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can have paragraphs not under headings? Might be okay but safer to put them under a heading like "About the role" or "Company Overview". Since "About the role" is in the examples, we could use that for the introductory mission statement and company overview. Thus we could have:

  About the role

  At General Dynamics Mission Systems, we create the technologies, products and services that help our nation’s heroes keep our nation safe. The work we do is so advanced, we are continuously moving the boundaries of what’s possible. Here you’ll work with the best, and your talent will be front and center on projects that impact the world. Are you up to the challenge? We apply advanced technologies such as Artificial Intelligence, Blockchain, AR/VR, Cloud Native and Quantum Physics to solve our customers’ missions in cyber, RF, undersea, interstellar and everything in between.

  Then Responsibilities section as above. But note that the responsibilities section also includes a paragraph: "Are you ready for an exciting career as a Systems Admin supporting our Nation's prestigious cyber initiatives? ..." That's part of responsibilities. We could include that as part of responsibilities intro. Thus we need to avoid duplication. Let's extract the exact text blocks: From posting: "Basic Qualifications Education Requirements: Bachelor’s degree in Computer Science, a related field or equivalent experience is required plus a minimum of 5 years of relevant experience; or Master's degree plus 3 years of relevant experience. Clearance Requirements: Ability to obtain a Department of Defense Secret security clearance is required at time of hire. Applicants selected will be subject to a U.S. Government security investigation and must meet eligibility requirements for access to classified information. Due to the nature of work performed within our facilities, U.S. citizenship is required." "Responsibilities For This Position At General Dynamics Mission Systems, we create the technologies, products and services that help our nation’s heroes keep our nation safe. The work we do is so advanced, we are continuously moving the boundaries of what’s possible. Here you’ll work with the best, and your talent will be front and center on projects that impact the world. Are you up to the challenge? We apply advanced technologies such as Artificial Intelligence, Blockchain, AR/VR, Cloud Native and Quantum Physics to solve our customers’ missions in cyber, RF, undersea, interstellar and everything in between. Responsibilities for this Position: Are you ready for an exciting career as a Systems Admin supporting our Nation's prestigious cyber initiatives? Do you want to challenge your administration skills and knowledge by supporting multiple Communities of Interests? If so, General Dynamics Mission Systems (GDMS) has an exciting career opportunity for you as an Advanced Systems Admin Specialist for the Information Technology - Limited Access Area (LAA) Team as part of Engineering Support Services. In your role as an Advanced Systems Admin Specialist, you will be responsible for the day-to-day administration and maintenance of multiple secure infrastructures, both physical and virtual, across GDMS. You will design, develop, build, and test new system infrastructure solutions as part of a collaborative team. You will serve as a front-line interface to users by addressing technical issues, conducting systems analysis, and ensuring systems remain current with evolving technologies. You will perform vulnerability scanning and system remediation. You will also perform OS and vendor software patching on servers and network devices, and update AV to maintain security and compliance. General system administrator duties such as monitoring system performance, managing backups, ensuring system availability, and implementing security measures are also integral to this position." "What you bring to our team: A Bachelor’s degree in systems engineering, a related specialized area or field and a minimum of 5 years of relevant experience or a master's degree plus a minimum of 3 years of relevant experience. You may also bring equivalent relevant experience and certifications. An advanced knowledge of RedHat Linux, Windows Server, VMware vSphere, Hyper-V, and/or application environments and related technologies. An ability to architect, deploy and continuously maintain secure, reliable, and flexible best practice infrastructures and systems. Experience with implementing Linux/Windows security controls to maintain system compliance. (STIGs, CIS Benchmarks) Subject Matter Expert in researching and troubleshooting complex technical issues. Familiarity with compliance controls: STIGs/CIS Benchmarks, NIST SP 800-171/800-53, Cybersecurity Maturity Model Certification (CMMC), System Security Plans. Experience working within