Senior Systems Engineer

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have a Requirements section for desired requirements. But we already have Qualifications; we could also have Requirements for desired. Let's decide: We'll have Requirements for the desired requirements (since they are not mandatory). Qualifications for mandatory qualifications. - Education Requirements: "Education Requirements Master’s degree in Mathematics, Engineering, Computer Science or other relevant discipline." This could be part of Qualifications or separate Education. Since we have Qualifications, we could include education there. But we could also make a separate Education section? Not in list of allowed headings; but we could fold into Qualifications. Probably include in Qualifications. - Clearance Requirements: "Clearance Requirements Possess an active TS/SCI security clearance with SCI and SAR eligibility". This is also a qualification; include in Qualifications. - Pay: "The pay range for this position in Massachusetts is $130,000/year to $180,000/year; however, base pay offered may vary depending on established government contract rates, job-related knowledge, skills, and experience, and other factors. MTSI also offers a full range of medical, financial, and other benefits dependent on the position offered. This information is provided to align with best practices for pay equity and transparency within the state of Massachusetts under the Massachusetts Equal Pay Act. Base pay information is based on market location." Thus we have Pay and Benefits. Benefits: "MTSI also offers a full range of medical, financial, and other benefits dependent on the position offered." That's vague but still a benefit statement. We should include Benefits section only if posting actually states them. It does state "full range of medical, financial, and other benefits". That's specific enough? It's not detailed but it's a statement. We'll include Benefits. - Schedule: Not explicitly stated besides travel up to 25% etc. No schedule like full-time, shift etc. So we should not create Schedule section. - Skills: Could we extract skills from qualifications? Might be redundant. But we could have a Skills section for technical skills like "Tactical Datalinks", "IP Communication networking", etc. However we already have many in Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So we might combine skills into Qualifications or Requirements. Since we already have Qualifications and Requirements, we may not need separate Skills. Thus sections: About the role, Responsibilities, Requirements (desired), Qualifications (mandatory incl education, clearance), Benefits, Pay. Check if any content for Benefits beyond that line: "MTSI also offers a full range of medical, financial, and other benefits dependent on the position offered." That's it. We'll include. Now produce HTML:

About the role

Senior Systems Engineer with MTSI you will provide technical and programmatic advice and support services on a suite of advanced weapon systems, sensors, and computer processing related technologies and programs. This position will be located Hanscom Air Force Base. Anticipate up to 25% travel, with surge periods of greater travel required, primarily in CONUS. The ideal candidate is willing to work in a fast-paced environment with high performance and results expectations, is well-rounded, tenacious, willing to learn, adapt, and grow.

Responsibilities

• Providing critical technical advisory support to integration planning and implementation for the Department of the Air Force (DAF) PEO C3BM Battle Network. This position requires active collaboration across multiple organizations and lines of effort.
• Supporting acquisition interoperability strategies for complex multi–system-of-systems (SoS) IT architectures, developing and maintaining SoS matrices, and conducting integrated assessments to evaluate performance, interoperability, and mission effectiveness.
• Executing mission engineering processes, drafting SoS requirements, and developing the Department of the Air Force (DAF) Battle Network architecture.
• Consulting with program representatives to refine functional requirements, assisting government officials with acquisition document reviews and approvals, and monitoring program execution and integration activities—such as schedules, risks, and dependencies—while providing advisory support to ensure successful outcomes.
• Provide excellent customer support and ability to communicate with all levels of leadership and/or customers. Assist in the coordination for onboarding and offboarding of personnel.

Requirements

• Experience with/or supporting Operational units and/or formal testing (DT & OT)
• Experience with the intel community (IC)
• Technical experience in Strategic Datalinks and related data exchanges
• Excellent working knowledge and experience with DON (Navy and Marine Corps) airborne platforms and communications
• Basic understanding of UCI
• Experience working with FFRDCs and UARCs

Qualifications

• 3+ years of relevant work experience supporting cross-functional teams across an enterprise, combination system of systems (SoS)
• Extensive acquisition experience particularly in supporting the development of acquisition interoperability strategies for a complex multi-SoS information technology architecture; developing SoS matrices; performing integrated SoS assessments; executing the mission engineering process; drafting (SoS) requirements; developing DAF Battle Network architecture; and developing consulting with numerous program representatives to evaluate functional requirements
• Experience supporting government officials in approval of acquisition documents (e.g. acquisition strategies), and monitoring & advising on program execution/integration (e.g. schedule, risks) on behalf of government officials
• Experience working on classified and special access programs
• Must be located within commuting distance of Hanscom AFB, MA to support in-person attendance needs
• Possess exceptional written and oral communication skills, can develop clear, concise, and logically written business communications, as well as deliver recommendations
• Excellent interpersonal and communications skills; briefing and meeting management skills required
• Experience and excellent working knowledge of DAF acquisitions processes and program office roles and responsibilities
• Working understanding of DAF MAJCOMs (ACC and GSC) roles and equities
• Experience with DoD aircraft, radio, OFP development, modifications, test, and data integrations
• Solid working knowledge & applied foundation of systems engineering in a governmental acquisition and operational context
• Strong technical experience in Tactical Datalinks and related data exchanges