Intermediate Quality Assurance Specialist

We need to output HTML fragment with sections: About the role, Responsibilities, Required Qualifications, Preferred Qualifications, What will help you succeed, Benefits. Also maybe About CM Labs? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The posting includes "About CM Labs" and "About The Role". The page already shows job title, so we should not repeat job title as heading. Should we include "About CM Labs"? It's not listed as a required heading but could be considered a section. The instruction says include a section ONLY when the posting has real, specific content for it. The posting has "About CM Labs" with content. Should we include it? The examples of headings include "About the role". Not "About the company". But we can include if we think it's substantive. However they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are typical headings; but we can also have other headings if needed? Probably we should stick to those headings. The "About CM Labs" could be considered "About the role"? No, it's about the company. Might be better to omit as not required. The instruction: "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." So we can include other headings if they exist in posting. The posting includes "About CM Labs" and "About The Role". The latter maps to "About the role". So we should have an

About the role

with its content. The "About CM Labs" could be omitted or maybe we could treat as a short paragraph before the role? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to preserve the "About CM Labs" content. If we omit that heading, we lose that info unless we embed it somewhere else. Could we put it as a

before the first heading? That would preserve it. The instruction says we can fold minor metadata into a short

or drop it. This is not minor metadata; it's a description of the company. Might be considered substantive. So we should include it as a

before the first heading, or maybe as a section with heading "About CM Labs". But the instruction didn't forbid other headings; it just gave examples. It said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for those sections, but we could also have other headings if needed. However to be safe, we can include a heading "About CM Labs" as

About CM Labs

. It's not in the list but seems reasonable. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can include About CM Labs. Thus sections: About CM Labs, About the role, Responsibilities, Required Qualifications, Preferred Qualifications, What will help you succeed, Benefits. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities, Required Qualifications, Preferred Qualifications, What will help you succeed (maybe it's a paragraph list?), Benefits. We need to preserve all substantive information. Let's extract content. About CM Labs: "At CM Labs Simulations, we develop high-fidelity simulation and workforce training systems that help organizations prepare safer, more skilled heavy equipment operators. Powered by our proprietary physics-based technology and Vortex Studio platform, our solutions combine simulation software, authentic machine behavior, and professional-grade simulator hardware and controls for customers in construction, ports, utilities, industrial, and defense sectors." About The Role: "CM Labs is looking for an Intermediate Quality Assurance Specialist to join our team in Sandy, Utah. In this role, you will help ensure the quality of our software applications and immersive simulator systems through hands-on testing, thoughtful investigation, and clear documentation. You will work alongside other QA professionals, technical designers, developers, and product managers across local and distributed teams. Your primary responsibility will be validating our simulation curriculum products and releases across software and simulator environments. As a secondary responsibility, you will investigate customer-reported issues affecting current and legacy CM Labs products, working with Customer Support and Development to reproduce problems, identify contributing factors, validate fixes, and communicate possible workarounds. You will take ownership of end-to-end test planning and execution for assigned features and communicate release readiness through clear reporting of test coverage, results, open defects, risks, and recommendations." Responsibilities: list bullet points (the block after "Responsibilities"): - Plan and perform functional, integration, regression, and exploratory testing of complete simulator systems, including software applications, simulator computers, displays, controls, peripherals, and supported hardware configurations. - Develop, maintain, and execute test plans, test cases, and other testing documentation. - Record test results and provide clear evidence of coverage, outcomes, defects, and remaining risks. - Identify, reproduce, investigate, and document defects with the information needed for effective resolution. - Participate in Agile development activities and collaborate with team members throughout planning, development, testing, and release. - Participate in discussions about test strategy, release readiness, and product quality. - Validate fixes for reported defects and confirm that the expected behavior has been restored without introducing regressions. - Provide timely updates, raise risks or blockers, and coordinate testing activities with colleagues. - Regularly monitor incoming support issues and investigate technical issues escalated by Customer Support for current and legacy CM Labs products, reproducing customer configurations where practical and identifying software, configuration, hardware, or compatibility factors contributing to the issue. - Communicate investigation findings, reproduction steps, and potential workarounds clearly to Development, Customer Support, and customers when appropriate. - Share responsibility for the setup, configuration, organization, and operational readiness of simulator equipment, computers, and test environments in the testing lab. - Contribute to improvements in QA practices, product knowledge, and team documentation. Required Qualifications: list bullet points: - Two to three years of professional experience in a software QA or testing role. - Understanding of QA fundamentals and software testing concepts, including test planning, test execution, defect reporting, and regression testing. - Strong analytical and troubleshooting skills, with the ability to investigate unfamiliar problems methodically. - Ability to produce clear, accurate, and useful test plans, release documentation, and technical documentation. - Strong organizational skills, with the ability to manage changing priorities and contribute effectively to multiple workstreams. - Comfortable troubleshooting Windows-based applications and integrated computer systems using logs, configuration files, command-line tools, and other diagnostic information. - Experience reading, modifying, and troubleshooting data and configuration files in formats such as XML, JSON, and CSV. - Working knowledge of computer hardware, peripherals, and basic networking concepts. - Ability to understand software configurations, versions, dependencies, and system interactions when investigating defects. - Effective written and verbal communication skills. - Able to work from the Sandy office a minimum of two days per week, with additional onsite presence when testing activities require it. Preferred Qualifications: list bullet points: - Experience testing systems that integrate software with computer hardware, controls, peripherals, or simulator equipment. - Experience with system configuration, computer hardware, networking, and technical support. - Experience using development and defect-management tools such as Jira, Confluence, Git, or GitHub. - Experience investigating issues reported from production or customer environments. - Familiarity with scripting or programming languages such as Python, PowerShell, C#, or similar for diagnostics, data analysis, test utilities, or automation. - Experience developing or maintaining automated tests, test utilities, or regression tools, including API testing or integration with CI/CD pipelines. - Familiarity with simulation, gaming, or virtual reality products and development environments. - Relevant technical education, training, or professional certification. What will help you succeed: paragraph bullet points? It's a list of statements: - A proactive approach, a willingness to take ownership of your work, and the judgment to seek guidance when needed. - Curiosity about how complex systems work and a strong capacity to learn new concepts. - Attention to detail without losing sight of overall product quality and risk. - A collaborative mindset and the ability to work with distributed teams. - The ability to balance planned testing activities, support investigations, documentation, and emerging priorities. Benefits: list bullet points: - Generous vacation and paid time off - Health, dental, and vision benefits - 401(k) plan with company matching - Summer Fridays - Additional time off during the holiday season - Hybrid work environment with flexibility based on testing needs We need to output HTML fragment only, no /, no markdown. We'll wrap each section in

  heading then content. For lists, use

  • ...

  . For prose, use

  . We need to ensure we don't include any boilerplate like EEO etc. Not present. Let's craft. First, maybe a

  for About CM Labs content. Then

  About the role

  with its paragraph. Then

  Responsibilities

  with
  list. Then

  Required Qualifications

  with
  . Then

  Preferred Qualifications

  with
  . Then

  What will help you succeed

  with
  (or

  ? It's a list; better

  ). Then

  Benefits

  with
  . Make sure to preserve all details exactly as given, no omission. Check for any missing details: In About the role, we included all sentences. Ensure we didn't miss any: "CM Labs is looking for an Intermediate Quality Assurance Specialist to join our team in Sandy, Utah. In this role, you will help ensure the quality of our software applications and immersive simulator systems through hands-on testing, thoughtful investigation, and clear documentation. You will work alongside other QA professionals, technical designers, developers, and product managers across local and distributed teams. Your primary responsibility will be validating our simulation curriculum products and releases across software and simulator environments. As a secondary responsibility, you will investigate customer-reported issues affecting current and legacy CM Labs products, working with Customer Support and Development to reproduce problems, identify contributing factors, validate fixes, and communicate possible workarounds. You will take ownership of end-to-end test planning and execution for assigned features and communicate release readiness through clear reporting of test coverage, results, open defects, risks, and recommendations." All there. Now Responsibilities list: ensure each bullet matches exactly. Let's copy them. - Plan and perform functional, integration, regression, and exploratory testing of complete simulator systems, including software applications, simulator computers, displays, controls, peripherals, and supported hardware configurations. - Develop, maintain, and execute test plans, test cases, and other testing documentation. - Record test results and provide clear evidence of coverage, outcomes, defects, and remaining risks. - Identify, reproduce, investigate, and document defects with the information needed for effective resolution. - Participate in Agile development activities and collaborate with team members throughout planning, development, testing, and release. - Participate in discussions about test strategy, release readiness, and product quality. - Validate fixes for reported defects and confirm that the expected behavior has been restored without introducing regressions. - Provide timely updates, raise risks or blockers, and coordinate testing activities with colleagues. - Regularly monitor incoming support issues and investigate technical issues escalated by Customer Support for current and legacy CM Labs products, reproducing customer configurations where practical and identifying software, configuration, hardware, or compatibility factors contributing to the issue. - Communicate investigation findings, reproduction steps, and potential workarounds clearly to Development, Customer Support, and customers when appropriate. - Share responsibility for the setup, configuration, organization, and operational readiness of simulator equipment, computers, and test environments in