Advisor II, Procurement Contracts - (US Only)
Catholic Relief Services · United States · 1 mo ago
RemoteRemotePurchasingFull-time
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 if posting has real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive content.
We need to parse the job description.
Key sections:
- Job Summary: description paragraph.
- Roles And Key Responsibilities: bullet list of responsibilities.
- Knowledge, Skills, And Abilities: bullet list.
- Qualifications: Basic Qualifications and Preferred Qualifications.
- What We Offer: Benefits description.
- About Us: description.
- About The Team: maybe not needed? It includes General Requirements (legal work, medical clearance). Might be considered as Requirements? Could be part of Requirements.
We need to decide headings: "About the role" could correspond to Job Summary. "Responsibilities" for Roles And Key Responsibilities. "Requirements" maybe for Qualifications? But we also have Skills section for Knowledge, Skills, And Abilities. "Qualifications" for Basic/Preferred Qualifications. "Benefits" for What We Offer. "Pay" only if posting states pay range: there is a note about Pay Range only applies to US applicants etc. It mentions pay range but not actual numbers. It says "The above Pay Range only applies..." but we don't see the actual range. It mentions note but no specific numbers. According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does mention Pay Range but not actual numbers; it's vague. Probably we should not include Pay section because no specific numbers given. Benefits we have description: "CRS offers U.S. based staff a comprehensive benefits package, including medical, dental, life insurance, vision, and a generous retirement savings plan. Benefits packages for successful candidates employed outside the U.S. are based on the country of employment/in-country office where the candidate will perform the role." That's substantive. So include Benefits.
Schedule: not mentioned. So omit.
Now we need to output HTML fragment with
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive content.
We need to parse the job description.
Key sections:
- Job Summary: description paragraph.
- Roles And Key Responsibilities: bullet list of responsibilities.
- Knowledge, Skills, And Abilities: bullet list.
- Qualifications: Basic Qualifications and Preferred Qualifications.
- What We Offer: Benefits description.
- About Us: description.
- About The Team: maybe not needed? It includes General Requirements (legal work, medical clearance). Might be considered as Requirements? Could be part of Requirements.
We need to decide headings: "About the role" could correspond to Job Summary. "Responsibilities" for Roles And Key Responsibilities. "Requirements" maybe for Qualifications? But we also have Skills section for Knowledge, Skills, And Abilities. "Qualifications" for Basic/Preferred Qualifications. "Benefits" for What We Offer. "Pay" only if posting states pay range: there is a note about Pay Range only applies to US applicants etc. It mentions pay range but not actual numbers. It says "The above Pay Range only applies..." but we don't see the actual range. It mentions note but no specific numbers. According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does mention Pay Range but not actual numbers; it's vague. Probably we should not include Pay section because no specific numbers given. Benefits we have description: "CRS offers U.S. based staff a comprehensive benefits package, including medical, dental, life insurance, vision, and a generous retirement savings plan. Benefits packages for successful candidates employed outside the U.S. are based on the country of employment/in-country office where the candidate will perform the role." That's substantive. So include Benefits.
Schedule: not mentioned. So omit.
Now we need to output HTML fragment with headings and appropriate content.
We must not include boilerplate like EEO, disclaimer, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should exclude the disclaimer about job description not exhaustive, equal opportunity, etc. Also exclude "About The Team General Requirements" maybe? It contains some requirements like legal work eligibility, medical clearance. That could be considered part of Requirements or Qualifications. But we need to decide if we keep it. It's substantive: "CRS offers are contingent on the selected candidate’s ability to legally work where the position is to be performed. Every government has a unique set of work permit eligibility requirements. All positions requiring residence or frequent travel outside a home country must undergo and clear a pre-employment medical clearance; some work permit processes require clearing a separate government administered medical examination. CRS prioritizes candidates who are citizens/ permanent residents of the countries where we have CRS offices." This is relevant to eligibility. Could be placed under a section like "Requirements" or "Eligibility". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put this under "Requirements". However we already might use Requirements for qualifications? Actually we have both Requirements and Qualifications headings allowed. We need to decide distribution.
Typically: "About the role" = summary. "Responsibilities" = duties. "Requirements" = maybe eligibility, travel, supervisory, languages? "Qualifications" = education/experience. "Skills" = knowledge, skills, abilities. "Benefits" = benefits. "Pay" = salary. "Schedule" = work schedule.
Thus we can assign:
- About the role: Job Summary paragraph.
- Responsibilities: list from Roles And Key Responsibilities.
- Requirements: includes Travel (up to 10%), Languages (Fluent English, preferred French/Spanish/Arabic), Supervisory Responsibilities: No, maybe also legal work eligibility, medical clearance, citizenship preference. Also maybe "Must be willing and able to travel up to 10%." That's a requirement.
- Qualifications: Basic Qualifications and Preferred Qualifications (education, experience).
- Skills: Knowledge, Skills, And Abilities list.
- Benefits: What We Offer.
We must not include headings with filler. Ensure each heading has substantive content.
We must not repeat job title.
We must not include markdown fences.
Now craft HTML.
We'll need About the role
then
About the role
thenJob Summary paragraph.
ThenResponsibilities
then- ... each responsibility.
About the role
The Advisor II, Procurement Contracts serves as Global Procurement’s technical subject