Technical Lead Engineer (PMPC Software Test)

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 like EEO, etc. Must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes Pay & Benefits section with pay range and benefits description. Also includes Shift (1st shift) maybe schedule? It says "Shift This position is for 1st shift". That's schedule info. Also includes "This position is expected to be 100% onsite." That's schedule/location. So we can include Schedule section with onsite and shift. Benefits: they described benefits generally. Pay: they gave pay range. So include Pay and Benefits sections. Also include About the role? The initial paragraph about Boeing innovating etc is generic but maybe considered About the role? It's more company overview. Could be considered About the role. But we need to decide if it's substantive. It's generic but still part of job description. Probably include as About the role. Responsibilities: there is a list under Position Responsibilities. Requirements: Basic Qualifications (Required Skills/Experience). Qualifications: Preferred Qualifications (Desired Skills/Experience). Skills: maybe combine? But we have separate sections for Requirements and Qualifications. Skills could be derived but maybe not needed. The instruction says use headings for those categories if content exists. We have content for Requirements (Basic Qualifications) and Qualifications (Preferred). Skills maybe not separate; we could omit Skills heading if no distinct skills list beyond those. But we could treat Requirements as skills. However better to follow: Requirements = Basic Qualifications, Qualifications = Preferred Qualifications. Skills maybe not needed. We'll include About the role, Responsibilities, Requirements, Qualifications, Pay, Benefits, Schedule. Ensure we don't include filler. Now extract content. About the role: The first paragraph: "At Boeing, we innovate and collaborate to make the world a better place. We're committed to fostering an environment for every teammate that's welcoming, respectful and inclusive, with great opportunity for professional growth. Find your future with us. The Boeing Company is looking for a Technical Lead Engineer (PMPC Software Test) to join our Air Proprietary Mission Systems team located in Berkeley, MO. This position will focus on supporting the Boeing Defense, Space & Security (BDS) business organization. The PMP Test Technical Lead is responsible for establishing software test plans, procedures and processes guiding software test. The test lead will be the primary software test technical point of contact for PMP. This role will be responsible for PMP Mission Systems software test across a variety of security levels, to include software developed by a variety of suppliers. The lead will be responsible for safety critical testing as well as mission critical level test strategies. This lead will help teams understand the compliance to standards and policy enforcement based on software processes. This role will also coordinate with other technical leads on the PMP software team, the Mission Systems Software test team, along with various other Missions Systems and systems test organizations on the program to ensure a cohesive test strategy." We should keep that as About the role. Responsibilities: The bullet list after "Position Responsibilities". It's a paragraph with multiple sentences separated by line breaks? Actually it's a list but not bullet. We'll convert to

• each responsibility. Let's list them: - Develop and maintain the PMP software test plan and vision working with the Mission Systems Chief Engineer, PMP Architect, Mission Systems Software test team lead and other PMP and Mission Systems technical leads - Develops and owns PMP software verification plans, test procedures, and test environments, executing the test procedures and documenting test results to ensure software requirements are met - Determines testing strategy to include models, emulation, simulation, dev kits, and full-up hardware - Ensures software teams develop, document, and execute appropriate software level testing - Ensures compliance and supports policy enforcement for applicable processes, reference architectures, and industry standards - Plans, executes, and documents software research and development projects - Responsible for coordinating across the Mission Systems team, as well as Flight Sim Labs, SEIT and more - Trains and mentors others - Works under minimal direction Also "This position is expected to be 100% onsite." That's schedule, not responsibility. Now Requirements (Basic Qualifications): list: - Active Secret U.S. Security Clearance (A U.S. Security Clearance that has been active in the past 24 months is considered active.) - This position requires ability to obtain Special Program Access, for which the U.S. Government requires U.S. Citizenship only - Bachelor's Degree - 7+ years of experience programming with Go, Java, C/C++, Rust, or Python - 5+ years of experience in hardware / software integration, emulation, and/or testing, preferably in a lab environment - 3+ years of experience leading software teams and/or projects - 3+ experience with the Software Development Lifecycle (including Requirements Analysis, Design, Code, Integration & Test) Note: "3+ experience" missing "years". We'll keep as is. Now Qualifications (Preferred Qualifications): list: - Bachelor of Science degree from an accredited course of study in engineering, engineering technology (includes manufacturing engineering technology), chemistry, physics, mathematics, data science, or computer science and 14+ years of related work experience or Bachelor's Degree and 18+ years of directly related work experience or 22+ years of related, relevant experience - 3+ years of experience in software architecture - Experience with embedded software architecture/development/design - Experience developing mission systems software on aircraft platforms - Experience with distributed and containerized software architecture - Hands on experience developing on the Linux platform and Windows - Experience with Agile software development and related processes - Familiar with safety critical software development - Experience with secure software development environments at various levels of security - Active Secret U.S. Security Clearance (again duplicate? It's listed again but we can keep once.) We should avoid duplication but preserve all substantive info. Could keep once. Now Pay: The posting includes "Pay & Benefits At Boeing, we strive to deliver a Total Rewards package..." and then "Summary Pay Range: $177,650 - $240,350". Also mentions variable compensation etc. We'll extract Pay section: include the pay range and mention that pay is based on experience etc. Could also include variable compensation opportunities. We'll keep substantive: "Pay is based upon candidate experience and qualifications, as well as market and business considerations. Summary Pay Range: $177,650 - $240,350". Also mention variable compensation opportunities? It says "Elements of the Total Rewards package include competitive base pay and variable compensation opportunities." That's substantive. We'll include. Benefits: The paragraph after Pay: "The Boeing Company also provides eligible employees with an opportunity to enroll in a variety of benefit programs, generally including health insurance, flexible spending accounts, health savings accounts, retirement savings plans, life and disability insurance programs, and a number of programs that provide for both paid and unpaid time away from work. The specific programs and options available to any given employee may vary depending on eligibility factors such as geographic location, date of hire, and the applicability of collective bargaining agreements." We'll include that. Schedule: includes "This position is expected to be 100% onsite. The selected candidate will be required to work onsite in Berkeley, MO." and "Shift This position is for 1st shift". Also maybe "Relocation This position offers relocation based on candidate eligibility." That's also schedule/relocation. We'll include schedule section with onsite location, shift, relocation. Now we must not include boilerplate like Export Control Requirements, Equal Opportunity Employer, etc. Remove those. Now produce HTML fragment with

  headings and

  or

  • . Ensure no extra text. Let's craft. Structure:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Requirements

    • ...
    ...

    Qualifications

    • ...
    ...

    Pay

    ...

    Benefits

    ...

    Schedule

    ...

    Make sure to preserve all info. Now write the content precisely. About the role paragraph: combine sentences. Let's copy: "At Boeing, we innovate and collaborate to make the world a better place. We're committed to fostering an environment for every teammate that's welcoming, respectful and inclusive, with great opportunity for professional growth. Find your future with us. The Boeing Company is looking for a Technical Lead Engineer (PMPC Software Test) to join our Air Proprietary Mission Systems team located in Berkeley, MO. This position will focus on supporting the Boeing Defense, Space & Security (BDS) business organization. The PMP Test Technical Lead is responsible for establishing software test plans, procedures and processes guiding software test. The test lead will be the primary software test technical point of contact for PMP. This role will be responsible for PMP Mission Systems software test across a variety of security levels, to include software developed by a variety of suppliers. The lead will be responsible for safety critical testing as well as mission critical level test strategies. This lead will help teams understand the compliance to standards and policy enforcement based on software processes. This role will also coordinate with other technical leads on the PMP software team, the Mission Systems Software test team, along with various other Missions Systems and systems test organizations on the program to ensure a cohesive test strategy." That's fine. Now Responsibilities list items as above. Now Requirements list. Now Qualifications list. Now Pay paragraph: "Elements of the Total Rewards package include competitive base pay and variable compensation opportunities. Pay is based upon candidate experience and qualifications, as well as market and business considerations. Summary Pay Range: $177,650 - $240,350." Now Benefits paragraph: "The Boeing Company also provides eligible employees with an opportunity to enroll in a variety of benefit programs, generally including health insurance, flexible spending accounts, health savings accounts, retirement savings plans, life and disability insurance programs, and a number of programs that provide for both paid and unpaid time away from work. The specific programs and options available to any given employee may vary depending on eligibility factors such as geographic location, date of hire, and the applicability of collective bargaining agreements." Now Schedule paragraph: "This position is expected to be 100% onsite. The selected candidate will be required to work onsite in Berkeley, MO. The position is for 1st shift. Relocation is offered based on candidate eligibility." Check that we didn't miss any substantive info: also mention "Export Control Requirements" etc removed. Also "CodeVue Coding Challenge" etc removed. Also "Drug Free Workplace" removed. Also "Visa Sponsorship" removed. Also "Equal Opportunity Employer" removed. Also "Summary Pay Range" we included. Also "Applications for this position will be accepted until Sept. 30, 2026" - that's a deadline, maybe considered substantive? It's not in the specified sections but could be included maybe in About the role? But instructions: preserve ALL substantive information; do not invent or summarize away detail. The deadline is substantive. Where to put? Could be in About the role or maybe a separate section like "Application deadline" but not in allowed headings. We could add a

    under About the role or maybe a separate heading like "Important Dates" but not allowed. The instruction says use headings for those specific sections only; but we can still include other info as

    without heading? It says use

    for section headings (e.g. About the role, Respons