Data & Analytics Consultant Intern - Summer 2027 (Hybrid in Indianapolis)

We need to output HTML fragment with sections: About the role? Actually we have company description, then "What To Expect From Your Summer At Resultant", then "Job Description", then "Qualifications", then "Core Skills & Competencies", then "Technical & Analytical Skills", then "Additional Information". We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We need to include sections only when posting has real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "All qualified applicants will receive consideration..." etc. Also remove "Equal Opportunity Employer" etc. Also remove "We embrace AI across everything we do..." maybe that's not boilerplate? It's more about interview instructions; maybe considered application instructions? It says "Feel free to use AI tools..." That's interview guidance, maybe considered application instructions? Probably remove. Also remove "What Our Team Members Say About Us…" maybe not needed? It's testimonials; could be considered extra but not required? It's not boilerplate but maybe we keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Testimonials not those, but could be considered extra fluff. However we need to preserve ALL substantive information; testimonials might be considered substantive? Might be okay to keep but maybe not needed. The sections we need: About the role? Could use "About the role" heading for company description and what to expect? Actually "About the role" could be the job description summary. But we have separate sections: Job Description (list of duties), Qualifications, Core Skills & Competencies, Technical & Analytical Skills, Additional Information (benefits etc). We need to use headings from the list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: About the role -> company description + what to expect? Responsibilities -> Job Description bullet list. Requirements -> Qualifications? Skills -> Core Skills & Competencies + Technical & Analytical Skills combined? Benefits -> Additional Information (benefits). Pay and Schedule only if present; posting mentions "Expectation of 3 days in office per week at a minimum." That's schedule info. Also mentions start date June 2027, must live in Indianapolis area. That's schedule/location. Pay not mentioned. So we can include Schedule section with that info. Benefits section: Additional Information includes benefits package: unlimited vacation, significant 401k contributions, opportunities to develop yourself. Also mentions Resultant compensates well, rewarding performance. So we can include Benefits. We must not create Pay section because not specified. We must not create headings with filler text. We need to output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

Company description... plus what to expect?

Maybe combine company description and "What To Expect From Your Summer At Resultant" into About the role. Then

Responsibilities

• ... each duty from Job Description list.

Then

Requirements

• ... qualifications list.

Then

Skills

Maybe split into two sub-sections? But we only have one Skills heading allowed. Could combine Core Skills & Competencies and Technical & Analytical Skills into one

with all items. Or we could have two headings? Not allowed; only those headings list. Could we have multiple Skills sections? Probably not; better to combine. Then

Benefits

• ... benefits.
Then

Schedule

... schedule info.

We must ensure we preserve all substantive info: company description, what to expect, job description duties, qualifications, core skills, technical skills, additional information (benefits, compensation, culture quotes? maybe we can keep quotes as part of Additional Information? But we removed testimonials? Might be considered substantive but not required. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the testimonials? They are quotes from team members; they are substantive but maybe not essential. However they are not boilerplate. Might be okay to keep as a paragraph under Additional Information or separate section? There's no heading for testimonials. Could include them in a paragraph under Additional Information or maybe under About the role? But they'd be extra. I'd include them as a paragraph under Additional Information after benefits. We must remove EEO statement, equal opportunity, etc. Also remove "All qualified applicants will receive consideration..." etc. Remove "We embrace AI across everything we do..." maybe considered application instructions? It's about interview guidance; could be considered application instructions, so remove. Also remove duplicated lines. Now craft content. Company Description: "Resultant is an outcomes-focused consulting firm committed to helping clients make technology a strategic asset and use data to guide better decisions. But we’re not just data and tech experts; we are problem solvers and industry experts who work alongside our clients to help them achieve their mission. We don’t solve problems for our clients. We solve problems with them. We take the time to deeply understand goals and roadblocks to drive toward outcomes that serve organizations, people, and communities. Through outcomes driven by data analytics, technology solutions, digital transformation, and beyond, our team works with clients in both the public and private sectors to solve their most complex challenges. We start by learning as much as we can about who they are, how they work, and what they’re striving for so we can feel their problems as our own. Partnering with our clients means their desired outcomes are always top of mind, their challenges and strengths guiding our efforts. We build client-focused relationships before we build unique solutions that blaze past expectations. Originally founded in Indianapolis in 2008, Resultant now employs more than 300 team members who operate remotely and from offices and hubs around the United States including Indianapolis, IN; Chicago, IL; Fort Wayne, IN; Denver, CO; Atlanta, GA; and Dallas, TX. We’re Resultant. Clients partner with us to see a difference. People join us to make one." What To Expect From Your Summer At Resultant: "Spend 10 weeks learning, contributing, and making connections at Resultant. You’ll work alongside Rezzers on meaningful projects, gain exposure to client work, and see firsthand how data and technology help our clients make a difference. Beyond your day-to-day work, you’ll connect with Rezzers across the organization through coffee chats, client spotlights, and interactive sessions covering topics like AI, consulting, communications, data, sales, and more. You’ll also collaborate with your intern cohort on a group project—giving you the opportunity to build new skills, solve a real business challenge, and make an impact of your own." Combine into About the role paragraph. Responsibilities (Job Description bullet list): list each duty: - Collaborate with cross-functional teams to support client projects and move work forward. - Engage with clients and stakeholders by asking thoughtful questions, synthesizing feedback, and presenting findings. - Identify, gather, and prepare data using structured, reproducible methods — including SQL, spreadsheets, basic scripting, and AI-assisted data prep tools. - Apply foundational analytical and statistical techniques, including AI-assisted pattern discovery and hypothesis generation, to uncover insights, trends, and patterns that address client needs. - Build clear data visualizations or reports using tools such as Power BI, Tableau, or spreadsheets, incorporating AI-assisted features where applicable to accelerate development. - Document business and functional requirements and translate insights into actionable plans and solution designs — including identifying opportunities where AI or automation can streamline manual processes. - Create process maps, workflow diagrams, and supporting documentation to clarify complex concepts. - Participate in testing activities by assisting with test scenarios, validating results (including outputs from AI-assisted tools), and ensuring solution quality. - Use AI copilots and prompting techniques to accelerate research, documentation, and analysis — while critically evaluating outputs for accuracy and applicability. - Use project and collaboration tools to stay organized and support team workflows. - Communicate status, risks, and insights clearly with teammates, clients, and stakeholders to maintain alignment and ensure project momentum. - Gain hands-on exposure to Resultant's AI-native delivery methodology and modern data platform practices. Requirements (Qualifications bullet list): - Rising Senior enrolled in a Bachelor's degree program in a relevant field of study, preferably graduating in the Spring of 2028. - Please note, this internship has a start date in June 2027. - Must live in the Indianapolis, IN area during the summer of 2027. - Expectation of 3 days in office per week at a minimum. - Must be legally authorized to work in the United States for any employer without sponsorship. Skills: combine Core Skills & Competencies and Technical & Analytical Skills. Core Skills list: - Exceptional written, verbal, and interpersonal communication skills. - Demonstrated ability to problem-solve, think creatively, and deliver results. - Strong organization, prioritization, and time-management abilities. - Ability to work independently and collaboratively within diverse, cross-functional teams. - Deep intellectual curiosity and a willingness to learn new tools, methods, and domains. - Comfortable interacting professionally with stakeholders including executives, managers, subject matter experts, and technical teams. - Experience working in deadline-driven environments. Technical & Analytical Skills list: - Understanding of relational database concepts, such as tables, keys, and simple normalization. - Ability to write basic SQL queries (SELECT, JOIN, WHERE, GROUP BY) to explore and analyze data. - Foundational knowledge of data structures and statistical concepts, including descriptive statistics and simple inferential ideas. - Exposure to ETL/ELT concepts, such as data cleaning, transformation, and preparing datasets for reporting or analysis. - Understanding of data modeling basics, including fact vs. dimension tables and star schema concepts. - Introductory experience with Python or R, especially for data manipulation or exploratory analysis. - Familiarity with data visualization tools (Power BI, Tableau, or similar) to build simple dashboards or charts. - Experience working with spreadsheets (Excel or Google Sheets) for analysis, formulas, pivot tables, and lightweight modeling. - Exposure to version control systems such as Git or GitHub, even at a basic level (e.g., cloning, committing, branching). - Exposure to project/collaboration tools such as Jira, Azure DevOps, Google Workspace, Office 365, etc. Benefits (Additional Information): "Resultant compensates well, rewarding performance that delivers positive outcomes for our clients and ensuring incentives are aligned to achieve our goals. Resultant leaders work hard, serving as a shining example of what it means to be a great Rezzer. They are servant leaders, helping their team to be successful in all possible ways. We have a great benefits package including unlimited vacation, significant 401k contributions, and several opportunities to develop yourself." We could also include the testimonials as a paragraph: maybe under Benefits or separate? Could add a paragraph after benefits: "What Our Team Members Say About Us…" with quotes. But that might be considered extra but not boilerplate. I'd include as a paragraph under Benefits or maybe separate section? There's no heading for testimonials; we could just add a

after benefits. Schedule: "Expectation of 3 days in office per week at a minimum. Must live in the Indianapolis, IN area during the summer of 2027. Internship start date in June 2027." We already included schedule info in Requirements; but we should not duplicate. The instruction: preserve ALL substantive information; we can keep it in Requirements and also in Schedule? Might duplicate. Better to keep schedule info only in Schedule section, and remove from Requirements. But Requirements includes start date and location and