Supply Chain Administrator

,

,
• , , , , , etc. However, the instructions say to format it as clean semantic HTML using specific tags:

  for paragraphs,

  for section headers,

  • for lists. No CSS classes, inline styles,
    s,
    tags. Preserve all original content word-for-word. No markdown fences, no explanation. I need to parse the given text and restructure it accordingly. The input includes HTML tags already, but I should treat it as raw text and output clean HTML per rules. However, the input is already HTML-like. The instruction: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." But the provided job description includes HTML tags. Perhaps the user expects me to clean up the existing HTML and restructure with proper semantic tags. I'll need to extract the text content, identify sections, and wrap appropriately. Let's analyze the content: - First paragraph: "With 75 years of experience..." (intro) - Then "Employee Contract Type: Local - Fixed Term Employee (Fixed Term)" - "Job Description:" - "JOB SUMMARY" (section header) - Summary paragraph. - "MAJOR RESPONSIBILITIES" (section header) - Subsections: "Business Requirements", "Planning", "Strategic Sourcing", "Supplier Contract and Relationship Management", "Procurement Execution", "Data Management, Analysis and Reporting", "Process, Procedure and Policy", "Control and Compliance". Each with bullet points. - "REQUIRED KNOWLEDGE, SKILL AND EXPERIENCE" (section header) with bullet points. - "Working Environment / Conditions:" (section header) with bullet points. - Then some paragraphs about background checks, misconduct disclosure, consent, women encouraged. - "Applicant Types Accepted: Local Applicants Only" I need to use

    for section headers. Which ones? The rules: "Use

    for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". So I should use

    for each major section: JOB SUMMARY, MAJOR RESPONSIBILITIES, REQUIRED KNOWLEDGE, SKILL AND EXPERIENCE, Working Environment / Conditions, maybe also the background check paragraphs? But those are not typical sections. Could treat them as paragraphs. Also "Employee Contract Type" and "Job Description" and "Applicant Types Accepted" could be headers. But the rule says "If text has no clear sections, just wrap paragraphs in

    tags". Here there are clear sections. I'll structure: - Intro paragraph(s) as

    . - "Employee Contract Type:" maybe as

    ? Not in example list but could be considered a section. However, it's a single line. Could be

    with strong? But rule: no inline styles, no ? Actually we can use ? The rule says no CSS classes, no inline styles, no

    s, no
    tags. It doesn't forbid or . But we should use semantic HTML: maybe for bold, for italics. But the instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That includes formatting? The original has , , . Should we keep them? The rule says "Use

    for introductory paragraphs and general text, Use

    for section headers, Use

    • for list items". It doesn't say to strip existing formatting. But we are to output clean semantic HTML. Probably we should keep the text content but not the presentational tags like , , . However, "Preserve ALL original content word-for-word" suggests we must keep the exact words, but not necessarily the HTML tags. The original content includes words like "JOB SUMMARY" with underline and bold. The words are "JOB SUMMARY". The formatting is not words. So we can output the text without the formatting tags, but using semantic tags like

      for headers. Thus, I'll convert: - For each section header (like JOB SUMMARY, MAJOR RESPONSIBILITIES, etc.) wrap in

      . - For bullet lists, use

      • with the text content (without the
      • tags from original? The original already has
        • . But we need to output clean HTML. I'll just extract the text of each list item and wrap in
        • . - For paragraphs, wrap in

          . - Remove
          tags, ,

          , etc. Also note there are empty

          and
          . Ignore empty paragraphs. Now, let's process step by step. First, the raw input is a string with HTML tags. I'll parse it mentally. I'll write the output HTML. Start with intro paragraph: "With 75 years of experience, our focus is on helping the most vulnerable children overcome poverty and experience fullness of life. We help children of all backgrounds, even in the most dangerous places, inspired by our Christian faith. Come join our 31,000+ staff working in nearly 100 countries and share the joy of transforming vulnerable children’s life stories!" That's one paragraph? In original, there are two

          tags: first with two sentences, second with "Come join...". Actually the first

          contains two sentences separated by
          
          . The second

          is empty? Wait: The input: "

          With 75 years of experience, our focus is on helping the most vulnerable children overcome poverty and experience fullness of life. We help children of all backgrounds, even in the most dangerous places, inspired by our Christian faith.
          
          Come join our 31,000+ staff working in nearly 100 countries and share the joy of transforming vulnerable children’s life stories!

          Employee Contract Type:

          Local - Fixed Term Employee (Fixed Term)

          Job Description:

          ..." So first

          includes both paragraphs? Actually there is a
          
          then "Come join...". That's still within same

          . Then a blank

          . Then

          Employee Contract Type:

          then text "Local - Fixed Term Employee (Fixed Term)" not wrapped in tag. Then empty

          . Then

          Job Description:

          . We need to preserve all text. So we'll have:

          With 75 years of experience, our focus is on helping the most vulnerable children overcome poverty and experience fullness of life. We help children of all backgrounds, even in the most dangerous places, inspired by our Christian faith. Come join our 31,000+ staff working in nearly 100 countries and share the joy of transforming vulnerable children’s life stories!

          Then "Employee Contract Type: Local - Fixed Term Employee (Fixed Term)" - could be a paragraph or a header. Since it's a label and value, maybe

          Employee Contract Type: Local - Fixed Term Employee (Fixed Term)

          but we cannot use ? The rule doesn't forbid . But we should avoid inline styles. Use semantic tags: maybe

          Employee Contract Type

          Local - Fixed Term Employee (Fixed Term)

          . However, the example headers list doesn't include "Employee Contract Type". But it's a section. I'll treat as

          Employee Contract Type

          and then paragraph. Similarly "Job Description:" is a header. Then "JOB SUMMARY" is a sub-header. But the rule: "Use

          for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". So we should use

          for those typical sections. For others, maybe just

          . However, to keep structure, I'll use

          for all clear section headers: "Employee Contract Type", "Job Description", "JOB SUMMARY", "MAJOR RESPONSIBILITIES", "Business Requirements", "Planning", "Strategic Sourcing", "Supplier Contract and Relationship Management", "Procurement Execution", "Data Management, Analysis and Reporting", "Process, Procedure and Policy", "Control and Compliance", "REQUIRED KNOWLEDGE, SKILL AND EXPERIENCE", "Working Environment / Conditions", maybe "Applicant Types Accepted". But that's many

          . That's okay. Now, for each subsection under MAJOR RESPONSIBILITIES, they are also headers (Business Requirements, Planning, etc.). Should they be

          as well? They are subsections. Could use

          for each. The rule says "section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It doesn't forbid subsections. I'll use

          for each. Now, the bullet points: each list item text should be in

          . The original list items have some formatting like for italics. We'll keep the text but not the tags? The rule: preserve all original content word-for-word. The words include "Work environment: Office-based with travel to the field". The italics are not words. So we can drop . But the text "Work environment: Office-based with travel to the field" is the content. We'll put that as

          text. Also there are some lines with etc. We'll just take the text. Now, the paragraphs after "Working Environment / Conditions:" include some important notes about background checks, misconduct disclosure, consent, women encouraged. These are paragraphs. We'll wrap each in

          . Finally "Applicant Types Accepted: Local Applicants Only" - maybe

          Applicant Types Accepted

          Local Applicants Only

          . Now, ensure no
          , no inline styles, no divs. Let's construct the HTML. I'll write it as a single string. Note: The original includes special characters like + for +, & for &. We'll keep them as is? The rule: preserve all original content word-for-word. So we should keep the entities? Probably we should decode them to actual characters? The input is HTML entities. The output HTML should contain the actual characters? The rule says "Preserve ALL original content word-for-word". That includes the entities? But the entities are not words, they are representations. Safer to keep as they appear in the text? The user gave the job description as a string with entities. In the output HTML, we can write the actual characters (like +, &). But to be safe, I'll keep the entities as they are? However, the output is HTML, so entities will be rendered. I'll convert + to + and & to & for readability. But the rule says word-for-word, maybe keep the exact characters. I'll keep the entities as they are in the source text? The source text shows "31,000+ staff". That's the raw text. If I output "31,000+ staff", that's different. But the user might expect the cleaned HTML to have the actual characters. Since the instruction is to format as clean semantic HTML, I think we should output the actual characters (since HTML will render them). But the rule "Preserve ALL original content word-for-word" suggests we should not change any characters. However, the original content is the text, not the HTML encoding. The text includes a plus sign. The encoding is due to HTML. I'll decode entities to their characters. Similarly, there are curly quotes: “ and ”. Keep them. Now, let's write. I'll start with the first paragraph.

          With 75 years of experience, our focus is on helping the most vulnerable children overcome poverty and experience fullness of life. We help children of all backgrounds, even in the most dangerous places, inspired by our Christian faith. Come join our 31,000+ staff working in nearly 100 countries and share the joy of transforming vulnerable children’s life stories!

          Then Employee Contract Type:

          Employee Contract Type

          Local - Fixed Term Employee (Fixed Term)

          Then Job Description header:

          Job Description

          Then JOB SUMMARY:

          JOB SUMMARY

          To support the effective implementation of procurement and supply chain operations through accurate administration, procurement coordination, supplier documentation management, reporting, and compliance with World Vision policies and procedures. The position helps ensure the timely and cost-effective acquisition of goods and services required for programme and operational activities.

          Then MAJOR RESPONSIBILITIES:

          MAJOR RESPONSIBILITIES

          Then Business Requirements:

          Business Requirements

          • Understand the department's business requirements and apply in the day-to-day work.

          Planning:

          Planning

          • Facilitate annual procurement planning sessions with key stakeholders
          • Consolidation and report on the Procurement Plans
          • Review and update Item Catalog prior to the planning process activity.
          • Advise and familiarize Operations with the use of the Item Catalog

          Strategic Sourcing:

          Strategic Sourcing

          • Advice on Market Assessment and Supplier Pre-Qualification process as per the directions from Coordinators and Advisors.
          • ending bid invitations, follow-up of bids, assist coordinating pre-bid meetings as per the direction from Coordinators and Specialist.
          • Maintain all supporting documents relating to the Sourcing Events based on the document management Supervise the Sourcing events Filed Offices and Assistance work relating to sourcing.
          • Preparation of Procurement Committee submission documents based on the direction given by the coordinators / specialists.

          Supplier Contract and Relationship Management:

          Supplier Contract and Relationship Management

          • Accurately complete the master data management form (contract/supplier/ item register)
          • Manage record keeping for all contract-related correspondence and documentation (Master Data Management).
          • Communicate contract-related information to all stakeholders to ensure optimum usage of contracts.
          • Collect feedback on supplier performance as per the established SPM guidelines.

          Procurement Execution:

          Procurement Execution

          • Advise on the RFP/RFQ process for spot buys as required
          • Liaise with Shared Services & Finance to resolve supplier inquiries
          • Release POs to suppliers for spot buys and assigned categories.

          Data Management, Analysis and Reporting:

          Data Management, Analysis and Reporting

          • Collect and organize data from projects and business units.
          • Analyze and check data for accuracy and produce the required reporting output in accordance with the Policies / Procedures & Guidelines as set by WV
          • Prepare weekly/monthly procurement status reports to update the customers and other stakeholders.
          • Perform Daily reconciliation exercises of all records and transactions performed within the same day and ensure that data validation, integrity and accuracy of data is meticulously maintained.
          • Consolidate all findings and convert them into useful formats as provided by SCM Manager

          Process, Procedure and Policy:

          Process, Procedure and Policy

          • Work with senior SCM teams to manage Internal customer satisfaction
          • Collect data to support performance scorecard reporting (i.e. KPIs)

          Control and Compliance:

          Control and Compliance

          • Maintain proper filing and record keeping as per the guidelines set by the management.

          Then REQUIRED KNOWLEDGE, SKILL AND EXPERIENCE:

          REQUIRED KNOWLEDGE, SKILL AND EXPERIENCE

          • Certification diploma in business management, Accounting / Procurement and logistics
          • One year of experience in Procurement and Logistics or Accounting field

          Working Environment / Conditions:

          Working Environment / Conditions

          • Work environment: Office-based with travel to the field
          • Travel: 5% Domestic & international travel is required.

          Then the paragraphs:

          All successful candidates will be required to undergo a police (criminal background) check, appropriate to the role and location, as well as a Counter-Terrorism Sanctions screening, as part of the clearance process prior to commencing employment.

          World Vision International also participates in the Inter-Agency Misconduct Disclosure Scheme (https://misconduct-disclosure-scheme.org/). In line with this Scheme, we will request information from applicants’ previous employers, as part of the reference checking process, regarding any findings of sexual exploitation, sexual abuse and/or sexual harassment during employment, as well as any such incidents under investigation at the time of separation.

          By applying for this role, applicants confirm their understanding of and consent to these recruitment procedures.

          WOMEN ARE STRONGLY ENCOURAGED TO APPLY

          Then Applicant Types Accepted:

          Applicant Types Accepted

          Local Applicants Only

          Now, ensure no extra tags. Also note that the original had some empty paragraphs and
          tags. We ignore them.

    Translated by AI — may not be perfect

    Show original