QA Field Technician

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No filler like "commensurate with experience". We must preserve all substantive info, no invention, no summarizing away detail. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines. No job title heading. No Job ID/requisition numbers as headings. We need to parse the posting. Content: - TransCore (TRN), a subsidiary of ST Engineering, is seeking an energetic and focused QA Specialist to join our team in Orlando, Florida. - Job Summary: TransCore is seeking a dependable QA Field Technician to support field testing of tolling and traffic systems prior to lane openings. This role is 100% field-based, working on active roadway sites across Florida in coordination with drivers, technicians, and test teams—this is not an office-based position. - Title Note: This position is classified internally as “QA Specialist” for payroll and documentation purposes. - Key Requirements (Read Before Applying) Field-based role-- Regular, in-person attendance is required at active project and test locations, as well as occasional visits to the Orlando office may be required based on business needs. - Ability to travel throughout Florida as required; a company vehicle will be provided while performing testing activities - Travel may include multiple consecutive days - Ability to work a flexible schedule, including nights, weekends, and holidays, as operational needs require. Overtime and extended hours may be required based on testing schedules. - Valid driver’s license and a safe driving record required - What You’ll Be Doing This role is ideal for individuals who prefer hands-on, outdoor work rather than a desk-based environment. In this role, you will regularly: - Work at roadway and tolling test sites - Coordinate and execute live vehicle test runs - Support testing activities in active traffic environments - Travel to project locations is required based on testing schedules. - Essential Duties and Responsibilities: Duties include, but are not limited to: - Conduct field testing of tolling and traffic systems in controlled test, staging, and live traffic environments - Coordinate and perform vehicle-based test runs with drivers and field teams - Record, analyze, and document test data and results - Audit roadside toll transactions for accuracy - Identify, document, and report system defects and issues - Support testing demonstrations for agency partners - Track installation status and maintain QA punch lists - Prepare reports using Microsoft Excel, Word, and Smartsheet - Communicate testing progress and results to QA and project teams - Maintain testing equipment and company vehicles - Support deployment and maintenance teams as needed - Perform other duties as assigned - Minimum Qualifications - High school diploma or GED preferred - Typically requires 2–5 years of experience in field operations, technical support, or similar hands-on environments preferred - Basic computer proficiency, including Microsoft Excel and Word - Ability to follow instructions and work in a structured testing environment - Strong organizational and multitasking skills - Ability to work effectively in fast-paced, high-pressure field environments - Work Environment / Physical Demands - Frequent outdoor work in varying weather conditions - Work performed near moving traffic and mechanical equipment - Ability to stand, walk, bend, and lift up to 50 pounds occasionally - Work supports transportation systems for major transportation agencies - Role supports critical roadway operations and system readiness prior to lane openings - TransCore complies with federal and state disability laws and provides reasonable accommodation for employees with disabilities. We need to extract sections: About the role (maybe job summary), Responsibilities (essential duties), Requirements (key requirements), Qualifications (minimum qualifications), Skills (maybe basic computer proficiency, organizational skills, etc.), Benefits (none mentioned), Pay (none), Schedule (flexible schedule, nights, weekends, holidays, overtime). We must only include sections if there is real specific content. Benefits: none mentioned, so omit. Pay: none, omit. Schedule: we have schedule info: flexible schedule including nights, weekends, holidays, overtime. That's specific, so include Schedule section. Now we need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We'll include About the role (job summary), Responsibilities (essential duties), Requirements (key requirements), Qualifications (minimum qualifications), Skills (maybe combine some skill-based qualifications like computer proficiency, organizational skills, ability to follow instructions, etc.), Schedule (flexible schedule). We should not duplicate content. We must preserve all substantive info; do not invent or summarize away detail. So we need to keep details like location Orlando, Florida, company vehicle provided, travel throughout Florida, multiple consecutive days, valid driver's license, safe driving record, etc. Also mention that role is 100% field-based, not office-based. Title note internal classification. We need to ensure we don't repeat job title as heading. Already not. We need to avoid boilerplate like "TransCore complies with federal and state disability laws..." That's EEO/equal-opportunity boilerplate; we should remove it. Also remove "TransCore complies..." line. Also remove duplicated lines: maybe "Travel to project locations is required based on testing schedules." appears twice? Actually appears in "What You’ll Be Doing" bullet and also earlier? It appears in bullet list under What You’ll Be Doing: "Travel to project locations is required based on testing schedules." Also earlier maybe not. We'll keep only one occurrence. We need to output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

TransCore (TRN), a subsidiary of ST Engineering, is seeking an energetic and focused QA Specialist to join our team in Orlando, Florida. The role is classified internally as “QA Specialist” for payroll and documentation purposes. TransCore is seeking a dependable QA Field Technician to support field testing of tolling and traffic systems prior to lane openings. This position is 100% field‑based, working on active roadway sites across Florida in coordination with drivers, technicians, and test teams; it is not an office‑based position.

But we need to preserve all substantive info: mention that it's seeking QA Specialist, location Orlando, Florida, internal classification, dependable QA Field Technician, support field testing prior to lane openings, 100% field-based, active roadway sites across Florida, coordination with drivers, technicians, test teams, not office-based. We could combine into a paragraph or multiple paragraphs. Use

for prose. Next

Responsibilities

• Conduct field testing of tolling and traffic systems in controlled test, staging, and live traffic environments
• Coordinate and perform vehicle‑based test runs with drivers and field teams
• Record, analyze, and document test data and results
• Audit roadside toll transactions for accuracy
• Identify, document, and report system defects and issues
• Support testing demonstrations for agency partners
• Track installation status and maintain QA punch lists
• Prepare reports using Microsoft Excel, Word, and Smartsheet
• Communicate testing progress and results to QA and project teams
• Maintain testing equipment and company vehicles
• Support deployment and maintenance teams as needed
• Perform other duties as assigned

We might also include "Work at roadway and tolling test sites", "Coordinate and execute live vehicle test runs", "Support testing activities in active traffic environments", "Travel to project locations is required based on testing schedules." Those are similar to responsibilities but maybe they belong under Responsibilities as well. The "What You’ll Be Doing" list includes those. We should include them as responsibilities too. To preserve all substantive info, we need to include those bullets. However we already have similar bullets: "Coordinate and perform vehicle‑based test runs" vs "Coordinate and execute live vehicle test runs". Slight difference but both should be included. Also "Work at roadway and tolling test sites" and "Support testing activities in active traffic environments" and "Travel to project locations is required based on testing schedules." We'll add them. Thus responsibilities list will be longer. Next

Requirements

• Field‑based role – regular, in‑person attendance required at active project and test locations; occasional visits to the Orlando office may be required based on business needs
• Ability to travel throughout Florida as required; a company vehicle will be provided while performing testing activities
• Travel may include multiple consecutive days
• Ability to work a flexible schedule, including nights, weekends, and holidays, as operational needs require; overtime and extended hours may be required based on testing schedules
• Valid driver’s license and a safe driving record required

Note: schedule info also appears in Schedule section; we might avoid duplication. But we need to preserve all substantive info; if we put schedule info in Requirements, we might duplicate in Schedule. Better to separate: Requirements includes travel, attendance, driver license, etc. Schedule section includes flexible schedule details. However the schedule info is also a requirement. To avoid duplication, we could put schedule details only under Schedule and not repeat under Requirements. But the requirement list includes "Ability to work a flexible schedule, including nights, weekends, and holidays, as operational needs require. Overtime and extended hours may be required based on testing schedules." That's schedule-specific. We could move that to Schedule section and keep Requirements without schedule. However the requirement list also includes other items. Let's decide: We'll put schedule details under Schedule section only, and not duplicate under Requirements. So Requirements will exclude schedule bullet. Thus Requirements bullets: - Field‑based role – regular, in‑person attendance required at active project and test locations; occasional visits to the Orlando office may be required based on business needs - Ability to travel throughout Florida as required; a company vehicle will be provided while performing testing activities - Travel may include multiple consecutive days - Valid driver’s license and a safe driving record required Now

Qualifications

• High school diploma or GED preferred
• Typically requires 2–5 years of experience in field operations, technical support, or similar hands‑on environments preferred
• Basic computer proficiency, including Microsoft Excel and Word
• Ability to follow instructions and work in a structured testing environment
• Strong organizational and multitasking skills
• Ability to work effectively in fast‑paced, high‑pressure field environments

Now

Skills

We could list skills like: ability to coordinate vehicle test runs, record/analyze/document data, audit toll transactions, identify/report defects, support demonstrations, track installation, prepare reports using Excel/Word/Smartsheet, communicate progress, maintain equipment, etc. But many of those are responsibilities. Skills section could include: computer proficiency (Excel, Word, Smartsheet), organizational/multitasking, communication, ability to work outdoors, etc. However we risk duplicating. The instruction: Prefer a few substantive sections over many thin ones. We could combine Skills into Qualifications or Responsibilities. But we have to use headings only when posting has real specific content for it. Does the posting have a distinct "Skills" section? Not explicitly; it's mixed. However we could still create a Skills section if we can extract skill-specific content not covered elsewhere. But we might be better to omit Skills section to avoid thin sections. The instruction: Prefer a few substantive sections over many thin ones. So we could omit Skills if it would be thin. However we have some skill-based items like "Basic computer proficiency, including Microsoft Excel and Word" already in Qualifications. "Strong organizational and multitasking skills" also in Qualifications. "Ability to follow instructions" also in Qualifications. So Skills would be thin