Mapping Specialist
Drone.vet · Sunnyvale, CA · 1 mo ago
OTHR$15/hrFull-time
We need to output HTML fragment with 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. Must not include boilerplate, EEO, etc. Must preserve all substantive info. Must not invent or summarize away detail. Must not include placeholder text.
We need to parse the posting.
First paragraph about company: "Applied Intuition, Inc. is powering the future of physical AI..." This is about the company, could be "About the role"? Actually "About the role" is typical heading for description of role. The company description could be placed under "About the role" or maybe separate "About the company". But only allowed headings are those listed. We can put company overview under "About the role". The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings. We need to include sections only when posting has real specific content.
We have content:
- About the role: description of role, mapping specialists, tasks, etc. Also company overview maybe.
- Responsibilities: list bullet points under "Key Responsibilities". Those are specific.
- Requirements: list bullet points under "Requirements". Those are specific.
- Preferred Qualifications: list bullet points under "Preferred Qualifications". Could be placed under "Qualifications" or "Skills"? The allowed headings include Qualifications and Skills. We could put "Qualifications" for required qualifications? Actually "Requirements" heading is for requirements. "Qualifications" could be for preferred qualifications. "Skills" could be for skills like programming, etc. But we need to decide.
We have "Preferred Qualifications" list. Also there is a line: "Don’t meet every single requirement? ..." That's encouragement, could be placed maybe under a note but not a heading. We can include as a paragraph under Requirements or Qualifications.
We also have schedule info: "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 a Schedule section.
Pay: Not mentioned. Benefits: Not mentioned. So we should NOT include Benefits or Pay sections because no specific content.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Schedule.
We need to decide what goes where.
About the role: Could include company overview and role description: "Applied Intuition, Inc. is powering the future of physical AI... We are seeking skilled Mapping Specialists to support the creation and refinement of high definition HD maps for autonomous vehicles..." plus details about the work.
Responsibilities: bullet list from "Key Responsibilities".
Requirements: bullet list from "Requirements".
Qualifications: bullet list from "Preferred Qualifications". Could also include "Bachelor's Degree or higher education" but that's already in Requirements. Actually Requirements includes "Bachelor's Degree or higher education". So Qualifications could be preferred qualifications.
Skills: Could include specific skills like "Experience working with point cloud data, 3D visualization environments, or lidar-based annotation tools", "Strong attention to detail", "Comfortable with repetitive, accuracy-focused tasks", "Self-sufficient and organized in remote, asynchronous, fast paced work environment". But those are already in Requirements. Might be redundant. Perhaps we can put technical skills under Skills: "Experience with point cloud data, 3D visualization, lidar annotation tools; Familiarity with Git, GitHub, Jira, Google Workspace, Slack; Basic scripting skills in Python or SQL; Experience with browser-based map editors; Familiarity with HD map standards (ADP, Apollo, Lanelet2, OpenDRIVE); Familiarity with feedback loops between mapping, perception, planning; Familiarity with log-based resimulation tooling and simulation-based map validation". However many of those appear in Requirements or Preferred Qualifications. To avoid duplication, we could keep Requirements as the list of required experience/education, Qualifications as preferred qualifications, and Skills maybe not needed if content overlaps. But we need to follow instruction: "Prefer a few substantive sections over many thin ones." So we could omit Skills if it would be thin. But we have some skill-specific content not captured elsewhere? Let's see.
Requirements list:
- 3+ years of experience in map creation and maintenance, ideally in a relevant field such as autonomous vehicle mapping, GIS, or 3D game design
- Bachelor's Degree or higher education
- A strong understanding of lane-level geometry at CM precision, routing, and HD (High-Definition) map structures used in autonomous driving.
- Experience working with point cloud data, 3D visualization environments, or lidar-based annotation tools
- Strong attention to detail and ability to follow precise digitization protocols
- Comfortable with repetitive, accuracy-focused tasks and versioned map delivery
- Self-sufficient and organized in remote, asynchronous, fast paced work environment
Preferred Qualifications list:
- Familiarity with autonomous vehicle maps, AV datasets, or HD mapping pipelines
- Background in HD map pipelines for AV systems, robotics, or mapping platforms
- Prior experience with ADP, Apollo, Lanelet2, OpenDRIVE, or similar HD map standards/formats
- Experience using browser-based map editors or web-based 3D tooling
- Programming: Basic scripting skills in Python or SQL and command line tooling
- Familiarity with feedback loops between mapping, perception, and planning teams
- Familiarity with log-based resimulation tooling and simulation-based map validation
Thus we could map:
- About the role: company overview + role description (first two paragraphs).
- Responsibilities: bullet list from Key Responsibilities.
- Requirements: bullet list from Requirements.
- Qualifications: bullet list from Preferred Qualifications.
- Schedule: paragraph about in-office expectation and flexibility.
We don't need Skills section.
Check if any content about Benefits or Pay: none, so omit.
Now we must ensure we don't include boilerplate: EEO, equal opportunity, accommodation, etc. Must remove those lines. Also remove "Learn more at applied.co." maybe keep as part of About the role? It's not boilerplate but it's a link; could be kept. However it's not essential; but we can keep as part of About the role.
Also remove "We are an in-office company..." that's schedule, we keep.
Remove "Applied Intuition is an equal opportunity employer..." etc. Remove all EEO lines.
Also remove "Don’t meet every single requirement? If you’re excited about this role but your past experience doesn’t align perfectly with every qualification in the job description, we encourage you to apply anyway. You may be just the right candidate for this or other roles." This is encouragement; could be kept as a note under Requirements or Qualifications. It's substantive? It's not a requirement but it's a statement encouraging applicants. Could be included as a paragraph under Requirements or Qualifications. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. Where to place? Probably under Requirements as a note.
Also remove "For US-Based Roles: Applied Intuition is committed to providing an accessible and inclusive application and interview experience..." That's accommodation info, which is EEO-related; should be removed per instruction to remove EEO/equal-opportunity boilerplate. So remove that.
Now produce HTML.
Structure:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings. We need to include sections only when posting has real specific content.
We have content:
- About the role: description of role, mapping specialists, tasks, etc. Also company overview maybe.
- Responsibilities: list bullet points under "Key Responsibilities". Those are specific.
- Requirements: list bullet points under "Requirements". Those are specific.
- Preferred Qualifications: list bullet points under "Preferred Qualifications". Could be placed under "Qualifications" or "Skills"? The allowed headings include Qualifications and Skills. We could put "Qualifications" for required qualifications? Actually "Requirements" heading is for requirements. "Qualifications" could be for preferred qualifications. "Skills" could be for skills like programming, etc. But we need to decide.
We have "Preferred Qualifications" list. Also there is a line: "Don’t meet every single requirement? ..." That's encouragement, could be placed maybe under a note but not a heading. We can include as a paragraph under Requirements or Qualifications.
We also have schedule info: "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 a Schedule section.
Pay: Not mentioned. Benefits: Not mentioned. So we should NOT include Benefits or Pay sections because no specific content.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Schedule.
We need to decide what goes where.
About the role: Could include company overview and role description: "Applied Intuition, Inc. is powering the future of physical AI... We are seeking skilled Mapping Specialists to support the creation and refinement of high definition HD maps for autonomous vehicles..." plus details about the work.
Responsibilities: bullet list from "Key Responsibilities".
Requirements: bullet list from "Requirements".
Qualifications: bullet list from "Preferred Qualifications". Could also include "Bachelor's Degree or higher education" but that's already in Requirements. Actually Requirements includes "Bachelor's Degree or higher education". So Qualifications could be preferred qualifications.
Skills: Could include specific skills like "Experience working with point cloud data, 3D visualization environments, or lidar-based annotation tools", "Strong attention to detail", "Comfortable with repetitive, accuracy-focused tasks", "Self-sufficient and organized in remote, asynchronous, fast paced work environment". But those are already in Requirements. Might be redundant. Perhaps we can put technical skills under Skills: "Experience with point cloud data, 3D visualization, lidar annotation tools; Familiarity with Git, GitHub, Jira, Google Workspace, Slack; Basic scripting skills in Python or SQL; Experience with browser-based map editors; Familiarity with HD map standards (ADP, Apollo, Lanelet2, OpenDRIVE); Familiarity with feedback loops between mapping, perception, planning; Familiarity with log-based resimulation tooling and simulation-based map validation". However many of those appear in Requirements or Preferred Qualifications. To avoid duplication, we could keep Requirements as the list of required experience/education, Qualifications as preferred qualifications, and Skills maybe not needed if content overlaps. But we need to follow instruction: "Prefer a few substantive sections over many thin ones." So we could omit Skills if it would be thin. But we have some skill-specific content not captured elsewhere? Let's see.
Requirements list:
- 3+ years of experience in map creation and maintenance, ideally in a relevant field such as autonomous vehicle mapping, GIS, or 3D game design
- Bachelor's Degree or higher education
- A strong understanding of lane-level geometry at CM precision, routing, and HD (High-Definition) map structures used in autonomous driving.
- Experience working with point cloud data, 3D visualization environments, or lidar-based annotation tools
- Strong attention to detail and ability to follow precise digitization protocols
- Comfortable with repetitive, accuracy-focused tasks and versioned map delivery
- Self-sufficient and organized in remote, asynchronous, fast paced work environment
Preferred Qualifications list:
- Familiarity with autonomous vehicle maps, AV datasets, or HD mapping pipelines
- Background in HD map pipelines for AV systems, robotics, or mapping platforms
- Prior experience with ADP, Apollo, Lanelet2, OpenDRIVE, or similar HD map standards/formats
- Experience using browser-based map editors or web-based 3D tooling
- Programming: Basic scripting skills in Python or SQL and command line tooling
- Familiarity with feedback loops between mapping, perception, and planning teams
- Familiarity with log-based resimulation tooling and simulation-based map validation
Thus we could map:
- About the role: company overview + role description (first two paragraphs).
- Responsibilities: bullet list from Key Responsibilities.
- Requirements: bullet list from Requirements.
- Qualifications: bullet list from Preferred Qualifications.
- Schedule: paragraph about in-office expectation and flexibility.
We don't need Skills section.
Check if any content about Benefits or Pay: none, so omit.
Now we must ensure we don't include boilerplate: EEO, equal opportunity, accommodation, etc. Must remove those lines. Also remove "Learn more at applied.co." maybe keep as part of About the role? It's not boilerplate but it's a link; could be kept. However it's not essential; but we can keep as part of About the role.
Also remove "We are an in-office company..." that's schedule, we keep.
Remove "Applied Intuition is an equal opportunity employer..." etc. Remove all EEO lines.
Also remove "Don’t meet every single requirement? If you’re excited about this role but your past experience doesn’t align perfectly with every qualification in the job description, we encourage you to apply anyway. You may be just the right candidate for this or other roles." This is encouragement; could be kept as a note under Requirements or Qualifications. It's substantive? It's not a requirement but it's a statement encouraging applicants. Could be included as a paragraph under Requirements or Qualifications. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. Where to place? Probably under Requirements as a note.
Also remove "For US-Based Roles: Applied Intuition is committed to providing an accessible and inclusive application and interview experience..." That's accommodation info, which is EEO-related; should be removed per instruction to remove EEO/equal-opportunity boilerplate. So remove that.
Now produce HTML.
Structure:
About the role
... company overview and role description ...
Responsibilities
- ... ...
Requirements
- ... ...
Don’t meet every single requirement? If you’re excited about this role but your past experience doesn’t align perfectly with every qualification in the job description, we encourage you to apply anyway. You may be just the right candidate for this or other roles.
Qualifications
- ... ...
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 that we haven't repeated any content inadvertently. Now craft the About the role paragraph. Original text: "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 Applied Intuition is seeking skilled Mapping Specialists to support the creation and refinement of high definition HD maps for autonomous vehicles. These maps are 100x more detailed than standard road maps and serve as foundational inputs to Autonomous Vehicle perception, planning, and localization systems. In this full time role, you’ll work with point clouds, aerial imagery, street-level imagery, and other 3D spatial datasets using Applied’s cartography web app. You’ll perform detailed digitization of road environments, adhering to strict mapping specifications, and contribute directly to improving AV stack performance. This is an excellent opportunity for professionals with a background in HD map creation, GIS mapping, spatial annotation, or 3D modeling for autonomy, robotics, simulation, or gaming who are comfortable with technical workflows and fast paced, iterative feedback cycles." We need to split: About the role should include company overview and role description but not schedule (we moved schedule to its own section). Also we should not repeat the schedule paragraph in About the role. So we need to remove schedule sentences from About the role. Thus About the role paragraph: combine company overview and role description up to "Iterative feedback cycles." but exclude schedule sentences. 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;