Senior Analyst, Procurement (Hybrid)
About the role
with. - Responsibilities: "What You Will Do" bullet list: Collaborate with key stakeholders to ensure SAP reflects the latest status, delivery dates, and facilitate the Procurement‑to‑Pay process. Maintain performance metrics for assigned suppliers on past due deliveries, supplier purchase order acknowledgements, and status updates. Manage stakeholder escalations on corrective actions and delivery expedites. We can put as
- ...
Qualifications
with maybe two subsections? But spec says use for section headings, and - for any list of duties/requirements/benefits. So we can have
Qualifications
then - ... must have ...
- ... preferred ...
maybe separate lists? Could do two but spec says use - for any list. Could have separate
for Must Have and Preferred with headings? But headings only . Could embed text inside
- . Simpler: one
with items each containing both must have and preferred separated by semicolons? Might lose clarity. Better: two under same heading? Might be okay.
We'll do:
Qualifications
Must Have
but we cannot use h4 (only h3 allowed). So we can't use other headings. So we need to keep within sections only. So we can have a single Qualifications
then a paragraph describing must have and preferred? But spec says use - for any list of duties/requirements/benefits. So we need to use
for qualifications list. We can embed both must have and preferred as separate list items, maybe with bold text? But we cannot add extra tags besides those allowed? The instruction didn't forbid other tags like or . It only said use for section headings, - for any list,
for prose. It didn't forbid other inline tags. Safer to stick to those only. So we can have two
sections: one for Must Have, one for Preferred, each preceded by a describing? But that would be extra
not a list. Could do:
Qualifications
Must Have:
...
Preferred:
...
But that uses which is not prohibited. Might be okay. However, to be safe, we could just include both in prose within . But spec says use
- for any list of duties/requirements/benefits. Qualifications is a list of requirements, so we should use
. Could combine must have and preferred into one list with each item containing both? Might be ambiguous.
Better: Provide two separate each preceded by a indicating category. That seems acceptable.
- Benefits: "What We Offer" paragraph: robust total rewards package 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.
We can put as
Benefits
- ...
maybe each benefit as list item.
- Pay: "The salary range for this role is 68,900 USD - 131,100 USD." Also mention that it's a good faith estimate etc. We should include that info. So Pay
The salary range for this role is 68,900 USD - 131,100 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.
- Schedule: Hybrid info: "Work Location: This is a hybrid role, eligible candidates must reside within commuting distance of Richardson, TX, Farmington, CT, Cedar Rapids, IA, Andover, MA, McKinney, TX or Tucson, AZ. Please consider the following role type definition as you apply for this role: 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. 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."
We can put under Schedule
... hybrid details ...
We should not include metadata like Date Posted, Country, Location, Position Role Type, U.S. Citizen requirement? Actually citizenship requirement is substantive: "U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract." That's a requirement, should be included under Qualifications maybe as a separate item. Also Security Clearance Type: None/Not Required etc. That's not needed? It's minor metadata but could be included as a short p. However spec says fold minor metadata into a short or drop it. Citizenship requirement is not minor; it's a requirement. So include in Qualifications list.
Security clearance not required maybe minor; could drop.
We also have info about application window closing approx 40 days etc. That's metadata; could drop or short p. Probably drop.
EEO boilerplate drop.
Now construct HTML.
We'll output:
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. Join us and help shape the future of aerospace and defense. The following position is to join the Enterprise Services Procurement team: ES-Procurement is hiring a Senior Procurement Analyst to support our shared services enterprise procurement team. Our team is comprised of procurement teams responsible for buying materials and services across a range of commodities from components and hardware through complex technical and facilities services. The procurement team manages and facilitates procurement from sourcing through payment to support our business units and corporate entities. Our ideal candidate will be able to manage multiple priorities, facilitate cross functional discussions, negotiate best price and delivery, and develop lasting relationships with the supply base.
Responsibilities
- Collaborate with key stakeholders to ensure SAP reflects the latest status, delivery dates, and facilitate the Procurement‑to‑Pay process.
- Maintain performance metrics for assigned suppliers on past due deliveries, supplier purchase order acknowledgements, and status updates.
- Manage stakeholder escalations on corrective actions and delivery expedites.
Qualifications
Must Have:
- University Degree and a minimum of 2 years prior relevant experience or an Advanced Degree in a related field and 1+ years of experience.
- 2+ years of experience with SAP, APEX, PRISM, ARIBA, and SRM.
- Experience with MS Office (Excel, PowerPoint, Word) and Adobe.
- U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract.
Preferred:
- CORE Apprentice and/or Champion Certification.
- Experience managing workload and prioritizing tasks.
- Attention to detail and focus on data accuracy and analysis.
- Experience working with stakeholders that support the procurement‑to‑pay process.
Benefits
- Robust total rewards package with compensation; healthcare, wellness, retirement and work/life benefits.
- Career development and recognition programs.
- Parental (including paternal) leave.
- Flexible work schedules.
- Achievement awards.
- Educational assistance.
- Child/adult backup care.
Pay
The salary range for this role is 68,900 USD - 131,100 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.
Schedule
This is a hybrid role; eligible candidates must reside within commuting distance of Richardson, TX, Farmington, CT, Cedar Rapids, IA, Andover, MA, McKinney, TX, or Tucson, AZ. Hybrid employees work regularly both onsite and offsite, with the onsite ratio determined in partnership with the leader. 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.
Check for any missing substantive info: The description about "Work Location: This is a hybrid role, eligible candidates must reside within commuting distance of Richardson, TX, Farmington, CT, Cedar Rapids, IA, Andover, MA, McKinney, TX or Tucson, AZ." included. Also mention about "Please consider the following role type definition as you apply for this role: Hybrid: Employees who are working
Qualifications
then- ... must have ...
- ... preferred ... maybe separate lists? Could do two
- for any list. Could have separate
- for Must Have and Preferred with headings? But headings only
- . Simpler: one
- with items each containing both must have and preferred separated by semicolons? Might lose clarity. Better: two
- for any list of duties/requirements/benefits. So we need to use
- for qualifications list. We can embed both must have and preferred as separate list items, maybe with bold text? But we cannot add extra tags besides those allowed? The instruction didn't forbid other tags like or . It only said use
- for any list,
for prose. It didn't forbid other inline tags. Safer to stick to those only. So we can have two
- sections: one for Must Have, one for Preferred, each preceded by a
- for any list of duties/requirements/benefits. Qualifications is a list of requirements, so we should use
- . Could combine must have and preferred into one list with each item containing both? Might be ambiguous.
Better: Provide two separate
- ...
- Collaborate with key stakeholders to ensure SAP reflects the latest status, delivery dates, and facilitate the Procurement‑to‑Pay process.
- Maintain performance metrics for assigned suppliers on past due deliveries, supplier purchase order acknowledgements, and status updates.
- Manage stakeholder escalations on corrective actions and delivery expedites.
- University Degree and a minimum of 2 years prior relevant experience or an Advanced Degree in a related field and 1+ years of experience.
- 2+ years of experience with SAP, APEX, PRISM, ARIBA, and SRM.
- Experience with MS Office (Excel, PowerPoint, Word) and Adobe.
- U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract.
- CORE Apprentice and/or Champion Certification.
- Experience managing workload and prioritizing tasks.
- Attention to detail and focus on data accuracy and analysis.
- Experience working with stakeholders that support the procurement‑to‑pay process.
- Robust total rewards package with compensation; healthcare, wellness, retirement and work/life benefits.
- Career development and recognition programs.
- Parental (including paternal) leave.
- Flexible work schedules.
- Achievement awards.
- Educational assistance.
- Child/adult backup care.
- each preceded by a
indicating category. That seems acceptable. - Benefits: "What We Offer" paragraph: robust total rewards package 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. We can put as
Benefits
Pay
The salary range for this role is 68,900 USD - 131,100 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.
- Schedule: Hybrid info: "Work Location: This is a hybrid role, eligible candidates must reside within commuting distance of Richardson, TX, Farmington, CT, Cedar Rapids, IA, Andover, MA, McKinney, TX or Tucson, AZ. Please consider the following role type definition as you apply for this role: 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. 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." We can put underSchedule
... hybrid details ...
We should not include metadata like Date Posted, Country, Location, Position Role Type, U.S. Citizen requirement? Actually citizenship requirement is substantive: "U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract." That's a requirement, should be included under Qualifications maybe as a separate item. Also Security Clearance Type: None/Not Required etc. That's not needed? It's minor metadata but could be included as a short p. However spec says fold minor metadata into a shortor drop it. Citizenship requirement is not minor; it's a requirement. So include in Qualifications list. Security clearance not required maybe minor; could drop. We also have info about application window closing approx 40 days etc. That's metadata; could drop or short p. Probably drop. EEO boilerplate drop. Now construct HTML. We'll output:
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. Join us and help shape the future of aerospace and defense. The following position is to join the Enterprise Services Procurement team: ES-Procurement is hiring a Senior Procurement Analyst to support our shared services enterprise procurement team. Our team is comprised of procurement teams responsible for buying materials and services across a range of commodities from components and hardware through complex technical and facilities services. The procurement team manages and facilitates procurement from sourcing through payment to support our business units and corporate entities. Our ideal candidate will be able to manage multiple priorities, facilitate cross functional discussions, negotiate best price and delivery, and develop lasting relationships with the supply base.
Responsibilities
Qualifications
Must Have:
Preferred:
Benefits
Pay
The salary range for this role is 68,900 USD - 131,100 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.
Schedule
This is a hybrid role; eligible candidates must reside within commuting distance of Richardson, TX, Farmington, CT, Cedar Rapids, IA, Andover, MA, McKinney, TX, or Tucson, AZ. Hybrid employees work regularly both onsite and offsite, with the onsite ratio determined in partnership with the leader. 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.
Check for any missing substantive info: The description about "Work Location: This is a hybrid role, eligible candidates must reside within commuting distance of Richardson, TX, Farmington, CT, Cedar Rapids, IA, Andover, MA, McKinney, TX or Tucson, AZ." included. Also mention about "Please consider the following role type definition as you apply for this role: Hybrid: Employees who are working
describing? But that would be extra
not a list. Could do:
Qualifications
Must Have:
- ...
Preferred:
- ...
. But spec says use
- for any list of duties/requirements/benefits. Qualifications is a list of requirements, so we should use
for section headings,
- for any list,
- under same heading? Might be okay.
We'll do:
Qualifications
Must Have
but we cannot use h4 (only h3 allowed). So we can't use other headings. So we need to keep withinsections only. So we can have a single
Qualifications
then a paragraph describing must have and preferred? But spec says use - for any list of duties/requirements/benefits. So we need to use
. Could embed text inside
- . Simpler: one
- but spec says use