ATE Test Software 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, navigation, legal, EEO, equal-opportunity, scam-warning, 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 job posting. Content: - Intro: "We are a customer focused provider of audio solutions. We exceed users’ expectations with well thought out design, integration, and service. Our purpose-built products meet our customers where they are at, enhancing their moment with a powerful experience through music." - Job Title: ATE Software Test Engineer (we should not repeat as heading) - Job Location: Tempe, AZ (100% Onsite) - "We are seeking an ATE Software Test Engineer to own development, deployment, and continuous improvement of automated End-of-Line (EOL) test software for audio amplifiers and electronic systems. This role is responsible for implementing test sequences, maintaining version-controlled test environments, integrating instrumentation and third-party systems, and enabling data-driven quality monitoring across global manufacturing sites. This role operates within the Quality organization and is distinct from product validation engineering, focusing specifically on production EOL test readiness, execution, and sustainment." - Key Responsibilities: then bullet list (though not bullet but paragraphs). We'll need to extract responsibilities as list items. Responsibilities sections: 1. EOL Test Software Development - Develop and maintain automated EOL test sequences using LabVIEW-based test executive frameworks. - Translate product test specifications, DFMEA outputs, and validation requirements into executable test scripts. - Implement modular, scalable, and reusable software architectures across multiple product platforms. - Ensure all test software is version controlled, traceable, and production-ready. 2. System Integration & Automation - Integrate test software with DAQ systems, DMMs, power supplies, and communication interfaces including CAN, CAN-FD, BLE, and A2B. - Develop custom integrations using Python, C, or other APIs for third-party tools and hardware. - Support standardized communication interfaces through common system connectors and abstraction layers. 3. Database & Data Analytics - Interface test systems with cloud-synced Oracle databases for test sequences, limits, and results storage. - Develop data analytics tools to monitor first pass yield, limit drift, and failure trends. - Ensure data integrity, traceability, and audit readiness of all production test records. 4. Production Deployment & Support - Release, deploy, and maintain test software across overseas manufacturing partners. - Support on-site test engineers and technicians during DV, PPAP, and ramp phases. - Troubleshoot test software failures and implement corrective actions. 5. Governance, Controls & Compliance - Enforce strict operator controls preventing unauthorized changes. - Ensure pass/fail integrity is maintained across all test sequences and results. - Ensure all EOL test processes meet internal quality standards and customer expectations. - Required Skills & Qualifications - Bachelor’s degree in Electrical Engineering, Computer Engineering, Software Engineering, or related field. - 3–7 years of experience in automated test development or production test systems. - Strong experience with National Instruments LabVIEW. - Experience integrating hardware using DAQ systems and test instrumentation. - Proficiency in Python, C, or similar programming languages. - Experience with database systems, preferably Oracle as well as SQL. - Strong understanding of production test concepts, yield, and statistical analysis. - Demonstrated ability to diagnose failures and perform root cause analysis. - Strong documentation and version control discipline. - Preferred Qualifications - Experience with automotive communication protocols including CAN, CAN-FD, A2B, and BLE. - Familiarity with manufacturing test system deployment at CM/ODM partners. - Experience with audio product testing or electronics manufacturing. - Exposure to DFMEA, PPAP, and quality systems. - About Rockford & Benefits - "Rockford Fosgate is an equal opportunity employer located in Tempe, Arizona. Join us and thrive in a dynamic office environment where your contributions truly make a difference. Enjoy the benefits of flexibility, competitive pay, affordable healthcare, a 401k match, and a pathway for growth." - Then application instructions: "Interested and qualified applicants are encouraged to send their resume and cover letter to jobs@rockfordcorp.com Visit www.rockfordfosgate.com to learn more about us." This is boilerplate/application instructions; we need to remove. Also need to remove EEO/equal-opportunity boilerplate: "Rockford Fosgate is an equal opportunity employer located in Tempe, Arizona." That's part of benefits section but also EEO. However we need to keep substantive info: location maybe. The location is already given earlier: Tempe, AZ (100% Onsite). The EEO statement can be removed as boilerplate. But we might keep "Join us and thrive in a dynamic office environment where your contributions truly make a difference." That's not boilerplate? It's somewhat generic but maybe keep as part of About the company? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove the EEO statement. The sentence "Join us and thrive in a dynamic office environment where your contributions truly make a difference." is not EEO but maybe fluff; but it's not specifically prohibited. However we might keep it as part of About the company? The instruction says "Prefer a few substantive sections over many thin ones." We could combine About the role and Benefits into sections. We need sections: About the role (maybe a brief description), Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule. We have no explicit Pay or Schedule info. The posting mentions "competitive pay" but not specific numbers. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "competitive pay" which is a statement about pay but not specific. Is that enough to create a Pay section? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It says "competitive pay" is a statement about pay, albeit vague. Does that count as stating them? Likely yes, they mention pay. However they also say "Enjoy the benefits of flexibility, competitive pay, affordable healthcare, a 401k match, and a pathway for growth." That's benefits. So we can have Benefits section with those items. Pay section maybe we could include "competitive pay" as a statement. But the rule says prefer few substantive sections over many thin ones. Could combine Benefits and Pay into one Benefits section? But they are separate headings allowed. However we should only create a section if there is real specific content. "competitive pay" is vague but still a statement. Might be okay to include Pay section with that phrase. However we might avoid creating a Pay section if we think it's too vague. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "competitive pay". So we can include Pay section with that sentence. Similarly Benefits: they list flexibility, competitive pay (already), affordable healthcare, 401k match, pathway for growth. So we can have Benefits section with those items. Schedule: they mention "100% Onsite" under Job Location. That's schedule? It's location, not schedule. No explicit schedule like full-time, part-time, shift. So we should not create Schedule section. Thus sections: About the role (maybe a paragraph summarizing role), Responsibilities (list), Requirements (maybe combine Required Skills & Qualifications and Preferred Qualifications? Could separate into Requirements and Preferred Qualifications). The headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use Requirements for required qualifications, Qualifications for preferred? Or Skills for skills? Let's think. We have Required Skills & Qualifications (list). Preferred Qualifications (list). Could map Required Skills & Qualifications to Requirements section (or Qualifications). Preferred Qualifications could be Skills? But Skills heading is allowed. However we already have skills listed in required. Might be redundant. Better: Use Requirements for required qualifications (degree, years, LabVIEW, etc.). Use Qualifications for preferred qualifications (experience with automotive protocols, etc.). Use Skills maybe not needed. Or we could combine required and preferred into Requirements and Qualifications sections. We also need About the role: a paragraph describing the role and company. Use the intro paragraphs: "We are a customer focused provider of audio solutions..." plus the seeking sentence. That can be About the role. We need to preserve all substantive info; do not invent or summarize away detail. So we need to include all bullet points exactly as given (or close). We must not omit any detail. Let's extract all substantive content: Intro: - "We are a customer focused provider of audio solutions. We exceed users’ expectations with well thought out design, integration, and service. Our purpose-built products meet our customers where they are at, enhancing their moment with a powerful experience through music." Job location: Tempe, AZ (100% Onsite) - we can include in About the role or a separate metadata paragraph. Since we cannot put Job ID/requisition numbers as headings, but location is fine as a paragraph. Role description: "We are seeking an ATE Software Test Engineer to own development, deployment, and continuous improvement of automated End-of-Line (EOL) test software for audio amplifiers and electronic systems. This role is responsible for implementing test sequences, maintaining version-controlled test environments, integrating instrumentation and third-party systems, and enabling data-driven quality monitoring across global manufacturing sites. This role operates within the Quality organization and is distinct from product validation engineering, focusing specifically on production EOL test readiness, execution, and sustainment." Responsibilities: as enumerated. Required Skills & Qualifications: list. Preferred Qualifications: list. About Rockford & Benefits: "Rockford Fosgate is an equal opportunity employer located in Tempe, Arizona. Join us and thrive in a dynamic office environment where your contributions truly make a difference. Enjoy the benefits of flexibility, competitive pay, affordable healthcare, a 401k match, and a pathway for growth." We need to remove EEO boilerplate: "Rockford Fosgate is an equal opportunity employer located in Tempe, Arizona." That's EEO statement; remove it. Keep the rest: "Join us and thrive in a dynamic office environment where your contributions truly make a difference. Enjoy the benefits of flexibility, competitive pay, affordable healthcare, a 401k match, and a pathway for growth." We might also keep location mention? Already have location earlier. Thus Benefits section: list items: flexibility, competitive pay, affordable healthcare, a 401k match, and a pathway for growth. Could be a

  • . Pay section: we could include "competitive pay" as a statement. But we already have competitive pay in Benefits. Might be redundant. Better to not create separate Pay section; just include competitive pay in Benefits. The rule says prefer few substantive sections over many thin ones. So we can omit Pay section. Schedule: none. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. We need to use

    for each section heading. Inside each section, we need

    for prose,

    • for lists. We must not repeat job title as heading. We must not include application instructions. Let's craft HTML. First, About the role: combine intro paragraphs and location and role description. Prose: maybe two paragraphs: first intro about company, second location and role description. We'll put location in a paragraph: "Job Location: Tempe, AZ (100% Onsite)". That's fine. Then