Business Analyst Intern
Imperial Supplies · Green Bay, WI · 2 wk ago
Full-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
Content:
- Work Location Type: Hybrid (maybe not needed)
- Company description: Imperial Supplies, a Grainger Company, national distributor... etc. This is about the role/company. Could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put company description under About the role.
- Then "Business Analyst Intern – Summer 2027" is the job title; we should not repeat as heading.
- Then description: "As a Business Analytics Intern at Imperial Supplies, we’ll help you design an experience that meets your learning objectives while giving you hands-on exposure to how analytics supports real business decisions. You will work closely with experienced analytics professionals and business stakeholders to transform data into actionable insights that drive sales, margin improvement, and operational efficiency. Imperial Supplies is a growing distributor of fleet maintenance products, headquartered in Green Bay since 1958, with a strong history of double-digit annual growth. This internship provides an opportunity to contribute to meaningful analytics initiatives while building practical skills in reporting, modeling, and stakeholder communication. Under general supervision, the Business Analytics Intern will support analytics and reporting initiatives by gathering business requirements, developing dashboards and analytical models, and presenting insights to stakeholders. This role blends elements of business analysis and data science, providing exposure to both descriptive reporting and advanced analytics."
That's prose; could go under About the role.
- Then "Internship details Paid internship during Fall 2026Duration of 12 weeks, up to 20 hours per week depending on student interest and availabilityWilling to provide supporting documentation for students seeking school credit"
We need to extract Pay, Schedule, Benefits. Pay: "Paid internship" but no amount. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It says Paid internship (implies pay) but no specific amount. The rule says do NOT emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Since we have no specific pay amount, we should not create a Pay section. Similarly Schedule: "Duration of 12 weeks, up to 20 hours per week depending on student interest and availability" That's specific schedule info. So we can include a Schedule section with that detail. Benefits: "Willing to provide supporting documentation for students seeking school credit" That's a benefit? Could be considered a benefit (school credit). But it's not typical benefits like health insurance. The rule: include a section ONLY when posting has real, specific content for it. This is specific: providing documentation for school credit. Could be considered a benefit. However the Benefits heading is typical for things like health, retirement, etc. But we could still include if we think it's a benefit. The instruction: "Prefer a few substantive sections over many thin ones." Might be better to combine schedule and maybe other details under About the role? But schedule is specific; we could create a Schedule section.
We also have "Key Responsibilities" list. That's Responsibilities section.
Then "Intern Goals & Learning Outcomes" maybe could be under Requirements or Qualifications? Actually it's goals/outcomes; could be under Requirements? But we have separate sections: Requirements, Qualifications, Skills. The posting includes "Internship Requirements" list. That's Requirements. Also there may be Qualifications? Not separate; maybe Requirements covers qualifications. Skills maybe not explicitly listed; but we could infer from requirements: foundational knowledge, experience with Excel, Power BI, SQL, Python, analytical curiosity, etc. Those could be Skills. But we should not invent content; we can put those under Requirements or Skills. The posting has "Internship Requirements" bullet list. That's likely the Requirements section. There's also "Current enrollment in a degree program related to Business Analytics, Data Analytics, Data Science, or a similar quantitative field" etc. That's qualifications. Could be under Qualifications. But we have both Requirements and Qualifications headings; we need to decide what to put where. The instruction: Use headings for those categories if content exists. We have content for Requirements (the bullet list). We also have content for Qualifications? The bullet list includes enrollment, foundational knowledge, experience/coursework, analytical curiosity, ability to manage priorities, communication skills. Those could be considered qualifications. But we might just put all under Requirements and skip Qualifications to avoid thin sections. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But headings are fixed; we cannot rename. We could put the bullet list under Requirements and leave Qualifications empty (not output). That's fine.
Skills: Not explicitly listed separate; we could extract skills from the bullet list: Experience or coursework using Excel; exposure to Power BI, SQL, and/or Python preferred; Strong analytical curiosity with attention to detail; Ability to manage multiple priorities and work in a collaborative, fast-paced environment; Effective written and verbal communication skills. Those are skills. Could put under Skills. But then Requirements would be just the enrollment? Actually the bullet list includes both qualifications and skills. To avoid duplication, we could split: Requirements: Current enrollment in a degree program related to Business Analytics, Data Analytics, Data Science, or a similar quantitative field. Qualifications: Foundational knowledge of data analysis concepts and business problem-solving. Skills: Experience or coursework using Excel; exposure to Power BI, SQL, and/or Python preferred; Strong analytical curiosity with attention to detail; Ability to manage multiple priorities and work in a collaborative, fast-paced environment; Effective written and verbal communication skills.
But we need to ensure we don't create thin sections with placeholder. Each would have substantive content.
We also have "Intern Goals & Learning Outcomes" which could be under Requirements? Or maybe under Qualifications? But we could treat as a separate section? Not in allowed headings. Could be included under About the role or Responsibilities? Probably better to incorporate into About the role as prose.
We also have "Internship details" which we already used for Schedule.
Now we need to remove boilerplate: EEO statements, etc. Remove all that.
Now produce HTML fragment:
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
Content:
- Work Location Type: Hybrid (maybe not needed)
- Company description: Imperial Supplies, a Grainger Company, national distributor... etc. This is about the role/company. Could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put company description under About the role.
- Then "Business Analyst Intern – Summer 2027" is the job title; we should not repeat as heading.
- Then description: "As a Business Analytics Intern at Imperial Supplies, we’ll help you design an experience that meets your learning objectives while giving you hands-on exposure to how analytics supports real business decisions. You will work closely with experienced analytics professionals and business stakeholders to transform data into actionable insights that drive sales, margin improvement, and operational efficiency. Imperial Supplies is a growing distributor of fleet maintenance products, headquartered in Green Bay since 1958, with a strong history of double-digit annual growth. This internship provides an opportunity to contribute to meaningful analytics initiatives while building practical skills in reporting, modeling, and stakeholder communication. Under general supervision, the Business Analytics Intern will support analytics and reporting initiatives by gathering business requirements, developing dashboards and analytical models, and presenting insights to stakeholders. This role blends elements of business analysis and data science, providing exposure to both descriptive reporting and advanced analytics."
That's prose; could go under About the role.
- Then "Internship details Paid internship during Fall 2026Duration of 12 weeks, up to 20 hours per week depending on student interest and availabilityWilling to provide supporting documentation for students seeking school credit"
We need to extract Pay, Schedule, Benefits. Pay: "Paid internship" but no amount. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It says Paid internship (implies pay) but no specific amount. The rule says do NOT emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Since we have no specific pay amount, we should not create a Pay section. Similarly Schedule: "Duration of 12 weeks, up to 20 hours per week depending on student interest and availability" That's specific schedule info. So we can include a Schedule section with that detail. Benefits: "Willing to provide supporting documentation for students seeking school credit" That's a benefit? Could be considered a benefit (school credit). But it's not typical benefits like health insurance. The rule: include a section ONLY when posting has real, specific content for it. This is specific: providing documentation for school credit. Could be considered a benefit. However the Benefits heading is typical for things like health, retirement, etc. But we could still include if we think it's a benefit. The instruction: "Prefer a few substantive sections over many thin ones." Might be better to combine schedule and maybe other details under About the role? But schedule is specific; we could create a Schedule section.
We also have "Key Responsibilities" list. That's Responsibilities section.
Then "Intern Goals & Learning Outcomes" maybe could be under Requirements or Qualifications? Actually it's goals/outcomes; could be under Requirements? But we have separate sections: Requirements, Qualifications, Skills. The posting includes "Internship Requirements" list. That's Requirements. Also there may be Qualifications? Not separate; maybe Requirements covers qualifications. Skills maybe not explicitly listed; but we could infer from requirements: foundational knowledge, experience with Excel, Power BI, SQL, Python, analytical curiosity, etc. Those could be Skills. But we should not invent content; we can put those under Requirements or Skills. The posting has "Internship Requirements" bullet list. That's likely the Requirements section. There's also "Current enrollment in a degree program related to Business Analytics, Data Analytics, Data Science, or a similar quantitative field" etc. That's qualifications. Could be under Qualifications. But we have both Requirements and Qualifications headings; we need to decide what to put where. The instruction: Use headings for those categories if content exists. We have content for Requirements (the bullet list). We also have content for Qualifications? The bullet list includes enrollment, foundational knowledge, experience/coursework, analytical curiosity, ability to manage priorities, communication skills. Those could be considered qualifications. But we might just put all under Requirements and skip Qualifications to avoid thin sections. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But headings are fixed; we cannot rename. We could put the bullet list under Requirements and leave Qualifications empty (not output). That's fine.
Skills: Not explicitly listed separate; we could extract skills from the bullet list: Experience or coursework using Excel; exposure to Power BI, SQL, and/or Python preferred; Strong analytical curiosity with attention to detail; Ability to manage multiple priorities and work in a collaborative, fast-paced environment; Effective written and verbal communication skills. Those are skills. Could put under Skills. But then Requirements would be just the enrollment? Actually the bullet list includes both qualifications and skills. To avoid duplication, we could split: Requirements: Current enrollment in a degree program related to Business Analytics, Data Analytics, Data Science, or a similar quantitative field. Qualifications: Foundational knowledge of data analysis concepts and business problem-solving. Skills: Experience or coursework using Excel; exposure to Power BI, SQL, and/or Python preferred; Strong analytical curiosity with attention to detail; Ability to manage multiple priorities and work in a collaborative, fast-paced environment; Effective written and verbal communication skills.
But we need to ensure we don't create thin sections with placeholder. Each would have substantive content.
We also have "Intern Goals & Learning Outcomes" which could be under Requirements? Or maybe under Qualifications? But we could treat as a separate section? Not in allowed headings. Could be included under About the role or Responsibilities? Probably better to incorporate into About the role as prose.
We also have "Internship details" which we already used for Schedule.
Now we need to remove boilerplate: EEO statements, etc. Remove all that.
Now produce HTML fragment:
About the role
Imperial Supplies, a Grainger Company, is a national distributor of quality maintenance products. Serving the fleet maintenance industry since 1958, Imperial has formed lasting relationships with customers by tailoring our services to meet their changing needs. Our welcoming workplace enables you to learn, grow and make a difference by keeping businesses running and their people safe. As a Great Place to Work-Certified™ company, we’re looking for passionate people to join our team as we continue leading the industry. As a Business Analytics Intern at Imperial Supplies, we’ll help you design an experience that meets your learning objectives while giving you hands-on exposure to how analytics supports real business decisions. You will work closely with experienced analytics professionals and business stakeholders to transform data into actionable insights that drive sales, margin improvement, and operational efficiency. Imperial Supplies is a growing distributor of fleet maintenance products, headquartered in Green Bay since 1958, with a strong history of double-digit annual growth. This internship provides an opportunity to contribute to meaningful analytics initiatives while building practical skills in reporting, modeling, and stakeholder communication. Under general supervision, the Business Analytics Intern will support analytics and reporting initiatives by gathering business requirements, developing dashboards and analytical models, and presenting insights to stakeholders. This role blends elements of business analysis and data science, providing exposure to both descriptive reporting and advanced analytics. Intern Goals & Learning Outcomes: By the end of the internship, the intern will understand how to identify and define business insight needs, document analytics requirements and expected outcomes, design and deliver dashboards and/or analytical models, build hands-on experience with Power BI, Python, and SQL, and communicate analytics results effectively to business stakeholders.
Then Responsibilities:Responsibilities
- Partner with business stakeholders to gather insight requirements, define deliverables, and estimate level of effort for analytics initiatives.
- Design, build, test, and maintain reports and dashboards in Power BI to support recurring monitoring of key metrics.
- Develop and validate analytical models using Python and SQL to support business decision-making and optimization efforts.
- Perform data collection, validation, and analysis from internal or third-party data sources to ensure accuracy and usability of outputs.
- Translate complex analytical findings into clear, actionable insights and present results to business stakeholders at varying levels.
- Document requirements, assumptions, and business value associated with analytics deliverables.
- Support continuous improvement efforts by identifying opportunities to automate manual reporting and improve existing dashboards or analytics processes.
Requirements
- Current enrollment in a degree program related to Business Analytics, Data Analytics, Data Science, or a similar quantitative field.
Qualifications
- Foundational knowledge of data analysis concepts and business problem-solving.
Skills
- Experience or coursework using Excel; exposure to Power BI, SQL, and/or Python preferred.
- Strong analytical curiosity with attention to detail.
- Ability to manage multiple priorities and work in a collaborative, fast-paced environment.
- Effective written and verbal communication skills.
Schedule
- Paid internship during Fall 2026.
- Duration of 12 weeks, up to 20 hours per week depending on student interest and availability.
- Willing to provide supporting documentation for students seeking school credit.