UX/UI Design Intern, Product Design Intern - S
for section headings, - for any list of duties/requirements/benefits, and
for prose.
We need to preserve ALL substantive information; do not invent or summarize away detail.
We need to remove boilerplate etc.
We need to format lists appropriately.
Let's extract each piece precisely.
**About the role** paragraph:
"Turn your classroom learning into real-world impact with H&R Block’s Embark 2027 Summer Internship Program, open to students studying Design, UX Design, and Product Design. This 11-week paid internship offers meaningful, real-world experience that aligns with your field of study while making a valuable impact on our organization. The Embark 2027 Summer Internship runs from May 17, 2027 – July 30, 2027. You’ll work at our corporate headquarters in the heart of downtown Kansas City’s Power & Light District, where you’re just steps, or a streetcar ride, away from incredible restaurants, entertainment, and city energy. Inside our building, you’ll have access to amenities that make work-life balance easy, including an onsite Starbucks, a company dining hall with plenty of options, a free fitness center, and free parking!"
Note: The amenities mention could be considered benefits, but it's also part of About the role description. However we might want to keep it in About the role as it's descriptive. But we also have Benefits section later; we could move amenities to Benefits. However the instruction says preserve ALL substantive information; we can duplicate? Better to not duplicate. We could keep amenities in About the role, but then Benefits section would also mention them if we list them again, causing duplication. To avoid duplication, we could either keep amenities in About the role and not list them again in Benefits, or move them to Benefits and remove from About the role. Which is better? The About the role paragraph currently includes that sentence. If we remove it, we lose some info about amenities. But we could keep it in About the role and still have Benefits section for other benefits (paid PTO, housing stipend). That's okay; we just won't duplicate amenities. However the Benefits section would then not include amenities; but we could still mention them there if we want, but that would duplicate. The instruction says preserve ALL substantive information; duplication is not prohibited but might be considered redundant. It didn't forbid duplication explicitly, but said "do NOT repeat the job title as a heading" and "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." It didn't forbid repeating content. However better to avoid duplication. We'll keep amenities in About the role and not repeat them in Benefits.
Thus About the role paragraph includes the amenities sentence.
Now Responsibilities: list after "some of the internship responsibilities will include:" then each line starts with a verb. Let's extract them exactly:
- Research customer needs and behaviors to identify opportunities and inform design decisions
- Create user flows, wireframes, mockups, and interactive prototypes for digital experiences
- Help design intuitive, accessible, and customer-centered experiences from concept through implementation
- Identify UX challenges and advocate for the user throughout the product development process
- Use customer feedback, research, and data to validate and iterate on designs
- Collaborate with Product, Engineering, Content, and other Design partners to bring experiences to life
- Apply established design systems and standards while exploring creative solutions to customer problems
- Participate in design critiques, product discussions, user testing, and other cross-functional team activities
- Present design concepts, recommendations, and rationale to team members and stakeholders
We need to preserve all. Use
- .
Now Requirements: includes education and work experience.
Education Required Qualifications: "High school diploma or equivalentSeeking to obtain a degree in UX Design, Graphic Design, Computer/Human Interaction, Computer Science, or some similar discipline with a GPA of 3.0 or aboveAbility to work as part of a diverse team and independentlyHighly motivated, organized, reliable, and detail-orientedStrong written and verbal communication skillsQuick learner and not afraid to work with new computer-based programs and databasesAbility to be effective and contribute in a fast-paced corporate environment"
Work Experience: "No previous work experience necessary"
We need to separate maybe into two lists: Education/Requirements and Work Experience? But both are requirements. Could combine into a single list under Requirements. However we need to preserve all info; we can make a list with items.
But note that some of those items are actually skills (e.g
for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. We need to remove boilerplate etc. We need to format lists appropriately. Let's extract each piece precisely. **About the role** paragraph: "Turn your classroom learning into real-world impact with H&R Block’s Embark 2027 Summer Internship Program, open to students studying Design, UX Design, and Product Design. This 11-week paid internship offers meaningful, real-world experience that aligns with your field of study while making a valuable impact on our organization. The Embark 2027 Summer Internship runs from May 17, 2027 – July 30, 2027. You’ll work at our corporate headquarters in the heart of downtown Kansas City’s Power & Light District, where you’re just steps, or a streetcar ride, away from incredible restaurants, entertainment, and city energy. Inside our building, you’ll have access to amenities that make work-life balance easy, including an onsite Starbucks, a company dining hall with plenty of options, a free fitness center, and free parking!" Note: The amenities mention could be considered benefits, but it's also part of About the role description. However we might want to keep it in About the role as it's descriptive. But we also have Benefits section later; we could move amenities to Benefits. However the instruction says preserve ALL substantive information; we can duplicate? Better to not duplicate. We could keep amenities in About the role, but then Benefits section would also mention them if we list them again, causing duplication. To avoid duplication, we could either keep amenities in About the role and not list them again in Benefits, or move them to Benefits and remove from About the role. Which is better? The About the role paragraph currently includes that sentence. If we remove it, we lose some info about amenities. But we could keep it in About the role and still have Benefits section for other benefits (paid PTO, housing stipend). That's okay; we just won't duplicate amenities. However the Benefits section would then not include amenities; but we could still mention them there if we want, but that would duplicate. The instruction says preserve ALL substantive information; duplication is not prohibited but might be considered redundant. It didn't forbid duplication explicitly, but said "do NOT repeat the job title as a heading" and "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." It didn't forbid repeating content. However better to avoid duplication. We'll keep amenities in About the role and not repeat them in Benefits. Thus About the role paragraph includes the amenities sentence. Now Responsibilities: list after "some of the internship responsibilities will include:" then each line starts with a verb. Let's extract them exactly: - Research customer needs and behaviors to identify opportunities and inform design decisions - Create user flows, wireframes, mockups, and interactive prototypes for digital experiences - Help design intuitive, accessible, and customer-centered experiences from concept through implementation - Identify UX challenges and advocate for the user throughout the product development process - Use customer feedback, research, and data to validate and iterate on designs - Collaborate with Product, Engineering, Content, and other Design partners to bring experiences to life - Apply established design systems and standards while exploring creative solutions to customer problems - Participate in design critiques, product discussions, user testing, and other cross-functional team activities - Present design concepts, recommendations, and rationale to team members and stakeholders We need to preserve all. Use
- . Now Requirements: includes education and work experience. Education Required Qualifications: "High school diploma or equivalentSeeking to obtain a degree in UX Design, Graphic Design, Computer/Human Interaction, Computer Science, or some similar discipline with a GPA of 3.0 or aboveAbility to work as part of a diverse team and independentlyHighly motivated, organized, reliable, and detail-orientedStrong written and verbal communication skillsQuick learner and not afraid to work with new computer-based programs and databasesAbility to be effective and contribute in a fast-paced corporate environment" Work Experience: "No previous work experience necessary" We need to separate maybe into two lists: Education/Requirements and Work Experience? But both are requirements. Could combine into a single list under Requirements. However we need to preserve all info; we can make a list with items. But note that some of those items are actually skills (e.g