IPT Lead / Engineering Project Manager - Millennium Space Systems
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Must not include sections with filler like "commensurate with experience", "not specified", etc. Must not create Pay/Schedule/Benefits unless posting actually states them.
Let's parse the posting.
Content:
- Company description: Millennium Space Systems ... (first paragraph). That's about the role? Could be "About the role" or "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map sections accordingly.
We have:
Job Summary: description of role, responsibilities high-level. Could be "About the role". We'll include that.
Then "Position Responsibilities": a list of responsibilities (multiple bullet-like sentences). We'll put under Responsibilities
with - items.
Then "Basic Requirements: (Required Skills/Experience):" list of requirements. That's "Requirements". We'll put under
Requirements
with list.
Then "Preferred Qualifications (Desired Skills/Experience)" list. That's "Qualifications" maybe. Could be "Qualifications". We'll put under Qualifications
with list.
Then "Skills": Not explicitly listed but we have some skills mentioned in Preferred Qualifications: e.g., "Broad knowledge of satellite subsystems...", "Understanding of PCB design...", etc. Could be separate Skills section. But we can incorporate them into Qualifications or Skills. The instruction says we can have Skills section if there is real specific content. There is content about skills: "Experience with Earned Value Management and project management fundamentals such as scope, budget, schedule, and risk management." That's in Basic Requirements. Also "Critical analysis and problem-solving skills across systems, hardware and software architectures", "Practical experience with lab equipment for hardware development, troubleshooting and data capture". Those are in Preferred Qualifications. Could create a Skills section pulling out skill statements. But we must not duplicate content. Better to keep them within Requirements and Qualifications. The instruction says we can have Skills section if there is real specific content. We could create a Skills section with bullet points derived from the text. However we must preserve ALL substantive information; we cannot omit details. If we put them only in Skills, we must ensure they are not omitted elsewhere. Could duplicate? The instruction says do not invent or summarize away detail. Duplication is okay? It says remove duplicated lines. So we should avoid duplicating same content. Better to keep content in one place. So we can have Requirements (basic) and Qualifications (preferred). Skills may be redundant. We'll skip Skills section unless there is distinct skill list not covered elsewhere. The posting includes "Experience with Earned Value Management and project management fundamentals such as scope, budget, schedule, and risk management." That's a skill but also part of Basic Requirements. So we can keep it in Requirements.
Now Benefits: The posting includes "Total Rewards" paragraph describing benefits: competitive base pay, variable compensation, health insurance, flexible spending accounts, health savings accounts, retirement savings plans, life and disability insurance, paid/unpaid time away. That's benefits. So we should include a Benefits section with those details.
Pay: The posting includes "Summary Pay Range Level 4: $144,599 - $215,000 Level 5: $174,500 - $260,000". That's specific pay ranges. So we should include Pay section.
Schedule: The posting includes "This position is expected to be 100% onsite." Also "Shift Shift 1 (United States of America)". That's schedule info. So we can include Schedule section with that info.
We must not include sections with filler like "commensurate with experience". Not present.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to strip out lines like "Stay safe from recruitment fraud!", "The only way to apply...", "Boeing is an Equal Opportunity Employer.", etc. Also "Conflict Of Interest", "Drug Free Workplace", "Total Rewards" we keep as benefits. "Relocation: Relocation assistance is not a negotiable benefit for this position." That's a benefit detail (no relocation). Could include in Benefits. "Export Control Requirement", "Safety Sensitive", "Security Clearance", "Visa Sponsorship", "Contingent Upon Award Program", "Shift Shift 1 (United States of America)" - these are details; some may fit under Requirements or Schedule. Security clearance is a requirement (must be US citizen, able to obtain clearance). That's a requirement. We'll include under Requirements maybe as a bullet.
We need to preserve ALL substantive information. So we must include details like: US citizenship requirement, security clearance, export control, drug free workplace, etc. Those are substantive. So we need to incorporate them appropriately.
Let's extract all substantive info sections:
- Company description (first paragraph) - could be About the role.
- Job Summary (paragraph after "Job Summary") - also about role.
- Position Responsibilities (list of responsibilities) - we will list each sentence as bullet.
- Basic Requirements (list) - we will list each bullet.
- Preferred Qualifications (list) - we will list each bullet.
- Total Rewards / Benefits description - we will list benefits.
- Pay range - we will list.
- Schedule: 100% onsite, Shift 1 (US). Also location? Not given specific city but "This position is expected to be 100% onsite. The selected candidate will be required to work onsite at one of the listed locations." Not listed locations in excerpt. We'll just note 100% onsite, Shift 1.
- Additional requirements: US Citizenship, ability to obtain security clearance (Top Secret/SCI), Conflict of Interest assessment, Drug Free Workplace, Export Control compliance (US Person), Safety Sensitive (not), Visa Sponsorship (no), Contingent Upon Award Program (not), Relocation assistance not negotiable.
We need to decide where to put these. Could add to Requirements section as extra bullets. Or create a separate section like "Additional Requirements". But only allowed headings are the predefined list. We could add them under Requirements (makes sense). Or under Qualifications. We'll put under Requirements.
We must not include headings with no content. So we will include sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
We must not include Skills if we don't have distinct content.
Now we need to format as HTML fragment: use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not include / or markdown.
We must ensure we preserve all substantive info, not invent or summarize away detail. So we need to copy the exact sentences where possible, but we can break into bullet points. Must not lose any detail.
Let's extract exact text.
Company description:
"Company Millennium Space Systems Millennium Space Systems, a part of Boeing Defense, Space and Security (BDS), is a fast, agile small satellite company focused on national security space. Our missions have direct impact to global security, like missile warning and Earth observation. Our team is curious, bold and innovative. We take risks, innovate and explore new techniques and technologies. We influence change because we challenge the status quo. And when we watch our satellites launch, we know each one of us made it happen."
Note there is duplication "Company Millennium Space Systems Millennium Space Systems". We should preserve the content but not duplicate lines. The duplicated phrase appears twice; we should output once. So we can write: "Millennium Space Systems, a part of Boeing Defense, Space and Security (BDS), is a fast, agile small satellite company focused on national security space. Our missions have direct impact to global security, like missile warning and Earth observation. Our team is curious, bold and innovative. We take risks, innovate and explore new techniques and technologies. We influence change because we challenge the status quo. And when we watch our satellites launch, we know each one of us made it happen."
Job Summary paragraph:
"Job Summary As an IPT Lead, you will drive execution for the development of avionics products. You will be responsible for budget, schedule and technical execution. You will lead a cross functional team across disciplines to ensure products meet technical objectives for mass, power, communication, etc. Our products include items such as Guidance Navigation and Control systems, batteries, avionics, power and other systems which fly aboard the satellites we develop. You will drive product development from concept, PDR, CDR, Qualification, and Production. The ideal candidate would have experience leading product development programs thru the entire product life cycle and have a keen understanding on how to manage cost, schedule, risk, and technical execution for a product development program in the Space sector. The position will require working with company and program management, multiple engineering teams, production, ATLO (Assembly, Test, and Launch Operations), and our Customers to deliver qualified subsystem products on time and on budget. Successful IPT Leads blend deep technical understanding of a diverse cross-functional engineering team with an ability to manage cost/schedule aspects and drive program success. You will work closely with your IPT Lead counterparts managing other areas of the satellite program(s) to ensure solutions meet needs at the program and mission level."
We'll put that as prose under About the role maybe. Or we could split: About the role includes company description and job summary. We'll combine into one
maybe multiple paragraphs. But we can just put the company description in a
and then the job summary in another
under same heading? The instruction: Use
for prose. So we can have multiple
under the heading.
Now Responsibilities: The bullet list starts after "Position Responsibilities". Each sentence seems a responsibility. Let's list them:
- Serve as the technical and programmatic focal point for delivery of products to customers on time, on budget, on quality thru excellent communication, negotiation, and leadership skills with the ability to interface across technical and programmatic boundaries
- Drive team execution (day to day) and execution of upcoming milestones.
- Work with engineering staff to identify and resolve blockers that impede technical progress and program execution.
- Coordinate with technical leads to manage technical project scope, planning, proposals, cost estimates, schedules, cost performance, Estimates at Completion (EAC), and Risk assessment throughout the product development lifecycle.
- Ensure technical deliverables such as performance budgets (power, mass, thermal, comm, etc.) are properly defined, tracked, and met throughout the mission lifecycle.
- Provide inputs into the EAC process thru schedule updates, Earned value management system updates (EVMS), and variance analysis.
- Lead discrepancy report closure thru root cause and corrective action (RCCA) process. Integrate lessons learned into the development process.
- Status key subsystem deliverables to program management, customers, and other stakeholders.
- Lead, coordinate, and manage smooth transition from engineering design to production.
- Lead execution of verification plans, procedures, results, and reports; monitor system-performance measures.
- Assist the chief engineer in technical briefings, Program Management Review (PMR) briefings, customer meetings, and risk & opportunity assessments.
We need to keep the exact phrasing. Some sentences have "thru" abbreviations; we keep as is.
Now Basic Requirements list:
"Basic Requirements: (Required Skills/Experience): Bachelor of Science degree in Engineering, Engineering Technology (including Manufacturing Technology), Computer Science, Data Science, Mathematics, Physics, Chemistry or non-US equivalent qualifications directly related to the work statement.9 or more years' engineering experience with new product development projects through all
Requirements
with list. Then "Preferred Qualifications (Desired Skills/Experience)" list. That's "Qualifications" maybe. Could be "Qualifications". We'll put underQualifications
with list. Then "Skills": Not explicitly listed but we have some skills mentioned in Preferred Qualifications: e.g., "Broad knowledge of satellite subsystems...", "Understanding of PCB design...", etc. Could be separate Skills section. But we can incorporate them into Qualifications or Skills. The instruction says we can have Skills section if there is real specific content. There is content about skills: "Experience with Earned Value Management and project management fundamentals such as scope, budget, schedule, and risk management." That's in Basic Requirements. Also "Critical analysis and problem-solving skills across systems, hardware and software architectures", "Practical experience with lab equipment for hardware development, troubleshooting and data capture". Those are in Preferred Qualifications. Could create a Skills section pulling out skill statements. But we must not duplicate content. Better to keep them within Requirements and Qualifications. The instruction says we can have Skills section if there is real specific content. We could create a Skills section with bullet points derived from the text. However we must preserve ALL substantive information; we cannot omit details. If we put them only in Skills, we must ensure they are not omitted elsewhere. Could duplicate? The instruction says do not invent or summarize away detail. Duplication is okay? It says remove duplicated lines. So we should avoid duplicating same content. Better to keep content in one place. So we can have Requirements (basic) and Qualifications (preferred). Skills may be redundant. We'll skip Skills section unless there is distinct skill list not covered elsewhere. The posting includes "Experience with Earned Value Management and project management fundamentals such as scope, budget, schedule, and risk management." That's a skill but also part of Basic Requirements. So we can keep it in Requirements. Now Benefits: The posting includes "Total Rewards" paragraph describing benefits: competitive base pay, variable compensation, health insurance, flexible spending accounts, health savings accounts, retirement savings plans, life and disability insurance, paid/unpaid time away. That's benefits. So we should include a Benefits section with those details. Pay: The posting includes "Summary Pay Range Level 4: $144,599 - $215,000 Level 5: $174,500 - $260,000". That's specific pay ranges. So we should include Pay section. Schedule: The posting includes "This position is expected to be 100% onsite." Also "Shift Shift 1 (United States of America)". That's schedule info. So we can include Schedule section with that info. We must not include sections with filler like "commensurate with experience". Not present. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to strip out lines like "Stay safe from recruitment fraud!", "The only way to apply...", "Boeing is an Equal Opportunity Employer.", etc. Also "Conflict Of Interest", "Drug Free Workplace", "Total Rewards" we keep as benefits. "Relocation: Relocation assistance is not a negotiable benefit for this position." That's a benefit detail (no relocation). Could include in Benefits. "Export Control Requirement", "Safety Sensitive", "Security Clearance", "Visa Sponsorship", "Contingent Upon Award Program", "Shift Shift 1 (United States of America)" - these are details; some may fit under Requirements or Schedule. Security clearance is a requirement (must be US citizen, able to obtain clearance). That's a requirement. We'll include under Requirements maybe as a bullet. We need to preserve ALL substantive information. So we must include details like: US citizenship requirement, security clearance, export control, drug free workplace, etc. Those are substantive. So we need to incorporate them appropriately. Let's extract all substantive info sections: - Company description (first paragraph) - could be About the role. - Job Summary (paragraph after "Job Summary") - also about role. - Position Responsibilities (list of responsibilities) - we will list each sentence as bullet. - Basic Requirements (list) - we will list each bullet. - Preferred Qualifications (list) - we will list each bullet. - Total Rewards / Benefits description - we will list benefits. - Pay range - we will list. - Schedule: 100% onsite, Shift 1 (US). Also location? Not given specific city but "This position is expected to be 100% onsite. The selected candidate will be required to work onsite at one of the listed locations." Not listed locations in excerpt. We'll just note 100% onsite, Shift 1. - Additional requirements: US Citizenship, ability to obtain security clearance (Top Secret/SCI), Conflict of Interest assessment, Drug Free Workplace, Export Control compliance (US Person), Safety Sensitive (not), Visa Sponsorship (no), Contingent Upon Award Program (not), Relocation assistance not negotiable. We need to decide where to put these. Could add to Requirements section as extra bullets. Or create a separate section like "Additional Requirements". But only allowed headings are the predefined list. We could add them under Requirements (makes sense). Or under Qualifications. We'll put under Requirements. We must not include headings with no content. So we will include sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We must not include Skills if we don't have distinct content. Now we need to format as HTML fragment: use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not include / or markdown.
We must ensure we preserve all substantive info, not invent or summarize away detail. So we need to copy the exact sentences where possible, but we can break into bullet points. Must not lose any detail.
Let's extract exact text.
Company description:
"Company Millennium Space Systems Millennium Space Systems, a part of Boeing Defense, Space and Security (BDS), is a fast, agile small satellite company focused on national security space. Our missions have direct impact to global security, like missile warning and Earth observation. Our team is curious, bold and innovative. We take risks, innovate and explore new techniques and technologies. We influence change because we challenge the status quo. And when we watch our satellites launch, we know each one of us made it happen."
Note there is duplication "Company Millennium Space Systems Millennium Space Systems". We should preserve the content but not duplicate lines. The duplicated phrase appears twice; we should output once. So we can write: "Millennium Space Systems, a part of Boeing Defense, Space and Security (BDS), is a fast, agile small satellite company focused on national security space. Our missions have direct impact to global security, like missile warning and Earth observation. Our team is curious, bold and innovative. We take risks, innovate and explore new techniques and technologies. We influence change because we challenge the status quo. And when we watch our satellites launch, we know each one of us made it happen."
Job Summary paragraph:
"Job Summary As an IPT Lead, you will drive execution for the development of avionics products. You will be responsible for budget, schedule and technical execution. You will lead a cross functional team across disciplines to ensure products meet technical objectives for mass, power, communication, etc. Our products include items such as Guidance Navigation and Control systems, batteries, avionics, power and other systems which fly aboard the satellites we develop. You will drive product development from concept, PDR, CDR, Qualification, and Production. The ideal candidate would have experience leading product development programs thru the entire product life cycle and have a keen understanding on how to manage cost, schedule, risk, and technical execution for a product development program in the Space sector. The position will require working with company and program management, multiple engineering teams, production, ATLO (Assembly, Test, and Launch Operations), and our Customers to deliver qualified subsystem products on time and on budget. Successful IPT Leads blend deep technical understanding of a diverse cross-functional engineering team with an ability to manage cost/schedule aspects and drive program success. You will work closely with your IPT Lead counterparts managing other areas of the satellite program(s) to ensure solutions meet needs at the program and mission level."
We'll put that as prose under About the role maybe. Or we could split: About the role includes company description and job summary. We'll combine into one
maybe multiple paragraphs. But we can just put the company description in a
and then the job summary in another
under same heading? The instruction: Use
for prose. So we can have multiple
under the heading.
Now Responsibilities: The bullet list starts after "Position Responsibilities". Each sentence seems a responsibility. Let's list them:
- Serve as the technical and programmatic focal point for delivery of products to customers on time, on budget, on quality thru excellent communication, negotiation, and leadership skills with the ability to interface across technical and programmatic boundaries
- Drive team execution (day to day) and execution of upcoming milestones.
- Work with engineering staff to identify and resolve blockers that impede technical progress and program execution.
- Coordinate with technical leads to manage technical project scope, planning, proposals, cost estimates, schedules, cost performance, Estimates at Completion (EAC), and Risk assessment throughout the product development lifecycle.
- Ensure technical deliverables such as performance budgets (power, mass, thermal, comm, etc.) are properly defined, tracked, and met throughout the mission lifecycle.
- Provide inputs into the EAC process thru schedule updates, Earned value management system updates (EVMS), and variance analysis.
- Lead discrepancy report closure thru root cause and corrective action (RCCA) process. Integrate lessons learned into the development process.
- Status key subsystem deliverables to program management, customers, and other stakeholders.
- Lead, coordinate, and manage smooth transition from engineering design to production.
- Lead execution of verification plans, procedures, results, and reports; monitor system-performance measures.
- Assist the chief engineer in technical briefings, Program Management Review (PMR) briefings, customer meetings, and risk & opportunity assessments.
We need to keep the exact phrasing. Some sentences have "thru" abbreviations; we keep as is.
Now Basic Requirements list:
"Basic Requirements: (Required Skills/Experience): Bachelor of Science degree in Engineering, Engineering Technology (including Manufacturing Technology), Computer Science, Data Science, Mathematics, Physics, Chemistry or non-US equivalent qualifications directly related to the work statement.9 or more years' engineering experience with new product development projects through all
for prose. We must not include / or markdown. We must ensure we preserve all substantive info, not invent or summarize away detail. So we need to copy the exact sentences where possible, but we can break into bullet points. Must not lose any detail. Let's extract exact text. Company description: "Company Millennium Space Systems Millennium Space Systems, a part of Boeing Defense, Space and Security (BDS), is a fast, agile small satellite company focused on national security space. Our missions have direct impact to global security, like missile warning and Earth observation. Our team is curious, bold and innovative. We take risks, innovate and explore new techniques and technologies. We influence change because we challenge the status quo. And when we watch our satellites launch, we know each one of us made it happen." Note there is duplication "Company Millennium Space Systems Millennium Space Systems". We should preserve the content but not duplicate lines. The duplicated phrase appears twice; we should output once. So we can write: "Millennium Space Systems, a part of Boeing Defense, Space and Security (BDS), is a fast, agile small satellite company focused on national security space. Our missions have direct impact to global security, like missile warning and Earth observation. Our team is curious, bold and innovative. We take risks, innovate and explore new techniques and technologies. We influence change because we challenge the status quo. And when we watch our satellites launch, we know each one of us made it happen." Job Summary paragraph: "Job Summary As an IPT Lead, you will drive execution for the development of avionics products. You will be responsible for budget, schedule and technical execution. You will lead a cross functional team across disciplines to ensure products meet technical objectives for mass, power, communication, etc. Our products include items such as Guidance Navigation and Control systems, batteries, avionics, power and other systems which fly aboard the satellites we develop. You will drive product development from concept, PDR, CDR, Qualification, and Production. The ideal candidate would have experience leading product development programs thru the entire product life cycle and have a keen understanding on how to manage cost, schedule, risk, and technical execution for a product development program in the Space sector. The position will require working with company and program management, multiple engineering teams, production, ATLO (Assembly, Test, and Launch Operations), and our Customers to deliver qualified subsystem products on time and on budget. Successful IPT Leads blend deep technical understanding of a diverse cross-functional engineering team with an ability to manage cost/schedule aspects and drive program success. You will work closely with your IPT Lead counterparts managing other areas of the satellite program(s) to ensure solutions meet needs at the program and mission level." We'll put that as prose under About the role maybe. Or we could split: About the role includes company description and job summary. We'll combine into one
maybe multiple paragraphs. But we can just put the company description in a
and then the job summary in another
under same heading? The instruction: Use
for prose. So we can have multiple
under the heading. Now Responsibilities: The bullet list starts after "Position Responsibilities". Each sentence seems a responsibility. Let's list them: - Serve as the technical and programmatic focal point for delivery of products to customers on time, on budget, on quality thru excellent communication, negotiation, and leadership skills with the ability to interface across technical and programmatic boundaries - Drive team execution (day to day) and execution of upcoming milestones. - Work with engineering staff to identify and resolve blockers that impede technical progress and program execution. - Coordinate with technical leads to manage technical project scope, planning, proposals, cost estimates, schedules, cost performance, Estimates at Completion (EAC), and Risk assessment throughout the product development lifecycle. - Ensure technical deliverables such as performance budgets (power, mass, thermal, comm, etc.) are properly defined, tracked, and met throughout the mission lifecycle. - Provide inputs into the EAC process thru schedule updates, Earned value management system updates (EVMS), and variance analysis. - Lead discrepancy report closure thru root cause and corrective action (RCCA) process. Integrate lessons learned into the development process. - Status key subsystem deliverables to program management, customers, and other stakeholders. - Lead, coordinate, and manage smooth transition from engineering design to production. - Lead execution of verification plans, procedures, results, and reports; monitor system-performance measures. - Assist the chief engineer in technical briefings, Program Management Review (PMR) briefings, customer meetings, and risk & opportunity assessments. We need to keep the exact phrasing. Some sentences have "thru" abbreviations; we keep as is. Now Basic Requirements list: "Basic Requirements: (Required Skills/Experience): Bachelor of Science degree in Engineering, Engineering Technology (including Manufacturing Technology), Computer Science, Data Science, Mathematics, Physics, Chemistry or non-US equivalent qualifications directly related to the work statement.9 or more years' engineering experience with new product development projects through all