Quality Assurance Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info; remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Content: - Intro: "Impinj is a leading RAIN RFID provider..." This is about company, maybe "About the role"? Actually "About the role" could be description of role. The posting includes "Team Overview:We are seeking a Quality Assurance Engineer to join our Reader Firmware team. You will focus on two key areas: testing our RFID readers through automation and manual testing and supporting our machine learning initiatives through manual data collection. The team’s goals are to continuously improve the quality of our products, the efficiency of our procedures, and ensure compliance with all regulatory requirements. This is a great opportunity for someone early in their quality assurance career. While you will start by maintaining and executing existing automated test cases, there is room for you to grow into writing your own automation as you build expertise. We’re looking for candidates who are curious and have a genuine interest in developing their technical skills over time.This role is based on site at our North Beacon Hill office in Seattle, WA." That's description of role, responsibilities overview. Then "What You Will Do:" bullet list. Then "What You Will Bring:" bullet list. Then "Compensation & Benefits:" paragraph about benefits, pay range. Then "US Export Controls:" paragraph about export controls (maybe not needed? It's substantive but maybe not required? It's not a standard heading; we could include as a paragraph under maybe "Additional Information"? But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put export controls under maybe "About the role" or as a paragraph under "Benefits"? Better to keep only sections with real content. Export controls is substantive but not fitting those headings; we could include as a

  after sections, not under a heading. The instruction: "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. Additional info can be in

  without heading. Then "Why work at Impinj:" paragraph about culture, benefits, etc. This could be part of Benefits or maybe separate but we can incorporate into Benefits section. We must not include boilerplate like EEO, equal opportunity, accommodation request, etc. Remove those lines. Also remove duplicated lines, application instructions (like "click here" maybe). The posting includes "For a more comprehensive list of US employment benefits, click here." That's application instruction? It's a link; we should remove that line. Also "Learn more about export compliance here." Remove. Also "Why work at Impinj:" section includes some boilerplate but it's substantive about culture; we can keep. We need to preserve all substantive information; do not invent or summarize away detail. Thus we need to extract: - About the role: maybe the team overview paragraph. - Responsibilities: the bullet list under "What You Will Do:". - Requirements: maybe the bullet list under "What You Will Bring:" includes education, experience, skills. Could be split into Requirements and Qualifications and Skills. But we should prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications into one section? But we have headings for Requirements, Qualifications, Skills. We could decide to use only Requirements and maybe Skills. However we need to follow instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must use all; we can use only those that have real content. So we can decide to have sections: About the role, Responsibilities, Requirements (including education, experience, skills), Benefits, Pay. Possibly Schedule not present (no schedule info). So omit Schedule. We need to ensure we don't create heading with filler like "commensurate with experience". Not present. Now extract details: About the role: The team overview paragraph: "We are seeking a Quality Assurance Engineer to join our Reader Firmware team. You will focus on two key areas: testing our RFID readers through automation and manual testing and supporting our machine learning initiatives through manual data collection. The team’s goals are to continuously improve the quality of our products, the efficiency of our procedures, and ensure compliance with all regulatory requirements. This is a great opportunity for someone early in their quality assurance career. While you will start by maintaining and executing existing automated test cases, there is room for you to grow into writing your own automation as you build expertise. We’re looking for candidates who are curious and have a genuine interest in developing their technical skills over time. This role is based on site at our North Beacon Hill office in Seattle, WA." We should keep that as prose

  . Responsibilities: bullet list under "What You Will Do:". List items: - Set up RFID readers to replicate real-world customer use cases (note: this work involves lifting, ladder use, and using hand tools such as screwdrivers, sockets, and wrenches) - Move RFID tags through test environments to mimic the way tags move through our customers' environments - Document test progress and results to ensure clarity and visibility - Set up, monitor, perform, and document data collection efforts for machine learning initiatives - Analyze and investigate issues, documenting findings through bugs and reports with clear, actionable details - Collaborate with software, hardware, and product teams to understand requirements and create and execute test plans - Update existing automated test cases and scripts, and implement new cases following existing patterns - Execute automated test cases and scripts and record their results We need to preserve the note in parentheses exactly. Now Requirements/Qualifications/Skills: bullet list under "What You Will Bring:". List: - Bachelor’s degree or equivalent experience in computer science, computer engineering, or related technical field - Familiarity with command line interfaces and executing scripts - Ability to edit and maintain text-based configuration files - Strong attention to detail - Experience with Python, C# or similar programming language - Ability to consistently lift and carry items weighing up to 20 pounds We could treat these as Requirements (education, experience) and Skills (technical). But we can combine into one Requirements section. Now Benefits and Pay: Under "Compensation & Benefits:" paragraph. We need to extract benefits and pay details. Paragraph: "The benefits listed below may vary depending on the nature of your employment with Impinj and the country where you work.The typical base pay range for this role across the US is $34.90/hr - $52.30/hr. Individual base pay depends on various factors such as complexity and responsibility of role, job duties, requirements, and relevant experience and skills. Both market wage data and the mid-point of the pay range is reviewed and used as the starting point for all new hire offers. Offers are made within the base pay range applicable at the time. At Impinj certain roles are eligible for additional rewards, including merit increases, annual bonus and stock. These awards are allocated based on individual performance. In addition, certain roles also have the opportunity to earn sales incentives based on revenue or utilization, depending on the terms of the plan and the employee’s role. US based employees have access to healthcare benefits; a 401(k) plan and company match among others.For a more comprehensive list of US employment benefits, click here." We need to preserve substantive info: pay range, benefits mention (healthcare, 401(k), company match, merit increases, annual bonus, stock, sales incentives). Also note that benefits may vary. We should not include the "click here" line (application instruction). So remove that sentence. Thus we have Benefits and Pay combined? Could separate: Benefits section for benefits, Pay section for pay range. Since we have both headings allowed, we can split. Benefits: healthcare benefits; 401(k) plan and company match; merit increases; annual bonus; stock; sales incentives (based on revenue/utilization). Also note that benefits may vary depending on employment nature and country. Pay: typical base pay range $34.90/hr - $52.30/hr; individual base pay depends on factors; market wage data and midpoint used; offers within range. We should keep the note about benefits may vary. Now also there is US Export Controls paragraph. This is substantive but not fitting headings. We could include as a

  after sections without heading. The instruction: "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. It might be okay to have additional

  without heading. However we should consider if we need to include it. It's substantive info about export controls. The instruction says preserve ALL substantive information. So we must include it. We can put it as a

  after the sections, maybe under a heading like "Additional Information"? But that heading is not in the list; but we could still use

  for it? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but it's implied to use those for sections. Safer to include it as a

  without a heading, after the sections. Similarly "Why work at Impinj:" paragraph is substantive about culture. We should include that as well. It includes: "Know you’re making a difference. Competitive benefits. Support for remote work or a desk with a view. Weekly Q&A sessions with our executive team. Impinj provides an environment that fosters openness and innovation and is developing technology that delivers a positive impact on the world. Collaboration and teamwork are highly valued, and accomplishments are duly celebrated. We have an open paid time-off policy paired with a respect for work/life balance. Our headquarters is located in Seattle with spectacular views of the Olympics, Lake Union, and Mt Baker, which can be enjoyed from our rooftop deck. Our Brazilian site is in Porto Alegre, Rio Grande do Sul state, at “Tecnopuc,” a technology park that offers a very nice workplace for the development of groundbreaking technologies. Impinj is committed to creating a diverse and inclusive work environment and welcomes applicants from all backgrounds." We should keep that as a

  maybe under a heading like "About the company" but not in list. Could incorporate into Benefits? But it's more about culture. Could be its own section but not in allowed headings. However we could treat it as part of Benefits? Not really. Better to include as a

  after sections, maybe with a heading like "About Impinj"? But that might be considered a heading not in list. The instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but the examples are those. I think it's okay to add other headings if needed, but to be safe we could avoid extra headings and just put as

  without heading. However the instruction says "Use

  for section headings (e.g ...)". It doesn't say you cannot have other headings, but it's implied to use those for sections. I'd rather not