Systems Engineering Architect

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. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like cookie/navigation/legal/EEO etc. The posting includes description, job duties, qualifications, etc. Also includes target salary range. Also schedule: Full-Time, Shift Day, Travel Yes - 10% of the time, Potential for Remote Work ORA_HYBRID, hybrid/remote position with periodic onsite visits, must be local to one of two sites. So we can include Schedule section with details: Full-Time, Day shift, up to 10% travel, hybrid/remote, periodic onsite visits at San Diego or Virginia Beach, must be local to one of those sites. Benefits: Not explicitly listed. No benefits mentioned. So we should not create Benefits section. Pay: target salary range $160,001 - $200,000. So include Pay section. Skills: Could extract from qualifications: experience with DevOps, Agile, PowerShell, XML, scripting, LAN design, US Navy networking, Cloud (AWS, Azure, Flankspeed Edge), SCRUM, Microsoft stack .NET/C#, Linux programming, IAT Level II Compliant (Security+), OS Cert, etc. Also leadership experience, pattern-based architecture, governance, security, Atlassian suite JIRA, etc. We'll put those in Skills. Qualifications: Education and experience requirements: Bachelors +14 years, Masters +12, PhD/JD +9. Supported DoD C4ISR systems... etc. Also clearance: Must be US Citizen, Active DoD Secret Clearance or higher to start. Also certification: IAT Level II Compliant (Security +) and OS Cert, need to obtain within 6 months if not hold. Responsibilities: Job Duties list. About the role: Could be from description paragraph: SAIC is seeking a Systems Architect who will lead various efforts... etc. We'll put that as About the role. We must not include headings with filler. Ensure we only output HTML fragment. Structure: Use

for each section heading. Then content: either

for prose,

• for lists. We need to preserve all substantive info; not invent or summarize away detail. So we need to include all details from posting. Let's extract details: About the role (description): - SAIC is seeking a Systems Architect who will lead various efforts and initiatives involving our tactical networks. - Person will design, develop, and sustain DOD system networks. - Person will work closely with development and sustainment engineering team to purpose and engineer solutions to improve, modernize, and sustain afloat networks using an agile methodology in a DevOps environment. - Must be willing and interested in learning new toolsets, templates and workflows as business needs evolve. - This role supports the TACNET Sustainment Team; TACNET CB-ISEA supports the sustainment and modernization of tactical networks to include Automated Digital Network System (ADNS), Consolidated Afloat Network and Enterprise Services (CANES), Combined Enterprise Regional Information Exchange System (CENTRIXS), Integration Shipboard Networking System (ISNS), Sensitive Compartmented Information (SCI) Networks, Flank speed Wireless. - Support will encompass a range of capabilities, from system installations, configuration management enforcement, system sustainment and upgrades, distance support, and emergent onsite Casualty Report (CASREP) support as needed for the warfighters. - The position requires up to 10% of OCONUS/CONUS travel in addition to occasional off-hours support. - Also, this role allows for some remote work from home opportunities. - This is a hybrid/remote position with periodic onsite visits at our SAIC office in San Diego, CA and/or Virginia Beach, VA. - MUST BE LOCAL TO ONE OF THE TWO SITES. Job Duties (Responsibilities): - Provide System life cycle software engineering support for our NAVWAR and NIWC customers. - Focus primarily on software components loaded on supported tactical networks to sustain currently fielded TACNET systems. - Includes analysis and modification to replace commercial off the shelf (COTS) components that are end of support (EOS) modifications to support new interfaces to other systems, and modifications to existing systems driven by customer requirements. - Analyze failure data, trouble reports, and other U.S. Navy Fleet communications to identify current system deficiencies. - Propose Solutions, conduct peer reviews, and work with production engineers to implement solutions. - Create and update engineering documentation and manage solutions through formal configuration management process. - Attend and participate in technical meetings, report on technical progress, prepare briefs and provide presentations. - Participation in Integrated Product Team (IPT), Technical Working Group) and engineering / design review meetings. - Engineering solutions will primarily be for Redhat/Linux based operating systems. - Provide root cause analysis and be comfortable recommending permanent configuration changes when necessary. - Develop, integrate, test, debug, and tune complex Software solutions designed to satisfy customer requirements. - Experience in developing and applying pattern-based architecture, governance and security to system changes and deployments. - Experience utilizing the Atlassian suite of tools to include JIRA supporting agile and sprint-based operations. - Leadership experience in the development and deployment of source code across multiple classification levels and environments. - Experience in creating or expressing low level work product activities and estimating durations with intent to aide creation of scope documents and schedules. - Work in cooperation with external partners, including consultants, agencies, and vendors, to troubleshoot intra-system issues, and to assist with system integration design solutions. - Strong development and support skills with experience in object-oriented programming as applicable to web-based programming languages. Qualifications (Education and Experience): - Bachelors and fourteen (14) years or more experience; Masters and twelve (12) years or more experience; PhD or JD and nine (9) years or more experience. - Supported DoD C4ISR systems in an enterprise level IT environment (ISNS, CANES, ADNS, SCI Network, CENTRIX, ORT, FSW). - 4 or more years’ experience in a DevOps based environment and is familiar with Agile practices. - 2 yrs. of experience with scripting program languages and automation using PowerShell scripting and XML development. - 2 years’ experience in the design, analysis and support of local area networks. - Knowledge of US Navy Ship and shore networking systems is a plus. - Experience in Cloud Computing Environments such as AWS, Microsoft Azure, and/or Flankspeed Edge. - Experience in SCRUM methodologies is a plus. - Experience in Microsoft stack - .NET4.0/C#, PowerShell. - Experience in Linux programming languages. - Certification: Current IAT Level II Compliant (Security +) and OS Cert. Would need to obtain within 6 months if does candidate does not currently hold both certifications. - Clearance: Must be a U.S. Citizen. Must have an Active DoD Secret Clearance or higher to start. Pay: Target salary range $160,001 - $200,000. Schedule: Full-Time, Shift Day, Travel Yes - 10% of the time, Potential for Remote Work ORA_HYBRID, hybrid/remote position with periodic onsite visits at SAIC office in San Diego, CA and/or Virginia Beach, VA, MUST BE LOCAL TO ONE OF THE TWO SITES. We might also include "Shift Day" as part of schedule. Now produce HTML. We need sections: About the role, Responsibilities, Qualifications, Skills, Pay, Schedule. Possibly also Requirements? The qualifications include requirements; but we could combine Requirements and Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). They said prefer a few substantive sections over many thin ones. We could combine Requirements and Qualifications into one section called Qualifications (or Requirements). But we have both Requirements and Qualifications headings as examples; we can choose to include only Qualifications if it covers both. However the posting has a "Qualifications REQUIREMENTS" heading; we could treat that as Qualifications. We'll not duplicate. Skills: we can extract from qualifications and duties: pattern-based architecture, governance, security, Atlassian JIRA, leadership experience, low-level work product estimation, external partner cooperation, OOP, web-based languages, DevOps, Agile, PowerShell, XML, LAN design, US Navy networking, Cloud (AWS, Azure, Flankspeed Edge), SCRUM, Microsoft stack .NET/C#, Linux programming, IAT Level II (Security+), OS Cert, etc. We'll list them. Now produce HTML. Make sure not to include any markdown fences. Just raw HTML. Let's craft:

  About the role

  SAIC is seeking a Systems Architect who will lead various efforts and initiatives involving our tactical networks. The person will design, develop, and sustain DOD system networks, working closely with development and sustainment engineering teams to purpose and engineer solutions to improve, modernize, and sustain afloat networks using an agile methodology in a DevOps environment. Must be willing and interested in learning new toolsets, templates and workflows as business needs evolve. This role supports the TACNET Sustainment Team; TACNET CB-ISEA supports the sustainment and modernization of tactical networks to include Automated Digital Network System (ADNS), Consolidated Afloat Network and Enterprise Services (CANES), Combined Enterprise Regional Information Exchange System (CENTRIXS), Integration Shipboard Networking System (ISNS), Sensitive Compartmented Information (SCI) Networks, and Flank speed Wireless. Support encompasses system installations, configuration management enforcement, system sustainment and upgrades, distance support, and emergent onsite Casualty Report (CASREP) support as needed for warfighters. The position requires up to 10% OCONUS/CONUS travel plus occasional off-hours support, allows some remote work from home, and is a hybrid/remote role with periodic onsite visits at SAIC offices in San Diego, CA and/or Virginia Beach, VA. Candidates must be local to one of these two sites.

  Responsibilities

  • Provide system life cycle software engineering support for NAVWAR and NIWC customers.
  • Focus primarily on software components loaded on supported tactical networks to sustain currently fielded TACNET systems.
  • Analyze and modify to replace end‑of‑support commercial off‑the‑shelf (COTS) components, support new interfaces to other systems, and modify existing systems per customer requirements.
  • Analyze failure data, trouble reports, and U.S. Navy Fleet communications to identify system deficiencies.
  • Propose solutions, conduct peer reviews, and work with production engineers to implement solutions.
  • Create and update engineering documentation; manage solutions through formal configuration management process.
  • Attend and participate in technical meetings; report on technical progress, prepare briefs and provide presentations.
  • Participate in Integrated Product Team (IPT), Technical Working Group, and engineering/design review meetings.
  • Engineering solutions primarily for Red Hat/Linux based operating systems.
  • Provide root cause analysis and be comfortable recommending permanent configuration changes when necessary.
  • Develop, integrate, test, debug, and tune complex software solutions to satisfy customer requirements.
  • Develop and apply pattern‑based architecture, governance, and security to system changes and deployments.
  • Utilize the Atlassian suite of tools (including JIRA) for agile and sprint‑based operations.
  • Provide leadership in developing and deploying source code across multiple classification levels and environments.
  • Create or express low‑level work product activities and estimate durations to aid scope documents and schedules.
  • Work with external partners (consultants, agencies