Technical Lead, Installation
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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 the 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/Benef sections unless posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting: - Intro: "Kapsch is one of Austria's most successful global technology companies..." This is about the company. Could be "About the role"? Actually "About the role" would be description of role. The intro is about company, not role. Could be "About the role" includes responsibilities? Usually "About the role" is a short description. We can include a section "About the role" with the description of the role: "The Technical Lead, Installation is responsible for the installation of tolling equipment across multiple projects." plus maybe "How You'll Make An Impact" bullet list. - Responsibilities: The bullet list under "How You'll Make An Impact" includes many tasks. Those are responsibilities. - Requirements/Qualifications/Skills: The "What Makes You a Great Fit" includes experience, abilities, etc. Could be split into Requirements and Skills. But we can combine into one section "Requirements" or "Qualifications". The instruction says we can use headings like Requirements, Qualifications, Skills. We need to decide which sections to include based on content. We have content for responsibilities, requirements/qualifications/skills, benefits, pay, schedule. - Benefits: "What We Offer" includes: opportunity to solve complex problems, career growth, stability, opportunity to develop within a global organization, competitive compensation ranging from $29.00 - $37.00 based on experience, skills, internal equity, and market data, plus plenty of opportunity for overtime, A full benefits package, including unlimited paid time off, 11 paid holidays, 401(k), a no-cost medical insurance option for employees and eligible dependents, and an FSA option. Thus we have Pay: competitive compensation ranging from $29.00 - $37.00 based on experience... plus overtime. So we can have a Pay section. Benefits: unlimited paid time off, 11 paid holidays, 401(k), no-cost medical insurance, FSA. Schedule: The posting mentions "Ability to flexible full time schedule to include days, evenings, weekends and holidays." and "Flexibility to work schedules driven by project requirements, including weekends, night shifts, and extended hours when required." Also "Availability to travel approximately 75% of the time". Travel is not schedule but could be part of schedule? Might be considered schedule. However schedule section should be included only if posting actually states them. It does mention schedule flexibility. So we can include a Schedule section with those details. We must not include filler like "commensurate with experience" etc. The pay section includes a range, that's specific. We need to remove boilerplate: The AI note, working rights, background check, accommodations, EEO, drug-free workplace. Those are legal/EEO boilerplate; remove them. Also remove duplicated lines: The posting may have duplicated content? Not obvious. We need to preserve all substantive information. So we need to include the company intro? The instruction says "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." The company intro is not a heading; we could include it as a paragraph before sections? The output should be only HTML fragment, no /. We can include a
for company overview if we want, but we need to decide if we need a section for it. The instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other paragraphs outside headings. We could include a brief intro paragraph about the company before the sections. However the instruction says "Prefer a few substantive sections over many thin ones." It doesn't forbid extra paragraphs. But we should include all substantive information. The company intro is substantive. So we can include a
at start. But we need to ensure we don't create sections with filler. We'll create sections: About the role (maybe short description), Responsibilities, Requirements (or Qualifications/Skills), Benefits, Pay, Schedule. We need to decide what goes into each. About the role: Could be a short paragraph summarizing the role: "The Technical Lead, Installation is responsible for the installation of tolling equipment across multiple projects." plus maybe "How You'll Make An Impact" is more like responsibilities. So About the role could be just that sentence. Responsibilities: list of tasks from "How You'll Make An Impact". We'll put each as
for company overview: "Kapsch is one of Austria's most successful global technology companies. With its comprehensive ITS (Intelligent Transportation Systems) portfolio, Kapsch is actively addressing the challenges of the present and the future with intelligent mobility solutions in a wide range of application areas. As a family-owned company founded in 1892 and headquartered in Vienna, Kapsch can look back on 130 years of experience with the future." Then sections:
About the role
The Technical Lead, Installation is responsible for the installation of tolling equipment across multiple projects.
Responsibilities
- Support installation manager in planning day-to-day installation activities.
- Perform pre-installation site visits, site acceptance visits and RF surveys.
- Manage project hardware inventory required for installation, this includes receiving, quality checks, burn-ins and staging.
- Coordinate daily installation activities.
- Supervise technicians and subcontractors performing installations, modifications, and repairs of toll systems equipment and related systems.
- Test toll collection systems through physical inspection and electronic test and measurement equipment procedures.
- Perform diagnosis of equipment problems with lane control servers and computers, cameras, message signs, scanners, and other tolling system equipment.
- Document field changes during installation.
- Complete installation checklist and configuration records.
- Follow all Client and Kapsch safety standards and requirements.
- Ensure all safety practices are followed and host regular safety meetings with internal and external resources.
Requirements
- Experience supervising day-to-day installation activities.
- Proven experience troubleshooting and diagnosing equipment and system issues in the field.
- Ability to read and interpret technical drawings, wiring diagrams, installation plans, and engineering documentation.
- Technical background in electrical or electronic.
- Hands-on experience with coaxial cable terminations and low-voltage systems (24V-48V).
- Strong knowledge of low-voltage troubleshooting.
- Experience with IP configuration, network-connected devices, and basic networking concepts.
- Familiarity with point-to-point wiring, cable routing, and field installation best practices.
- Ability to lead technicians and subcontractors while ensuring safety, quality, and adherence to project schedules.
- Comfortable working in a fast-paced field environment with changing priorities and multiple concurrent activities.
- Ability to work a flexible full-time schedule to include days, evenings, weekends and holidays.
- Ability to work outdoors in all weather conditions.
- Availability to travel approximately 75% of the time, based on project needs.
- Flexibility to work schedules driven by project requirements, including weekends, night shifts, and extended hours when required.