Program Cost Control Principal Specialist

We need to output HTML fragment with sections: headings

for sections like 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 metadata like Job ID, etc. Must remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting. Key sections: - About the role: description of company and role? The posting includes: "At RTX, the world's largest aerospace and defense company..." and "Join us and help shape the future of aerospace and defense." Also "What You Will Do" list. Thus we can have an

About the role

with paragraphs summarizing company description and role purpose. - Responsibilities: list of duties under "What You Will Do". Use

• . - Qualifications: includes "Qualifications You Must Have:" and "Qualifications We Prefer:" maybe combine into Requirements? The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. Likely we can have Requirements (mandatory) and Qualifications (preferred) or Skills. But we must not create sections with filler. We have both mandatory and preferred qualifications. Could put mandatory under Requirements, preferred under Qualifications, and maybe Skills under Qualifications? However we have a separate Skills heading possible. But we have skills like Excel, SAP, EVM etc. Those are qualifications/skills. Could put them under Skills. Better: Use Requirements for mandatory qualifications (citizenship, degree, experience, etc). Use Qualifications for preferred qualifications (communication, PMX, etc). Use Skills for technical skills (Excel, SAP, EVM, etc). But we must avoid duplication. Let's extract: Mandatory qualifications (You Must Have): - Typically requires a Bachelor's Degree in Finance, Accounting, Economics, or related field and a minimum of 5 years of relevant experience OR an Advanced Degree in related field and minimum of 3 years experience. - Experience using Microsoft Office applications, including Excel (pivot tables, advanced formulas, and data analysis), PowerPoint, and Word to analyze data and prepare reports and presentations. - Experience with financial systems, including SAP, SAP Business Warehouse (or equivalent). - Experience with Earned Value Management (EVM), including SPI, CPI, TCPI, IEAC, VAC, EAC analysis, or equivalent financial forecasting methodologies. - Experience working with cross-functional organizations, including Contracts, Operations, Engineering, Supply Chain, and other business functions. - U.S. citizenship is required because access to certain financial management systems is restricted by government contractual requirements. Preferred qualifications (We Prefer): - Experience preparing written and verbal communications for stakeholders at multiple organizational levels, including summarizing and presenting information. - Experience with PMX/PMTools and the RPlan forecasting system. - Experience analyzing data to identify issues, evaluate alternatives, and support resolution using established processes and available information. - Experience reviewing work products for accuracy, completeness, and consistency before submission. - Active DoD Secret or Top Secret security clearance. Skills: maybe the technical skills like Excel, SAP, EVM etc could be under Skills. But they already appear in mandatory qualifications. Could move them to Skills to avoid duplication. However we must preserve all substantive info; moving is okay as long as not lost. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Moving is fine as long as we keep the detail. We could have sections: About the role, Responsibilities, Requirements (citizenship, degree, experience), Qualifications (preferred), Skills (technical), Benefits, Pay, Schedule. Check if we have Benefits: The posting includes "What We Offer:" describing total rewards package, parental leave, flexible work schedules, achievement awards, educational assistance, child/adult backup care, etc. Also later: "Hired applicants may be eligible for benefits, including but not limited to, medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, and holidays." Also mention incentive compensation. So we have benefits content. Pay: The posting includes "The salary range for this role is 86,800 USD - 165,200 USD." Also mention that salary range is good faith estimate. So we have Pay. Schedule: The posting includes "Hybrid: Employees who are working in Hybrid roles will work regularly both onsite and offsite. Ratio of time working onsite will be determined in partnership with your leader." Also mention interview steps may be in-person. So we have Schedule (Hybrid). Also maybe mention "Hybrid" role type earlier. Thus we can include sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Now we need to strip boilerplate: Remove Date Posted, Country, Location, Position Role Type, Security Clearance Type/Status, etc. Also remove "Learn More & Apply Now!", "Privacy Policy and Terms", EEO statements, etc. Also remove "As part of our commitment..." about interview process? That's maybe part of schedule? Could keep as part of Schedule? It's about interview process, not job schedule. Might be considered boilerplate? It's about hiring process; maybe we can keep as part of Schedule? But it's not about work schedule. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The interview process statement is not exactly application instructions but could be considered part of hiring process. Safer to remove it. Also remove "Hybrid: Employees who are working in Hybrid roles will work regularly both onsite and offsite. Ratio of time working onsite will be determined in partnership with your leader." That's schedule info, keep. Also remove "The salary range provided is a good faith estimate representative of all experience levels." Keep as part of Pay. Also remove "Specific benefits are dependent upon the specific business unit as well as whether or not the position is covered by a collective-bargaining agreement." Keep as part of Benefits. Also remove "Hired applicants may be eligible for annual short-term and/or long-term incentive compensation programs depending on the level of the position and whether or not it is covered by a collective-bargaining agreement." Keep as part of Benefits (incentive). Also remove "Payments under these annual programs are not guaranteed and are dependent upon a variety of factors including, but not limited to, individual performance, business unit performance, and/or the company’s performance." Keep as part of Benefits. Also remove "This role is a U.S.-based role. If the successful candidate resides in a U.S. territory, the appropriate pay structure and benefits will apply." Could keep as part of Pay or Benefits? It's about pay structure; maybe keep in Pay. Also remove "RTX anticipates the application window closing approximately 40 days from the date the notice was posted. However, factors such as candidate flow and business necessity may require RTX to shorten or extend the application window." That's application instruction; remove. Also remove EEO statements. Now craft HTML. We'll need

  About the role

  then

  paragraphs. Let's write About the role: combine company description and role purpose. Paragraph 1: "At RTX, the world's largest aerospace and defense company, 185,000 great minds are united by purpose and inspired to make a difference solving the world’s most complex problems. With our three market leading businesses, world-class operations and investments in research and development, we offer capabilities and opportunity no one else can. Together, we push the boundaries of known science and find new ways to connect and protect our world. Raytheon brings the strength of more than 100 years of experience and renowned engineering expertise to meet the needs of today’s mission and stay ahead of tomorrow’s threat. We deliver solutions that help our nation and allies defend freedoms and deter aggression, creating a safer, more secure world." Paragraph 2: "Join us and help shape the future of aerospace and defense." Maybe also include brief role purpose: "Support program financial execution by working with Program Business Managers, Integrated Product Team (IPT) Leads, Program Managers, and Finance teams." But that's responsibilities; we can keep there. Now Responsibilities: list from "What You Will Do". Items: - Support program financial execution by working with Program Business Managers, Integrated Product Team (IPT) Leads, Program Managers, and Finance teams. - Support program cost reporting, Earned Value Management (EVM), and financial analysis activities. - Prepare internal cost reports and analyze cost data, financial planning systems, and program performance metrics. - Compile quarterly Estimate at Completion (EAC) submissions for review by program and finance leadership. - Prepare monthly cost and performance analysis supporting Earned Value reporting. - Analyze financial performance at the functional and product level, including variances to budget, baseline, and EAC. - Process approved Baseline Change Requests (BCRs) and support the Latest Revised Estimate (LRE) process using established financial tools. - Use PRISM (Material Requirements Planning system) to analyze grouping, pegging, and distribution impacts for material cost analysis. - Respond to billing, funding, financial data inquiries, and ad hoc financial analysis requests. - Support the Advanced Products & Solutions (APS) business area within the Advanced Open Integrated Solutions (AOIS) Finance team as a Principal Specialist, Program Cost Controls (Cost, Schedule, and Control Analyst). Make each as

• . Now Requirements (mandatory): list: - Bachelor's Degree in Finance, Accounting, Economics, or a related field and a minimum of 5 years of relevant experience OR an Advanced Degree in related field and minimum of 3 years experience. - Experience using Microsoft Office applications, including Excel (pivot tables, advanced formulas, and data analysis), PowerPoint, and Word to analyze data and prepare reports and presentations. - Experience with financial systems, including SAP, SAP Business Warehouse (or equivalent). - Experience with Earned Value Management (EVM), including Schedule Performance Index (SPI), Cost Performance Index (CPI), To-Complete Performance Index (TCPI), Independent Estimate at Completion (IEAC), Variance at Completion (VAC), and Estimate at Completion (EAC) analysis, or equivalent financial forecasting methodologies. - Experience working with cross-functional organizations, including Contracts, Operations, Engineering, Supply Chain, and other business functions. - U.S. citizenship is required because access to certain financial management systems is restricted by government contractual requirements. Now Qualifications (preferred): list: - Experience preparing written and verbal communications for stakeholders at multiple organizational levels, including summarizing and presenting information. - Experience with PMX/PMTools and the RPlan forecasting system. - Experience analyzing data to identify issues, evaluate alternatives, and support resolution using established processes and available information. - Experience reviewing work products for accuracy, completeness, and consistency before submission. - Active DoD Secret or Top Secret security clearance. Now Skills: maybe we can list technical skills: Excel (pivot tables, advanced formulas, data analysis), PowerPoint, Word, SAP, SAP Business Warehouse, PRISM (Material Requirements Planning system), EVM metrics (SPI, CPI, TCPI, IEAC, VAC, EAC), Baseline Change Requests (BCRs), Latest Revised Estimate (LRE) process, financial tools. But many of these already appear in Requirements; we could avoid duplication by not having Skills section, but we need to decide. The instruction: "Prefer a few substantive sections over many thin ones." Having Skills may be thin if we just repeat. Could combine technical skills into Requirements or Qualifications. However we already have Requirements covering many technical skills. Could keep Skills empty? Not allowed. So maybe we omit Skills section entirely, and instead include technical skills under Requirements and Qualifications. That would reduce number of sections. The instruction says we can use those headings but only when posting has real specific content. It doesn't require us to use all headings. So we can