Quest Analytics Internship Program - Summer 2027 in Kansas City

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes description of internship, opportunities, what you'll need, what you'll appreciate, etc. No explicit Pay, Schedule, Benefits. There's mention of "What You’ll Appreciate" but not benefits. No pay or schedule. So we should not create those sections. We need headings:

for each section. Use

• for lists. Use

  for prose. We need to preserve all substantive information, not invent. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions (Apply TODAY! careers.questanalytics.com). Also remove "About Quest Analytics" maybe considered boilerplate? It's about company but maybe considered substantive? It's description of company; could be part of About the role? The instruction: "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." The "About Quest Analytics" is company overview; could be part of About the role? Probably we can include a short paragraph about the company under About the role. We need sections: About the role (mission, what they do, internship program). Responsibilities (list of duties for each track? Could be under Responsibilities). Requirements (must live in KC metro area, able to work without visa sponsorship, pursuing degree, juniors preferred, prior internship a plus). Qualifications (education, technical skills). Skills (maybe combine technical and soft skills). Benefits (none). Pay (none). Schedule (none). So we will output About the role, Responsibilities, Requirements, Qualifications, Skills. We need to ensure we don't include filler like "commensurate with experience". Not present. Let's extract content. About the role: "Your Quest: Build the tools that improve healthcare access At Quest Analytics, headquartered in Overland Park, KS, our mission is to make healthcare more accessible for all Americans. We are a healthcare technology company focused on improving provider network management and helping healthcare organizations ensure their members have access to the care they need. Our technology, data, and expertise help health plans and healthcare organizations solve complex challenges involving provider data, network accuracy, adequacy, accessibility, and regulatory compliance. Our Summer Internship Program gives students the opportunity to work alongside experienced professionals on meaningful projects that contribute to real products, data solutions, and business outcomes. Interns aren't here just to observe, you'll have the opportunity to build, analyze, problem-solve, collaborate, and make an impact. We have an exciting opportunity for highly talented and motivated individuals to join us as part of our 2027 Internship Program. If you live in the Kansas City area and are ready to gain real-world experience, we’d love to meet you." That's substantive. Responsibilities: The three tracks description: Software Engineering, Data Engineering, Data Science. Could be listed as responsibilities. Also "Interns will be aligned to a team and project based on their skills, interests, academic background, and business needs." Also "AI & Emerging Technology" section about expectations. Could be part of responsibilities or requirements. We'll treat as responsibilities: list of duties for each track. We'll create

  • for each track with its description. Requirements: Must live in the Kansas City metro area; Able to work without visa sponsorship now and in the future; Education: Pursuing a Bachelor’s or Master’s degree in Computer Science, Software Engineering, Data Science, Data Analytics, Data Engineering, or related field; Juniors and above preferred (2+ years of degree experience); Prior internship experience in data engineering, analytics, or data science is a plus. Qualifications: Could be technical skills list? But we have separate Skills section. Qualifications maybe education and experience? But we already have education in Requirements. Could treat Qualifications as technical skills? However instruction: Use sections only when posting has real specific content. We have technical skills listed under "Technical Skills". That's specific. So we can put that under Skills. Qualifications maybe we can include "Education" and "Experience"? But we already have education in Requirements. Might combine. Better: Requirements: eligibility (location, visa, education level, year, prior internship). Qualifications: degree field, technical skills? Actually the posting separates "Education" under "What You'll Need". Then "Technical Skills". Then "Data Science Skills". Then "Soft Skills". So we could have Qualifications: Education field (Bachelor/Master in CS etc). Skills: Technical skills (programming, languages, databases, tools) plus Data Science skills plus Soft Skills. Let's do: - About the role (paragraph) - Responsibilities (list of three tracks) - Requirements (location, visa, education level, year, prior internship) - Qualifications (degree field) - Skills (technical, data science, soft) We'll not include Benefits, Pay, Schedule. Now craft HTML. We need to ensure no extra text outside HTML. Let's write:

    About the role

    Your Quest: Build the tools that improve healthcare access At Quest Analytics, headquartered in Overland Park, KS, our mission is to make healthcare more accessible for all Americans. We are a healthcare technology company focused on improving provider network management and helping healthcare organizations ensure their members have access to the care they need. Our technology, data, and expertise help health plans and healthcare organizations solve complex challenges involving provider data, network accuracy, adequacy, accessibility, and regulatory compliance. Our Summer Internship Program gives students the opportunity to work alongside experienced professionals on meaningful projects that contribute to real products, data solutions, and business outcomes. Interns aren't here just to observe, you'll have the opportunity to build, analyze, problem-solve, collaborate, and make an impact. We have an exciting opportunity for highly talented and motivated individuals to join us as part of our 2027 Internship Program. If you live in the Kansas City area and are ready to gain real-world experience, we’d love to meet you.

    Responsibilities

    • Software Engineering – Contribute to the full software development lifecycle by helping plan, design, develop, test, and deploy features and applications that support our healthcare technology solutions. Work alongside experienced engineers to write quality code, troubleshoot issues, and improve existing products and functionality. Gain hands-on experience using modern AI-assisted development tools, including Claude Code, to support coding, debugging, testing, documentation, and development workflows.
    • Data Engineering – Help build, maintain, and improve the data infrastructure that powers our products and analytics solutions. Work with large, complex datasets to support daily data operations, develop and optimize data ingestion pipelines, automate data processes, and monitor and troubleshoot data workflows to ensure reliable, high-quality data. Explore opportunities to use AI-assisted tools, including Claude Code, to accelerate development, automate workflows, and improve engineering efficiency.
    • Data Science – Apply statistics, machine learning, and AI to explore complex healthcare data and solve real-world business problems. Support data exploration, model development and evaluation, experimentation, and the communication of analytical findings. Work with emerging technologies, including generative AI, Large Language Models (LLMs), and AI-assisted development tools such as Claude Code, to explore new approaches to analytics and problem solving.
    • Interns will be aligned to a team and project based on their skills, interests, academic background, and business needs.

    Requirements

    • Must live in the Kansas City metro area
    • Able to work without visa sponsorship now and in the future
    • Pursuing a Bachelor’s or Master’s degree in Computer Science, Software Engineering, Data Science, Data Analytics, Data Engineering, or related field
    • Juniors and above preferred (2+ years of degree experience)
    • Prior internship experience in data engineering, analytics, or data science is a plus

    Qualifications

    • Degree in Computer Science, Software Engineering, Data Science, Data Analytics, Data Engineering, or a related field (Bachelor’s or Master’s)
    But that duplicates education. Maybe better to put education under Qualifications and not repeat in Requirements. However Requirements already includes education pursuit. Could adjust: Requirements: location, visa, year, prior internship. Qualifications: degree field. Let's do that. Thus: Requirements: - Must live in the Kansas City metro area - Able to work without visa sponsorship now and in the future - Juniors and above preferred (2+ years of degree experience) - Prior internship experience in data engineering, analytics, or data science is a plus Qualifications: - Pursuing a Bachelor’s or Master’s degree in Computer Science, Software Engineering, Data Science, Data Analytics, Data Engineering, or related field Now Skills: combine technical, data science, soft. We'll list bullet points. Technical Skills: - Programming: Python and SQL - Additional languages: C#/.NET preferred; Java or C++ also relevant - Databases: SQL Server and relational databases; exposure to NoSQL or MongoDB is a plus - Data & Development Tools: Databricks, Spark, Git - Analytics & Visualization: Excel, Power BI, PowerPoint - Frontend Development: HTML, CSS/Sass, React, and TypeScript are a plus for Software Engineering candidates - Software & Data Engineering Skills: Understanding of object-oriented programming concepts; C#/.NET experience preferred; Ability to troubleshoot and debug applications; Ability to write performant SQL queries against complex data models; Understanding of relational databases, data structures, and software development fundamentals; Exposure to data pipelines, ETL/ELT processes, distributed data processing, APIs, or cloud-based technologies is a plus; Familiarity with source control and collaborative development using Git Data Science Skills: - Statistics, probability, and exploratory data analysis - Machine learning fundamentals, including supervised and unsupervised learning - Classification and regression techniques - Model development, validation, and evaluation - Feature engineering and data preprocessing - Natural language processing (NLP) - Python data science libraries such as pandas, NumPy, scikit-learn, or similar tools - Data visualization and communicating analytical findings - Experimentation, hypothesis testing, and quantitative problem solving - Generative AI and Large Language Models (LLMs) are a plus - Exposure to prompt engineering, embeddings, vector search, retrieval-augmented generation (RAG), or other applied AI techniques is a plus Soft Skills: - Strong communication and collaboration skills - Ability to communicate data topics and results clearly - Self-motivated, proactive, and effective in a remote environment - Strong problem-solving mindset and team player attitude We could group under Skills heading with subheadings? But instruction: use

    for section headings only. No subheadings. Could just list all skills as bullet list, but that loses categorization. Could still list all bullet points; it's okay. We'll create a single

    • for each skill item, but that'll be long. Could group using separate
      under same heading? Probably okay to have multiple
      under same

      . We'll do that. Thus:

      Skills

      Technical Skills

      but we cannot use

      because only

      allowed for section headings. The instruction: use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

      for section headings. Could we use

      for subheadings? Might be okay but safer to avoid extra headings. We could just list all skills as bullet points without subheadings. That's fine. Thus:

      Skills

      • Programming: Python and SQL
      • Additional languages