Tactical Data Link Program Engineering Manager (PEM) II

We need to output HTML fragment with sections: h3 for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to parse the job description and extract content. Sections: - About the role: likely description of role, overview. Could be first paragraph after intro: "We are looking for a Program Engineering Manager (PEM) to support various programs..." etc. Also "Our C4ISR team plays a key role..." etc. Might be considered About the role. - Responsibilities: list of duties. There's "Specific Job Responsibilities Include, But Are Not Limited To" then a list of items separated by periods? Actually they are sentences. We need to convert to

• . Also later "Key Aspects Of This Role" also responsibilities. We'll combine. - Requirements: likely "Required Education, Experience, & Skills". That includes required education, experience, skills. Could be split into Requirements (education/experience) and Skills? But we have separate sections for Qualifications, Skills. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly. We have "Required Education, Experience, & Skills" which includes education, experience, and skills. Could split: Requirements (education/experience) and Skills (skills). Also there is "Preferred Education, Experience, & Skills". Could be Qualifications? Usually Qualifications includes required and preferred. We'll treat Required as Requirements, Preferred as Qualifications? Or Qualifications could be both required and preferred? But we have separate Skills heading. Let's decide: - Requirements: Required Education, Experience, & Skills (but we will extract education and experience requirements, maybe also required skills? Might be okay to put required skills under Skills section. - Qualifications: Preferred Education, Experience, & Skills (preferred). - Skills: maybe we can extract skill statements from both required and preferred? But we risk duplication. Better to follow instruction: include a section only when posting has real specific content for it. We have content for Requirements (required education/experience). We have content for Qualifications (preferred). We have content for Skills (maybe we can extract skill statements like "Strong planning and organizational skills", "Proven written and oral communication skills", etc. Those are in required section. Could put them under Skills. - Benefits: there is "Employee Benefits:" paragraph. - Pay: "Pay Information Full-Time Salary Range: $153377 - $260743". Also note about market pay structures. We'll include Pay section with that range. - Schedule: mention hybrid work format: "Because this role involves a combination of collaborative/in-person and independent work, it will take the form of a hybrid work format. It will require mostly in-person, on-site work with the potential for allowing some remote work." That's schedule info. Now we need to avoid filler like "commensurate with experience". Not present. We must not include boilerplate like EEO, legal, etc. At end there is "About BAE Systems Electronic Systems" etc. That's company description; could be considered About the role? Might be extra but could be included under About the role? The instruction: "Prefer a few substantive sections over many thin ones." We could include About the role with overview of role and maybe company description? But company description is not about the role specifically. Might be considered boilerplate? It's not navigation/legal/EEO but it's generic company info. Might be okay to include under About the role? However the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description is not those. Could keep as part of About the role? Might be considered extra but not prohibited. However we should preserve ALL substantive information; do not invent or summarize away detail. So we should keep company description if it's substantive. But where to put? Could be under About the role? Or maybe we create a separate section "About BAE Systems"? Not in allowed headings. So we could incorporate into About the role as extra paragraph. But we need to avoid duplication. Let's extract sections: About the role: Could include the paragraph describing C4ISR team, role purpose, location, etc. Let's gather: - "Our C4ISR team plays a key role in the military defense and operational stability of governments, businesses, and societies worldwide today, and indications are that it will only become more important moving forward, given its growing role in how decisions are made, threats are addressed, and agreements are enforced. The world’s nations are in a race for C4ISR superiority – a significant national advantage – and the ability to lead through innovation could determine who wins. C4ISR is an abbreviation created and used by the U.S. Department of Defense (US DoD), U.S. intelligence agencies, and U.S. allies which stands for “Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance. We are looking for a Program Engineering Manager (PEM) to support various programs in our Wayne NJ facility in our Adaptive Communications & Sensing (AC&S) Tactical Data Link (TDL) product line." That seems like About the role. Also maybe include "This position will be posted for at least 5 calendar days. The posting will remain active until the position is filled, or a qualified pool of candidates is identified." That's posting info, maybe not needed. We'll keep About the role as above. Responsibilities: combine "Specific Job Responsibilities Include, But Are Not Limited To" list and "Key Aspects Of This Role". Let's extract each bullet. From Specific Job Responsibilities: - Partner with the Program Manager, Chief Engineer and functional staff to develop and deliver products and systems that meet our customers’ needs. - Partner and collaborate across all the disciplines, functions, and business areas to effectively support engineering across the enterprise. - Meet cost, schedule and technical performance for projects through their life cycle. - Ensure preparation and approval of competitive engineering bids that are executable, meet established price-to-win targets, and grow the business. - Serve as overall customer (internal / external) engineering point of contact for the project. - Identify and support the development of critical skills and resources. - Develop and maintain measures related to engineering performance. - Ensure proper application of process based on the size and complexity of the project. - Establish goals, performance standards, budgets and staffing plans. - Improve processes and skills that accelerate program execution and improve quality. - Lead and develop others. - This position requires collaborating and interfacing with Engineering, Operations, Business Development, Contracts, Subcontracts, Finance, and Procurement functions within the company as well as with internal and external customers to ensure that the portfolio’s financial, schedule and technical objectives are met and that the highest level of customer satisfaction is achieved. From Key Aspects Of This Role: - Accountability for all aspects of program initiation, planning and execution (cost, schedule, technical performance, quality, customer engagement, etc.) and ensuring program commitments are met. - Responsibility and accountability to the Business for program execution, profitability, timeliness, and overall success. Make decisions that are cost effective to the company and ensures assigned projects meet financial commitments for orders, sales, profit and cash flow. - Creation of new business strategies and the development of strategic and financial plans - Understanding of life cycle management - Working with various contract types - Earned Value Management - Communication with clear, concise messaging to teams, internal leadership and customers We'll combine into a single ul. Requirements: Required Education, Experience, & Skills (education/experience). Let's extract: - Requires qualified candidates to hold an active Secret security clearance. - Bachelor's Degree in Science, Engineering, or Math and 12+ years engineering development/production work experience or Master’s Degree with 8+ years of engineering development/production experience - Experience as a Cost Account Manager (CAM) in an Earned Value Management System (EVMS), program scheduling, task codes, program metrics, and staffing determination - Project engineering management including organizational design, planning, estimating, design management, and product verification. - Experience leading diverse multi-disciplinary teams in the solution of complex technical problems. - Demonstrated leadership skills (soft skills, strategic thinking, business acumen, building teams, building customer relationships, leading the entire engineering team). - Monitoring the project to ensure work scope, schedule, and budget are well defined, maintained, and met - Capable of leading a team in defining, generating, and reviewing project requirements and documentation - Performing or guiding technical studies to refine project requirements - Providing the coordination between resource managers/supervisors and the program team for staffing needs - Strong planning and organizational skills with the ability to diagnose, resolve complex problems and to develop improved methods to increase program efficiency. - Proven written and oral communication skills, including presentation skills. - Strong team building skills that enable collaboration and coordination within and across teams, functions, and other business units. - Strong presentation and organizational skills - Strong communication skills with ability to influence and shape the behavior and performance of teams executing complex requirements Note some overlap with skills; we can keep these under Requirements (education/experience) but many are skills. However we have separate Skills section; we could move skill statements to Skills. But the instruction: we should not invent or summarize away detail. We can keep them under Requirements; having Skills section maybe redundant but we can still include if we have specific skill content not already covered. However we might duplicate. Better to follow typical pattern: Requirements = education/experience; Qualifications = preferred; Skills = skill statements. Let's extract skill statements from required and preferred. From required: many skill statements: Demonstrated leadership skills, Strong planning and organizational skills, Proven written and oral communication skills, Strong team building skills, Strong presentation and organizational skills, Strong communication skills with ability to influence..., etc. From preferred: "5+ years’ experience as a Program Engineering Manager (PEM), Program Manager (PM), or Technical Project Manager", "Knowledge of defense contract types", "Experience in all the phases of the program life cycle", "Project Management Professional (PMP) certification", "Experience in developing product roadmaps", "Experience in proposal development activities and capturing new business", "Experience in structured problem solving with demonstrated ability to systematically determine root cause", "Domain Knowledge, UHF/VHF/HF communication solutions experience, including NSA certification", "Ability to obtain a Top Secret / SCI level of clearance". We could put those under Qualifications (preferred) and Skills (skill statements). But there is overlap. Simplify: We'll create sections: - About the role (overview) - Responsibilities (list) - Requirements (required education/experience/clearance) - Qualifications (preferred education/experience/skills/certifications) - Skills (key skill statements) maybe we can omit if we feel it's thin. But we have many skill statements; we could put them under Skills. But we need to avoid duplication: If we put skill statements under Skills, we should not also list them under Requirements or Qualifications. So we need to parse and allocate. Let's decide: Requirements: education, experience, clearance. - Requires active Secret security clearance. - Bachelor's Degree in Science, Engineering, or Math and 12+ years engineering development/production work experience OR Master’s Degree with 8+ years of engineering development/production experience. That's it for requirements (education/experience/clearance). We'll not include skill statements here. Qualifications: preferred education/experience/skills/certifications. - 5+ years’ experience as a Program Engineering Manager (PEM), Program Manager (PM), or Technical Project Manager - Knowledge of defense contract types - Experience in all the phases of the program life cycle - Project Management Professional (PMP) certification - Experience in developing product roadmaps - Experience in proposal development activities and capturing new business - Experience in structured problem solving with demonstrated ability to systematically determine root cause - Domain Knowledge, UHF/VHF/HF communication solutions experience, including NSA certification - Ability to obtain a Top Secret / SCI level