HIL Test Engineer - System Test
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we must only include sections when posting has real specific content. We have content for About the role? The "Who we are" and "Meet the team" could be considered About the role? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map sections accordingly. We need to avoid repeating job title as heading. No Job ID. Remove boilerplate like EEO etc. Also remove application instructions (none present). We need to preserve all substantive info.
We need to decide sections: Perhaps "About the role" could combine "Who we are" and "Meet the team" and "Roles Overview". But we could also have separate sections: "About the role" (company overview), "Responsibilities", "Ideal Candidate" (maybe as Requirements/Qualifications/Skills), "Knowledge, Skills and Abilities" (maybe as Requirements). However we must not create sections with filler like "commensurate with experience". We have no Pay, Schedule, Benefits info. So we omit those sections.
We need to use - for any list of duties/requirements/benefits. So for responsibilities list, we need to turn each bullet into
- . The responsibilities paragraph is a long sentence with many duties separated by periods? Actually it's a paragraph with multiple sentences each describing a duty. We can split into list items per duty. Similarly Ideal Candidate bullet list: each sentence starting with "Has strong HIL instincts:" etc. We'll turn each into
- . Knowledge, Skills and Abilities: Required and Preferred sections; we can make subheadings? But only allowed headings are those listed; we could embed Required and Preferred as
with bold? But we must not invent headings not allowed? The instruction only says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Probably we should stick to those headings only. So we can have sections: About the role, Responsibilities, Requirements (maybe combine Ideal Candidate and Knowledge, Skills and Abilities), Skills (maybe separate). But we need to avoid thin sections. Let's think.
We have content: company overview, team description, role overview (scope). That could be About the role.
Responsibilities: we have a block starting with "Responsibilities:" then a paragraph with many duties. We'll make list.
Ideal Candidate: list of traits.
Knowledge, Skills and Abilities: Required and Preferred lists.
We could map Ideal Candidate to "Requirements" and Knowledge, Skills and Abilities to "Qualifications" or "Skills". But we have both Required and Preferred; we could combine into Requirements section with sublists? Might be okay.
Better: Use sections: About the role, Responsibilities, Requirements, Qualifications, Skills. But we need to ensure we don't create empty sections.
Let's extract content.
About the role: combine "Who we are:", "Meet the team:", "Roles Overview:" (the paragraph after Roles Overview:). We'll keep as prose (
). Might be long but okay.
Responsibilities: list each duty.
Requirements: maybe Ideal Candidate traits.
Qualifications: Knowledge, Skills and Abilities Required.
Skills: Knowledge, Skills and Abilities Preferred (or maybe Skills section for both required and preferred). But we need to avoid duplication.
Alternatively, we could have just three sections: About the role, Responsibilities, Requirements (which includes Ideal Candidate, Knowledge, Skills and Abilities). But the instruction says prefer a few substantive sections over many thin ones. So maybe three sections is fine.
Let's do:
About the role
...combined...
Responsibilities
- ...
...
Requirements
Ideal Candidate traits...
... (list of traits)
Knowledge, Skills and Abilities (Required)
... (list)
Preferred qualifications
... (list)
But we need to avoid headings inside Requirements besides the h3. Using for subheadings is okay.
We must not repeat job title. No metadata.
Now we need to extract the exact text preserving all substantive information, not inventing or summarizing away detail. We must keep details.
Let's copy the relevant sections.
Who we are: "Glydways is reimagining what public transit can be. We believe that mobility is the gateway to opportunity—connecting people to housing, education, employment, commerce, and care. By making transportation more accessible, affordable, and sustainable, we empower communities to thrive and unlock economic and social prosperity. Our mission is to revolutionize transit with a solution that delivers high capacity, exceptional user experiences, unmatched affordability, and minimal environmental impact. The Glydways system is a groundbreaking network of carbon-neutral, interconnected transit pathways powered by standardized autonomous vehicles on dedicated roadways. Operating 24/7 with on-demand access, it offers personalized and efficient mobility—without the burden of heavy upfront infrastructure costs or ongoing taxpayer subsidies. With Glydways, we’re building more than a transportation system; we’re creating a future where everyone, everywhere, has the freedom to move."
Meet the team: "At Glydways, the Test Engineering team is responsible for proving that our integrated autonomous transit system is safe, reliable, and ready for real-world operation. We work across autonomy, vehicle hardware, embedded software, systems engineering, safety, infrastructure, operations, quality, and deployment teams. Our work spans simulation, software-based test environments, Hardware-in-the-Loop (HIL) testing, lab testing, vehicle testing, test-track operations, and project-site commissioning. This role focuses on Hardware-in-the-Loop (HIL) testing and the test environments that allow Glydways to exercise real controllers, software, networks, interfaces, and failure modes before they reach vehicles, the test track, or customer sites."
Roles Overview: "We are seeking a System Test Engineer who can build, operate, and improve Hardware-in-the-Loop (HIL) test capabilities for a complex autonomous transit system. This role is ideal for someone who is comfortable at the boundary between test engineering, embedded systems, controls, software, hardware interfaces, automation, and data analysis. You will help ensure that system behavior, safety functions, regressions, and edge cases can be tested earlier, more often, and more repeatedly through high-quality HIL environments. You will develop HIL test procedures, automate regression tests, manage test configurations and data, analyze results, and improve the benches, simulators, harnesses, dashboards, and workflows that make system testing more scalable. We are open to candidates across a range of experience levels, from strong mid-level engineers through staff-level technical leaders. Scope and title will be calibrated based on experience. More senior candidates will be expected to own larger HIL capabilities, improve test architecture and process, mentor others, and represent test evidence in readiness and release discussions. This role will include hands-on work with test benches, controllers, networks, lab equipment, vehicles, and Glydways test facilities. Some travel or on-site presence should be expected for integration campaigns, test environment bring-up, and major release demonstrations."
Now Responsibilities block: after "Responsibilities:" we have a paragraph with many duties separated by periods. Let's extract sentences:
"Develop and execute Hardware-in-the-Loop (HIL) test plans, procedures, and automated test cases for integrated autonomous transit behavior."
"Build, configure, maintain, and improve HIL benches, test harnesses, simulated interfaces, real hardware interfaces, network setups, timing synchronization, data acquisition, and test data management."
"Translate requirements, operational scenarios, safety needs, and regression concerns into repeatable HIL tests with clear pass/fail criteria."
"Expand automated regression coverage so system behavior can be tested earlier and more frequently before vehicle or track testing."
"Execute and troubleshoot tests involving embedded controllers, vehicle subsystems, autonomy interfaces, communications, diagnostics, fault handling, and degraded-mode behavior."
"Analyze logs, telemetry, traces, dashboards, and bench observations to determine test outcomes, identify anomalies, and support root-cause analysis."
"Track HIL test failures from discovery through closure, including issue classification, impact assessment, regression scope, and verification of fixes."
"Improve test automation, simulators, tooling, dashboards, data pipelines, and reporting workflows to increase coverage, repeatability, execution speed, and confidence in test results."
"Support readiness reviews by preparing evidence on test environment readiness, configuration status, prerequisite completion, approved procedures, safety controls, and open issue disposition."
"Collaborate closely with embedded software, autonomy, vehicle engineering, systems engineering, safety, quality, operations, and deployment teams."
"Build lightweight tools, scripts, widgets, dashboards, or utilities when existing tools are not sufficient for the test work."
Now Ideal Candidate block: after "Ideal Candidate:" we have bullet-like sentences each starting with "Has strong HIL instincts:" etc. Let's extract each:
"Has strong HIL instincts: knows how to combine real hardware, simulated interfaces, automation, instrumentation, and data capture into a trustworthy test environment."
"Can turn ambiguity into clarity: drive vague, high-level needs into concrete bench tests, automated checks, pass/fail criteria, and release evidence."
"Thinks in interfaces and failure modes: understands how software, controllers, networks, sensors, actuators, timing, configuration, and operating assumptions interact."
"Has strong follow-through: closes the last 5% by cleaning up evidence, resolving ambiguity, documenting decisions, and leaving work in a reusable state."
"Communicates clearly and proactively: chooses the right medium and level of detail for the audience, creates durable artifacts when needed, and helps cross-functional teams align around complex technical problems."
"Is hands-on and data-driven: comfortable in the lab, with hardware, in logs, in Python, and in issue-tracking and requirements tools."
"Enjoys building practical tools and improving test infrastructure when that makes the test program more effective."
"Learns quickly and willingly adapts to new tools, workflows, and technical domains when the work requires it."
Now Knowledge, Skills and Abilities: Required and Preferred.
Required: after "Required:" we have list:
"Bachelor’s degree in Engineering, Computer Science, Robotics, Aerospace, Mechanical Engineering, Electrical Engineering, Systems Engineering, or a related technical field."
"4+ years of experience in system test, Hardware-in-the-Loop (HIL) testing, embedded systems test, systems integration, product validation, autonomous systems, robotics, transportation, aerospace, automotive, medical devices, industrial automation, or other complex hardware/software systems."
"Experience developing or executing integration-level or system-level tests, including scenario design, test procedures, acceptance criteria, execution, analysis, and reporting."
"Experience working with complex electromechanical or cyber-physical systems that combine software, controls, sensors, networks, hardware, safety constraints, and operational procedures."
"Ability to analyze logs, telemetry, traces, test data, and system behavior using tools such as Python, dashboards, log viewers, notebooks, or equivalent analysis environments."
"Demonstrated ability to collaborate across multidisciplinary teams and communicate technical risk, test outcomes, and blockers clearly."
Preferred: after "Preferred:" we have list:
"Hands-on experience building, maintaining, or extending Hardware-in-the-Loop (HIL) benches, test harnesses, simulators, automated regression frameworks, or continuous integration-driven test execution."
"Experience with embedded systems, controller testing, vehicle networks, diagnostics, fault injection, real-time systems, or hardware/software integration."
"Ability to read, modify, or write C
- for any list of duties/requirements/benefits. So for responsibilities list, we need to turn each bullet into
- . The responsibilities paragraph is a long sentence with many duties separated by periods? Actually it's a paragraph with multiple sentences each describing a duty. We can split into list items per duty. Similarly Ideal Candidate bullet list: each sentence starting with "Has strong HIL instincts:" etc. We'll turn each into
- . Knowledge, Skills and Abilities: Required and Preferred sections; we can make subheadings? But only allowed headings are those listed; we could embed Required and Preferred as
with bold? But we must not invent headings not allowed? The instruction only says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Probably we should stick to those headings only. So we can have sections: About the role, Responsibilities, Requirements (maybe combine Ideal Candidate and Knowledge, Skills and Abilities), Skills (maybe separate). But we need to avoid thin sections. Let's think. We have content: company overview, team description, role overview (scope). That could be About the role. Responsibilities: we have a block starting with "Responsibilities:" then a paragraph with many duties. We'll make list. Ideal Candidate: list of traits. Knowledge, Skills and Abilities: Required and Preferred lists. We could map Ideal Candidate to "Requirements" and Knowledge, Skills and Abilities to "Qualifications" or "Skills". But we have both Required and Preferred; we could combine into Requirements section with sublists? Might be okay. Better: Use sections: About the role, Responsibilities, Requirements, Qualifications, Skills. But we need to ensure we don't create empty sections. Let's extract content. About the role: combine "Who we are:", "Meet the team:", "Roles Overview:" (the paragraph after Roles Overview:). We'll keep as prose (
). Might be long but okay. Responsibilities: list each duty. Requirements: maybe Ideal Candidate traits. Qualifications: Knowledge, Skills and Abilities Required. Skills: Knowledge, Skills and Abilities Preferred (or maybe Skills section for both required and preferred). But we need to avoid duplication. Alternatively, we could have just three sections: About the role, Responsibilities, Requirements (which includes Ideal Candidate, Knowledge, Skills and Abilities). But the instruction says prefer a few substantive sections over many thin ones. So maybe three sections is fine. Let's do:
About the role
...combined...
Responsibilities
- ... ...
Requirements
Ideal Candidate traits...
- ... (list of traits)
Knowledge, Skills and Abilities (Required)
- ... (list)
Preferred qualifications
- ... (list)
for subheadings is okay. We must not repeat job title. No metadata. Now we need to extract the exact text preserving all substantive information, not inventing or summarizing away detail. We must keep details. Let's copy the relevant sections. Who we are: "Glydways is reimagining what public transit can be. We believe that mobility is the gateway to opportunity—connecting people to housing, education, employment, commerce, and care. By making transportation more accessible, affordable, and sustainable, we empower communities to thrive and unlock economic and social prosperity. Our mission is to revolutionize transit with a solution that delivers high capacity, exceptional user experiences, unmatched affordability, and minimal environmental impact. The Glydways system is a groundbreaking network of carbon-neutral, interconnected transit pathways powered by standardized autonomous vehicles on dedicated roadways. Operating 24/7 with on-demand access, it offers personalized and efficient mobility—without the burden of heavy upfront infrastructure costs or ongoing taxpayer subsidies. With Glydways, we’re building more than a transportation system; we’re creating a future where everyone, everywhere, has the freedom to move." Meet the team: "At Glydways, the Test Engineering team is responsible for proving that our integrated autonomous transit system is safe, reliable, and ready for real-world operation. We work across autonomy, vehicle hardware, embedded software, systems engineering, safety, infrastructure, operations, quality, and deployment teams. Our work spans simulation, software-based test environments, Hardware-in-the-Loop (HIL) testing, lab testing, vehicle testing, test-track operations, and project-site commissioning. This role focuses on Hardware-in-the-Loop (HIL) testing and the test environments that allow Glydways to exercise real controllers, software, networks, interfaces, and failure modes before they reach vehicles, the test track, or customer sites." Roles Overview: "We are seeking a System Test Engineer who can build, operate, and improve Hardware-in-the-Loop (HIL) test capabilities for a complex autonomous transit system. This role is ideal for someone who is comfortable at the boundary between test engineering, embedded systems, controls, software, hardware interfaces, automation, and data analysis. You will help ensure that system behavior, safety functions, regressions, and edge cases can be tested earlier, more often, and more repeatedly through high-quality HIL environments. You will develop HIL test procedures, automate regression tests, manage test configurations and data, analyze results, and improve the benches, simulators, harnesses, dashboards, and workflows that make system testing more scalable. We are open to candidates across a range of experience levels, from strong mid-level engineers through staff-level technical leaders. Scope and title will be calibrated based on experience. More senior candidates will be expected to own larger HIL capabilities, improve test architecture and process, mentor others, and represent test evidence in readiness and release discussions. This role will include hands-on work with test benches, controllers, networks, lab equipment, vehicles, and Glydways test facilities. Some travel or on-site presence should be expected for integration campaigns, test environment bring-up, and major release demonstrations." Now Responsibilities block: after "Responsibilities:" we have a paragraph with many duties separated by periods. Let's extract sentences: "Develop and execute Hardware-in-the-Loop (HIL) test plans, procedures, and automated test cases for integrated autonomous transit behavior." "Build, configure, maintain, and improve HIL benches, test harnesses, simulated interfaces, real hardware interfaces, network setups, timing synchronization, data acquisition, and test data management." "Translate requirements, operational scenarios, safety needs, and regression concerns into repeatable HIL tests with clear pass/fail criteria." "Expand automated regression coverage so system behavior can be tested earlier and more frequently before vehicle or track testing." "Execute and troubleshoot tests involving embedded controllers, vehicle subsystems, autonomy interfaces, communications, diagnostics, fault handling, and degraded-mode behavior." "Analyze logs, telemetry, traces, dashboards, and bench observations to determine test outcomes, identify anomalies, and support root-cause analysis." "Track HIL test failures from discovery through closure, including issue classification, impact assessment, regression scope, and verification of fixes." "Improve test automation, simulators, tooling, dashboards, data pipelines, and reporting workflows to increase coverage, repeatability, execution speed, and confidence in test results." "Support readiness reviews by preparing evidence on test environment readiness, configuration status, prerequisite completion, approved procedures, safety controls, and open issue disposition." "Collaborate closely with embedded software, autonomy, vehicle engineering, systems engineering, safety, quality, operations, and deployment teams." "Build lightweight tools, scripts, widgets, dashboards, or utilities when existing tools are not sufficient for the test work." Now Ideal Candidate block: after "Ideal Candidate:" we have bullet-like sentences each starting with "Has strong HIL instincts:" etc. Let's extract each: "Has strong HIL instincts: knows how to combine real hardware, simulated interfaces, automation, instrumentation, and data capture into a trustworthy test environment." "Can turn ambiguity into clarity: drive vague, high-level needs into concrete bench tests, automated checks, pass/fail criteria, and release evidence." "Thinks in interfaces and failure modes: understands how software, controllers, networks, sensors, actuators, timing, configuration, and operating assumptions interact." "Has strong follow-through: closes the last 5% by cleaning up evidence, resolving ambiguity, documenting decisions, and leaving work in a reusable state." "Communicates clearly and proactively: chooses the right medium and level of detail for the audience, creates durable artifacts when needed, and helps cross-functional teams align around complex technical problems." "Is hands-on and data-driven: comfortable in the lab, with hardware, in logs, in Python, and in issue-tracking and requirements tools." "Enjoys building practical tools and improving test infrastructure when that makes the test program more effective." "Learns quickly and willingly adapts to new tools, workflows, and technical domains when the work requires it." Now Knowledge, Skills and Abilities: Required and Preferred. Required: after "Required:" we have list: "Bachelor’s degree in Engineering, Computer Science, Robotics, Aerospace, Mechanical Engineering, Electrical Engineering, Systems Engineering, or a related technical field." "4+ years of experience in system test, Hardware-in-the-Loop (HIL) testing, embedded systems test, systems integration, product validation, autonomous systems, robotics, transportation, aerospace, automotive, medical devices, industrial automation, or other complex hardware/software systems." "Experience developing or executing integration-level or system-level tests, including scenario design, test procedures, acceptance criteria, execution, analysis, and reporting." "Experience working with complex electromechanical or cyber-physical systems that combine software, controls, sensors, networks, hardware, safety constraints, and operational procedures." "Ability to analyze logs, telemetry, traces, test data, and system behavior using tools such as Python, dashboards, log viewers, notebooks, or equivalent analysis environments." "Demonstrated ability to collaborate across multidisciplinary teams and communicate technical risk, test outcomes, and blockers clearly." Preferred: after "Preferred:" we have list: "Hands-on experience building, maintaining, or extending Hardware-in-the-Loop (HIL) benches, test harnesses, simulators, automated regression frameworks, or continuous integration-driven test execution." "Experience with embedded systems, controller testing, vehicle networks, diagnostics, fault injection, real-time systems, or hardware/software integration." "Ability to read, modify, or write C