Intermediate Systems Engineer - IT Infrastructure & Applications

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the job description. We must not repeat job title as heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. We need to preserve all substantive information. Let's extract sections: - About the role: The introductory paragraph about nSI being ESOP, mission, role description. Could be "About the role". We'll put that as prose. - Responsibilities: The list after "Responsibilities :" includes bullet-like sentences. We'll create

• for each specific responsibility. - Basic Qualifications: Could be under Requirements or Qualifications. The posting has "Basic Qualifications:" and "Preferred Qualifications:" We can combine into Requirements (basic) and Qualifications (preferred) or Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which headings to use based on content. We have Basic Qualifications (must-haves) and Preferred Qualifications (nice-to-haves). Could map Basic Qualifications to "Requirements" and Preferred Qualifications to "Qualifications" or "Skills". The list includes many items; we can split. Better: Use "Requirements" for basic qualifications (must have). Use "Qualifications" for preferred qualifications (nice to have). Or "Skills" for technical skills. But we have both. We'll produce:

  About the role

  ...

  Responsibilities

  ...

  Requirements

  ...
  (basic qualifications)

  Qualifications

  ...
  (preferred qualifications) We might also have Benefits section: there is a "Benefits Of Working At NSI" paragraph with list of benefits. So we can add

  Benefits

  ...
  Pay: The posting mentions "Final compensation for this position is determined by a variety of factors..." but no specific pay range. According to instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does not state a specific pay number or range, just says compensation determined by factors. That is not a concrete pay statement. Should we include Pay? Probably not, because it's not a specific pay figure. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states compensation determined by factors, but not actual pay. I'd interpret that as not enough to create a Pay section. So omit Pay. Schedule: Not mentioned. Omit. Now we need to strip boilerplate: EEO statement, equal opportunity, etc. Also remove "nou Systems, Inc. (nSI) is now officially a 100% ESOP company!" that's part of about role, keep. Remove "For our complete EEO/AA and Pay Transparency statement, please visit ..." Remove "U.S. citizenship is required for most positions." (but we already have citizenship requirement in qualifications; but that line is duplicate; we can keep the requirement but not the generic statement). We'll keep the citizenship requirement as part of qualifications. Also remove "nou (pronounced ‘new’) Systems: Since its founding in 2012, nou Systems has built a reputation..." That's about company; we can keep as part of About the role? It's after the job description; but it's substantive about company. Could include in About the role. We'll incorporate. Now let's craft content. About the role paragraph: Combine first paragraph and company description. Original: "nou Systems, Inc. (nSI) is now officially a 100% ESOP company! We value teamwork and collaboration, and this transition allows us to take that commitment to a new level. nSI empowers our customers by supplying products, services, and expertise with powerful, data driven insights that transform defense systems and improve capabilities. We are pleased to announce the opening for a Intermediate Systems Engineer, focused on IT Infrastructure & Applications who will join our Teams Next - Systems Engineering & Analyses (TN SEA) team in Huntsville, AL or Colorado Springs, CO and become part of our rapidly growing technology company operating in missile defense, cybersecurity, test range modernization, biotechnology, and space control marketspaces. You will be part of the IT Strategy & Implementation Team within the Missile Defense Agency's Transformation Task Force (MDA/TF) office." Then later: "nou (pronounced ‘new’) Systems: Since its founding in 2012, nou Systems has built a reputation for excellence in innovative engineering, prototype development, and technical and professional services in multiple markets, including missile defense, cybersecurity, test range modernization, and space control. Our diverse and highly skilled team delivers state-of-the-art products from concepts and prototypes to fully developed and integrated solutions. We offer significant advancement and personal career development opportunities within our dynamic high-tech company. Our culture is firmly established in treating our employees like family." We'll combine into a cohesive paragraph. Now Responsibilities: The bullet list after "Specific responsibilities include:" includes many items each ending with a period. We'll extract each as
• . List: - Elicit, develop, and manage requirements for enterprise IT modernization initiatives, working directly with government stakeholders, mission owners, and application owners to translate operational needs into engineering requirements. - Baseline the current-state environment through application portfolio analysis, infrastructure inventory, and dependency mapping across facilities, systems, and interfaces. - Develop target-state architectures and supporting documentation, including architecture diagrams, interface definitions, data flows, and transition roadmaps. - Conduct Analyses of Alternatives (AoAs) and trade studies to support disposition decisions for legacy applications and infrastructure, including rehost, replatform, refactor, and retire recommendations. - Support planning and sequencing of data center consolidation and workload migration activities, including migration wave definition, dependency and cutover risk analysis, and coordination of technical dependencies against program cost and schedule. - Apply systems engineering "V" processes across the acquisition lifecycle, maintaining requirements traceability from stakeholder need through architecture, design, and transition. - Author and review technical documentation, white papers, and decision briefings that communicate architectural direction to both technical and non-technical audiences, including senior government leadership. - Coordinate across cybersecurity, infrastructure, applications, and program management stakeholders to ensure modernization efforts are technically sound, secure, and executable. Also earlier responsibilities paragraph: "You'll be part of a dynamic team of government civilians and defense contractors supporting MDA's Office of the Chief Information Officer within MDA/TF. The work requires a breadth of skills and the ability to coordinate across multiple organizations. The position requires: an understanding of IT infrastructure and applications, of systems engineering (particularly the left side of the V), of data center consolidation, of legacy application modernization, and of workload migration, along with the program management perspective needed to connect those disciplines to real cost, schedule, and risk. The emphasis of this role is on the front end of the engineering lifecycle. You will work directly with stakeholders to elicit and develop requirements, baseline the current-state environment, define target-state architectures, and evaluate alternatives before solutions are built." We could incorporate those as part of responsibilities as well, but they are somewhat overlapping with specific list. To avoid duplication, we could keep the specific list and maybe include the earlier paragraph as prose before list. But instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that earlier paragraph too. We could include it as part of responsibilities section as prose before the
  . That's fine. Thus Responsibilities section:

  You'll be part of a dynamic team ... evaluate alternatives before solutions are built.

  then
  with the eight items. Now Requirements (basic qualifications): list: - Bachelor's in a STEM field - 7+ years working on missile defense-related or other complex, large DoD program/project. - Works independently, as a team member, or leading teams/tasks, applying engineering rigor to solve engineering/scientific problems. - Must possess an active Secret clearance and be eligible for TS/SCI. - Must be a U.S. citizen to be eligible for this position. Lacking any one of these disqualifies you from this position. We'll put each as
  • . Now Qualifications (preferred qualifications): list all items under "Preferred Qualifications:": - Information technology background paired with a formal systems engineering background; ability to operate credibly with both IT infrastructure teams and systems engineering organizations - Demonstrated strength in front-end ("left side of the V") systems engineering: requirements elicitation and development, concept of operations, functional decomposition, architecture definition, interface definition, and requirements traceability - Program management perspective, with the ability to think in terms of schedule, dependencies, cost, and risk; prior experience serving in a program or project management capacity is highly valued - Experience supporting data center consolidation, closure, or relocation efforts - Experience with legacy application modernization and application portfolio rationalization - Experience planning or executing workload migrations from legacy on-premises environments to modern hosting environments, including cloud (AWS GovCloud, Azure Government) and virtualized on-premises infrastructure (VMware vSphere) - Familiarity with the Risk Management Framework (RMF), ATO package development, NIST 800-series controls, and DISA STIGs - Familiarity with Zero Trust architecture principles and Identity, Credential, and Access Management (ICAM) concepts - Working knowledge of DoD Impact Level 5 and 6 (IL5/IL6) hosting environments, virtualization, containerization, and Infrastructure as Code concepts, sufficient to evaluate and direct vendor-proposed solutions - Project Management Professional (PMP) certification and/or DoD 8140/8570 baseline certification (e.g., Security+, CASP+, CISSP) - Prior experience supporting MDA or another large DoD agency in an engineering or advisory capacity - Strong oral and written communication skills, including experience briefing senior government stakeholders We'll put each as
  • . Now Benefits: list from "Benefits Of Working At NSI nou Systems, Inc. offers a comprehensive, total rewards package that includes competitive compensation and diverse benefits that reflect our company culture of service, excellence, and a supportive work environment. Benefits may vary based on status but the majority of our positions include the following:" then list: - Competitive Wages* - Medical, Rx, Dental & Vision Insurance - Medical plan with Health Savings Account eligibility - Company-funded Life, Short-Term & Long-Term Disability Insurance - Personal Time Off, Vacation, and Paid Holidays - 401(k) Retirement Plan - Employee Stock Ownership Plan (ESOP) - Flexible Spending Accounts - Norton LifeLock - Tuition Reimbursement - Personal Development, Technical Learning Opportunities, & Lunch-n-Learns - Corporate Sponsored Events & Community Outreach We'll put each as
  • . Note the asterisk after Competitive Wages* maybe footnote; keep as is. We should not include the line "Final compensation for this position is determined by a variety of factors, such as a candidate’s relevant work experience, skills, certifications, and geographic location." That's about pay but not specific; we decided not to create Pay section. However we could include that sentence in About the role or Benefits? It's about compensation; maybe we could include in Benefits as a note? But instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation determined by factors, but not a specific pay range or schedule. I'd say we can omit Pay section entirely, but we could include that sentence in Benefits as a note? It's about compensation, not benefits. Safer to omit. Now we need to output only HTML fragment, no /, no markdown. Let's construct. We'll need to escape any special characters? Not needed. Let's write:

    About the role