Program Cost Controls Lead
On-siteFinanceFull-time
We need to output HTML fragment with sections: About the role (maybe from description), Responsibilities, Requirements, Qualifications, Skills?, Benefits, Pay, Schedule. Must include only sections with real content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Must preserve all substantive info.
We need to parse the posting.
Key sections:
- Date posted, country, location, role type: Onsite. This is metadata; we can fold into a short
maybe.
- Position Role Type: Onsite. Not needed as heading.
- U.S. Citizen, U.S. Person, or Immigration Status Requirements: The ability to obtain and maintain a U.S. government issued security clearance is required. U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance. Security Clearance Type: DoD Clearance: Secret. Security Clearance Status: Active and existing security clearance required after day 1.
- Then a paragraph about RTX (company description). That's "About the role"? Actually it's about company. Could be "About the role" or "About RTX". The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" containing the company description and maybe location.
- "What You Will Do:" list of duties. That's Responsibilities.
- "Qualifications You Must Have:" list. That's Requirements (or Qualifications). They also have "Qualifications We Prefer:" which could be Skills or Preferred Qualifications. We can treat as "Qualifications" (maybe split into Required and Preferred). But we need to follow headings: Requirements, Qualifications, Skills. Could map: Requirements = mandatory qualifications; Qualifications = preferred qualifications; Skills = maybe specific skills (like SAP, EVM, etc). However we have both mandatory and preferred qualifications listed. We could put mandatory under "Requirements", preferred under "Qualifications". Then we could also have a "Skills" section for tools like SAP, EVM, etc. But we might avoid duplication.
Better: Use "Requirements" for mandatory qualifications (degree, experience, citizenship, clearance). Use "Qualifications" for preferred qualifications (SAP, EVM, FAR, etc). Use "Skills" maybe not needed if we already covered. But we could still include a Skills section for specific technical skills: SAP financial tools, Earned Value Management, MRP, FAR, CAS, GAAP, etc. However those are already in preferred qualifications. To avoid duplication, we could combine.
The instruction: Prefer a few substantive sections over many thin ones. So maybe we have: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Schedule maybe not present (no schedule details besides Onsite). There's mention "Onsite: Employees who are working in onsite roles will work primarily onsite." That's schedule info (onsite). Could include Schedule section with that statement.
Benefits: "What We Offer:" paragraph describing total rewards package, list some benefits. 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 salary range for this role is 118,300 USD - 224,900 USD." Also mention incentive compensation not guaranteed. So we can include Pay section with salary range and note about incentive.
Schedule: Onsite statement.
We must not include boilerplate like EEO, privacy policy, application window, etc. Also remove duplicated lines like "Clearance Information: Clearance Information:" etc. Also remove "Learn More & Apply Now!" etc.
We must preserve all substantive information. So we need to include the company description paragraph, the responsibilities bullet list, the qualifications mandatory, qualifications preferred, benefits, pay, schedule.
We must not invent or summarize away detail. Must keep details like degree, years experience, etc.
We must not include placeholders like "commensurate with experience". Not present.
We must not repeat job title.
We must not include Job ID/requisition numbers.
We must not include application instructions like "Learn More & Apply Now!" etc.
We must not include cookie/navigation/legal/EEO etc.
Thus final HTML:
About the role
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.
Maybe also include location and onsite? Could add a short p: "Location: US-CA-GOLETA-H01 ~ 6380 Hollister Ave ~ BLDG H01, Goleta, CA. Position is onsite."
But location is metadata; we can fold into short p.
Better: after About the role, we could have a p with location and onsite.
But we already have Schedule section for onsite. So location maybe not needed.
But we need to preserve all substantive info; location is substantive. So we should include it somewhere. Could add a p after About the role: "Location: US-CA-GOLETA-H01 ~ 6380 Hollister Ave ~ BLDG H01, Goleta, CA. Position is onsite."
But then Schedule section will repeat onsite; maybe we can combine location and schedule into one p under About the role, and Schedule section could be omitted if we consider schedule covered. However instruction: include a section ONLY when posting has real, specific content for it. Schedule content: "Onsite: Employees who are working in onsite roles will work primarily onsite." That's specific. So we should have Schedule section.
Thus we can keep location in About the role or separate p. Let's put location in About the role p.
Now Responsibilities: list bullet points from "What You Will Do:".
We need to convert each sentence into
. Let's extract:
- Perform forecasting, risk identification, and financial planning activities.
- Perform cost and schedule analysis.
- Coordinate the development of quarterly Estimates at Completion (EACs).
- Provide financial analysis and recommendations to Program Teams and Leads.
- Prepare financial charts for Program Management Reviews, monthly operating reviews, financial overviews, and other required reporting.
- Perform cost, schedule, financial analysis and reporting, and funding planning activities using standard company tools and processes.
- Implement and maintain Earned Value Management (EVM) processes.
- Support the development and delivery of Contract Data Requirements Lists (CDRLs).
- Establish and maintain program logs, including Work Authorization, Contract Modification Logs, and Risks & Opportunities (R&Os).
Make sure we keep all.
Now Requirements (mandatory qualifications): from "Qualifications You Must Have:":
- Typically requires a bachelor's degree in Accounting, Finance, Business, or a related field and a minimum of 8 years of relevant experience; or an advanced degree in a related field and a minimum of 5 years of relevant experience.
- Experience working with cross-functional teams, including Contracts, Operations, Engineering, and Supply Chain, in program development and execution.
- Experience using Microsoft Office applications, including Excel, Word, and PowerPoint.
- Ability to obtain and maintain a U.S. government security clearance.
- U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance.
Also earlier we had security clearance specifics: DoD Clearance: Secret, Active and existing security clearance required after day 1. Should we include that? It's part of requirements. Yes, we should include those details. So add:
- Must have an active and existing DoD Secret security clearance (required after day 1).
But we need to preserve exact wording: "Security Clearance Type: DoD Clearance: Secret Security Clearance Status: Active and existing security clearance required after day 1." We can phrase as bullet: "Active and existing DoD Secret security clearance required after day 1."
Now Qualifications (preferred): from "Qualifications We Prefer:" list:
- Experience using SAP financial tools or systems.
- Experience with Earned Value Management (EVM).
- Experience with manufacturing or Material Requirements Planning (MRP) in the aerospace and defense industry.
- Working knowledge of Federal Acquisition Regulations (FAR), Cost Accounting Standards (CAS), and Generally Accepted Accounting Principles (GAAP).
- Experience identifying, analyzing, and resolving program or financial issues.
- Experience managing multiple priorities and meeting established deadlines.
- Experience implementing process improvements.
- Experience communicating financial and program information to stakeholders at multiple organizational levels.
- Prior Program Controls experience.
- Active security clearance.
Note: Active security clearance already in requirements; but it's also listed as preferred. We can keep it but maybe duplicate; but we should preserve all substantive info, even if duplicate. However we might avoid duplication by noting it's already required. But to preserve all info, we could include it but maybe note it's also preferred. However duplication may be okay but could be considered redundant. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not inventing or summarizing away; it's preserving. So we can keep duplicate.
Now Benefits: from "What We Offer:" and later benefits list.
We need to capture:
- total rewards package that goes above and beyond with compensation; healthcare, wellness, retirement, and work/life benefits; career development and recognition programs.
- Some of the benefits we offer include parental (including paternal) leave, flexible work schedules, achievement awards, educational assistance, and child/adult backup care.
- 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.
- 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. 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.
We should keep all.
Now Pay: salary range and note about incentive compensation.
- The salary range for this role is 118,300 USD - 224,900 USD.
- The salary range provided is a good faith estimate representative of all experience levels.
- RTX considers several factors when extending an offer, including but not limited to, the role, function and associated responsibilities, a candidate’s work experience, location, education/training, and key skills.
- Hired applicants may be eligible for benefits... (already in benefits). For pay we might also mention incentive compensation programs not guaranteed. Already in benefits but could also be in pay. We'll keep in Pay: salary range and note that it's a good faith estimate; also mention that hired applicants may be eligible for annual short-term and/or long-term incentive compensation programs depending on level and collective bargaining, payments not guaranteed.
Now Schedule: Onsite statement.
- Onsite: Employees who are working in onsite roles will work primarily onsite. This includes all production and maintenance employees, as they are essential to the development of our products.
We could keep that