Power Electrical Engineer Intern (Summer 2027)

We need to output HTML fragment with sections: headings

for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. Let's parse the posting. We have: - About Torus (company description) – not a heading we need? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should not include "About Torus" as a heading; we can embed that info maybe in a

before sections? 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." It doesn't forbid other headings like About Torus, but they said use

for section headings (e.g. About the role, Responsibilities...). Likely they expect only those headings. So we should not output About Torus heading; we can include its content in a

before sections? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the company description somewhere. Could put it in a

before any headings. Then we have "About The Role" – that matches "About the role" heading. So we will have

About the role

and then content. Then "Who You Are" – that could be Requirements/Qualifications/Skills. We need to map. Then "Internship Responsibilities" – heading Responsibilities. Then "Experience" – likely Qualifications. Then "Additional Details" – includes Background Check, Location + Travel, Schedule, Compensation, Work Authorization, Physical Requirements, Our Perks & Benefits. We need to extract specific content for sections: Responsibilities, Requirements (maybe Who You Are), Qualifications (Experience), Skills (maybe part of Who You Are), Benefits (Our Perks & Benefits), Pay (Compensation), Schedule (Schedule). Also maybe we can include a short paragraph for metadata like location etc. We must not create sections with filler like "commensurate with experience". The posting includes compensation "$22-28/hour depending on experience". That's specific, so we can include Pay section. Schedule: "First Shift 8:00 am - 4:30 pm Duration Temporary from May - August (We can flex with your school schedule.) Possibility to extend as a part-time employee ~20 hrs/wk." That's specific, so include Schedule. Benefits: "While interns are ineligible for benefits, we believe in fostering growth and development. If a full-time eligible position becomes available, you’ll become eligible for our comprehensive benefits package. Learn more about what we offer below." Then they list Financial, Health & Wellness, Time Off, Culture & Community. That's specific content, so we can include Benefits section with that detail. Requirements: Could be "Who You Are" list: Inspired by Torus’ mission..., Strong attention to detail..., Must possess strong problem-solving skills..., Safety conscious..., Communication Skills..., Time Management..., Flexibility... That's a list of traits. We'll put under Requirements or maybe Qualifications. The instruction says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide where to put each piece. We have "Experience" which includes education, GPA, hands-on experience, CAD, Google/MS Office, previous internship plus, Eagerness to learn, ability to commit, availability, work authorization. That's qualifications. We have "Who You Are" which is more about personal attributes/skills. Could be Skills. We have "Internship Responsibilities" which is responsibilities. Thus: - About the role: paragraph from "About The Role" section. - Responsibilities: list from "Internship Responsibilities". - Requirements: maybe we can combine "Who You Are" as Requirements? Or we could treat "Who You Are" as Skills. Let's map: Requirements: maybe the mandatory items: Must possess strong problem-solving skills, Safety conscious, Communication Skills, Time Management, Flexibility. Also "Strong attention to detail and ability to follow precise instructions and specifications." That seems like requirement. Qualifications: Education, GPA, hands-on experience, CAD, Office software, previous internship plus, Eagerness to learn, ability to commit, availability, work authorization. Skills: maybe technical skills: Arduino, C-programming, soldering, basic understanding of electrical circuits, basic understanding of industry principles, CAD experience with SOLIDWORKS, Google/MS Office. But we have overlapping. We need to avoid duplication. Let's decide to put: - About the role: paragraph. - Responsibilities: bullet list. - Requirements: bullet list of personal/soft requirements from "Who You Are": Inspired by mission, Strong attention to detail, Strong problem-solving skills, Safety conscious, Communication Skills, Time Management, Flexibility. - Qualifications: bullet list of education/experience: Continuing Bachelor's degree in Electrical Engineering or related field, Completed Freshman year (2 semesters), Strong academic performance (GPA 3.0 or higher), Hands-on experience with Arduino, C-programming, soldering preferred, Basic understanding of electrical circuits and components, Basic understanding of industry principles and practices relevant to department, CAD experience with SOLIDWORKS, Working knowledge of Google Office Suite, Microsoft Office Suite, Previous internship or work experience in related field is a plus but not required, Eagerness to learn and take on new challenges, Ability to commit to full duration, Availability to work scheduled hours, Authorization to work in US. - Skills: maybe we can combine technical skills: Arduino, C-programming, soldering, basic electrical circuits, industry principles, CAD SOLIDWORKS, Google/MS Office. But that overlaps with Qualifications. Perhaps we can omit Skills section to avoid thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Skills into Qualifications or Requirements. But we need to follow the allowed headings; we can omit Skills if not substantive. Let's see if we have enough content for Skills separate: we have technical skills list. Could be separate but might be thin. However we already have Qualifications covering many of those. Might be better to have Skills separate for technical skills, and Qualifications for education/experience. Let's decide: Skills: Arduino, C-programming, soldering, basic understanding of electrical circuits and components, basic understanding of industry principles and practices relevant to department, CAD experience with SOLIDWORKS, Working knowledge of Google Office Suite, Microsoft Office Suite. Qualifications: Continuing Bachelor's degree in Electrical Engineering or related field, Completed Freshman year (2 semesters), Strong academic performance (GPA 3.0 or higher), Previous internship or work experience in related field is a plus but not required, Eagerness to learn and take on new challenges, Ability to commit to full duration, Availability to work scheduled hours, Authorization to work in US. Requirements: Inspired by Torus’ mission..., Strong attention to detail and ability to follow precise instructions and specifications., Must possess strong problem-solving skills to troubleshoot and resolve assembly issues effectively., Safety conscious: Demonstrated commitment to maintaining a safe working environment. Familiarity with safety regulations and practices related to electrical and mechanical assembly., Communication Skills: Ability to collaborate effectively with team members, engineers, and supervisors to ensure smooth workflow and efficient problem-solving., Time Management: Strong organizational and time management skills. Ability to prioritize tasks effectively to meet deadlines without compromising quality., Flexibility: Willingness to adapt to changing priorities and work on multiple projects simultaneously. Ability to work effectively under pressure and in a fast-paced manufacturing environment. That seems good. Now Benefits: we need to include the details: While interns are ineligible for benefits, we believe in fostering growth and development. If a full-time eligible position becomes available, you’ll become eligible for our comprehensive benefits package. Learn more about what we offer below. Then list: 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 put that as a

• each maybe with subheadings? But we only allowed
  • for list. Could embed headings inside
  • ? Probably okay to have
  • Financial: ...
  . We'll keep simple. Pay: "$22-28/hour depending on experience (Note: We have the flexibility to hire at different levels, which may impact the corresponding pay range.)" Schedule: "First Shift 8:00 am - 4:30 pm Duration Temporary from May - August (We can flex with your school schedule.) Possibility to extend as a part-time employee ~20 hrs/wk." Also we have location + travel details: Onsite at GigaOne warehouse in Salt Lake City (84040), working in air-conditioned warehouse/manufacturing and cleanroom environments. Break area equipped with refrigerator, microwave, coffee maker, and vending machines. Occasional work may be required at South Salt Lake HQ or Springville R&D facilities (partially air-conditioned). This is location metadata; we can put in a short

  before sections or after About the role. Not a heading. Also we have Background Check, Work Authorization, Physical Requirements. Those could be folded into Requirements or Qualifications? Physical Requirements maybe part of Requirements? But we already have Requirements for personal attributes. Physical Requirements could be added to Requirements as bullet items. However we must not create filler. They are specific. Let's add them to Requirements as additional bullet items. Work Authorization: "Applicants must already have the legal authorization to work in the US without requiring any employer sponsorship." Already covered in Qualifications (Authorization to work in US). So we can keep that. Background Check: "All candidates are subject to a background check." Could be a short note. We'll add a short

  for metadata: location, background check, etc. Now we need to output only HTML fragment, no /, no markdown. Let's construct. Start with a

  for company description? Actually we have About Torus paragraph. We'll put that as a

  before sections. Then

  About the role

  then

  with the paragraph. Then

  Responsibilities

  then
  • ... etc. Then

    Requirements

    then
    with items. Then

    Qualifications

    then
    . Then

    Skills

    then
    . Then

    Benefits

    then
    . Then

    Pay

    then

    . Then

    Schedule

    then

    . We need to ensure we don't repeat content. Let's extract exact phrasing. About The Role paragraph: "As a Power Electrical Engineer Intern, you will play a vital role in developing, testing and maturing an energy storage product line. You'll contribute to the design and assembly of the electrical systems that make resilient, scalable energy storage possible.