Manager, Procurement

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, remove boilerplate: Date posted, Country, Location, Position Role Type, Security Clearance Type/Status, etc. Also remove EEO, privacy policy, etc. We need to preserve substantive info. Let's extract sections: - About the role: The paragraph after "At Raytheon, the foundation..." up to "The selected individual will be responsible for leading procurement efforts...". Actually the "About the role" could be the introductory description. We'll create

About the role

with paragraphs. - Responsibilities: The bullet list under "What You Will Do:" includes many items. We'll put them in

• . - Requirements: There's "Qualifications You Must Have:" includes Bachelor's + 8 years or advanced degree + 5 years, U.S. citizenship required. Also maybe "Security Clearance Type: None/Not Required" but that's not a requirement; we can ignore. - Qualifications: There's "Qualifications We Prefer:" list. Could be separate section "Preferred Qualifications" but we only have headings list: Qualifications (maybe combine required and preferred?). The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements and Qualifications separate. We'll put required qualifications under Requirements, preferred under Qualifications. - Skills: Not explicitly listed but we could infer from preferred qualifications: Project planning and management skills, SAP, technical requirements, ITAR, FAR/DFARS, written contractual authorization, etc. Could be placed under Skills. However we should only create Skills section if posting has real specific content for it. The posting does list skills under "Qualifications We Prefer". Those are skills/experience. Could treat as Skills. But we already have Qualifications section for preferred qualifications. Might be better to put those under Qualifications. The instruction says we can have Skills section; but we need to decide based on content. Since there is explicit list of skills/experience, we could create Skills section. However we also have Qualifications We Prefer which is similar. To avoid duplication, we could combine required qualifications under Requirements, and preferred qualifications plus skills under Qualifications. Or we could split: Requirements = mandatory; Qualifications = preferred; Skills = maybe not needed. I'd follow the headings list: Requirements, Qualifications, Skills. We'll put mandatory under Requirements, preferred under Qualifications, and maybe specific technical skills under Skills (like SAP, ITAR, FAR/DFARS, etc). But the preferred list already includes those. Might be okay to put them under Qualifications and not have Skills. But we need to avoid empty sections. Let's see if we have content for Benefits, Pay, Schedule. Benefits: The posting includes "What We Offer" paragraph about values, then 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." That's specific benefits. So we can create Benefits section with that list. Pay: The posting includes "The salary range for this role is 107,500 USD - 204,500 USD." That's specific pay. So we create Pay section with that sentence. Schedule: Not mentioned explicitly. There's "flexible work schedules" under benefits but not a schedule definition. No explicit schedule like full-time, part-time, shift. So we should not create Schedule section. Now we need to ensure we don't repeat job title as heading. Not needed. We need to remove duplicated lines: e.g., U.S. citizenship appears multiple times; we should keep only once in Requirements. We need to preserve all substantive information; do not invent or summarize away detail. Let's craft HTML. Structure:

  About the role

  At Raytheon, the foundation of everything we do is rooted in our values and a higher calling – to help our nation and allies defend freedoms and deter aggression. We bring 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. Our team solves tough, meaningful problems that create a safer, more secure world. Operations and Supply Chain (OSC) has an excellent opportunity to join our energetic, and collaborative environment in support of the Naval Power (NP) procurement team. The selected individual will be responsible for leading procurement efforts in support of multiple programs within the Product Support business area.

  Then Responsibilities:

  Responsibilities

  • Issue and conflict resolution of medium/high complexity in accordance with all regulatory (FAR/DFAR) and corporate compliance requirements for various subcontract types (Cost Types, Firm Fixed price, Time & Materials)
  • Nurture professional business relationships with first tier subcontractors
  • Provide comprehensive Supply Chain support for gate/metrics reviews
  • Perform procurement and supplier management activities in support of U.S. Government and Commercial contracts. (Issue RFQs/RFPs, negotiations, supplier management)
  • Administer and manage high dollar and complex material and service procurements (PO placement) and subcontracts
  • Utilize source selection techniques, compile, and analyze data to perform price analyses, conduct negotiations (including terms and conditions) and identify supplier risks.
  • Ensure that requirements (prime contract, quality, terms, and conditions) are properly communicated to suppliers and manage supplier performance to cost, schedule, and quality requirements.
  • Work closely with the program office to identify solutions to sourcing issues that require ingenuity, creativity, and innovation.
  • Monitor procurement reports and help drive performance to meet company metric targets.
  • Communicate clearly and be proactive in a very fast-paced environment.
  • Be flexible, innovative, work with speed and agility yet be thorough and compliant with government and Raytheon regulations, while successfully driving tasks to completion.
  • Assist in the training of peer procurement professionals as needed.
  Requirements:

  Requirements

  Typically requires a Bachelor’s and a minimum of 8 years prior relevant experience, or an Advance Degree in a related field and a minimum of 5 years’ experience. U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract.

  Qualifications (preferred):

  Qualifications

  • Bachelor’s or Masters’ degree in supply chain, business, engineering, or related field
  • Project planning and management skills (ex: MS Project, EVMS)
  • Experience in working with development type of procurement and major subcontracts
  • Experience in a SAP based environment
  • Experience with technical requirements of procured hardware and services – including Statement of Work (SOW) review
  • Familiarity with the International Traffic in Arms Regulations (ITAR)
  • Demonstrated knowledge / compliance with Federal Acquisition Regulations (FAR/DFARS)
  • Experience in written contractual authorization/vehicles (Cost Plus, Firm Fixed Price etc.) and experience assessing proposal compliance (FAR 15.4)
  Benefits:

  Benefits

  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.

  Pay:

  Pay

  The salary range for this role is 107,500 USD - 204,500 USD.

  We should not include Schedule. Check for any other substantive content: The "What We Offer Our values drive our actions..." paragraph about values could be part of About the role or maybe a separate section? But we already have About the role covering the intro. Could add a paragraph about values under About the role. However we already have a paragraph; we could extend it to include that values paragraph. Let's incorporate: After the first paragraph, we could add another paragraph about values. But we must not invent; we can include that content. Let's adjust About the role to include the values paragraph. Original text after the intro: "What We Offer Our values drive our actions, behaviors, and performance with a vision for a safer, more connected world. At RTX we value: Safety, Trust, Respect, Accountability, Collaboration, and Innovation. RTX Corporation is an Aerospace and Defense company that provides advanced systems and services for commercial, military and government customers worldwide. It comprises three industry-leading businesses – Collins Aerospace Systems, Pratt & Whitney, and Raytheon. Its 185,000 employees enable the company to operate at the edge of known science as they imagine and deliver solutions that push the boundaries in quantum physics, electric propulsion, directed energy, hypersonics, avionics and cybersecurity. The company, formed in 2020 through the combination of Raytheon Company and the United Technologies Corporation aerospace businesses, is headquartered in Arlington, VA." That's substantive; we can include in About the role. Thus About the role will have multiple paragraphs. Now ensure we didn't include any boilerplate like "As part of our commitment to maintaining a secure hiring process..." etc. That's about interview process; could be considered substantive? It's about hiring process; but it's not a section heading we have; we could maybe include it under About the role or maybe a separate section like "Hiring Process". But not in allowed headings; we could drop it as it's not required to preserve? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep that info somewhere. Where to put? Could add a paragraph under About the role or maybe a separate section like "Additional Information". But we only allowed specific headings; we could incorporate into About the role as it's still about the role/company. It's not boilerplate; it's about interview process. Let's include it as a paragraph in About the role. Also the sentence about "As part of our commitment to maintaining a secure hiring process, candidates may be asked to attend select steps of the interview process in-person at one of our office locations, regardless of whether the role is designated as on-site, hybrid or remote." That's substantive. Also the sentence about "RTX anticipates the application window closing approximately 40 days from the date the notice was posted." That's also substantive; maybe we could put under About the role or a separate section like "Application Timeline". Not in headings; we could add to About the role. Also the EEO statements etc are boilerplate to remove. Thus we need to incorporate those substantive bits. Let's gather all substantive paragraphs not covered: - Intro about Raytheon values and mission (we have) - Description of OSC opportunity and role (we have) - The "What We Offer Our values drive..." paragraph (we can add) - The secure hiring process sentence. - The application window sentence. - The "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." That's also substantive; maybe include in Pay or About the role. Could add to Pay section as a note. - The "Hired applicants may be eligible for annual short-term and/or long-term incentive compensation programs..." That's also substantive; could be part of Benefits or Pay. We'll add to Benefits maybe as extra sentence. - The "Payments under these annual programs are not guaranteed..." also substantive; include