Data Quality Specialist

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: Company description: first paragraph about Applied Intuition. That's not a heading; maybe we can include as a

before sections? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other

content outside sections. So we can include a brief intro paragraph. Then "About The Role" heading: we have content: "As a Data Quality Specialist you will be a critical component of our autonomous vehicle data pipeline. You will ensure the integrity and quality of data collected from our test vehicles, which is essential for training and improving our self-driving systems. Your meticulous review and verification processes will help maintain high data standards and facilitate the development of more accurate and reliable autonomous driving algorithms." Then bullet list under "At Applied Intuition, You Will": list of duties. Then "We're Looking For Someone Who Has": list of requirements. Then "Nice To Have": list of nice-to-have. Then compensation paragraph: "Compensation at Applied Intuition for eligible roles includes base salary, equity, and benefits. Base salary is a single component of the total compensation package, which may also include equity in the form of options and/or restricted stock units, comprehensive health, dental, vision, life and disability insurance coverage, 401k retirement benefits with employer match, learning and wellness stipends, and paid time off. Note that benefits are subject to change and may vary based on jurisdiction of employment." Then "Applied Intuition pay ranges reflect the minimum and maximum intended target base salary for new hire salaries for the position. The actual base salary offered to a successful candidate will additionally be influenced by a variety of factors including experience, credentials & certifications, educational attainment, skill level requirements, interview performance, and the level and scope of the position." Then "Compensation Range: $30 - $40". Likely per hour? Not specified but it's a range. We need to include Pay section only if posting actually states them. It does state compensation range. So we should include a Pay section with that range. Benefits: we have description of benefits (health, dental, vision, etc). So we can include Benefits section. Schedule: there is mention: "We are an in-office company, and our expectation is that full-time employees primarily work from their Applied Intuition office 5 days a week. However, we also recognize the importance of flexibility and trust our employees to manage their schedules responsibly. This may include occasional remote work, starting the day with morning meetings from home before heading to the office, or leaving earlier when needed to accommodate family commitments. This in-office expectation does not apply to contractor positions". That's schedule info. So we can include Schedule section. Qualifications vs Requirements vs Skills: The posting has "We're Looking For Someone Who Has" (requirements) and "Nice To Have" (nice-to-have). Could map Requirements to the required list, Skills maybe to nice-to-have? Or we could combine. The instruction: prefer a few substantive sections over many thin ones. We could have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly also Skills? But we have nice-to-have which could be Skills. However we might combine Requirements and Skills into one section? But we need to follow headings list; we can include only those with real content. We have content for Requirements (the required list). We have content for Skills (nice-to-have list). We have Benefits, Pay, Schedule. Also About the role. We should not include Qualifications if not distinct; but we could treat Requirements as Qualifications. However we have both Requirements and Qualifications headings in the list; we can choose to use Requirements for required qualifications, and Skills for nice-to-have. That seems reasonable. We must not include filler like "commensurate with experience". Not present. We must not include duplicated lines. We must output only HTML fragment, no /, no markdown fences. Let's craft:

Applied Intuition, Inc. is powering the future of physical AI. Founded in 2017 and now valued at $15 billion, the Silicon Valley company is creating the digital infrastructure needed to bring intelligence to every moving machine on the planet. Applied Intuition services the automotive, defense, trucking, construction, mining and agriculture industries in three core areas: tools and infrastructure, operating systems, and autonomy. Eighteen of the top 20 global automakers, as well as the United States military and its allies, trust the company’s solutions to deliver physical intelligence. Applied Intuition is headquartered in Sunnyvale, California, with offices in Washington, D.C.; San Diego; Ft. Walton Beach, Florida; Ann Arbor, Michigan; London; Stuttgart; Munich; Stockholm; Bangalore; Seoul; and Tokyo. Learn more at applied.co. We are an in-office company, and our expectation is that full-time employees primarily work from their Applied Intuition office 5 days a week. However, we also recognize the importance of flexibility and trust our employees to manage their schedules responsibly. This may include occasional remote work, starting the day with morning meetings from home before heading to the office, or leaving earlier when needed to accommodate family commitments. This in-office expectation does not apply to contractor positions

Then

About the role

with paragraph. Then

Responsibilities

with

• ... list. Then

  Requirements

  with
  • ... required list. Then

    Skills

    with
    • ... nice-to-have list. Then

      Benefits

      with
      • ... benefits list. Then

        Pay

        with

        Compensation Range: $30 - $40

        maybe also include description? But we already have benefits separate. The pay range is specific; we can include that. Then

        Schedule

        with

        ... schedule description (maybe we already included schedule in intro paragraph; but we should not duplicate. We could move schedule description to Schedule section and remove from intro. However the instruction: preserve ALL substantive information; we can keep it in Schedule section and not duplicate. The intro paragraph currently includes schedule info; we could remove that from intro and put in Schedule section. Let's do that: keep intro paragraph about company description only (without schedule). Then Schedule section will have the schedule details. Thus we need to adjust. Let's craft intro paragraph: company description only (first paragraph up to Learn more at applied.co). Then we will have About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Check that we haven't omitted any substantive info: we need to include the note about in-office expectation etc. That will go in Schedule section. Also need to include the line "We are an in-office company, and our expectation is that full-time employees primarily work from their Applied Intuition office 5 days a week. However, we also recognize the importance of flexibility and trust our employees to manage their schedules responsibly. This may include occasional remote work, starting the day with morning meetings from home before heading to the office, or leaving earlier when needed to accommodate family commitments. This in-office expectation does not apply to contractor positions". That's schedule. Now ensure we didn't miss any other info: The "Note that benefits are subject to change and may vary based on jurisdiction of employment." Should be included in Benefits section maybe as a note. Also the paragraph about compensation: "Compensation at Applied Intuition for eligible roles includes base salary, equity, and benefits. Base salary is a single component of the total compensation package, which may also include equity in the form of options and/or restricted stock units, comprehensive health, dental, vision, life and disability insurance coverage, 401k retirement benefits with employer match, learning and wellness stipends, and paid time off." That's benefits description; we can include in Benefits section. The paragraph about pay ranges: "Applied Intuition pay ranges reflect the minimum and maximum intended target base salary for new hire salaries for the position. The actual base salary offered to a successful candidate will additionally be influenced by a variety of factors including experience, credentials & certifications, educational attainment, skill level requirements, interview performance, and the level and scope of the position." Could be included in Pay section as a note. We must not invent or summarize away detail; we need to preserve all substantive information. So we should include those sentences as part of Benefits and Pay sections. Let's structure: Intro

        company description.

        About the role

        As a Data Quality Specialist you will be a critical component...

        Responsibilities

        • Review and validate data collected from test drives to ensure completeness, accuracy, and relevance
        ... etc.

        Requirements

        • 2+ years experience in data analysis, quality assurance, or related technical field
        ... etc.

        Skills

        • Experience with data visualization tools
        ... etc.

        Benefits

        • comprehensive health, dental, vision, life and disability insurance coverage
        • 401k retirement benefits with employer match
        • learning and wellness stipends
        • paid time off
        • equity in the form of options and/or restricted stock units
        plus a

        Note that benefits are subject to change and may vary based on jurisdiction of employment.

        plus maybe the earlier sentence about compensation includes base salary, equity, benefits. But equity already in list; base salary is part of Pay. We could include a

        Base salary is a single component of the total compensation package, which may also include equity... etc.

        but that duplicates equity. Might be okay but we risk duplication. Better to keep Benefits section focusing on non-salary benefits; we can include a sentence about total compensation package includes base salary, equity, benefits. But base salary will be in Pay section. So we can include a

        Total compensation package includes base salary, equity, and benefits.

        then list benefits. Let's include that.

        Pay

        Applied Intuition pay ranges reflect the minimum and maximum intended target base salary for new hire salaries for the position. The actual base salary offered to a successful candidate will additionally be influenced by a variety of factors including experience, credentials & certifications, educational attainment, skill level requirements, interview performance, and the level and scope of the position.

        Compensation Range: $30 - $40

        Schedule

        We are an in-office company, and our expectation is that full-time employees primarily work from their Applied Intuition office 5 days a week. However, we also recognize the importance of flexibility and trust our employees to manage their schedules responsibly. This may include occasional remote work, starting the day with morning meetings from home before heading to the office, or leaving earlier when needed to accommodate family commitments. This in-office expectation does not apply to contractor positions.

        Check we haven't missed any other substantive info: The "Please reference the job posting’s subtitle for where this position will be located." That's a minor metadata about location; we can drop as per instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it. This is minor metadata about location; we could drop it or include in a short p. Since we already have schedule section, location is not