LiDAR Processing Technician

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (maybe Qualifications), Skills, Benefits, Pay, Schedule. Use

for each heading. Use

• for lists. Use

  for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove application instructions (How to apply). Also remove duplicated lines. Keep substantive info. We need to parse the posting. Key sections: - Intro paragraph: "Thomas & Hutton is seeking a detail-oriented LiDAR Processing Technician to support our surveying and geospatial teams through accurate processing, classification, and drafting of LiDAR data. This role focuses on transforming raw point cloud data into high-quality deliverables using TopoDOT and AutoCADD. The ideal candidate has a strong technical foundation, an understanding of survey workflows, and a commitment to accuracy, efficiency, and continuous improvement." That's about the role. - Key Responsibilities: list bullet points. - Required Qualifications: list bullet points. - Preferred Qualifications: list bullet points. - Why Thomas & Hutton? includes bullet list of benefits: Competitive salary plus annual bonus; Condensed work schedule for better work-life balance; Top-tier health, dental, vision, and prescription coverage; 401(k), generous PTO, holidays, and tuition assistance; Thomas & Hutton University and hands-on mentoring to advance your career. - Schedule: On-site: Monday–Thursday 7:30 a.m.–5:30 p.m.; Friday 7:30 a.m.–11:30 a.m. Occasional evening and weekend work may be required. - Pay: Not explicitly given except "Competitive salary plus annual bonus". That's a benefit, but we can put under Benefits. Pay section only if posting actually states them. It says "Competitive salary plus annual bonus". That's a statement about pay/compensation. So we could include a Pay section with that statement. However the instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive salary plus annual bonus, so we can include Pay. But also benefits list includes health etc. So we could have Benefits section for health, PTO etc. Pay section for salary+bonus. Schedule: we have schedule details. We must not include filler like "commensurate with experience". Not present. We need to avoid duplication: The "Why Thomas & Hutton?" includes bullet list that also mentions condensed work schedule (which overlaps with Schedule). But we can keep both; but maybe we should avoid duplication. The schedule is separate; the benefit list includes "Condensed work schedule for better work-life balance". That's a benefit description; we can keep it under Benefits. The Schedule section will have explicit schedule. We need to preserve all substantive info; not invent or summarize away detail. So we need to include all bullet points exactly as given (or close). We must not omit any. Let's extract bullet points: Key Responsibilities: - Process, classify, and analyze LiDAR point cloud data using TopoDOT - Generate survey-grade deliverables including: - Topographic surfaces and contours - Breaklines, features, and planimetric mapping - Draft and edit drawings in AutoCADD in accordance with company and client standards - Perform quality control (QC) checks to ensure accuracy, completeness, and compliance with project specifications - Collaborate with surveyors, project managers, and field crews to clarify data requirements and resolve discrepancies - Manage large datasets efficiently while meeting project schedules and deadlines - Maintain organized project files and documentation - Assist in developing and improving LiDAR processing workflows and best practices Required Qualifications: - Proficiency in TopoDOT for LiDAR processing and feature extraction required - Strong working knowledge of AutoCADD - Understanding of surveying principles, coordinate systems, and datums - Experience working with point clouds from mobile or aerial LiDAR systems - Ability to interpret survey control, field notes, and project specifications - Strong attention to detail and accuracy - Effective communication and teamwork skills Preferred Qualifications: - TopoDOT Experience required (maybe duplicate? Actually says "TopoDOT Experience required" under Preferred Qualifications but also required earlier; we keep as is) - 2+ years of LiDAR processing or survey drafting experience - Experience with drone LiDAR or mobile LiDAR datasets - Experience with additional software such as Civil 3D, or MicroStation Why Thomas & Hutton? (Benefits): - Competitive salary plus annual bonus - Condensed work schedule for better work-life balance - Top-tier health, dental, vision, and prescription coverage - 401(k), generous PTO, holidays, and tuition assistance - Thomas & Hutton University and hands-on mentoring to advance your career Schedule: - On-site: Monday–Thursday 7:30 a.m.–5:30 p.m.; Friday 7:30 a.m.–11:30 a.m. - Occasional evening and weekend work may be required. We also have some prose about mission etc. That's boilerplate? It's about mission, values, career development programs etc. Might be considered boilerplate but it's substantive about company culture. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The mission paragraph is not exactly boilerplate; it's about company values. Might be okay to keep as prose under About the role or a separate section like "About the company". But we only have headings for specific categories; we could include a paragraph under About the role (the intro) and maybe another paragraph about company values under a section like "About Thomas & Hutton". However the instruction says to use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we can use those headings; we could also add others if needed but better to stick to those. The mission paragraph could be placed under About the role as additional prose. We also have a line: "Please note: Sponsorship is not available for this position. Thomas & Hutton is a Drug-Free Workplace and an E-Verify participant. We are an equal opportunity employer. Qualified minorities, women, veterans and individuals with disabilities are encouraged to apply. We may use artificial intelligence (AI) tools to support parts of the hiring process, such as reviewing applications and analyzing resumes. These tools assist our recruitment team but do not replace human judgment. Final hiring decisions are ultimately made by humans. If you would like more information about how your data is processed, please contact us." This is EEO/legal boilerplate; should be removed. Also "How to apply: Ready to design the systems that support communities and essential infrastructure? Apply today at www.thomasandhutton.com/careers." Remove. Now we need to output HTML fragment only. Structure:

  About the role

  Thomas & Hutton is seeking a detail-oriented LiDAR Processing Technician to support our surveying and geospatial teams through accurate processing, classification, and drafting of LiDAR data. This role focuses on transforming raw point cloud data into high-quality deliverables using TopoDOT and AutoCADD. The ideal candidate has a strong technical foundation, an understanding of survey workflows, and a commitment to accuracy, efficiency, and continuous improvement.

  Thomas & Hutton’s mission of “Building Relationships and Solutions for Success” shapes how we serve our clients, strengthen our communities, and invest in our team. As a private employee-owned firm consistently recognized as a Top Workplace and recipient of PSMJ's Build a Better World Award, we're known not only for exceptional projects but for how we treat people and our communities. When you join Thomas & Hutton, you'll discover a career with real purpose. We equip you with cutting-edge tools, technology, and software to work efficiently and excel. Our career development programs, including PaTHways and T&H University, combine with approachable leadership and a collaborative environment to support your professional growth at every stage. Pair that with industry-leading benefits, genuine work-life balance, and meaningful opportunities to give back through T&H Helping Hands, and it's clear why so many professionals choose to grow their careers here.

  But note: The mission paragraph includes mention of PaTHways and T&H University etc. That's substantive; we can keep. Now Responsibilities:

  Responsibilities

  • Process, classify, and analyze LiDAR point cloud data using TopoDOT
  • Generate survey-grade deliverables including:
    • Topographic surfaces and contours
    • Breaklines, features, and planimetric mapping
  • Draft and edit drawings in AutoCADD in accordance with company and client standards
  • Perform quality control (QC) checks to ensure accuracy, completeness, and compliance with project specifications
  • Collaborate with surveyors, project managers, and field crews to clarify data requirements and resolve discrepancies
  • Manage large datasets efficiently while meeting project schedules and deadlines
  • Maintain organized project files and documentation
  • Assist in developing and improving LiDAR processing workflows and best practices
  But note nested list: we can keep as separate
• with inner
  . That's fine. Now Requirements (maybe combine Required and Preferred Qualifications under Qualifications? The instruction says headings: Requirements, Qualifications, Skills. We could have Required Qualifications under Requirements, Preferred Qualifications under Qualifications, and maybe Skills under Skills? But we have skills listed in responsibilities and qualifications. Could combine. However we need to follow instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should include those headings if we have content. We have Required Qualifications and Preferred Qualifications. We could put Required under Requirements, Preferred under Qualifications. Skills maybe we can extract from responsibilities? But we could also put a Skills section summarizing technical skills: TopoDOT, AutoCAD, etc. However we must not invent or summarize away detail; we could list skills from the qualifications. But we already have them under Requirements and Qualifications. Might be redundant to have Skills section. Better to not create Skills if no specific content beyond what's already covered. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Required and Preferred into Qualifications section, and maybe not have Requirements separate. But we need to follow the example headings; it's not mandatory to use all. We'll decide to have Requirements (for required qualifications) and Qualifications (for preferred). That seems reasonable. Thus:

  Requirements

  • Proficiency in TopoDOT for LiDAR processing and feature extraction required
  • Strong working knowledge of AutoCADD
  • Understanding of surveying principles, coordinate systems, and datums
  • Experience working with point clouds from mobile or aerial LiDAR systems
  • Ability to interpret survey control, field notes, and project specifications
  • Strong attention to detail and accuracy
  • Effective communication and teamwork skills

  Qualifications

  • TopoDOT Experience required
  • 2+ years of LiDAR processing or survey drafting experience
  • Experience with drone LiDAR or mobile LiDAR datasets
  • Experience with additional software such as Civil 3D, or MicroStation
  Now Benefits:

  Benefits

  • Competitive