Amber — Data Entry Clerk - Wyoming Department of Transportation

We need to output HTML fragment with headings

for sections: 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 as heading. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions? The instruction says: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we need to drop "How to Apply" and other application instructions. Also drop "Optional Self-Interview" etc. Also drop contact info? Might be considered metadata; we can fold minor metadata into a short

or drop it. The posting includes contact Samuel Andoh etc. That's minor metadata; we could include a short

with contact? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include contact in a

. But also we need to preserve all substantive information. The substantive info includes: About FuntoNetwork, The Opportunity, Core Responsibilities, What You Bring, Earnings, Payments, and Tax Records. Also maybe the project status snapshot? That's metadata: "Data Entry Clerk Role Snapshot Project Status: 🟡 Amber - Closing Soon - Apply by September 16, 2026". That's minor metadata; we could include as a short

. Also "RFP Status & Award Report" etc are links; maybe drop as navigation? Probably drop. We need sections: About the role (maybe combine About FuntoNetwork and The Opportunity). Responsibilities (Core Responsibilities). Requirements (maybe "What You Bring" includes experience, communication, etc). Qualifications (maybe "Relevant experience for this staffing role or equivalent transferable experience." etc). Skills (maybe "Strong communication, documentation, and schedule reliability." etc). Benefits (maybe "Earnings, Payments, and Tax Records" could be Benefits? Actually that's about payments tracking; not exactly benefits like health insurance. Could be considered Pay? The posting mentions earnings tracking but not actual pay rate. So we should not create Pay or Benefits sections unless posting actually states them. It does not state pay amount, schedule, or benefits like health. So we should omit Pay, Benefits, Schedule sections. Also we should not create sections with filler like "commensurate with experience". So we will include only sections that have substantive content: About the role, Responsibilities, Requirements, Qualifications, Skills. Possibly also a short

for metadata like project status and contact. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities we need a list. For Requirements maybe list. For Qualifications maybe list. For Skills maybe list. We must preserve all substantive information; do not invent or summarize away detail. So we need to capture each bullet from the posting. Let's extract substantive content: About FuntoNetwork: "At FuntoNetwork, we connect experienced workers and consultants with upcoming project opportunities through a mobile-first platform built for discovery, review, application submission, payment tracking, and worker support." The Opportunity: "FuntoNetwork is seeking a Data Entry Clerk for upcoming staffing opportunity: As-Needed Temporary Employment Services. Records, forms, structured data entry, and quality review support." We could combine these into About the role section. Core Responsibilities (list): - Role coverage: Records, forms, structured data entry, and quality review support. - Tooling: Use role-appropriate tools such as Excel or Google Sheets, Power BI or Tableau, SharePoint, evidence-tracking dashboards, and role-appropriate data-collection tools. - Review the role scope, assignment background, supporting materials, deadline, and client requirements that relate to your assigned work. - Provide reliable temporary staffing support for the assigned agency program or department. - Follow site, attendance, confidentiality, safety, and reporting requirements. - Coordinate with FuntoNetwork on onboarding, scheduling, timesheets, issue resolution, and replacement coverage when needed. - Communicate clearly with FuntoNetwork staffing operations and assigned site contacts. - Support quality control, status updates, and readiness for your assigned portion of the work. What You Bring (list): - Relevant experience for this staffing role or equivalent transferable experience. - Strong communication, documentation, and schedule reliability. - Ability to complete required screening, eligibility verification, and onboarding steps. - Experience supporting public-sector, education, utility, healthcare, transportation, enterprise, or staffing assignments is preferred. - Attention to detail and ability to provide complete role-specific application materials. Earnings, Payments, and Tax Records (list?): - Workers and consultants will be able to track project earnings, payment status, and tax records inside the FuntoNetwork mobile app. - Approved payments for this project opportunity will be processed through the app, and workers will be able to request withdrawals from their available balance directly inside the app. - The app will also provide access to relevant payment history and tax-related records for worker tracking and reporting. This is substantive but not exactly benefits; maybe we could treat as "Benefits" but the instruction says only create Benefits section if posting actually states them. This is about payment tracking, not benefits like health insurance. Could be considered "Pay" but they didn't state pay rate. So maybe we should not create Pay/Benefits sections. However we could include a short paragraph under a generic section like "Additional Information". But we are limited to headings list; we could omit this info? But we must preserve ALL substantive information. So we need to include it somewhere. Perhaps we can include a

  after the sections, not under a heading. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

  • for any list of duties/requirements/benefits, and

    for prose. Do NOT repeat the job title as a heading ... Prefer a few substantive sections over many thin ones." It doesn't forbid having extra

    paragraphs outside sections. So we can add a

    for earnings/payments info. Also we need to include minor metadata like project status and contact in a short

    . Could combine. Thus final HTML: maybe:

    Project Status: 🟡 Amber - Closing Soon - Apply by September 16, 2026. Contact: Samuel Andoh, Account Manager, samuel.andoh@funtonetwork.com, www.funtonetwork.com

    About the role

    At FuntoNetwork, we connect experienced workers and consultants with upcoming project opportunities through a mobile-first platform built for discovery, review, application submission, payment tracking, and worker support. FuntoNetwork is seeking a Data Entry Clerk for upcoming staffing opportunity: As-Needed Temporary Employment Services. Records, forms, structured data entry, and quality review support.

    Responsibilities

    • Role coverage: Records, forms, structured data entry, and quality review support.
    • Tooling: Use role-appropriate tools such as Excel or Google Sheets, Power BI or Tableau, SharePoint, evidence-tracking dashboards, and role-appropriate data-collection tools.
    • Review the role scope, assignment background, supporting materials, deadline, and client requirements that relate to your assigned work.
    • Provide reliable temporary staffing support for the assigned agency program or department.
    • Follow site, attendance, confidentiality, safety, and reporting requirements.
    • Coordinate with FuntoNetwork on onboarding, scheduling, timesheets, issue resolution, and replacement coverage when needed.
    • Communicate clearly with FuntoNetwork staffing operations and assigned site contacts.
    • Support quality control, status updates, and readiness for your assigned portion of the work.

    Requirements

    • Relevant experience for this staffing role or equivalent transferable experience.
    • Strong communication, documentation, and schedule reliability.
    • Ability to complete required screening, eligibility verification, and onboarding steps.
    • Experience supporting public-sector, education, utility, healthcare, transportation, enterprise, or staffing assignments is preferred.
    • Attention to detail and ability to provide complete role-specific application materials.
    We could also have Qualifications and Skills sections but they'd overlap with Requirements. To avoid thin sections, we can combine Requirements and Qualifications into one? But we need to follow instruction: prefer a few substantive sections over many thin ones. So we could have only About the role, Responsibilities, Requirements. That covers all. The "What You Bring" is essentially requirements. So we can put that under Requirements. No need for Qualifications/Skills separate. Thus we have three sections. Now we need to include earnings/payments info as a

    after sections maybe under a heading like "Payment Tracking"? But we shouldn't create Benefits/Pay unless posting states them. It does state payment tracking but not pay rate. Could we treat as a section "Payment Tracking"? Not in allowed headings list. The instruction says use those headings for sections; but we could still create other headings? It says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive list. But they say "Prefer a few substantive sections over many thin ones." So we could add a section like "Payment Tracking" if we want, but better to avoid extra sections. We can put that info in a

    after the sections. Thus final HTML fragment:

    Project Status: 🟡 Amber - Closing Soon - Apply by September 16, 2026. Contact: Samuel Andoh, Account Manager, samuel.andoh@funtonetwork.com, www.funtonetwork.com

    About the role

    At FuntoNetwork, we connect experienced workers and consultants with upcoming project opportunities through a mobile-first platform built for discovery, review, application submission, payment tracking, and worker support. FuntoNetwork is seeking a Data Entry Clerk for upcoming staffing opportunity: As-Needed Temporary Employment Services. Records, forms, structured data entry, and quality review support.

    Responsibilities

    • Role coverage: Records, forms, structured data entry, and quality review support.
    • Tooling: Use role-appropriate tools such as Excel or Google Sheets, Power BI or Tableau, SharePoint, evidence-tracking dashboards, and role-appropriate data-collection tools.
    • Review the role scope, assignment background, supporting materials, deadline, and client requirements that relate to your assigned work.
    • Provide reliable temporary staffing support for the assigned agency program or department.
    • Follow site, attendance, confidentiality, safety, and reporting requirements.
    • Coordinate with FuntoNetwork on onboarding, scheduling, timesheets, issue resolution, and replacement coverage when needed.
    • Communicate clearly with FuntoNetwork staffing operations and assigned site contacts.
    • Support quality control, status updates, and readiness for your assigned portion of the work.

    Requirements

    • Relevant experience for this staffing role or equivalent transferable experience.
    • Strong communication, documentation, and schedule reliability.
    • Ability to complete required screening, eligibility verification, and onboarding steps.
    • Experience supporting public-sector, education, utility, healthcare, transportation, enterprise, or staffing assignments is preferred.
    • Attention to detail and ability to provide complete role-specific application materials.

    Workers and consultants can track project earnings, payment status, and tax records inside the FuntoNetwork mobile app. Approved payments are processed through the