Embedded Software Test Automation Engineer
for section headings.
Use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
Thus we should strip the EEO paragraph at end, also the "#VR-LI1" maybe.
Also remove "Why IDEXX" maybe? That's promotional but could be considered boilerplate? It's not required but could be considered fluff. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why IDEXX" is not explicitly listed, but could be considered promotional; but we might keep if it's substantive? It's more marketing. Safer to remove? The instruction says preserve ALL substantive information; does "Why IDEXX" count as substantive? It's about company mission, maybe not essential to role. Might be considered boilerplate? Not sure. Safer to keep? The instruction only mandates removal of certain types; not all fluff. So we can keep it if we want, but we need to avoid duplication. It's not duplicated. Could keep as a paragraph under maybe "About the role" or separate? But we have no heading for it. Could include as a paragraph under About the role? Might be okay.
But we need to follow the rule: include a section ONLY when the posting has real, specific content for it. So we need to decide which sections we have content for.
We have:
- About the role: yes.
- Responsibilities: yes.
- Requirements: yes (the Required list).
- Qualifications: maybe we can combine Strongly Preferred and Preferred as Qualifications.
- Skills: maybe we can extract programming languages etc. But that's already in Requirements. Could make Skills separate but might be thin. Better to combine into Requirements.
- Benefits: yes.
- Pay: yes (base salary range, bonus, merit increases). Could be part of Benefits? But we have separate Pay section allowed. We'll include Pay.
- Schedule: no content, so omit.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We need to ensure we don't repeat info.
Let's extract precise content.
About the role: Combine first paragraph(s) up to "Why does this role matter?" maybe include that as part of About.
Original text:
"As an Embedded Software Test Automation Engineer, you will join our Instrument Development team and help build the test automation frameworks, infrastructure, and tools that ensure the quality, reliability, and performance of IDEXX diagnostic instrumentation. You will play a key role in advancing reusable test automation capabilities across multiple product lines, designing solutions that can be leveraged across instruments rather than rebuilt for each individual platform. Experience with AI-assisted, spec-driven development workflows is required. At IDEXX, our diagnostic instruments directly support veterinary professionals in delivering real-time clinical care to companion animals around the world. As part of a highly collaborative engineering organization, you'll work alongside software, electrical, mechanical, systems, and biological engineering teams to develop and maintain premium point-of-care analyzers. Your contributions will help ensure our instruments meet the highest standards of quality throughout their lifecycle while enabling teams to develop and deliver innovative products more efficiently. Why does this role matter? Test automation is critical to scaling the development of complex embedded systems while maintaining quality and reliability. In this role, you'll help establish reusable automation frameworks, data pipelines, and CI/CD integrations that improve engineering efficiency across multiple instrument platforms. You'll have the opportunity to contribute both strategically and hands-on, influencing technical direction while continuing to solve challenging engineering problems that ultimately support veterinary professionals and the animals they serve."
We'll keep that as About.
Responsibilities: The list under "In This Role You will ..." each bullet starts with "You will". Let's extract each bullet as list items.
List:
- design and build reusable automated test frameworks, tooling, and infrastructure that can be leveraged across multiple embedded instrument platforms.
- develop, maintain, and continuously improve automated test code used to validate embedded software systems.
- define and maintain automated test strategies across the software development lifecycle, ensuring appropriate test coverage and scalability.
- integrate automated testing into CI/CD pipelines and support the operation of automated test environments, including hardware-in-the-loop (HIL) systems.
- collaborate with engineering teams to identify automation opportunities and improve testing efficiency, quality, and reliability across products.
- contribute to technical direction, standards, and best practices for test automation while supporting and mentoring other engineers as needed.
- participate in reviews of test architectures, automation designs, and engineering solutions to promote maintainability, scalability, and long-term success.
- design data pipelines and tooling to parse, validate, transform, and manage test telemetry and configuration data.
- help establish scalable approaches to test data management that support the introduction of new instruments and data sources.
- contribute directly to embedded software and product development efforts as project priorities require, applying strong engineering judgment and software development fundamentals.
- work as a self-directed team member who values collaboration, continuous learning, and delivering high-quality engineering solutions.
We'll put each as
- .
Requirements: The "Required What you need to succeed:" list.
Let's extract each line:
- Bachelor's degree in Computer Science, Computer Engineering, Software Engineering, or a related technical field, or equivalent practical experience.
- 5+ years of experience in embedded software test automation, including designing test infrastructure or frameworks that support multiple product platforms.
- Experience designing, building, and maintaining automated test frameworks and hardware-in-the-loop (HIL) testing environments.
- Experience integrating automated testing into CI/CD pipelines and software delivery processes.
- Strong programming skills in at least two of the following languages: C, C++, Python, Lua, Go, or Rust.
- Experience working with Linux operating systems.
- Strong analytical, troubleshooting, and problem-solving skills with attention to detail.
- Experience using Generative AI development tools to support software engineering activities.
- Strong verbal and written communication skills, including the ability to communicate complex technical concepts across cross-functional teams.
- Demonstrated ability to work effectively both independently and in collaborative team environments.
- Ability to balance responsibilities across test automation, software quality, and hands-on embedded software development as business needs evolve.
We'll put as list.
Qualifications: Strongly Preferred and Preferred.
Strongly Preferred:
- Experience with AI-assisted and spec-driven development workflows, including tools and approaches such as OpenSpec.
- Familiarity with microcontroller-based embedded systems.
Preferred:
- Familiarity with VHDL.
We'll combine as Qualifications list.
Benefits: From "What You Can Expect From Us":
- Base salary range starting at $125,000 based on experience
- Opportunity for annual cash bonus
- Performance-based merit increases
- Health / Dental / Vision Benefits
- Day-One 5% matching 401k
- Additional benefits including but not limited to financial support, pet insurance, mental health resources, volunteer paid days off, employee stock program, foundation donation matching, and much more
We need to separate Pay and Benefits? The instruction says we can have Pay section separate. But we have base salary, bonus, merit increases as Pay. Benefits: health/dental/vision, 401k, additional benefits.
Thus we will create Pay section with:
- Base salary range starting at $125,000 based on experience
- Opportunity for annual cash bonus
- Performance-based merit increases
Benefits section with:
- Health / Dental / Vision Benefits
- Day-One 5% matching 401k
- Additional benefits including but not limited to financial support, pet insurance, mental health resources, volunteer paid days off, employee stock program, foundation donation matching, and much more
We must not include Schedule.
Now we need to output HTML fragment with headings
and content.
We must not include any extra text outside HTML.
Let's craft:
About the role
... (the about text)
Responsibilities
- ...
...
Requirements
...
Qualifications
...
Benefits
...
Pay
...
Check for duplication: Ensure we didn't repeat any content elsewhere.
Check that we didn't include any boilerplate like "Why IDEXX" etc. We omitted that.
Check that we didn't include any EEO paragraph.
Now verify that we preserved all substantive info: Did we miss any? Let's review original posting for any other substantive info not captured.
Original includes: "As an Embedded Software Test Automation Engineer, you will join our Instrument Development team..." captured.
Also includes: "Experience with AI-assisted, spec-driven development workflows is required." That is in About? Actually we included that sentence in About: "Experience with AI-assisted, spec-driven development workflows is required." Yes we included that in the first paragraph.
Also includes: "At IDEXX, our diagnostic instruments directly support veterinary professionals..." captured.
Also includes: "As part of a highly collaborative engineering organization..." captured.
Also includes: "Your contributions will help ensure our instruments meet the highest standards of quality throughout their lifecycle while enabling teams to develop and deliver innovative products more efficiently." captured.
Also includes: "Why does this role matter? Test automation is critical to scaling the development of complex embedded systems while maintaining quality and reliability. In this role, you'll help establish reusable automation frameworks, data pipelines, and CI/CD integrations that improve engineering efficiency across multiple instrument platforms. You'll have the opportunity to contribute both strategically and hands-on, influencing technical direction while continuing to solve challenging engineering problems that ultimately support veterinary professionals and the animals they serve." captured.
Then "In This Role You will ..." captured as Responsibilities.
Then "Required What you need to succeed:" captured as Requirements.
Then "Strongly Preferred" and "Preferred" captured as Qualifications.
Then "Our Tech Stack" paragraph: "This role supports embedded software platforms developed using a variety of technologies, including C, C++, Python, Lua, Go, and Rust running on Linux-based systems. The environment includes automated test frameworks, hardware-in-the-loop (HIL) systems, CI/CD pipelines, telemetry and test data processing workflows, and modern AI-assisted development tools. We look for engineers who bring strong software engineering fundamentals, a passion for
for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we should strip the EEO paragraph at end, also the "#VR-LI1" maybe. Also remove "Why IDEXX" maybe? That's promotional but could be considered boilerplate? It's not required but could be considered fluff. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why IDEXX" is not explicitly listed, but could be considered promotional; but we might keep if it's substantive? It's more marketing. Safer to remove? The instruction says preserve ALL substantive information; does "Why IDEXX" count as substantive? It's about company mission, maybe not essential to role. Might be considered boilerplate? Not sure. Safer to keep? The instruction only mandates removal of certain types; not all fluff. So we can keep it if we want, but we need to avoid duplication. It's not duplicated. Could keep as a paragraph under maybe "About the role" or separate? But we have no heading for it. Could include as a paragraph under About the role? Might be okay. But we need to follow the rule: include a section ONLY when the posting has real, specific content for it. So we need to decide which sections we have content for. We have: - About the role: yes. - Responsibilities: yes. - Requirements: yes (the Required list). - Qualifications: maybe we can combine Strongly Preferred and Preferred as Qualifications. - Skills: maybe we can extract programming languages etc. But that's already in Requirements. Could make Skills separate but might be thin. Better to combine into Requirements. - Benefits: yes. - Pay: yes (base salary range, bonus, merit increases). Could be part of Benefits? But we have separate Pay section allowed. We'll include Pay. - Schedule: no content, so omit. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We need to ensure we don't repeat info. Let's extract precise content. About the role: Combine first paragraph(s) up to "Why does this role matter?" maybe include that as part of About. Original text: "As an Embedded Software Test Automation Engineer, you will join our Instrument Development team and help build the test automation frameworks, infrastructure, and tools that ensure the quality, reliability, and performance of IDEXX diagnostic instrumentation. You will play a key role in advancing reusable test automation capabilities across multiple product lines, designing solutions that can be leveraged across instruments rather than rebuilt for each individual platform. Experience with AI-assisted, spec-driven development workflows is required. At IDEXX, our diagnostic instruments directly support veterinary professionals in delivering real-time clinical care to companion animals around the world. As part of a highly collaborative engineering organization, you'll work alongside software, electrical, mechanical, systems, and biological engineering teams to develop and maintain premium point-of-care analyzers. Your contributions will help ensure our instruments meet the highest standards of quality throughout their lifecycle while enabling teams to develop and deliver innovative products more efficiently. Why does this role matter? Test automation is critical to scaling the development of complex embedded systems while maintaining quality and reliability. In this role, you'll help establish reusable automation frameworks, data pipelines, and CI/CD integrations that improve engineering efficiency across multiple instrument platforms. You'll have the opportunity to contribute both strategically and hands-on, influencing technical direction while continuing to solve challenging engineering problems that ultimately support veterinary professionals and the animals they serve." We'll keep that as About. Responsibilities: The list under "In This Role You will ..." each bullet starts with "You will". Let's extract each bullet as list items. List: - design and build reusable automated test frameworks, tooling, and infrastructure that can be leveraged across multiple embedded instrument platforms. - develop, maintain, and continuously improve automated test code used to validate embedded software systems. - define and maintain automated test strategies across the software development lifecycle, ensuring appropriate test coverage and scalability. - integrate automated testing into CI/CD pipelines and support the operation of automated test environments, including hardware-in-the-loop (HIL) systems. - collaborate with engineering teams to identify automation opportunities and improve testing efficiency, quality, and reliability across products. - contribute to technical direction, standards, and best practices for test automation while supporting and mentoring other engineers as needed. - participate in reviews of test architectures, automation designs, and engineering solutions to promote maintainability, scalability, and long-term success. - design data pipelines and tooling to parse, validate, transform, and manage test telemetry and configuration data. - help establish scalable approaches to test data management that support the introduction of new instruments and data sources. - contribute directly to embedded software and product development efforts as project priorities require, applying strong engineering judgment and software development fundamentals. - work as a self-directed team member who values collaboration, continuous learning, and delivering high-quality engineering solutions. We'll put each as
and content.
We must not include any extra text outside HTML.
Let's craft:
About the role
... (the about text)
Responsibilities
- ... ...
Requirements
- ...
Qualifications
- ...
Benefits
- ...
Pay
- ...