Software Engineering Test Intern (Summer 2027)

We need to output HTML fragment with sections: About the role (maybe Position Summary?), Responsibilities, Qualifications, maybe About Us? The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to extract substantive content: Position Summary (maybe "About the role") includes description: "We are seeking a dedicated and proactive individual to join our Core Engineering team as a Software Engineer in Test Intern. This internship offers an excellent opportunity to gain hands-on experience building automated test infrastructure for intelligent monitoring and power management products. The ideal candidate is passionate about software development applied to quality engineering, enjoys writing code that validates firmware behavior, and is eager to apply Generative AI tools to test automation workflows." Responsibilities: list of bullet points (multiple sentences). We need to format as

  • each. Qualifications: list bullet points. About Us: includes Core Principles, Strategic Priorities, Vertiv Behaviors, About Vertiv description. Might be considered "About Us" section. Could also be "About the company". Not listed as a standard heading but we can use "About Us". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples; we can use other headings if needed, but better to stick to those. However "About Us" is not in list but could be considered similar to "About the role"? Actually "About the role" is for role summary. "About Us" could be separate but not in list. Might be okay to use "About Us" as heading? 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 to be safe we could incorporate About Us content into "About the role" or maybe "Qualifications"? Better to have a section "About Us" as it's substantive. The instruction didn't forbid; it just gave examples. I'll include "About Us". We must remove boilerplate: Equal Opportunity Employer, Work Authorization, etc. Also remove "Physical & Environmental Demands None", "Time Travel Required None". Also remove "No calls or agencies please." etc. Also remove "Work Authorization ..." and EEO paragraph. Also remove "If you have a disability..." etc. We need to preserve all substantive info: Position Summary, Responsibilities, Qualifications, About Us (Core Principles, Strategic Priorities, Vertiv Behaviors, About Vertiv). Also maybe "About Vertiv" description. We need to format lists. Let's extract responsibilities bullet points: - Develop and maintain automated test cases in Python that validate firmware functionality across network management protocols (Redfish, SNMP, Modbus, BACnet). - Build and extend API-level test automation targeting Redfish/REST interfaces on embedded power and monitoring hardware. - Integrate automated tests into CI/CD pipelines (GitLab CI) to support continuous validation of firmware builds. - Create and configure virtualized test environments for repeatable automated test execution. - Develop test utilities, data parsers, and reporting scripts that support the broader test engineering team. - Use Generative AI coding tools to accelerate test development and code review workflows. - Learn and use Agile Development practices for test planning and execution. - Stay current with trends in test automation and software engineering in test, continuously seeking opportunities to enhance your skills and apply new techniques. Qualifications bullet points: - Must be pursuing a degree in Computer Science, Computer Engineering, Software Engineering, or a related field. - Coursework or project experience in Python or another scripting language. - Excellent written and verbal communication skills. - Demonstrated work ethic and detail-orientation. - Strong analytical and critical thinking skills. - Ability and willingness to learn in a fast-paced environment and produce high-quality work. - Collaboration and teamwork. - Familiarity with version control (Git) is a plus. - Exposure to REST APIs, CI/CD concepts, or Linux command-line environments is a plus. About Us content: - OUR CORE PRINCIPLES: Safety. Integrity. Respect. Teamwork. Inclusion. - OUR STRATEGIC PRIORITIES: High-Performance Culture Customer Focus Operational Excellence Innovation Financial Strength - VERTIV BEHAVIORS: Own it Act with urgency Foster a customer-first mindset Think big and execute Lead by example Drive continuous improvement Learn and seek out development Promote transparent & open communication - About Vertiv: Vertiv (NYSE: VRT) brings together hardware, software, analytics and ongoing services to enable its customers’ vital applications to run continuously, perform optimally and grow with their business needs. Vertiv solves the most important challenges facing today’s data centers, communication networks, and commercial and industrial facilities with a portfolio of power, cooling and IT infrastructure solutions and services that extend from the cloud to the edge of the network. Headquartered in Westerville, Ohio, USA, Vertiv employs around 34,000 people and does business in more than 130 countries. Visit Vertiv.com to learn more. We need to format these as prose or lists. For Core Principles, Strategic Priorities, Vertiv Behaviors we could list as

    • . For About Vertiv description as

      . We must not include filler like "commensurate with experience". Not present. Now produce HTML fragment:

      About the role

      We are seeking a dedicated and proactive individual to join our Core Engineering team as a Software Engineer in Test Intern. This internship offers an excellent opportunity to gain hands-on experience building automated test infrastructure for intelligent monitoring and power management products. The ideal candidate is passionate about software development applied to quality engineering, enjoys writing code that validates firmware behavior, and is eager to apply Generative AI tools to test automation workflows.

      Responsibilities

      • Develop and maintain automated test cases in Python that validate firmware functionality across network management protocols (Redfish, SNMP, Modbus, BACnet).
      • Build and extend API-level test automation targeting Redfish/REST interfaces on embedded power and monitoring hardware.
      • Integrate automated tests into CI/CD pipelines (GitLab CI) to support continuous validation of firmware builds.
      • Create and configure virtualized test environments for repeatable automated test execution.
      • Develop test utilities, data parsers, and reporting scripts that support the broader test engineering team.
      • Use Generative AI coding tools to accelerate test development and code review workflows.
      • Learn and use Agile Development practices for test planning and execution.
      • Stay current with trends in test automation and software engineering in test, continuously seeking opportunities to enhance your skills and apply new techniques.

      Qualifications

      • Must be pursuing a degree in Computer Science, Computer Engineering, Software Engineering, or a related field.
      • Coursework or project experience in Python or another scripting language.
      • Excellent written and verbal communication skills.
      • Demonstrated work ethic and detail-orientation.
      • Strong analytical and critical thinking skills.
      • Ability and willingness to learn in a fast-paced environment and produce high-quality work.
      • Collaboration and teamwork.
      • Familiarity with version control (Git) is a plus.
      • Exposure to REST APIs, CI/CD concepts, or Linux command-line environments is a plus.

      About Us

      Core Principles

      • Safety
      • Integrity
      • Respect
      • Teamwork
      • Inclusion

      Strategic Priorities

      • High-Performance Culture
      • Customer Focus
      • Operational Excellence
      • Innovation
      • Financial Strength

      Vertiv Behaviors

      • Own it
      • Act with urgency
      • Foster a customer-first mindset
      • Think big and execute
      • Lead by example
      • Drive continuous improvement
      • Learn and seek out development
      • Promote transparent & open communication

      Vertiv (NYSE: VRT) brings together hardware, software, analytics and ongoing services to enable its customers’ vital applications to run continuously, perform optimally and grow with their business needs. Vertiv solves the most important challenges facing today’s data centers, communication networks, and commercial and industrial facilities with a portfolio of power, cooling and IT infrastructure solutions and services that extend from the cloud to the edge of the network. Headquartered in Westerville, Ohio, USA, Vertiv employs around 34,000 people and does business in more than 130 countries. Visit Vertiv.com to learn more.

      We used

      for subheadings; but instruction only mentions

      for section headings. Using

      might be okay but maybe better to keep everything under

      sections only. Could we incorporate Core Principles etc as

      directly under About Us without subheadings? But then it's less clear. The instruction didn't forbid other heading levels, but said use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't say we cannot use other headings, but to be safe we could avoid

      and just use

      for those headings? However we need to preserve structure. Could we make each of those as

      sections? That would be many sections but they are substantive. The instruction says prefer a few substantive sections over many thin ones. So maybe better to keep About Us as one section with paragraphs and lists, without subheadings. We can embed the principles as a list preceded by a short sentence. Let's do:

      About Us

      Vertiv’s Core Principles: Safety, Integrity, Respect, Teamwork, Inclusion.

      Strategic Priorities: High-Performance Culture, Customer Focus, Operational Excellence, Innovation, Financial Strength.

      Vertiv Behaviors: Own it, Act with urgency, Foster a customer-first mindset, Think big and execute, Lead by example, Drive continuous improvement, Learn and seek out development, Promote transparent & open communication.

      About Vertiv: Vertiv (NYSE: VRT) brings together hardware, software, analytics and ongoing services to enable its customers’ vital applications to run continuously, perform optimally and grow with their business needs. Vertiv solves the most important challenges facing today’s data centers, communication networks, and commercial and industrial