Digital Enterprise Apps Intern

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. Job posting includes: "What We're Looking For" repeated. Then description: Are you a hard-working... Barge Design Solutions looking for intern. Location: Nashville, TN Number of positions available: 1 Schedule: Summer 2027. Then "You Will Gain Experience In" list of duties. Then "Education & Experience Qualifications" heading repeated. Then list of qualifications. Then "Additional Details:" includes: paid internship full-time 40 hrs/week, in-person, interns not eligible for company benefits, housing assistance not provided. Then "Why join us?" description about company. Then EEO boilerplate etc to remove. We need to produce sections: About the role (maybe intro), Responsibilities (the "You Will Gain Experience In" list), Requirements (maybe location, schedule, number of positions?), Qualifications (Education & Experience Qualifications), Skills (maybe analytical etc), Benefits (maybe none? They said interns not eligible for company benefits, housing assistance not provided. So no benefits to list. Pay: they said paid internship but no amount. According to rule: do NOT create Pay section unless posting actually states them. It says paid internship but no amount; that is not specific pay info. Should we include Pay? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It states paid internship but not amount. Is that considered stating them? It states it's paid, but not amount. The rule says "unless the posting actually states them." Could interpret as states pay info (like salary, hourly). Since no amount, maybe we should not create Pay section. However we have Schedule: they gave Schedule: Summer 2027. That's a schedule (timeframe). So we can create Schedule section with that content. Also location and number of positions could go under About the role or maybe a separate section? There's no heading for location/number of positions; we could put them in About the role paragraph. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, equal opportunity, scam warning, etc. Also remove duplicated lines, navigation, cookie, legal. We need to preserve all substantive information. Let's extract substantive content: Intro: "What We're Looking For: Are you a hard-working and dedicated college student who is looking to gain valuable work experience in your field? Do you want to gain experience while learning from great mentors and leaders? Barge Design Solutions is looking for someone like you to intern with us next summer." Location: Nashville, TN Number of positions available: 1 Schedule: Summer 2027 Responsibilities (You Will Gain Experience In): - Supporting enterprise applications used across business and project operations - Assisting with application configuration, testing, documentation, and ongoing system improvements - Working with business users to understand processes, requirements, and opportunities for improvement - Supporting application testing, issue identification, and resolution - Assisting with documenting business processes, workflows, system requirements, and user procedures - Supporting data review and reporting associated with enterprise business systems - Gaining exposure to system implementations, enhancements, upgrades, and integrations - Collaborating with Digital team members and business stakeholders to support project deliverables and process improvements Education & Experience Qualifications: - Must be pursuing a Bachelor's degree or Master's degree from an accredited university - Major: Industrial Engineering, Information Systems, Business Information Systems, or related field - Current GPA of 3.0 or higher - Interest in enterprise technology, business systems, process improvement, and digital solutions - Strong analytical and problem-solving skills - Strong organizational, written, and verbal communication skills - Ability to work collaboratively with both technical and non-technical team members - You must be at least 18 years of age Additional Details: - This is a paid internship working full-time hours (40) per week - This is an in-person work opportunity - Interns are not eligible for company benefits - Housing assistance is not provided Why join us? (company description): - Barge Design Solutions, Inc., is an engineering and architecture firm with diverse in-house multidisciplinary practice areas. - The employee-owned company is more than 650+ people strong and serves clients nationwide from multiple U.S. locations. - Barge is ranked on Engineering News-Record (ENR)’s Top 500 Design Firms and Architectural Record’s Top 300 Architecture Firms and is a certified Great Place To Work®. - Our Primary Purpose For Being In Business Is Ultimately To Create a Better Life By Unleashing The Potential Of Our People, Clients And Communities. - This Purpose Is Supported By Our Company’s Core Values Because At The End Of The Day, Barge CARES Collaborate – Help and expect help. Teamwork is essential in what we do. Authentic – Honesty, integrity and trust are at the heart of everything we do. We are who we say we are. Responsible – We are accountable for our work, our attitude, and our actions. We make Barge better. Excellence – We go all in and expect more of ourselves than others expect of us. Service – We are humble. We use our gifts in service of others. We believe that if we are living out our purpose for being in business and integrating our values into everything we do, we will ultimately achieve our vision to be the firm best known for being selected when it matters most. We need to decide sections: About the role (intro + location + number of positions + schedule?), Responsibilities, Qualifications (Education & Experience Qualifications), Skills (maybe separate analytical etc but they are already in qualifications). Could combine qualifications and skills. But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map: - About the role: intro paragraph (What We're Looking For) plus location, number of positions, schedule? But schedule also could be its own section. Since we have schedule info, we can make Schedule section. - Requirements: maybe age requirement? Or maybe we could put "Must be at least 18 years of age" as requirement. But also major, GPA etc are qualifications. Could treat Requirements as eligibility (location? schedule?). However we have schedule separate. Better: Use sections as they make sense: About the role: intro paragraph (What We're Looking For) plus location and number of positions. Responsibilities: the list of duties. Qualifications: Education & Experience Qualifications (degree, major, GPA, interest). Skills: Strong analytical and problem-solving skills, Strong organizational, written, and verbal communication skills, Ability to work collaboratively with both technical and non-technical team members. Schedule: Summer 2027 (maybe also full-time 40 hrs/week? That's more about hours; could be in Schedule or Additional Details. But we have schedule heading; we can put "Summer 2027, full-time (40 hours per week), in-person". However the posting says "Schedule: Summer 2027" and Additional Details says full-time 40 hrs/week, in-person. We could combine. Benefits: none (interns not eligible for company benefits, housing assistance not provided). Since no benefits offered, we should not create Benefits section per rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state that interns are not eligible for company benefits and housing assistance not provided. That's a statement about benefits (lack thereof). Should we include Benefits section? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about benefits (that they are not eligible). So we could include a Benefits section with that info. However the instruction: "Prefer a few substantive sections over many thin ones." Might be better to incorporate that info into Additional Details paragraph under About the role or maybe a separate "Details" but we don't have a heading for that. We could put it in a paragraph under About the role or maybe under a generic section? There's no heading for "Additional Details". We could incorporate into About the role or maybe under "Schedule"? Not ideal. We could create a section "Details" but not allowed headings list. Only allowed headings are those specified. So we must fit content into those headings. Thus we need to decide where to put the info about paid internship, full-time, in-person, no benefits, no housing assistance. We could put "Paid internship working full-time hours (40) per week, in-person" under Schedule section (since schedule includes timing and hours). And "Interns are not eligible for company benefits. Housing assistance is not provided." could go under Benefits section (since it's about benefits). Even though it's stating lack of benefits, it's still about benefits. So we can create Benefits section with those two lines. Pay: we have no specific pay amount, so we should not create Pay section. Thus sections: - About the role: intro + location + number of positions. - Responsibilities: list. - Qualifications: education/major/GPA/interest. - Skills: analytical, communication, collaboration. - Schedule: Summer 2027, full-time (40 hrs/week), in-person. - Benefits: Interns are not eligible for company benefits. Housing assistance is not provided. We should not include Requirements heading if we don't have separate content; we could omit. Check if any content missing: The "Why join us?" company description is substantive; we need to preserve it. Where to put? Could be part of About the role (maybe a paragraph about company). Or we could create a separate section but no heading matches. Could put under About the role as additional paragraph. Thus About the role will include: intro, location, number of positions, company description (Why join us?). That seems okay. Now ensure we don't repeat headings unnecessarily. Let's craft HTML:

About the role

Are you a hard-working and dedicated college student who is looking to gain valuable work experience in your field? Do you want to gain experience while learning from great mentors and leaders? Barge Design Solutions is looking for someone like you to intern with us next summer. Located in Nashville, TN, this is a single position opportunity.

Barge Design Solutions, Inc., is an engineering and architecture firm with diverse in-house multidisciplinary practice areas. The employee-owned company is more than 650+ people strong and serves clients nationwide from multiple U.S. locations. Barge is ranked on Engineering News-Record (ENR)’s Top 500 Design Firms and Architectural Record’s Top 300 Architecture Firms and is a certified Great Place To Work®. Our Primary Purpose For Being In Business Is Ultimately To Create a Better Life By Unleashing The Potential Of Our People, Clients And Communities. This Purpose Is Supported By Our Company’s Core Values Because At The End Of The Day, Barge CARES Collaborate – Help and expect help. Teamwork is essential in what we do. Authentic – Honesty, integrity and trust are at the heart of everything we do. We are who we say we are. Responsible – We are accountable for our work, our attitude, and our actions. We make Barge better. Excellence – We go all in and expect more of ourselves than others expect of us. Service – We are humble. We use our gifts in service of others. We believe that if we are living out our purpose for being in business and integrating our values into everything we do, we will ultimately achieve our vision to be the firm best known for being selected when it matters most.

Responsibilities

• Supporting enterprise applications used across business and project operations
• Assisting with application configuration, testing, documentation, and ongoing system improvements
• Working with business users to understand processes, requirements, and opportunities for improvement
• Supporting application testing, issue identification, and resolution