Sr. Specialist, Project Chief Engineer

We need to output HTML fragment with sections: About the role? Actually we need headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Only include sections where posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented or summarizing away detail. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO etc. We need to parse the posting. Key info: - Intro paragraph about L3Harris culture etc. Could be "About the role" or maybe "About the company"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. Job Description: "Join L3Harris as a Senior Specialist Project Engineer, where you will lead the technical, schedule, and cost execution of multidisciplinary design teams across new product development, production, and Internal Research and Development (IRAD) programs. In this role, you will partner closely with Program Management, Engineering, Manufacturing, and cross-functional teams to drive projects from concept through completion while ensuring alignment to customer needs, business objectives, and program commitments. This is an opportunity to make a visible impact by guiding complex engineering efforts in a collaborative environment focused on innovation, execution, and mission-critical solutions." That's about the role. Could be placed under "About the role" heading. Essential Functions list: bullet list of duties. That is Responsibilities. Qualifications: bullet list of requirements (education, experience). That could be Requirements or Qualifications. The instruction includes both Requirements and Qualifications headings. We need to decide where to put what. Usually Requirements = mandatory qualifications; Qualifications = maybe preferred? But we have both mandatory qualifications and preferred additional skills. So we can put mandatory qualifications under "Requirements" and preferred skills under "Skills" or "Qualifications". The instruction includes Skills heading. So we can put Preferred Additional Skills under Skills. Also we have "Qualifications" heading maybe for education/experience? But we already used Requirements for that. Could also put Qualifications for education/experience and Skills for preferred skills. Let's see: The posting has "Qualifications:" section with bullet points (education/experience, leading teams, technical lead, autonomous vehicle experience, ocean engineering). Then "Preferred Additional Skills:" section with bullet points (degree fields, AUV experience, at-sea test, familiarity, proficiency with MS Project and CAD, working knowledge of EVM, experience supporting DoD programs, strong communication). So we can map: - Requirements: the mandatory qualifications (education/experience, leading teams, technical lead, autonomous vehicle experience, ocean engineering). Or we could call that "Qualifications". But we need to avoid duplicate headings; we can choose either. Let's follow typical: Requirements = mandatory; Qualifications = maybe education/experience? But we have both. Let's decide: We'll create:

About the role

with the job description paragraph.

Responsibilities

with the Essential Functions list (bulleted).

Requirements

with the mandatory qualifications list (education/experience, leading teams, technical lead, autonomous vehicle experience, ocean engineering).

Skills

with the Preferred Additional Skills list.

Pay

with salary range: $106,500 - $197,500.

Schedule

with job schedule: 9/80 Regular (9/80 Employees work 9 out of every 14 days – totaling 80 hours worked – and have every other Friday off). We might also include Benefits section: they list benefits: health and disability insurance, 401(k) match, flexible spending accounts, EAP, education assistance, parental leave, paid time off, company-paid holidays. That's substantive. So include Benefits. We must not include boilerplate like EEO, legal, etc. Also must not include duplicated lines. Also must not include application instructions. Also must not include "In compliance with pay transparency requirements" maybe part of Pay section but we can keep that sentence? It says "In compliance with pay transparency requirements, the salary range for this role is $106,500 - $197,500. This is not a guarantee of compensation or salary, as final offer amount may vary based on factors including but not limited to experience and geographic location." That's substantive about pay. We can include that as part of Pay section. It's not boilerplate; it's required transparency statement. Keep it. Benefits: "L3Harris also offers a variety of benefits, including health and disability insurance, 401(k) match, flexible spending accounts, EAP, education assistance, parental leave, paid time off, and company-paid holidays. The specific programs and options available to an employee may vary depending on date of hire, schedule type, and the applicability of collective bargaining agreements." That's substantive. We must not include EEO statements etc. Now produce HTML fragment: only the sections, each with

heading and then content: either

for prose or

• for lists. We need to preserve all substantive information; do not invent or summarize away detail. So we must keep the exact wording? We should preserve the meaning but not necessarily exact wording? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the details, not omit any. We can rephrase slightly but must not lose detail. Safer to keep the original sentences. Let's extract each piece. About the role: The paragraph from Job Description: "Join L3Harris as a Senior Specialist Project Engineer, where you will lead the technical, schedule, and cost execution of multidisciplinary design teams across new product development, production, and Internal Research and Development (IRAD) programs. In this role, you will partner closely with Program Management, Engineering, Manufacturing, and cross-functional teams to drive projects from concept through completion while ensuring alignment to customer needs, business objectives, and program commitments. This is an opportunity to make a visible impact by guiding complex engineering efforts in a collaborative environment focused on innovation, execution, and mission-critical solutions." We'll put that in

  . Responsibilities: Essential Functions list (each starts with a verb). We'll keep each as

• . The list: - Lead the day-to-day technical, schedule, and cost execution of engineering projects with minimal oversight, ensuring alignment with program objectives and customer requirements. - Coordinate across Program Management, Engineering, Manufacturing, resource managers, suppliers, subcontractors, and customers to support efficient project execution and overall team performance. - Monitor and communicate project status, milestones, risks, opportunities, and resolution plans to management and stakeholders in a timely manner. - Develop, maintain, and report engineering project schedules, plans, budgets, and earned value management metrics, and support resource planning for development programs. - Ensure technical contractual obligations, baseline requirements, cost, schedule, and quality expectations are met through close collaboration with Program Managers and Lead Engineers. - Provide technical leadership in customer meetings, technical presentations, and internal and external design reviews. - Support proposal and new business activities through development of work breakdown structures, task descriptions, basis of estimates, and other cost estimating inputs. - Drive compliance with applicable procedures & plans while identifying and implementing process, product, and system improvements. - Contribute to strategic and operational goals by helping develop new processes, standards, and solutions that improve program and business performance. - Able to travel up to 10% as needed to support program execution, customer meetings, supplier coordination, and design reviews. - Able to analyze technical issues and support development, integration, test, and production activities in a complex engineering environment. - Ability to obtain and maintain a US security clearance if required by the program or customer. We need to keep the bullet points exactly as given, maybe preserve punctuation. Requirements: The qualifications bullet list: - Bachelor’s Degree and a minimum of 6 years of prior related experience, or a Graduate Degree and a minimum of 4 years of prior related experience. In lieu of a degree, a minimum of 10 years of prior related experience. - At least 1 year of experience leading multi-disciplined teams in an engineering environment. - At least 1 year of experience serving as a Technical Lead on a development or production program. - At least 1 year of hands-on technical experience with autonomous vehicles, which may include vehicle assembly and disassembly, operations, autonomous vehicle development or deployment, sea testing experience, or other autonomous vehicle experience. - At least 1 year of experience with ocean engineering, underwater infrastructure, and autonomous undersea vehicles and operations. We'll keep each as
• . Skills: Preferred Additional Skills bullet list: - Bachelor of Science degree in Naval Architecture, Ocean Engineering, Mechanical Engineering, Electrical Engineering, Systems Engineering, Physics, or Computer Systems Engineering. - Experience working with, operating, and/or designing autonomous underwater vehicles (AUVs). - At-sea test experience and detailed technical knowledge of autonomous underwater vehicle (AUV) systems, subsystem integration, and field operations. - Familiarity with ocean engineering applications, underwater systems, and undersea vehicle deployment and recovery operations. - Proficiency with Microsoft Project and computer-aided design (CAD) tools used for engineering development, planning, and coordination. - Working knowledge of Earned Value Management (EVM) principles and experience supporting metric tracking and reporting for engineering or Department of Defense (DoD) programs. - Experience supporting Department of Defense (DoD) development or production programs in a classified or mission-focused environment. - Strong communication and collaboration skills with the ability to work effectively across engineering, program management, manufacturing, suppliers, and customers. We'll keep each as
• . Pay: We'll include the sentence: "In compliance with pay transparency requirements, the salary range for this role is $106,500 - $197,500. This is not a guarantee of compensation or salary, as final offer amount may vary based on factors including but not limited to experience and geographic location." We can put that in

  . Schedule: The job schedule line: "Job Schedule: 9/80 Regular (9/80 Employees work 9 out of every 14 days – totaling 80 hours worked – and have every other Friday off)". We'll put that in

  . Benefits: The benefits paragraph: "L3Harris also offers a variety of benefits, including health and disability insurance, 401(k) match, flexible spending accounts, EAP, education assistance, parental leave, paid time off, and company-paid holidays. The specific programs and options available to an employee may vary depending on date of hire, schedule type, and the applicability of collective bargaining agreements." We'll put that in

  . We must not include any other sections like About the company etc. The intro paragraph about L3Harris culture etc is maybe not needed? It's generic boilerplate about company values. Might be considered boilerplate? It's not a standard EEO but it's about company culture. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The intro about L3Harris dedication etc might be considered boilerplate? It's not EEO but it's generic fluff. However it's substantive? It's describing company culture. The instruction says "Prefer a few substantive sections over many thin ones." Could include it under About the role? But we already used About the role for job description. Could we merge the intro paragraph into About the role? The instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid adding other headings, but we should only include sections when posting has real specific content. The intro paragraph about L3Harris is generic but still specific to the company. Might be considered boilerplate? It's not EEO or legal. It's about company values. Could be considered part of About the role? Might be okay to