Systems Integration Engineer
PeopleTec, Inc. · Huntsville, AL · 1 mo ago
Quality AssuranceFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule as appropriate. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (EEO, legal, scam warning, navigation, cookie, duplicated lines, application instructions). Also must not include sections with filler like "commensurate with experience" etc. We need to see what content is present.
The posting includes:
- Opportunity PeopleTec is currently seeking a Systems Integration Engineer to support our Huntsville, AL location.
- The candidate will serve as a Systems Integration Engineer within a Project Management Office (PMO) within PAE Fires and will be responsible for providing technical support to the program's Chief Engineer and the Product Manager.
- The candidate will own the end-to-end physical and logical system baseline across multi-vendor sensor and effector payloads through design, development, acquisition, integration, testing, fielding, and sustainment.
- The candidate will prepare and present systems integration findings, reports, and improvement plans to senior management and stakeholders.
- Will work within and/or lead a multidisciplinary team to achieve program goals.
- Perform other tasks as assigned by the Chief Engineer and/or Product Manager.
- The candidate will be required to interface with internal PMs across PAE Fires and external organizations to include HQDA, ASA(ALT), JIATF 401, ATEC, AMCOM, and others for coordination and synchronization of systems integration technical and programmatic objectives.
- Duties: (list)
- Provide technical support and leadership in systems integration across the system lifecycle (design, development, acquisition, integration, testing, fielding, and sustainment).
- Enforce Modular Open Systems Approach (MOSA) compliance across edge computing enclosures and payload mounts.
- Define interface boundaries between sensor feeds, compute racks, and weapon links.
- Manage Engineering Change Proposals (ECPs) and Interface Control Documents (ICDs).
- Develop and maintain System ICDs, the MOSA Conformance Verification Plan, and the System Specification Baseline.
- Ensure compliance with defense and industry standards by managing systems integration processes effectively.
- Interface with internal teams and external organizations to coordinate systems integration objectives and strategies.
- Prepare and present systems integration findings, reports, and improvement plans to senior management and stakeholders.
- Conduct strategic planning and coordination to support program objectives.
- Provide technical guidance and leadership to peer and subordinate engineers within the systems integration team.
- Use digital tools and methodologies to manage cost, schedule, and performance for assigned activities.
- Perform other tasks as assigned by the Chief Engineer and/or Product Manager.
- Qualifications Required Skills/Experience:
- 5+ years of relevant experience.
- Additional education may be substituted for years of experience.
- Demonstrated experience in systems integration, particularly within defense or aerospace industries.
- Knowledge of Modular Open Systems Approach (MOSA), SysML/MBSE, MIL-STD-810/461, and sensor interface protocols.
- Strong knowledge of industry standards and defense requirements.
- Excellent communication and presentation skills.
- Ability to lead and work within a multidisciplinary team.
- Previous experience working in a U.S. Government Program Office (required).
- Travel: 25%
- Must be a U.S. Citizen
- An active DoD Secret clearance is required to perform this work.
- Candidates are required to have an active Secret clearance upon hire, and the ability to maintain this level of clearance during their employment.
- Education Requirements: Bachelor's degree in Engineering (or related technical discipline).
- Desired Skills: Top Secret clearance preferred
- Overview People First. Technology Always. PeopleTec, Inc. is an employee-owned small business founded in Huntsville, AL that provides exceptional customer support by employing and retaining a highly skilled workforce.
- Culture: The name "PeopleTec" was deliberately chosen to remind us of our core value system - our people. Our company's foundation was built on placing our employees and customers first. With an award-winning atmosphere, we have matured into a company that boasts the best and brightest across multiple technical fields.
- Career: At PeopleTec, we value your long-term goals. Whether it's through our continuing-education opportunities, our robust training programs, or our "People First" benefits package, PeopleTec truly believes that our best investments are our people. Come Experience It.
- #cjpost #dpost (maybe ignore)
- EEO Statement etc (remove)
- PeopleTec, Inc. participates in E-Verify (maybe remove as boilerplate? It's legal but not EEO; but it's still a statement; we should remove legal/EEO/equal-opportunity/scam-warning boilerplate. "PeopleTec, Inc. participates in E-Verify" is legal; likely remove.
We need to decide sections.
We have content for:
- About the role: could be the introductory paragraph(s) describing role, location, purpose. Could include the first paragraph(s) before duties.
- Responsibilities: the duties list.
- Requirements: maybe qualifications required skills/experience, education, citizenship, clearance, travel.
- Qualifications: maybe education requirements? But we already have qualifications. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we need to decide which sections to include based on actual content.
We have:
- About the role: we can include the initial description: "Opportunity PeopleTec is currently seeking a Systems Integration Engineer to support our Huntsville, AL location. The candidate will serve as a Systems Integration Engineer within a Project Management Office (PMO) within PAE Fires and will be responsible for providing technical support to the program's Chief Engineer and the Product Manager. The candidate will own the end-to-end physical and logical system baseline across multi-vendor sensor and effector payloads through design, development, acquisition, integration, testing, fielding, and sustainment. The candidate will prepare and present systems integration findings, reports, and improvement plans to senior management and stakeholders. Will work within and/or lead a multidisciplinary team to achieve program goals. Perform other tasks as assigned by the Chief Engineer and/or Product Manager. The candidate will be required to interface with internal PMs across PAE Fires and external organizations to include HQDA, ASA(ALT), JIATF 401, ATEC, AMCOM, and others for coordination and synchronization of systems integration technical and programmatic objectives."
That seems like role overview.
- Responsibilities: the Duties list (the bullet list after "Duties:").
- Requirements: maybe the qualifications required skills/experience (5+ years, etc.) plus education, citizenship, clearance, travel.
- Qualifications: maybe education requirements? But we already used qualifications for required skills. Could separate: Requirements = mandatory qualifications (experience, clearance, citizenship, etc.) and Qualifications = desired/preferred (Top Secret clearance preferred). However the instruction says we can use both headings if there is real content. We have "Education Requirements Bachelor's degree in Engineering (or related technical discipline)." That's a qualification. Also "Desired Skills Top Secret clearance preferred". That's a skill/qualification.
We also have "Overview People First..." etc which is company overview; could be placed under "About the company" but not in allowed headings. Not required to include. Could omit or put under About the role? Probably better to omit as not required.
We have "Career: ..." about benefits; could be used for Benefits section if there is mention of benefits: "People First" benefits package, continuing-education opportunities, robust training programs. That is substantive benefits info. So we can create a Benefits section with that.
We have no explicit Pay or Schedule info besides Travel 25% (which is under Requirements maybe). No explicit salary or schedule (like full-time, shift). So we should NOT create Pay or Schedule sections because they'd be filler.
We have Skills: maybe we can list specific skills: knowledge of MOSA, SysML/MBSE, MIL-STD-810/461, sensor interface protocols, industry standards, defense requirements, communication, presentation, leadership, multidisciplinary team, digital tools for cost/schedule/performance. That could go under Skills section. But we already have many of those in Responsibilities/Requirements. To avoid duplication, we could still include a Skills section summarizing technical skills. The instruction: Prefer a few substantive sections over many thin ones. So we need to decide which sections are most substantive.
We have:
- About the role (intro)
- Responsibilities (duties list)
- Requirements (experience, clearance, citizenship, travel, education)
- Skills (technical skills like MOSA, SysML, etc.)
- Benefits (People First benefits, continuing education, training)
We could combine Requirements and Qualifications into one section, but we have both required and desired. Could have Requirements (mandatory) and Qualifications (desired). That seems okay.
We must not repeat job title as heading. So we will not include "Systems Integration Engineer" as heading.
We must not include Job ID/requisition numbers.
We must output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
...
Responsibilities
- ... ...
Requirements
- 5+ years of relevant experience.
- Additional education may be substituted for years of experience.
- Demonstrated experience in systems integration, particularly within defense or aerospace industries.
- Knowledge of Modular Open Systems Approach (MOSA), SysML/MBSE, MIL-STD-810/461, and sensor interface protocols.
- Strong knowledge of industry standards and defense requirements.
- Excellent communication and presentation skills.
- Ability to lead and work within a multidisciplinary team.
- Previous experience working in a U.S. Government Program Office (required).
- Must be a U.S. Citizen.
- An active DoD Secret clearance is required to perform this work; candidates must have an active Secret clearance upon hire and maintain it during employment.
- Travel: 25%.
- Bachelor's degree in Engineering (or related technical discipline).