Intern - Electrical Engineer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only sections that have real specific content. No job title heading. No Job ID. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines. Must preserve all substantive info.
We need to parse the posting.
Content:
- Intro: "Itron is innovating new ways for utilities and cities to manage energy and water. We create a more resourceful world to protect essential resources for today and tomorrow. Join us." repeated twice. Then "For decades, Itron has been delivering critical energy and water infrastructure services to customers around the globe--and we're just getting started. Join us and help design the future of resource management."
- Role description: "This Electrical Engineer Intern will support Itron’s lab team in Raleigh, working on site with experienced engineers to maintain lab operations. In this role, you'll help develop automation solutions that improve lab efficiency while maintaining high standards for engineering quality, safety, and documentation. Success comes from applying sound technical judgment, communicating effectively with the team, leveraging AI-powered engineering tools responsibly, and creating organized, reproducible work that others can build upon."
- Duties & Responsibilities: list bullet points.
- Required Skills & Experience: bullet list.
- Preferred Skills & Experience: bullet list.
- Availability: "Available to work approximately 40 hours per week during the summer, on site in a lab environment in Raleigh, North Carolina."
- Professional written and verbal communication skills (maybe part of required? It's listed after availability but before Preferred? Actually after "Available to work..." then "Professional written and verbal communication skills." Might be part of required.
- Benefits Info: "This position also includes a competitive benefit package including; financial, social, health and wellbeing programs, paid vacation, 401k matching, employee stock purchase program,, and more!"
- Then EEO etc which we remove.
- Also "Itron is committed to building an inclusive and diverse workforce..." remove.
- "If you are excited about this role but your past experiences don't perfectly align..." remove.
- "The successful candidate's starting wage will be determined based on permissible, non-discriminatory factors such as skills and experience." This is about pay but not specific numbers. According to rules: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state benefits (competitive benefit package). So we can include Benefits section. Pay: they mention starting wage determined based on factors but no actual wage or range. That's not specific; we should not create Pay section because it's not specific (just says determined based on factors). So omit Pay.
- Schedule: they mention availability to work approx 40 hours per week during the summer, on site. That's schedule info (hours per week, location). So we can include Schedule section.
- Also maybe "About the role" section: we can have an introductory paragraph summarizing role.
- Responsibilities: list duties.
- Requirements: maybe combine Required Skills & Experience and also some other like enrollment, Python ability, etc. Could be "Requirements" section.
- Qualifications: maybe Preferred Skills & Experience as "Preferred Qualifications" or "Preferred Skills". But we have headings list: Skills, Benefits, Pay, Schedule. We can also have "Skills" section for required and preferred? But we have separate Required and Preferred. Could combine into Skills? However we have headings for Skills (generic). Could put required skills under Skills, and preferred under maybe "Preferred Skills" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map:
- About the role: intro paragraph.
- Responsibilities: duties list.
- Requirements: required skills & experience (including enrollment, Python, etc.)
- Qualifications: preferred skills & experience.
- Skills: maybe we could combine required and preferred? But we already used Requirements and Qualifications. Could still have Skills for something else like technical skills? Might be redundant. Better to not include Skills if we already covered. But we need to follow rule: Prefer a few substantive sections over many thin ones. So we can have About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. That's six sections. That's fine.
We must not include sections with filler like "commensurate with experience". Not present.
Now we need to format lists using - . Use
for prose.
We must preserve all substantive information. Let's extract details.
Intro paragraphs:
- "Itron is innovating new ways for utilities and cities to manage energy and water. We create a more resourceful world to protect essential resources for today and tomorrow. Join us." (duplicate but we keep once.)
- "For decades, Itron has been delivering critical energy and water infrastructure services to customers around the globe--and we're just getting started. Join us and help design the future of resource management."
- Role description: "This Electrical Engineer Intern will support Itron’s lab team in Raleigh, working on site with experienced engineers to maintain lab operations. In this role, you'll help develop automation solutions that improve lab efficiency while maintaining high standards for engineering quality, safety, and documentation. Success comes from applying sound technical judgment, communicating effectively with the team, leveraging AI-powered engineering tools responsibly, and creating organized, reproducible work that others can build upon."
We can combine these into About the role paragraph(s). Could be multiple
tags.
Now Responsibilities (Duties & Responsibilities):
List:
- Identify and debug issues across Itron mesh networks, smart-city RF communications, lab computers, and connected test equipment.
- Set up and run engineering tests, verify data quality, analyze results, and compile clear test reports.
- Collaborate with senior lab engineers on Raleigh lab projects, prototypes, investigations, and process improvements.
- Support lab maintenance, equipment organization, calibration tracking, and safe operation of electrical test setups.
- Develop Python-based automation tools for test execution, data processing, equipment control, and reporting.
- Use AI coding agents to assist with code generation, refactoring, debugging, unit-test creation, documentation, and repetitive development tasks.
- Write clear task specifications and prompts for coding agents, define acceptance criteria, and provide the context needed for reliable results.
- Review, test, and validate AI-generated code before use; identify incorrect assumptions, security concerns, unsafe behavior, and maintainability issues.
- Use source control and issue-tracking practices to document changes, preserve traceability, and collaborate with engineers.
Now Requirements (Required Skills & Experience):
List:
- Enrolled in an accredited electrical engineering, computer engineering, computer science, or related degree program, with at least two years of college-level coursework completed.
- Ability to program in Python and read, troubleshoot, and modify existing code.
- Basic understanding of software development practices, including modular design, debugging, testing, and documentation.
- Practical ability to use AI coding assistants or agents while independently reviewing and validating their output.
- Ability to translate an engineering task into clear requirements, constraints, test cases, and completion criteria for an AI coding agent.
- Experience organizing, cleaning, maintaining, or calibrating lab equipment.
- Awareness of electrical hazards and ability to follow established safety procedures when working around energized or high-voltage equipment.
- Available to work approximately 40 hours per week during the summer, on site in a lab environment in Raleigh, North Carolina.
- Professional written and verbal communication skills.
Note: The availability and location might be better placed in Schedule section. But it's also a requirement. We could keep it in Requirements but also have Schedule section. To avoid duplication, we could move availability to Schedule and keep requirement list without that line. However the instruction: preserve ALL substantive information; do not invent or summarize away detail. If we move it to Schedule, we still preserve it. It's okay to not duplicate. We'll put availability in Schedule section.
Thus Requirements list excludes the availability line.
Now Qualifications (Preferred Skills & Experience):
List:
- Related internship, research, laboratory, or project experience.
- Coursework or hands-on experience in RF systems, analog and digital electronics, embedded systems, or data acquisition.
- Experience with Linux and command-line tools.
- Experience with Git, pull requests, code reviews, issue tracking, or CI/CD workflows.
- Ability to program in C, C++, C#, Rust, or another compiled language.
- Experience using AI coding agents in an IDE or development workflow, including prompt iteration, context management, tool use, and multi-step task execution.
- Experience creating unit tests, integration tests, test fixtures, or automated validation scripts.
- Familiarity with APIs, serial communications, network troubleshooting, or instrument-control interfaces.
- Experience working safely with hand tools and power tools.
Now Benefits:
- "This position also includes a competitive benefit package including; financial, social, health and wellbeing programs, paid vacation, 401k matching, employee stock purchase program,, and more!" Need to clean duplicate commas. Keep as is but maybe fix punctuation? We should preserve substantive info; we can keep the sentence as is, maybe remove extra comma. The original: "financial, social, health and wellbeing programs, paid vacation, 401k matching, employee stock purchase program,, and more!" There's double comma before "and more". We could keep as is but it's weird. Better to correct to single comma? The rule: do not invent or summarize away detail. Changing punctuation might be considered altering detail? It's minor but could be considered altering. Safer to keep exactly as given? However the double comma is likely a typo; preserving it keeps the typo. I'd keep it as is.
Now Schedule:
- "Available to work approximately 40 hours per week during the summer, on site in a lab environment in Raleigh, North Carolina."
Also maybe mention on-site lab environment.
Now we need to output HTML fragment only.
Structure:
About the role
...
...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Benefits
...
Schedule
...
Make sure no extra sections.
Now check for any other substantive info: "Itron is transforming how the world manages energy, water and city services..." etc is boilerplate? It's more marketing but maybe considered boilerplate? It's not about the role. It's likely considered boilerplate/legal? It's a generic statement about the company. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This paragraph about transforming how the world manages energy... is not EEO but could be considered generic marketing. Might be considered boilerplate? It's not specifically about the job. I'd remove it to keep focused. Also the repeated "Join us" lines we already have in intro; we can keep one.
We have duplicated lines: The intro repeats "Itron is innovating new ways..." twice. We'll keep once.
Now ensure we didn't miss any substantive info: The bit about "Itron is proud to be an Equal Opportunity Employer." Remove. Accommodation contact: remove. The line about "If you require an accommodation to apply, please contact..." remove.
Now check for any other specifics: "Professional written and verbal communication skills." Already in Requirements.
Now ensure we didn't include any filler like "commensurate with experience". Not present.
Now produce HTML.
Let's craft the About the role paragraphs:
Paragraph1: "Itron is innovating new ways for utilities and cities to manage energy and water. We create a more resourceful world to protect essential resources for today and tomorrow. Join us."
Paragraph2: "For decades, Itron has been delivering critical energy and water infrastructure services to customers around the globe--and we're just getting started. Join us and help design the future of resource management."
Paragraph3: "This Electrical Engineer Intern will support Itron’s lab team in
for prose. We must preserve all substantive information. Let's extract details. Intro paragraphs: - "Itron is innovating new ways for utilities and cities to manage energy and water. We create a more resourceful world to protect essential resources for today and tomorrow. Join us." (duplicate but we keep once.) - "For decades, Itron has been delivering critical energy and water infrastructure services to customers around the globe--and we're just getting started. Join us and help design the future of resource management." - Role description: "This Electrical Engineer Intern will support Itron’s lab team in Raleigh, working on site with experienced engineers to maintain lab operations. In this role, you'll help develop automation solutions that improve lab efficiency while maintaining high standards for engineering quality, safety, and documentation. Success comes from applying sound technical judgment, communicating effectively with the team, leveraging AI-powered engineering tools responsibly, and creating organized, reproducible work that others can build upon." We can combine these into About the role paragraph(s). Could be multiple
tags. Now Responsibilities (Duties & Responsibilities): List: - Identify and debug issues across Itron mesh networks, smart-city RF communications, lab computers, and connected test equipment. - Set up and run engineering tests, verify data quality, analyze results, and compile clear test reports. - Collaborate with senior lab engineers on Raleigh lab projects, prototypes, investigations, and process improvements. - Support lab maintenance, equipment organization, calibration tracking, and safe operation of electrical test setups. - Develop Python-based automation tools for test execution, data processing, equipment control, and reporting. - Use AI coding agents to assist with code generation, refactoring, debugging, unit-test creation, documentation, and repetitive development tasks. - Write clear task specifications and prompts for coding agents, define acceptance criteria, and provide the context needed for reliable results. - Review, test, and validate AI-generated code before use; identify incorrect assumptions, security concerns, unsafe behavior, and maintainability issues. - Use source control and issue-tracking practices to document changes, preserve traceability, and collaborate with engineers. Now Requirements (Required Skills & Experience): List: - Enrolled in an accredited electrical engineering, computer engineering, computer science, or related degree program, with at least two years of college-level coursework completed. - Ability to program in Python and read, troubleshoot, and modify existing code. - Basic understanding of software development practices, including modular design, debugging, testing, and documentation. - Practical ability to use AI coding assistants or agents while independently reviewing and validating their output. - Ability to translate an engineering task into clear requirements, constraints, test cases, and completion criteria for an AI coding agent. - Experience organizing, cleaning, maintaining, or calibrating lab equipment. - Awareness of electrical hazards and ability to follow established safety procedures when working around energized or high-voltage equipment. - Available to work approximately 40 hours per week during the summer, on site in a lab environment in Raleigh, North Carolina. - Professional written and verbal communication skills. Note: The availability and location might be better placed in Schedule section. But it's also a requirement. We could keep it in Requirements but also have Schedule section. To avoid duplication, we could move availability to Schedule and keep requirement list without that line. However the instruction: preserve ALL substantive information; do not invent or summarize away detail. If we move it to Schedule, we still preserve it. It's okay to not duplicate. We'll put availability in Schedule section. Thus Requirements list excludes the availability line. Now Qualifications (Preferred Skills & Experience): List: - Related internship, research, laboratory, or project experience. - Coursework or hands-on experience in RF systems, analog and digital electronics, embedded systems, or data acquisition. - Experience with Linux and command-line tools. - Experience with Git, pull requests, code reviews, issue tracking, or CI/CD workflows. - Ability to program in C, C++, C#, Rust, or another compiled language. - Experience using AI coding agents in an IDE or development workflow, including prompt iteration, context management, tool use, and multi-step task execution. - Experience creating unit tests, integration tests, test fixtures, or automated validation scripts. - Familiarity with APIs, serial communications, network troubleshooting, or instrument-control interfaces. - Experience working safely with hand tools and power tools. Now Benefits: - "This position also includes a competitive benefit package including; financial, social, health and wellbeing programs, paid vacation, 401k matching, employee stock purchase program,, and more!" Need to clean duplicate commas. Keep as is but maybe fix punctuation? We should preserve substantive info; we can keep the sentence as is, maybe remove extra comma. The original: "financial, social, health and wellbeing programs, paid vacation, 401k matching, employee stock purchase program,, and more!" There's double comma before "and more". We could keep as is but it's weird. Better to correct to single comma? The rule: do not invent or summarize away detail. Changing punctuation might be considered altering detail? It's minor but could be considered altering. Safer to keep exactly as given? However the double comma is likely a typo; preserving it keeps the typo. I'd keep it as is. Now Schedule: - "Available to work approximately 40 hours per week during the summer, on site in a lab environment in Raleigh, North Carolina." Also maybe mention on-site lab environment. Now we need to output HTML fragment only. Structure:
About the role
...
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
...
Schedule
...
Make sure no extra sections. Now check for any other substantive info: "Itron is transforming how the world manages energy, water and city services..." etc is boilerplate? It's more marketing but maybe considered boilerplate? It's not about the role. It's likely considered boilerplate/legal? It's a generic statement about the company. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This paragraph about transforming how the world manages energy... is not EEO but could be considered generic marketing. Might be considered boilerplate? It's not specifically about the job. I'd remove it to keep focused. Also the repeated "Join us" lines we already have in intro; we can keep one. We have duplicated lines: The intro repeats "Itron is innovating new ways..." twice. We'll keep once. Now ensure we didn't miss any substantive info: The bit about "Itron is proud to be an Equal Opportunity Employer." Remove. Accommodation contact: remove. The line about "If you require an accommodation to apply, please contact..." remove. Now check for any other specifics: "Professional written and verbal communication skills." Already in Requirements. Now ensure we didn't include any filler like "commensurate with experience". Not present. Now produce HTML. Let's craft the About the role paragraphs: Paragraph1: "Itron is innovating new ways for utilities and cities to manage energy and water. We create a more resourceful world to protect essential resources for today and tomorrow. Join us." Paragraph2: "For decades, Itron has been delivering critical energy and water infrastructure services to customers around the globe--and we're just getting started. Join us and help design the future of resource management." Paragraph3: "This Electrical Engineer Intern will support Itron’s lab team in