2027 Summer Intern: Finance - Pricing Operations
Hubbell Incorporated · St Louis, MO · 2 days ago
Sales$22.5–$29/hrFull-time
We need to output HTML fragment with 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. Must not include boilerplate like EEO, etc. Must preserve all substantive info.
Let's parse the posting.
Job Overview: description of internship program, focus on automating pricing index model updates, gaining experience in pricing analytics, process improvement, data management, automation, creating scalable solutions, supporting pricing activities, reducing operational risk.
"A Day In The Life": bullet points of daily activities.
"What will help you thrive in this role?" includes requirements: Full-time enrollment, pursuing Bachelor's or Master's related, Minimum 3.0 GPA, Experience with Microsoft Office products. Then "Preferred Qualifications": Strong proficiency in Excel, VBA, Power Query; Experience with pricing analytics, data analysis, or commodity-based index models; Ability to work with complex datasets and process automation tools; Familiarity with customer pricing agreements and pricing operations is a plus.
Then "Intern compensation is determined based on academic standing and expected graduation date. Hourly rates for this position range from $22.50 to $29.00 per hour."
Thus we have Pay info.
We have no explicit Benefits or Schedule. So we should not include Benefits or Schedule sections unless they have real content. There's no mention of benefits or schedule. So omit those sections.
We need sections: About the role (maybe from Job Overview), Responsibilities (from "A Day In The Life" and maybe other duties), Requirements (minimum qualifications), Qualifications (preferred qualifications), Skills (maybe combine? but we can separate). The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include those headings that have content.
We need to decide what goes where.
About the role: likely the Job Overview paragraph(s). Could combine the first paragraph and maybe the Hubbell description? The Hubbell description about company might be considered "About the role"? Usually "About the role" is description of the role. The company description could be considered "About the company" but not requested. We could include it under About the role? Might be okay but maybe better to keep only role description. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine company description into About the role? Might be okay but it's not about the role. However we could omit company description if not needed? But we must preserve ALL substantive information. So we need to include company description somewhere. Where? Could be part of About the role? Or maybe we could add a section "About the company" but not in allowed headings. The allowed headings list is examples, not exhaustive? It says "use
. The bullet points are sentences starting with "On Any Given Day, You’ll Make a Difference By Applying skills..." etc. We'll extract each sentence as a list item.
Let's list them:
- Applying skills and knowledge learned in the classroom to on-the-job experiences.
- Working on comprehensive, value-added projects.
- Working in teams and with colleagues in a professional environment.
- Developing technical skills specific to your major.
- Providing opportunities for professional development by building relationships and learning about other parts of the business.
- Providing a presentation to the local management team at the end of the program.
- Gaining knowledge of the industry as it pertains to the Hubbell business location.
- Gaining experience in planning and organizational skills.
- Working on challenging robust projects that will provide practical experience.
- Assisting with process improvement.
- Managing multiple projects with overlapping tasks and working independently with minimal supervision.
- Providing support and assistance to co-workers as appropriate.
We need to ensure we keep all.
Now Requirements: list:
- Full-time enrollment in an accredited college or university throughout the internship program period (May-August 2027), pursuing a Bachelor's or Master's degree related to the internship.
- Minimum 3.0 GPA.
- Experience with Microsoft Office products.
We could keep as
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include those headings that have content.
We need to decide what goes where.
About the role: likely the Job Overview paragraph(s). Could combine the first paragraph and maybe the Hubbell description? The Hubbell description about company might be considered "About the role"? Usually "About the role" is description of the role. The company description could be considered "About the company" but not requested. We could include it under About the role? Might be okay but maybe better to keep only role description. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine company description into About the role? Might be okay but it's not about the role. However we could omit company description if not needed? But we must preserve ALL substantive information. So we need to include company description somewhere. Where? Could be part of About the role? Or maybe we could add a section "About the company" but not in allowed headings. The allowed headings list is examples, not exhaustive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for those categories. It doesn't forbid other headings, but likely they expect only those. However we need to preserve company description; maybe we can put it under About the role as a brief intro. That might be acceptable.
Alternatively we could create a section "About the role" containing the job overview and company description. That would preserve all.
Responsibilities: from "A Day In The Life" bullet points.
Requirements: from "What will help you thrive in this role?" the required items: Full-time enrollment, pursuing Bachelor's or Master's related, Minimum 3.0 GPA, Experience with Microsoft Office products.
Qualifications: Preferred Qualifications list.
Skills: maybe we could list specific skills like Excel, VBA, Power Query, pricing analytics, data analysis, commodity-based index models, complex datasets, process automation tools, customer pricing agreements, pricing operations. But those are already in Preferred Qualifications. Could move them to Skills. But we need to avoid duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the info but can reorganize. We could put required skills under Skills, and preferred qualifications under Qualifications. But the posting lumps them as "Preferred Qualifications". We could treat that as Qualifications section. Skills could be maybe derived from required: Experience with Microsoft Office products (skill). But we could also include technical skills like Excel, VBA, Power Query under Skills. However that would duplicate content from Preferred Qualifications. Might be okay if we keep both but not duplicate? The instruction says do not repeat? It doesn't explicitly forbid duplication but says preserve all info, not invent or summarize away detail. Duplication is not prohibited but might be unnecessary. Better to keep the Preferred Qualifications as Qualifications section, and maybe Skills section could be empty? But we must not emit a heading followed by filler/placeholder text. So we cannot have a Skills section with no content. So we should omit Skills if no specific content beyond what's already covered. However we have "Experience with Microsoft Office products" which is a skill. Could put that under Skills. But then we would need to move it from Requirements? Actually Requirements includes that. Could we split: Requirements: enrollment, GPA; Skills: Microsoft Office; Qualifications: preferred. That would preserve all info without duplication. Let's see.
Requirements: Full-time enrollment in an accredited college or university throughout the internship program period (May-August 2027), pursuing a Bachelor's or Master's degree related to the internship (required); Minimum 3.0 GPA (required). Experience with Microsoft Office products (maybe skill). But we could keep it under Requirements as it's a requirement. The posting says "Experience with Microsoft Office products" under "What will help you thrive in this role?" It's not labeled required or preferred but seems required? It's listed with required items? It says "Full-time enrollment ... (required) Minimum 3.0 GPA (required) Experience with Microsoft Office products". No explicit (required) but likely required. We'll treat as requirement.
Thus Requirements: enrollment, degree, GPA, MS Office.
Qualifications: Preferred Qualifications list.
Skills: maybe we could list technical skills like Excel, VBA, Power Query, pricing analytics, data analysis, commodity-based index models, complex datasets, process automation tools, customer pricing agreements, pricing operations. But those are already in Qualifications. To avoid duplication, we could omit Skills section.
Pay: we have hourly rate range.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay.
Now we need to format.
About the role: combine Job Overview paragraph and maybe company description? Let's include both: The Hubbell Internship Program description and the company description paragraphs (starting from "Hubbell Incorporated Hubbell creates critical infrastructure solutions...").
We need to preserve all substantive info. So include the internship program description, the focus on automating pricing index model updates, gaining experience, etc. Also include the company description about Hubbell, its mission, segments, etc. That is substantive.
Thus About the role will contain two paragraphs: first about internship program, second about Hubbell company.
Responsibilities: list from "A Day In The Life". Each bullet as
- .
Qualifications (Preferred): list:
- Strong proficiency in Excel, VBA, and Power Query.
- Experience with pricing analytics, data analysis, or commodity-based index models.
- Ability to work with complex datasets and process automation tools.
- Familiarity with customer pricing agreements and pricing operations is a plus.
Pay:
Intern compensation is determined based on academic standing and expected graduation date. Hourly rates for this position range from $22.50 to $29.00 per hour.
Now we need to output only HTML fragment, no /, no markdown fences. Thus:About the role
...first paragraph...
...second paragraph...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Pay
...
Make sure not to include extra whitespace? It's fine. Now let's craft the paragraphs. First paragraph (About the role - internship description): "The Hubbell Internship Program is a 10 to 12-week program providing students the opportunity to gain corporate experience, learn about all aspects of our business, and prepare students with the kind of experience needed to have a rewarding career at Hubbell. This intern will focus on automating and improving customer pricing index model updates by developing tools and processes that reduce manual work, streamline commodity refreshes, and improve the consistency and accuracy of pricing files. The intern will gain experience in pricing analytics, process improvement, data management, and automation while creating scalable solutions that support ongoing customer pricing activities and reduce operational risk." Second paragraph (company description): "Hubbell Incorporated creates critical infrastructure solutions that power our customers, communities, people and the planet. Our company is strategically aligned around enabling grid modernization and electrification. As more products plug in to an aging grid, Hubbell solutions enable the transition to a more reliable, resilient and efficient energy infrastructure. Founded in 1888 our innovation has made us a leading global manufacturer of high quality electrical and utility solutions enabling customers to operate critical infrastructure reliably and efficiently. The company operates in two segments. Hubbell Utility Solutions (HUS) enable the grid to conduct, communicate and control energy across utility applications and Hubbell Electrical Solutions (HES) are essential to managing power across a wide range of industries and applications. Our vertical market solutions can be applied to markets including Data Centers, Renewables, Commercial Buildings, Industrial, Telecom and Transportation. Supporting both of our business segments is our corporate and Hubbell Unified Business Solutions teams that provide consistent process, tools technologies across our businesses. We are committed to operating sustainably and ethically while promoting an inclusive and supportive culture for our people to grow and develop in their careers. Our employees proudly work and serve our communities from our headquarters in Shelton, CT, across the United States and around the globe." We could also include the Hubbell Utility Solutions description? That's already included in the company description paragraph (the part about HUS and HES). Actually the company description paragraph includes that. The posting also had a separate "Hubbell Utility Solutions" paragraph after the company description. That repeats some info. We need to preserve all substantive info; we already covered HUS and HES in the company description paragraph. The separate Hubbell Utility Solutions paragraph says: "Hubbell Utility Solutions (HUS) enable the grid to conduct, communicate and control energy across utility applications. HUS provides the critical components that allow the grid to reliably transmit and distribute energy, as well as the communications and controls technologies to make the grid smarter and more flexible." This is somewhat redundant but