Sales Specialist Intern
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, EEO, etc. Must preserve all substantive info.
Let's parse the posting.
Content:
- Intro paragraph: "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." This is generic marketing; maybe we can keep as part of About the role? But the instruction: "Prefer a few substantive sections over many thin ones." We can include an "About the role" section that contains the description after "About The Role". The intro before "About The Role" maybe can be considered part of About the role? But we need to preserve all substantive info. The intro is generic but still part of posting. Could include in About the role.
Then "About The Role" paragraph: "At Itron, we are shaping a more resourceful world by delivering innovative technology solutions that help utilities and cities better manage energy and water. Our Sales Internship – Technology & Utilities Focus is an immersive program designed to develop future leaders through real-world experience, cross-functional collaboration, and exposure to the evolving landscape of utility technology. This rotational internship offers a unique opportunity to work alongside seasoned professionals across Sales, Solution Architecture, and Executive Leadership. You’ll gain hands-on experience in how Itron delivers value to customers through data-driven, customer-centric solutions that support a more sustainable future. In this role you'll learn how we identify customer challenges and craft compelling, customer-first value propositions that drive impact, collaborate with technical experts to understand how Itron’s solutions are designed, configured, and positioned to meet complex utility needs, and gain strategic insight by observing executive- level decision-making, customer engagement, and leadership in action."
Then "Duties & Responsibilities" bullet list (actually sentences separated by periods). We need to format as - .
List items:
- Participate in a structured rotational program across three core teams: Sales Specialists, Solution Architecture/Pre-Sales, and Leadership Immersion.
- Contribute to a capstone project that integrates your learnings from each rotation. You’ll present your findings and recommendations to Itron leadership at the end of the program.
- Engage in team meetings, customer calls, and internal training sessions to deepen your understanding of Itron’s business, solutions, and customer relationships.
- Receive ongoing mentorship and feedback from leaders across departments to support your personal and professional growth.
- Demonstrate Itron’s core values—customer centricity, authenticity, accountability, agility, collaboration, and innovation—in every aspect of your work.
Then "Required Skills & Experience" bullet list:
- Currently pursuing a Bachelor’s degree in Business, Engineering, Technology, or related experience.
- Strong interest in sales, technology, and the utilities or energy sector.
- Excellent communication, collaboration, and problem-solving skills.
- A self-starter with a growth mindset and a passion for learning.
- Ability to work effectively in a hybrid environment and adapt to changing priorities.
Then "Preferred Skills & Experience" bullet list:
- Previous internship or project experience in sales, customer engagement, or technical solutioning.
- Familiarity with smart grid, IoT, or energy management technologies.
- Demonstrated leadership in academic, extracurricular, or community settings.
Then "Travel: 0 – 10%" and "Physical Demands This is a typical office job, with no special physical requirements or unusual work environment.This position will be a hybrid role and tied to our Austin, TX location."
Then EEO etc which we must remove.
Also there is a statement: "Itron is committed to building an inclusive and diverse workforce and providing an authentic workplace experience for all employees. If you are excited about this role but your past experiences don't perfectly align with every requirement, we encourage you to apply anyway. In the end, you may be just who we are looking for! The successful candidate's starting wage will be determined based on permissible, non-discriminatory factors such as skills and experience."
We need to decide if we include Pay section. The posting mentions starting wage determined based on skills/experience but no specific number. According to rule: 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. The posting does not give a specific pay figure or range; it just says wage will be determined based on skills/experience. That is essentially placeholder. So we should NOT create a Pay section.
Schedule: Not mentioned besides hybrid role and travel 0-10%. No explicit schedule (full-time, part-time). So we should not create Schedule section.
Benefits: Not mentioned. So no Benefits section.
We could include a "Travel" or "Location" info maybe under a generic section? But headings limited to those specified. We could incorporate travel/location into Responsibilities or About the role? Probably better to add a short paragraph under About the role or maybe a separate section like "Details" but not allowed. So we can incorporate into About the role or Responsibilities as a note.
We must not include boilerplate like EEO, accommodation contact, etc.
We must preserve all substantive information: that includes travel 0-10%, hybrid role tied to Austin, TX location, physical demands statement (typical office job, no special physical requirements). Also the statement about encouraging to apply even if not perfect alignment. Also the statement about starting wage determined based on skills/experience (though we decided not to create Pay section, we could include that sentence in About the role or maybe a separate short paragraph? But we must not create Pay heading. We can include that sentence in About the role or maybe a "Details" paragraph but we don't have a heading for that. Could add a
after About the role before Responsibilities? But we need to keep structure: we can have multiple
under a section. So we can include that sentence in About the role section as part of the description.
Similarly, the statement about encouraging to apply if not perfect alignment can be included in About the role or maybe a separate section like "Encouragement" but not needed. We'll include in About the role.
Now we need to output only HTML fragment, no markdown fences.
We'll produce:
About the role
... combined paragraphs ...
Then Responsibilities
- ...
...
Then Required Skills & Experience
...
Then Preferred Skills & Experience
...
Potentially also a section for "Travel & Location" but not in allowed headings. Could we add a Details
? Not allowed per instruction: only those headings. So we must not create other headings. So we need to embed travel/location/physical demands somewhere else. Perhaps we can add a after Responsibilities before Required Skills, but that would be orphaned text not under a heading. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid having stray paragraphs outside headings, but likely they expect sections only. Safer to embed that info in About the role or Responsibilities as a paragraph.
Let's embed after About the role paragraph a short paragraph about location, travel, physical demands.
Thus About the role section will have multiple
tags.
Now check for any duplicate lines: we must remove duplicated lines. There's no duplicate.
Now ensure we don't include any boilerplate like "Itron is committed to building an inclusive and diverse workforce..." That's substantive? It's about diversity commitment. Could be considered substantive but maybe it's boilerplate EEO. However it's not exactly EEO statement; it's a diversity commitment. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This line is about inclusive and diverse workforce, which could be considered EEO boilerplate. Safer to remove it. Also the sentence "If you are excited about this role but your past experiences don't perfectly align with every requirement, we encourage you to apply anyway. In the end, you may be just who we are looking for!" is encouraging to apply; not boilerplate, it's substantive motivational. Keep.
The statement about starting wage determined based on permissible, non-discriminatory factors such as skills and experience: that's also generic but maybe considered boilerplate? It's about compensation determination. Could be considered boilerplate but it's substantive about pay. Since we are not making Pay section, we could keep it in About the role as a note.
Now we need to ensure we don't include any application instructions or contact info. Remove the accommodation contact line and EEO statement.
Now produce final HTML.
Let's craft About the role paragraph(s):
Paragraph 1: "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."
Paragraph 2: "At Itron, we are shaping a more resourceful world by delivering innovative technology solutions that help utilities and cities better manage energy and water. Our Sales Internship – Technology & Utilities Focus is an immersive program designed to develop future leaders through real-world experience, cross-functional collaboration, and exposure to the evolving landscape of utility technology. This rotational internship offers a unique opportunity to work alongside seasoned professionals across Sales, Solution Architecture, and Executive Leadership. You’ll gain hands-on experience in how Itron delivers value to customers through data-driven, customer-centric solutions that support a more sustainable future. In this role you'll learn how we identify customer challenges and craft compelling, customer-first value propositions that drive impact, collaborate with technical experts to understand how Itron’s solutions are designed, configured, and positioned to meet complex utility needs, and gain strategic insight by observing executive- level decision-making, customer engagement, and leadership in action."
Paragraph 3: "The successful candidate's starting wage will be determined based on permissible, non-discriminatory factors such as skills and experience. If you are excited about this role but your past experiences don't perfectly align with every requirement, we encourage you to apply anyway. In the end, you may be just who we are looking for!"
Paragraph 4: "This is a hybrid role tied to our Austin, TX location with travel expected between 0–10%. The position is a typical office job with no special physical requirements or unusual work environment."
Now Responsibilities list as above.
Required Skills & Experience list.
Preferred Skills & Experience list.
Now ensure we don't include any headings for Requirements, Qualifications, etc. We have Required Skills & Experience and Preferred Skills & Experience. Could we combine them into Skills? The instruction allows Skills heading. But we have both required and preferred; we could make a Skills section with two sublists? But they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have a Skills heading and inside we could have required and preferred as paragraphs or subheadings? But subheadings not allowed. Better to keep Required Skills & Experience and Preferred Skills & Experience as separate headings? Those are not in the allowed list exactly but they are similar to Skills. The allowed list includes Skills. Could we use Skills heading and then inside we have two
paragraphs: one for Required, one for Preferred? That would lose the distinction but still convey info. However the instruction: "Prefer a few substantive sections over many thin ones." Having two separate headings may be thin. Better to combine into Skills heading with two paragraphs: "Required Skills & Experience:" and "Preferred Skills & Experience:" as bold? But we cannot use bold? We can use inside . That's okay.
Thus we will have:
Skills
<
after About the role before Responsibilities? But we need to keep structure: we can have multiple
under a section. So we can include that sentence in About the role section as part of the description. Similarly, the statement about encouraging to apply if not perfect alignment can be included in About the role or maybe a separate section like "Encouragement" but not needed. We'll include in About the role. Now we need to output only HTML fragment, no markdown fences. We'll produce:
About the role
... combined paragraphs ...
ThenResponsibilities
- ... ...
Required Skills & Experience
- ...
Preferred Skills & Experience
- ...
Details
? Not allowed per instruction: only those headings. So we must not create other headings. So we need to embed travel/location/physical demands somewhere else. Perhaps we can add aafter Responsibilities before Required Skills, but that would be orphaned text not under a heading. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid having stray paragraphs outside headings, but likely they expect sections only. Safer to embed that info in About the role or Responsibilities as a paragraph. Let's embed after About the role paragraph a short paragraph about location, travel, physical demands. Thus About the role section will have multiple
tags. Now check for any duplicate lines: we must remove duplicated lines. There's no duplicate. Now ensure we don't include any boilerplate like "Itron is committed to building an inclusive and diverse workforce..." That's substantive? It's about diversity commitment. Could be considered substantive but maybe it's boilerplate EEO. However it's not exactly EEO statement; it's a diversity commitment. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This line is about inclusive and diverse workforce, which could be considered EEO boilerplate. Safer to remove it. Also the sentence "If you are excited about this role but your past experiences don't perfectly align with every requirement, we encourage you to apply anyway. In the end, you may be just who we are looking for!" is encouraging to apply; not boilerplate, it's substantive motivational. Keep. The statement about starting wage determined based on permissible, non-discriminatory factors such as skills and experience: that's also generic but maybe considered boilerplate? It's about compensation determination. Could be considered boilerplate but it's substantive about pay. Since we are not making Pay section, we could keep it in About the role as a note. Now we need to ensure we don't include any application instructions or contact info. Remove the accommodation contact line and EEO statement. Now produce final HTML. Let's craft About the role paragraph(s): Paragraph 1: "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." Paragraph 2: "At Itron, we are shaping a more resourceful world by delivering innovative technology solutions that help utilities and cities better manage energy and water. Our Sales Internship – Technology & Utilities Focus is an immersive program designed to develop future leaders through real-world experience, cross-functional collaboration, and exposure to the evolving landscape of utility technology. This rotational internship offers a unique opportunity to work alongside seasoned professionals across Sales, Solution Architecture, and Executive Leadership. You’ll gain hands-on experience in how Itron delivers value to customers through data-driven, customer-centric solutions that support a more sustainable future. In this role you'll learn how we identify customer challenges and craft compelling, customer-first value propositions that drive impact, collaborate with technical experts to understand how Itron’s solutions are designed, configured, and positioned to meet complex utility needs, and gain strategic insight by observing executive- level decision-making, customer engagement, and leadership in action." Paragraph 3: "The successful candidate's starting wage will be determined based on permissible, non-discriminatory factors such as skills and experience. If you are excited about this role but your past experiences don't perfectly align with every requirement, we encourage you to apply anyway. In the end, you may be just who we are looking for!" Paragraph 4: "This is a hybrid role tied to our Austin, TX location with travel expected between 0–10%. The position is a typical office job with no special physical requirements or unusual work environment." Now Responsibilities list as above. Required Skills & Experience list. Preferred Skills & Experience list. Now ensure we don't include any headings for Requirements, Qualifications, etc. We have Required Skills & Experience and Preferred Skills & Experience. Could we combine them into Skills? The instruction allows Skills heading. But we have both required and preferred; we could make a Skills section with two sublists? But they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have a Skills heading and inside we could have required and preferred as paragraphs or subheadings? But subheadings not allowed. Better to keep Required Skills & Experience and Preferred Skills & Experience as separate headings? Those are not in the allowed list exactly but they are similar to Skills. The allowed list includes Skills. Could we use Skills heading and then inside we have two
paragraphs: one for Required, one for Preferred? That would lose the distinction but still convey info. However the instruction: "Prefer a few substantive sections over many thin ones." Having two separate headings may be thin. Better to combine into Skills heading with two paragraphs: "Required Skills & Experience:" and "Preferred Skills & Experience:" as bold? But we cannot use bold? We can use inside . That's okay.
Thus we will have:
<Skills