Jobs · Information Technology · Texas

2027 Summer Intern: Technology Business Analyst & Project Coordination

PepsiCo · Plano, TX · 1 mo ago
On-siteInformation Technology$21.09–$44.4/hrFull-time
We need to output HTML fragment with sections: About the role? The posting includes Overview (intro), Functional Description, Responsibilities, Technical Skills, Qualifications, Minimum Qualifications, Compensation, Benefits. Also location note maybe part of Qualifications? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
  • for any list of duties/requirements/benefits, and

    for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. We need to decide which sections to include based on content. We have: - Overview (intro) - could be "About the role" maybe? But they said "About the role" as example heading. The overview is generic about PepsiCo, not specific to role. Might still be appropriate as "About the role"? However they said do NOT repeat the job title as a heading (the page already shows it). The overview is not job title. Could be "About the role" but it's more about company. Might be okay. - Functional Description: describes digital journey, etc. Could be part of "About the role" or separate "Functional Description". Not in list of headings but we can use any heading? They gave examples but not limited. Probably we should stick to those headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content. Responsibilities: we have bullet points for Business Analyst role profile and Project Coordination role profile. So we can put under Responsibilities. Technical Skills: we have bullet list: Understanding and usage of tools used during requirements gathering including full Microsoft Office Suite. Also note about location? Actually location note: "While final work placement will be in one of the following two locations, no specific location is guaranteed pre-offer. Actual working location will be determined and identified at the point of offer. Plano, TX Purchase, NY". This could be under "Qualifications" maybe? Or separate "Location". Not in list; but we could embed in Qualifications as a note. Qualifications: we have bullet list: Currently pursuing a degree in: Business Administration, Business Information Systems, Computer Science, Computer Engineering, Engineering, Finance, Information Systems, MIS or Software Engineering (other related majors may be considered). Minimum GPA 3.0. Technology related experience a plus. Ability to learn new technologies and processes information quickly. Ability to adapt to changes in timelines and sequences. Excellent verbal and written communication skills. Ability to participate in ten or twelve-week internship program May - August. Minimum Qualifications - Each candidate is expected to: This position is limited to persons with indefinite right to work in the United States. Graduate with bachelor’s or master’s degree within one (1) year of internship completion. Compensation: "Compensation: The expected compensation hourly pay ranges for hires into our 2027 campus intern openings is $21.09 - $44.40 hourly. Role, degree discipline, degree level, and location are part of the process when determining actual starting salary for positions. Hourly pay for our campus hires is pre-determined and non-negotiable." Benefits: "We love to convert our interns to full-time opportunities! Our full-time positions have a comprehensive benefits package to support our employees and their families, subject to elections and eligibility: Medical, Dental, Vision, Disability, Health and Dependent Care Reimbursement Accounts, Employee Assistance Program (EAP), Insurance (Accident, Group Legal, Life), Defined Contribution Retirement Plan." We should not include EEO statement etc. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. We need to decide sections: About the role (maybe combine Overview + Functional Description). Responsibilities (list). Qualifications (list). Skills (Technical Skills). Pay (Compensation). Benefits (list). Possibly Schedule? Not mentioned except internship program duration (ten or twelve-week internship program May - August). That could be considered Schedule? Might be better to include under Qualifications as ability to participate in ten or twelve-week internship program May - August. Not a schedule heading. We should not create Schedule section unless posting actually states them. It does mention internship program duration, but not schedule like full-time/part-time. Might be considered schedule? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state internship program duration, which is schedule-related. Could we create a Schedule section? Might be okay but they gave example headings: Schedule. Could include that. However they said prefer a few substantive sections over many thin ones. Might be better to incorporate internship duration into Qualifications or About the role. I'll include sections: About the role (Overview + Functional Description). Responsibilities. Qualifications (including GPA, major, right to work, degree timeline, ability to participate in internship). Skills (Technical Skills). Pay (Compensation). Benefits. We need to use

    for each section heading. Use
    • for any list of duties/requirements/benefits. Use

      for prose. We must preserve all substantive information; do not invent or summarize away detail. Let's craft. About the role: combine Overview and Functional Description paragraphs. We'll put them in

      maybe multiple paragraphs. Responsibilities: we have two role profiles: Business Analyst role profile consists of - Uses knowledge of business processes to analyze options, define requirements, and create functional designs for technology solutions to business problems. Responsible for connecting the business needs with the technical teams to provide them the requirements. Responsible for working closely with business partners to document business requirements and write user stories Utilize dashboard tools like Tableau and PowerBI. The Project Coordination role profile consists of – Plans and manages the delivery of technology projects. Using the latest agile / scrum methodologies, you will have the opportunity to utilize tools like Azure DevOps and Tableau/PowerBI. We need to keep the bullet points. Could format as

      • ... each bullet. We need to preserve the dash and details. Qualifications: list items: Currently pursuing a degree in: Business Administration, Business Information Systems, Computer Science, Computer Engineering, Engineering, Finance, Information Systems, MIS or Software Engineering (other related majors may be considered). Minimum GPA 3.0. Technology related experience a plus. Ability to learn new technologies and processes information quickly. Ability to adapt to changes in timelines and sequences. Excellent verbal and written communication skills. Ability to participate in ten or twelve-week internship program May - August. Minimum Qualifications - Each candidate is expected to: This position is limited to persons with indefinite right to work in the United States. Graduate with bachelor’s or master’s degree within one (1) year of internship completion. We could split into two lists: one for "Qualifications" and another for "Minimum Qualifications"? But we can combine. We need to preserve all details. Skills: Technical Skills: Understanding and usage of tools used during requirements gathering including full Microsoft Office Suite. Also note about location? Actually location note is separate. Should we include location under Qualifications? Could add a bullet: Work location: Plano, TX or Purchase, NY (final placement determined at offer). That is substantive. We should include location note as part of Qualifications maybe. Pay: Compensation paragraph. Benefits: list of benefits. Let's craft HTML. We'll start with

        About the role

        then

        ...

        maybe two paragraphs. Then

        Responsibilities

        • ...
        • ...
        Then

        Qualifications

        • ...
        • etc. Then

          Skills

          • ...
          Then

          Pay

          ...

          Then

          Benefits

          • ...
          Make sure not to include any empty sections. Check for any duplicated lines: we need to avoid repeating same content. Let's write. About the role paragraph: combine Overview and Functional Description. Overview: "At PepsiCo, you'll find the opportunity to grow your career, make an impact, and help shape what's next. As one of the world's leading food and beverage companies, our beloved brands—including Gatorade, Lay's, and Quaker—help create smiles with every sip and bite. Behind our products is a connected system that starts with how we source and grow ingredients alongside farmers and extends to how we make, move, and deliver products while driving positive impact for our business and communities. At the heart of PepsiCo are our people: professionals who bring curiosity, drive, and fresh thinking, working together to turn ideas into action. Across functions, teams, and markets, we collaborate to solve challenges, unlock new opportunities, and create meaningful impact for our consumers, customers, and communities. No matter your role, you'll be part of a connected community where your contributions matter, your voice is heard, and your development is supported. With opportunities to grow, belong, and smile, PepsiCo offers more than a place to build your career—it offers the chance to help create what's next." Functional Description: "PepsiCo is on a digital journey to become an intelligent company that derives its competitive advantage and sustainable growth from our ability to quickly anticipate and adapt to a constantly changing context having the consumer at the heart of the digital transformation. We will enhance the human experience and maximize value through the power of digital solutions, driving a deeply interconnected internal ecosystem of people, processes, systems, and data to engage seamlessly with consumers, customers, employees, partners and communities. Digital Evolution is critical to driving PepsiCo’s ambitions around being FASTER, STRONGER, and BETTER." We can combine into two paragraphs. Now Responsibilities: need to capture both role profiles. Business Analyst role profile consists of - Uses knowledge of business processes to analyze options, define requirements, and create functional designs for technology solutions to business problems. Responsible for connecting the business needs with the technical teams to provide them the requirements. Responsible for working closely with business partners to document business requirements and write user stories Utilize dashboard tools like Tableau and PowerBI. Project Coordination role profile consists of – Plans and manages the delivery of technology projects. Using the latest agile / scrum methodologies, you will have the opportunity to utilize tools like Azure DevOps and Tableau/PowerBI. We'll make two
        • items. Qualifications: list items. Let's list each as separate
        • . - Currently pursuing a degree in: Business Administration, Business Information Systems, Computer Science, Computer Engineering, Engineering, Finance, Information Systems, MIS or Software Engineering (other related majors may be considered). - Minimum GPA 3.0. - Technology related experience a plus. - Ability to learn new technologies and processes information quickly. - Ability to adapt to changes in timelines and sequences. - Excellent verbal and written communication skills. - Ability to participate in ten or twelve-week internship program May - August. - This position is limited to persons with indefinite right to work in the United States. - Graduate with bachelor’s or master’s degree within one (1) year of internship completion. - Work location: Pl

Similar jobs