Anlyst, Procurement

We need to output HTML fragment with sections: About the role (maybe from description), Responsibilities, Qualifications (must have), Preferred qualifications (maybe combine?), Skills, Benefits, Pay, Schedule. Must include only sections with real content. We need to parse the posting. First, remove boilerplate: Date Posted, Country, Location, Position Role Type, etc. Also remove EEO, privacy policy, etc. We need to preserve substantive info. Let's extract sections: - About the role: The paragraph starting "At Raytheon, the foundation...". Also maybe "What You Will Do:" is responsibilities. - Responsibilities: bullet list after "What You Will Do:" includes many items. - Qualifications You Must Have: bullet list? It says "This role typically requires a bachelor’s degree. U.S. Person (U.S. citizen, permanent resident, refugee or asylee) or eligible to obtain necessary export authorizations required." plus link. So we can put that as prose. - Qualifications We Prefer: many bullet-like sentences. - Skills: maybe derived from preferred qualifications? Could treat as Skills section. - Benefits: "As part of our commitment..." includes benefits list: 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, holidays. Also mention short-term/long-term incentive compensation programs. - Pay: "The salary range for this role is 57,200 USD - 108,800 USD." - Schedule: Not explicitly given. There's mention of flexible work schedules under benefits, but not a schedule. No explicit schedule like full-time, part-time. So we should not create Schedule section unless posting actually states it. It does not. So omit. - Also maybe "Position Role Type: Remote" but we shouldn't put as heading; could be in a short paragraph metadata. We need to avoid repeating job title as heading (not given). Also avoid Job ID/requisition numbers. We need to output only HTML fragment, no /. Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. Let's craft sections:

  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.

  Responsibilities

  • Lead supplier negotiations on price, schedule, and terms & conditions.
  • Ensure compliance with FAR/DFARS, RTX terms, and export/import regulations.
  • Review Statements of Work (SOWs) and develop PIAs/NDAs.
  • Manage proposal and quotation activities, documentation, and compliance packages.
  • Identify, qualify, and perform due diligence on suppliers; seek alternates as needed.
  • Conduct cost, price, and best-value analysis to support sourcing decisions.
  • Oversee post-award supplier performance in alignment with business unit directives.
  • Drive supplier engagement to meet critical program milestones.
  • Balance strategic planning with daily tactical execution.
  • Collaborate cross-functionally with EXIM, Legal, and senior leadership.

  Qualifications (Required)

  This role typically requires a bachelor’s degree. U.S. Person (U.S. citizen, permanent resident, refugee or asylee) or eligible to obtain necessary export authorizations required. https://www.ecfr.gov/current/title-22/chapter-I/subchapter-M/part-120/subpart-C/section-120.62

  We could also include "U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract." That's earlier. Should we include? Yes, it's substantive. So combine. Thus:

  U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract. This role typically requires a bachelor’s degree. U.S. Person (U.S. citizen, permanent resident, refugee or asylee) or eligible to obtain necessary export authorizations required. link

  Preferred Qualifications

  • Experience with and knowledge of SAP procurement software tools, such as PRISM and APEX
  • Experience with purchase order management, including documentation, and contract negotiation
  • Experience with internal, across the businesses; external with suppliers
  • Experience with supplier negotiations (price, schedules and terms & conditions) with the proficiency to perform and comprehend price analyses, source selection/justification
  • Proficient in RTX' supply chain systems and SAP PRISM purchasing tools
  • Skilled at engaging senior management, cross-functional teams, and program leaders on key business matters
  • Strong communicator with excellent time management, adaptability, and leadership presence
  • Able to make timely decisions, manage multiple priorities, and perform in a fast-paced, dynamic environment
  • Experienced in negotiating terms and conditions, with the ability to coach others in developing negotiation skills
  We could also treat some as Skills but it's okay.

  Skills

  But we already have preferred qualifications covering skills. The instruction: Prefer a few substantive sections over many thin ones. Could combine Preferred Qualifications and Skills into one section called "Preferred Qualifications & Skills". But we need to decide. We have sections: About the role, Responsibilities, Qualifications (Required), Preferred Qualifications, Benefits, Pay. We need Benefits section. Extract benefits: "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 not benefit but process. Then: "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: "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." Thus benefits list. We'll create

  Benefits

  with
  list. Pay section:

  Pay

  The salary range for this role is 57,200 USD - 108,800 USD.

  We should not include Schedule. We also might include a short paragraph for metadata like remote etc. Could be placed under About the role or separate small paragraph but not as heading. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include a short paragraph for location/remote etc. Perhaps after About the role we add a p: "Position: Remote (U.S.-based)." But we need to preserve all substantive information; location is US-AZ-REMOTE (Remote). Also Position Role Type: Remote U.S. Citizen, etc. We could include that in a short p. Let's add after About the role:

  Position: Remote (U.S.-based). U.S. citizenship required.

  But we already have citizenship in qualifications. Might duplicate. Better to include location/remote info: "Location: Remote (U.S.-based)." Keep it short. We must not repeat job title as heading (none). Ensure we don't include boilerplate like EEO, privacy policy, etc. Now produce final HTML. Check for any missing substantive info: The description about Raytheon's businesses, 185,000 employees, etc. That's part of About the role? It's after "What We Offer". Actually after "What We Offer Our values drive..." includes description of RTX corporation. That is substantive about company. Should we include? It's about the company, not the role. Might be considered part of "About the role" or maybe a separate section "About RTX". But instruction: Prefer few substantive sections over many thin ones. Could include that in About the role paragraph as additional sentences. Thus About the role paragraph could be longer: include the mission statement plus company description. Let's combine: At Raytheon, the foundation... (first paragraph). Then second paragraph: "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." We'll include that. Now ensure we didn't include any boilerplate like "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..." That's not a benefit but process; maybe we can include under a small note but not required. Could drop as it's not a benefit but still substantive? It's about interview process. The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those; it's about interview process. Might be considered application instructions? It's about interview steps. Could be considered part of application instructions. Safer to drop. Thus we omit that sentence. Now final HTML. Check for any other substantive: "The salary range provided is a good faith estimate representative of all experience levels." That's extra detail about pay. Should we include? It's substantive about pay. We can add to Pay section:

  The salary range for this role is 57,200 USD - 108,800 USD. The salary range provided is a good faith estimate representative of all experience levels.

  Also "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." That's also about pay/offer. Could add to Pay section. Thus Pay section includes multiple sentences. Now Benefits: include the list and also mention incentive compensation programs. Thus Benefits
  list of 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, holidays. Then another
  for incentive compensation? Could combine as separate
  but we can just add a sentence after list