Procurement Officer

Here's a thinking process: 1. **Analyze User Input:** - User is acting as a job listing editor. - I receive raw scraped text from a job website. - Job is to extract ONLY actual job information and return it in a clean, readable format. - Must REMOVE specific things: social sharing, author bylines, "you may also like", navigation, comments, ads, cookie notices, duplicate text, category labels not part of job, stray numbers/formatting artifacts. - Must KEEP and STRUCTURE: job title, company, location, description/responsibilities, requirements/qualifications, how to apply, salary, deadline, job ID/reference, contract type/level. - Return ONLY the cleaned job text. No commentary, headers like "Here is the cleaned version", or markdown formatting. Just the clean job listing text. Wait, the actual prompt I'm given is a bit different. It says: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." Then there are rules: - Use

for introductory paragraphs and general text - Use

for section headers - Use

• for list items - No CSS classes, no inline styles, no
  s, no
  tags - Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase - If text has no clear sections, just wrap paragraphs in

  tags - Return ONLY the HTML. No markdown fences, no explanation, no preamble. Then it gives a job description in HTML format (the raw scraped text). I need to convert this into clean semantic HTML following the rules. Let me re-read carefully. The initial part about "You are a job listing editor... Remove... Keep..." seems to be system context/instructions, but then the actual task given is: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." followed by rules about HTML tags, preserving content word-for-word, etc. The input includes a job description that's already in HTML format (with

  ,

  , , , ,

  ,
  • , etc.). I need to transform it into the specified clean semantic HTML format. Let's parse the input text structure and decide how to map it to the required HTML tags. Input HTML: ```

    POSITION OVERVIEW

    FHI 360 is seeking a Procurement Officer under the EpiC project, Maternal, Neonatal, and Child Health activity being implemented in Liberia in the four high-burden counties,

    Montserrado, Nimba, Lofa, and Bong, on improving maternal, neonatal, and child health outcomes by increasing the use of and access to high-quality services and eliminating preventable maternal and newborn deaths. The Procurement Officer will support activities related to the procurement of goods and services in accordance with FHI 360 policies, U.S. Department of State (DOS) rules and regulations, and other applicable donor requirements in support of the EpiC MNCH Liberia project. The position reports directly to the Operations Manager and is based at the FHI 360 Liberia office in Monrovia.

    Accountabilities

    • Ensure compliance with U.S. Department of State (DOS) rules and regulations, FHI 360 policies, and applicable donor requirements.
    • Support procurement activities for the EpiC MNCH Liberia project in accordance with DOS rules and regulations and FHI 360 procurement policies and procedures.
    • Request quotations/proposals (RFQs/RFPs), organize and facilitate bid evaluation processes, review quotations, and conduct cost/price analyses.
    • Ensure timely procurement of goods and services required by the project, including preparation and submission of complete procurement packages for timely review and approval.
    • Manage sourcing activities for a variety of commercial goods and services.
    • Provide purchase information to the Inventory Committee to facilitate timely and accurate inventory updates for the project.
    • Support the project team and collaborate with administrative staff to develop and regularly update procurement plans, including the pre-procurement tracker.
    • Maintain complete and accurate procurement documentation in accordance with established protocols. This includes updating procurement trackers, maintaining complete electronic procurement files, and reconciling e-files with the procurement tracker on a weekly basis or as required.
    • Contribute to the development and maintenance of supplier and vendor lists, monitor and keep track of suppliers’ performance.
    • Liaise with FHI 360 Liberia staff on procurement-related matters and provide appropriate procurement support and guidance.
    • Perform other related duties as assigned.

    Applied Knowledge & Skills

    • Ability to develop and implement effective strategies to meet programmatic deadlines and deliverables.
    • Sound judgment and the ability to extract, interpret, analyze, and present data, as well as resolve operational problems effectively.
    • Ability to work independently with minimal supervision and collaborate effectively with individuals from diverse national and cultural backgrounds.
    • Ability to work accurately under time constraints and pressure, while dealing patiently, efficiently, effectively, and tactfully with staff members and external stakeholders.
    • High level of confidentiality, initiative, sound judgment, and attention to detail.
    • Good administrative, planning, and organizational skills, with the ability to work seamlessly with administrative and operations staff within the Liberia office.

    Problem Solving & Impact:

    • Works on problems that are diverse in scope and require evaluation of identifiable factors.
    • Exercises judgment within defined practices and policies in selecting methods and techniques for obtaining solutions.
    • Decisions made generally affect own job or specific functional area

    Education:

    • A minimum of 3–5 years of relevant professional experience in procurement, logistics, or a related field, preferably within the development sector and on donor-funded projects.
    • Bachelor’s degree in Procurement, Business Administration, Accounting, Supply Chain Management, or a related field.

    Experience

    • Excellent written and verbal communication skills in English.
    • Previous experience working with an international organization is preferred.
    • Proficiency in Microsoft Word, Microsoft Excel, and cloud-based data storage and collaboration platforms such as SharePoint.
    • Demonstrated ability to work independently, exercise initiative, and effectively manage a high-volume workflow.
    • Strong attention to detail and demonstrated ability to perform detailed work with a high level of accuracy.

    TYPE AND NATURE OF CONTACTS

    • Maintain routine coordination with FHI 360 employees, particularly MNCH staff at the central office in Monrovia, as well as consultants working on-site and in the field.
    • Coordinate work assignments with other staff and contribute to resolving operational and procurement-related issues with tact and professionalism, including occasional interaction with external stakeholders.
    • Work closely with FHI 360 MNCH program staff, finance, administration, and operations teams to ensure effective and timely procurement support.

    FHI 360 is committed to providing a safe environment for all employees, beneficiaries, and anyone contracted by FHI 360. This includes taking measures to protect vulnerable people from Sexual Exploitation and Abuse (SEA) by either FHI 360 employees or associated personnel. FHI 360 abides by child safeguarding principles. FHI 360’s Safeguarding Policies apply and flow out to all FHI 360 staff, board members, volunteers, and partner staff (subcontractors, consultants, vendors, and sub-recipients), regardless of the funding mechanism or amount of contract, agreement, or purchase order.

    FHI 360 offers a competitive compensation package and is an equal opportunity employer. Interested candidates are encouraged to apply online at Join our team - FHI 360. Please note that only pre-selected candidates will be contacted.

    The expected hiring salary range for this role is USD 13,667 - 20,000 for annual  basic salary. When determining an offer amount, FHI 360 factors in multiple considerations, including but not limited to: relevant years of experience and education possessed by the applicant, internal equity, market pay,  and budget. For internal candidates, salary placement will also follow FHI 360’s current promotional increase guidelines.

    
    

    This job posting summarizes the main duties of the job. It neither prescribes nor restricts the exact tasks that may be assigned to carry out these duties. This document should not be construed in any way to represent a contract of employment. Management reserves the right to review and revise this document at any time.

    
    

    FHI 360 is an equal opportunity employer whereby we do not engage in practices that discriminate against any person employed or seeking employment based on race, color, religion, sex, sexual orientation, gender identity, national or ethnic origin, age, marital status, physical or mental disability, protected Veteran status, or any other characteristic protected under applicable law.

    
    

    Our values and commitments to safeguarding: FHI 360 is committed to preventing any type of abuse, exploitation and harassment in our work environments and programs, including sexual abuse, exploitation and harassment. FHI 360 takes steps to safeguard the welfare of everyone who engages with our organization and programs and requires that all personnel, including staff members and volunteers, share this commitment and sign our code of conduct. All offers of employment will be subject to appropriate screening checks, including reference, criminal record and terrorism finance checks. FHI 360 also participates in the Inter-Agency Misconduct Disclosure Scheme (MDS), facilitated by the Steering Committee for Humanitarian Response. In line with the MDS, we will request information from job applicants’ previous employers about any substantiated findings of sexual abuse, exploitation and/or harassment during the applicant’s tenure with previous employers. By applying, job applicants confirm their understanding of these recruitment procedures and consent to these screening checks.

    
    

    FHI 360 will consider for employment all qualified applicants, including those with criminal histories, in a manner consistent with the requirements of applicable state and local laws.

    
    

    FHI 360 will never ask you for your career site username or password, and we will never request money, goods or services during the application, recruitment or employment  process. If you have questions or concerns about correspondence from us, please email CareerCenterSupport@fhi360.org.
    
    FHI 360 fosters the strength and health of its workforce through a competitive benefits package, professional development and policies and programs that support a healthy work/life balance. Join our global workforce to make a positive difference for others — and yourself.

    
    

    Please click here to continue searching FHI 360's Career Portal.
     

    ``` Rules for output: - Use

    for introductory paragraphs and general text - Use

    for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role) - Use

    • for list items (duties, requirements, qualifications, skills) - No CSS classes, no inline styles, no
      s, no
      tags - Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase - If text has no clear sections, just wrap paragraphs in

      tags - Return ONLY the HTML. No markdown fences, no explanation, no preamble. I need to convert the input into this structure. Let's analyze the sections and content. The input has: - `

      POSITION OVERVIEW

      ` - This is a title. The rules say use

      for section headers. But this is a main title. I'll treat it as a heading. Maybe

      POSITION OVERVIEW

      ? But the rule says "Use

      for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Rule)". It doesn't say what to do with the main title. I'll probably use

      for it, or maybe keep it as is but replace the tag. The rule says "Preserve ALL original content word-for-word". So the text "POSITION OVERVIEW" must appear exactly. I'll wrap it in

      POSITION OVERVIEW

      . But wait, the original has `

      POSITION OVERVIEW

      `. The content is "POSITION OVERVIEW". I need to output exactly that text, but in

      maybe? The rule says "Use

      for section headers (e.g. Responsibilities, Qualifications, ...)". It doesn't explicitly say the main title must be

      , but it's a section header. I'll use

      POSITION OVERVIEW

      . However, the rule "Preserve ALL original content word-for-word" might mean I shouldn't change the tag structure arbitrarily, but I have to follow the output format rules. I think I should output `

      POSITION OVERVIEW

      ` since the original heading text is "POSITION OVERVIEW" and I'm to use

      for section headers. Let's look at the paragraphs and sections. Structure seems to be: - Position overview description text (after the title) - Accountabilities (with

      • ) - Applied Knowledge & Skills (with
        • ) - Problem Solving & Impact (with
          • ) - Education (with
            • ) - Experience (with
              • ) - TYPE AND NATURE OF CONTACTS (with
                • ) - Then a long paragraph about FHI 360 commitment, salary, etc. - Then equal opportunity, safeguarding, etc. The rules say: "Use

                  for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". I need to map the input sections to these headers. Input sections based on bold/underlined text: - `Accountabilities` -> Responsibilities - `Applied Knowledge & Skills` -> Skills (or maybe Knowledge & Skills) - `Problem Solving & Impact:` -> maybe not a section header with

                  , but it has a
                  after it. The text "Problem Solving & Impact:" followed by a
                  . I'll treat it as a section header

                  Problem Solving & Impact

                  and then the
                  . - `Education:` -> Education - `Experience` -> Experience - `TYPE AND NATURE OF CONTACTS` -> maybe "About the Role" or similar. I'll use

                  TYPE AND NATURE OF CONTACTS

                  or map to "About the Role". The rule lists "About the Role" as an example, but I should preserve the original text. I'll use

                  TYPE AND NATURE OF CONTACTS

                  . - Then there's salary info, application instructions, equal opportunity, etc. Also, there are paragraphs that are not under those section headers: the introductory description, the final paragraphs about FHI 360 values, application link, etc. Rules: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So I must include all text exactly as is, but format with the allowed tags. "If text has no clear sections, just wrap paragraphs in

                  tags". So I'll wrap everything in

                  or

                  or

                  • as appropriate. Let's plan the output structure: Start with the title: `

                    POSITION OVERVIEW

                    ` Then the introductory paragraph(s). The input has `

                    FHI 360 is seeking a Procurement Officer...

                    ` and then another `

                    Montserrado, Nimba, Lofa, and Bong, on improving...

                    `. Actually, looking at the input: `

                    POSITION OVERVIEW

                    FHI 360 is seeking a Procurement Officer under the EpiC

  Translated by AI — may not be perfect

  Show original