Data Admin / Data Wrangler

We need to output HTML fragment with sections: headings

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do NOT repeat job title as heading (page already shows it). Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Key info: - Work Designation: Home-based (Remote). - Schedule: Monday-Friday, 8:00 AM - 5:00 PM (CST or similar US business hours). - Equipment: Candidate to use their own or supplier-owned PC/MAC, accessing systems via Virtual Desktop. - Rate: $50-58/hr, W2. - Engagement Type: Contract. - Project Overview: This role supports a large-scale enterprise initiative to replace 34,000 computers by the end of Q1 2027. The project requires extensive coordination to clean, process, and format user and device data, as well as project coordination work to ensure PC orders are processed accurately, efficiently, and on schedule. Our client is seeking an experienced Data Analyst / Data Wrangler to support the pre-deployment data preparation phase of this initiative. This individual will be responsible for cleaning and validating large datasets, filling gaps in existing records, and ensuring all user and device data is accurate and complete ahead of the mass PC replacement rollout. - Key Responsibilities: bullet list (list items). - Required Skills & Experience: bullet list. - Preferred Skills: Power BI experience... - Ideal Candidate Profile: paragraph. - Salary/Rate: $50-$58/HR (depends on experience level). This is a contract position with candidates expected to work 40 hours/ week. - About Us: description of PTP, AI-assisted interview process, etc. This is boilerplate? It's about the company, but maybe we should keep as "About the company"? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Us" section is not exactly boilerplate but it's generic company description. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It doesn't explicitly say to remove company description. However, they say "Prefer a few substantive sections over many thin ones." The "About Us" might be considered not substantive to the role. Usually we would include "About the role" or "Project Overview". The "About Us" could be omitted as it's not directly about the role. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The "About Us" is substantive about the company but maybe not needed for the role. However, they didn't say to remove it. But they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Us" is not those. But we might still include it as a section like "About the company" but they only gave allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list "About the company" or "About Us". So we should not create a heading not in that list. So we should omit the About Us section, or we could fold its content into a

  without a heading? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." It doesn't forbid other headings not listed, but they said "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, but likely they expect only those headings. Safer to stick to those. Thus we need sections: About the role (maybe from Project Overview), Responsibilities (Key Responsibilities), Requirements (maybe Required Skills & Experience), Qualifications (maybe Ideal Candidate Profile?), Skills (Preferred Skills?), Pay (Rate), Schedule (Schedule). Benefits? Not mentioned. So we omit Benefits. We need to ensure we don't create sections with filler. All sections have content. We need to use

  for each section heading. Inside each, we can have

  for prose and

  • for lists. We must not repeat job title as heading. Not needed. We must not include Job ID etc. We need to preserve all substantive information: that includes Work Designation (Home-based (Remote)), Equipment, Rate, Engagement Type, Project Overview, Responsibilities, Required Skills, Preferred Skills, Ideal Candidate Profile, Salary/Rate, Schedule (Monday-Friday 8-5 CST). Also maybe mention W2, Contract, 40 hours/week. We need to incorporate Work Designation and Equipment maybe into About the role section as prose. Let's craft:

    About the role

    Home-based (remote) position; candidate uses own or supplier-owned PC/MAC accessing systems via Virtual Desktop. Schedule: Monday‑Friday, 8:00 AM‑5:00 PM CST (or similar US business hours). Engagement type: Contract, W2, 40 hours/week. Rate: $50‑$58 per hour.

    This role supports a large‑scale enterprise initiative to replace 34,000 computers by the end of Q1 2027. The project requires extensive coordination to clean, process, and format user and device data, as well as project coordination work to ensure PC orders are processed accurately, efficiently, and on schedule. The client seeks an experienced Data Analyst / Data Wrangler to support the pre‑deployment data preparation phase. Responsibilities include cleaning and validating large datasets, filling gaps in existing records, and ensuring all user and device data is accurate and complete ahead of the mass PC replacement rollout.

    But we might split responsibilities into its own section. Better: About the role includes brief overview; Responsibilities separate. Let's do:

    About the role

    Home‑based (remote) role; candidate supplies own or supplier‑owned PC/MAC and connects via Virtual Desktop. Schedule: Monday‑Friday, 8:00 AM‑5:00 PM CST (or similar US business hours). Contract (W2) engagement, 40 hours/week, pay rate $50‑$58/hr.

    The position supports a large‑scale enterprise initiative to replace 34,000 computers by end of Q1 2027, requiring cleaning, processing, and formatting of user and device data to ensure accurate PC ordering and deployment.

    Then Responsibilities:

    Responsibilities

    • Perform advanced Excel‑based work (“Excel gymnastics”), including complex formulas, data wrangling, and data transformation
    • Identify and remove duplicate records (deduping) across large, multi‑source datasets
    • Conduct data analysis to surface missing, inconsistent, or inaccurate information
    • Fill in missing data within an existing spreadsheet to establish complete, accurate pre‑requisite data for all impacted users
    • Cross‑reference and validate data against Active Directory (AD) structure and attributes
    • Ensure data integrity and accuracy to support downstream PC ordering and deployment processes
    • Quickly adapt to shifting priorities, new data sources, and evolving project requirements as the initiative progresses
    • Collaborate with project coordination and deployment teams to ensure data readiness aligns with rollout timelines
    • Flag data anomalies or risks that could impact the success of device deployment for individual users or groups
    Requirements (maybe Required Skills & Experience):

    Requirements

    • Proven experience in data analysis, data wrangling, and data cleansing, ideally in a large‑scale IT asset or device deployment context
    • Advanced Excel proficiency – comfortable with complex formulas, lookups, pivot tables, and large dataset manipulation
    • Solid understanding of Active Directory (AD) structure and how user/device data maps within it
    • Strong experience deduplicating and reconciling data across multiple, potentially inconsistent sources
    • High attention to detail and a strong analytical mindset
    • Demonstrated ability to work accurately and efficiently under pressure amid rapidly changing requirements
    • Strong organizational skills with the ability to manage large volumes of data without losing accuracy
    Qualifications (maybe Ideal Candidate Profile):

    Qualifications

    The ideal candidate is a highly analytical, detail‑driven professional who thrives in a fast‑paced, high‑change environment. They should be comfortable working independently with messy, incomplete datasets, applying strong problem‑solving skills to fill gaps and resolve inconsistencies, while maintaining accuracy under tight deadlines as project needs evolve.

    Skills (Preferred Skills):

    Skills

    • Power BI experience – to help build reporting dashboards off the cleaned/processed data
    Pay:

    Pay

    $50‑$58 per hour (depends on experience level). W2 contract.

    Schedule:

    Schedule

    Monday‑Friday, 8:00 AM‑5:00 PM CST (or similar US business hours). Expected 40 hours/week.

    We should not include Benefits section as not mentioned. We need to ensure we didn't repeat any info unnecessarily. The About the role includes schedule and pay; we also have separate Pay and Schedule sections. Might be duplication. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we should combine Pay and Schedule into About the role, and not create separate Pay/Schedule sections if they are already covered. However, they said include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The posting does have specific content for Pay and Schedule, so we could include them. But we risk duplication. However, we could keep them separate but ensure not to repeat same sentences. In About the role we could keep a brief overview, and then Pay and Schedule sections give details. But the About the role already includes schedule and pay; we could keep them brief there and then more detail in dedicated sections. That's okay. But we need to avoid duplication of exact same sentences. Let's adjust About the role to not include the exact pay and schedule details, just mention remote, contract, etc. Then Pay and Schedule sections give specifics. Let's rewrite:

    About the role

    Home‑based (remote) Data Analyst / Data Wrangler position; candidate uses own or supplier‑owned PC/MAC accessing systems via Virtual Desktop. Contract (W2) engagement supporting a large‑scale enterprise initiative to replace 34,000 computers by end of Q1 20