Electrical Test Engineer

We need to output HTML fragment with sections using

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: - About Torus (company description) - not a required heading; we can ignore or maybe not include because not in list? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only output those headings if content exists. The "About Torus" is not one of those; we can drop it (it's boilerplate? It's company overview but not required heading). We can ignore. - About The Role: we have a paragraph describing role. That's content for "About the role". So we output

About the role

then

with that prose. - Responsibilities: we have bullet list items. So

Responsibilities

then

• ... each. - Requirements: The posting has "Required Experience" list. That's requirements. So

  Requirements

  then
  . - Qualifications: Not separate; maybe "Preferred Experience" could be Qualifications or Skills. The instruction includes Qualifications and Skills sections. We have "Preferred Experience" list. Could treat as Qualifications. Also there is "Additional Details" with background check, location, schedule, compensation, physical requirements, perks & benefits. Those map to Pay, Schedule, Benefits, maybe also other sections. We need to decide which sections to include based on actual content. We have: - Pay: Compensation $100,000-130,000 (with note). So we can include Pay section. - Schedule: "Full-Time, Salaried". Also maybe mention occasional travel. So Schedule section. - Benefits: "Our Perks & Benefits" includes details: Financial Employee Rewards Package including equity, 401(k), life insurance, disability, health benefits, PTO, holidays, parental leave, culture & community items. So Benefits section. - Qualifications: Could be "Required Experience" (we already used for Requirements). But maybe Requirements is for required experience, Qualifications for preferred? The instruction says use both headings if content exists. We have Required Experience (requirements) and Preferred Experience (qualifications). So we can map Required Experience to Requirements, Preferred Experience to Qualifications. - Skills: Could be derived from required experience list includes proficiencies etc. But we already used those in Requirements. Might be redundant. Better to keep Requirements for required experience, Qualifications for preferred experience, and maybe Skills for specific technical skills (like LabVIEW, PLC, PID, etc). However the instruction says prefer a few substantive sections over many thin ones. We could combine Required Experience and Preferred Experience into Requirements and Qualifications respectively, and maybe not include Skills if content overlaps. But we need to preserve all substantive information. If we omit Skills heading, we must still include the skill details somewhere else (e.g., within Requirements or Qualifications). That's okay as long as we don't lose info. Thus we can have sections: - About the role - Responsibilities - Requirements (Required Experience) - Qualifications (Preferred Experience) - Benefits - Pay - Schedule We should not include sections like Skills if not needed. Now we need to format lists. Let's extract content precisely. About the role paragraph: "The Electrical Test Engineer verifies our mission at the bench. You'll design, build and test the automated test systems that prove our electrical equipment works (1000v and lower). Energy storage, LV power distribution, grid-tied inverters, motor drives, and control panels all have to pass through your testing gauntlet before they leave our warehouse. Every product that ships has been thoroughly vetted by systems you designed and procedures you built. This role is based at GigaOne in Salt Lake City, on a growing team, working in an environment where your testing catches problems early and keeps quality relentless." We'll put that in a

  . Responsibilities list items: From the posting: - Test System Development and Automation - Design, develop, and maintain automated electrical test systems for product development, verification, validation, and production testing. - Design and build test fixtures, electrical interfaces, breakout boxes, and test harnesses. - Develop and maintain test software using LabVIEW. - Integrate NI DAQ hardware, instrumentation, PLCs, and other test equipment into automated test systems. - Develop tools for data analysis, visualization, and automated reporting. - Product Verification and Validation - Develop and execute test plans and procedures to verify electrical, controls, and system-level product requirements. - Perform functional, performance, fault, stress, and certification testing of energy storage systems, inverters, power electronics, control systems, and associated electrical equipment. - Test and characterize closed-loop control systems, including PID-controlled systems, grid-interactive controls, and power management functions. - Analyze test data, identify trends and anomalies, and report findings to the design team. - Troubleshooting and Root Cause Analysis - Troubleshoot electrical, controls, firmware, and communication issues using oscilloscopes, DMMs, power analyzers, DAQ systems, and other laboratory equipment. - Perform root-cause analysis of test failures and work with design and firmware engineers to identify and implement corrective actions. - Laboratory Ownership - Maintain test equipment, calibration records, test fixtures, and laboratory documentation. - Configure and operate laboratory equipment including programmable power supplies, electronic loads/load banks, grid simulators, oscilloscopes, power analyzers, and data acquisition systems. - Collaboration, Documentation, and Production Support - Collaborate with electrical, firmware, software, mechanical, and systems engineers to define test requirements and improve product testability. - Provide test data and technical feedback to engineering teams throughout the product development lifecycle. - Document test configurations, procedures, results, failures, and corrective actions in clear engineering reports. We need to preserve all. We'll output each as

  • . Could keep the heading bold? Not needed. Requirements (Required Experience): List: - Bachelor’s degree in Electrical Engineering, Mechatronics, or related field (or equivalent experience) - 2+ years of related experience in Electrical Test Engineering or a related field experience - Proficient with Data Acquisition Systems (National Instruments preferred) - Understand PID control theory and state machines - Proficient in PLC programming, LabVIEW, Python, C/C++ or equivalent - Hands-on experience with electrical measurement tools (DMM, oscilloscope, power meters, etc.) and electrical assembly tools (wire striping/crimping, soldering, etc) - Experience using power tools (drill, Sawzall, etc.) - Excellent attention to detail, organizational skills, and problem-solving abilities. - Effective communication and teamwork skills. We'll output each as
  • . Qualifications (Preferred Experience): - Familiarity with batteries, motors, inverters and DC-DC converters - Experience with industrial communication protocols and interfaces (Modbus RTU/TCP, CAN, Ethernet, and RS-232/RS-485) We'll output as
  • . Benefits: From "Our Perks & Benefits": - Benefits eligibility is based on employment status. - Financial Employee Rewards Package including equity - 401(k) Retirement Savings Plan - Torus paid life and AD&D Insurance with options to purchase additional coverage - Voluntary short- and long-term disability insurance - Health & Wellness: Health Benefits Package: Choice between traditional PPO or HSA-eligible medical plans with Torus covering 50% of medical premiums; Dental insurance; and Vision insurance - Plan participants have access to telehealth services, mental health support and coaching, and exclusive discounts on brands, dining, entertainment, and more. - Time Off: Unlimited discretionary PTO or 10 days annual PTO - 10 paid company holidays - Waiting period-free 100% paid parental leave - Culture & Community: Regular company-wide offsites to showcase our progress and learnings. A time to step back, think strategically, and work on the business together. - Team members receive Torus branded gear - Peer Recognition Program - Fully stocked break rooms with free snacks and drinks. Because great work deserves great fuel. We'll output each as
  • under Benefits. Pay: - Compensation $100,000-130,000 (Note: We have the flexibility to hire at different levels, which may impact the corresponding pay range.) We'll output as

    maybe. Schedule: - Full-Time, Salaried - May require occasional onsite work in South Salt Lake warehouse and/or Springville R&D center (air-conditioned and non air-conditioned). - Occasional travel to client sites may be required. We'll output as

  • maybe. We also have location + travel details: "Location + Travel The role is onsite based at GigaOne, our Salt Lake City warehouse (air-conditioned and non air-conditioned areas). May require occasional onsite work in South Salt Lake warehouse and/or Springville R&D center (air-conditioned and non air-conditioned). Occasional travel to client sites may be required." This is similar to schedule but also location. Since we have Schedule section, we can include location details there as well. But we should not duplicate. We'll include location and travel in Schedule section. Physical requirements etc. Are those considered part of Benefits? Not exactly. They are not Pay/Schedule/Benefits. Could be omitted? The instruction says include a section ONLY when posting has real, specific content for it. Physical requirements is specific content but not among the allowed headings. The allowed headings list does not include Physical Requirements. So we should not create a heading for it; we could drop it? But we must preserve ALL substantive information. However we cannot invent headings not in list. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but the examples given are those. Safer to stick to those headings only. Physical requirements could be placed under Requirements or Qualifications? It's not exactly a requirement but could be considered a requirement. We could add them under Requirements as additional bullet points. That would preserve info. Similarly, "Background Check" could be under Requirements? Not exactly. Could be omitted? It's substantive. Could be placed under Requirements as a bullet: "All candidates are subject to a background check." That seems appropriate. Thus we can incorporate background check, physical requirements, location/travel into appropriate sections (Requirements, Schedule). Let's see. We have Requirements currently includes education, experience, proficiencies. We can add background check and physical requirements as additional bullets. Schedule currently includes full-time, salaried, occasional onsite work, occasional travel. We can also mention location: onsite at GigaOne in Salt Lake City warehouse (air-conditioned and non air-conditioned areas). That's location detail. Thus we will incorporate. Now we need to ensure we don't create sections with filler like "commensurate with experience". Not present. Now produce HTML. We'll output:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Requirements

    • ...
    ...

    Qualifications

    • ...
    ...

    Benefits

    • ...
    ...

    Pay

    $100,000-1