Junior Business Intelligence Engineer

We need to output HTML fragment with sections for headings where content exists. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. No Job ID etc. Remove boilerplate. We need to extract substantive content. Let's parse the posting. First paragraph: "The Medpace Analytics and Business Intelligence team is growing rapidly..." This is about the role. Could be "About the role". We'll put that in

. Then "What’s in this for you?" bullet list: Work in a collaborative..., Build production-grade..., Develop your craft..., Gain business... That's benefits? Actually it's "What's in this for you?" could be considered Benefits or maybe "What you'll get". But we have Benefits section only if posting actually states them. This is more like benefits/perks. We'll treat as Benefits. Then "Responsibilities" heading appears explicitly. We'll put that as

Responsibilities

and list items. Then "What you bring to the table – and why we need you!" seems like Responsibilities or maybe Qualifications? Actually it's a list of duties. Could be considered Responsibilities as well. But we already have Responsibilities section; we could combine. However the posting has a separate "What you bring to the table – and why we need you!" which is essentially responsibilities. We'll merge into Responsibilities. Then "Qualifications" heading appears. We'll put that. Then "Preferred:" items under Qualifications? Actually after Qualifications there is a list of Preferred items. Those are also qualifications/skills. We'll include them under Qualifications (maybe as subpoints). Or we could have a Skills section. But we have Skills heading optional. The posting mentions proficiency in Python and SQL, understanding of relational databases, etc. Those are qualifications. We'll put them under Qualifications. Then "Medpace Overview" etc. That's company overview, not needed? Could be "About the role"? Already have. Might be extra but we can include as part of About the role? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to include Medpace Overview, Why Medpace?, Purpose-Driven Work, Collaborative Culture, Continuous Growth & Development, Other Employee Benefits, Cincinnati Headquarters Experience, What To Expect Next. However many of those are boilerplate? They are not cookie/navigation/legal/EEO etc. They are company description and benefits. We should keep them if they are substantive. However we must only include sections when posting has real, specific content for it. We have sections: About the role, Responsibilities, Qualifications, Benefits, maybe Skills, maybe Pay/Schedule if present. Pay and Schedule not mentioned. So we omit those. We also have "Other Employee Benefits" which is benefits. We already have Benefits section from "What's in this for you?" plus "Other Employee Benefits". We'll combine. We also have "Cincinnati Headquarters Experience" which is location/office details; could be part of Benefits or maybe not a standard heading. Could be included under Benefits or maybe as a separate section like "Work Environment". But we only have allowed headings list; we could put under Benefits or maybe under About the role? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not limited to those? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings. So we need to map content to those headings. Thus we need sections: About the role, Responsibilities, Qualifications, Benefits, Skills maybe. Pay and Schedule omitted. We need to decide what goes where. About the role: description of team, mission, what the intern will do high-level. Responsibilities: detailed duties. Qualifications: required and preferred qualifications. Skills: maybe specific technical skills like Python, SQL, Git, Azure, etc. Could be separate. Benefits: what's in this for you, other employee benefits, Cincinnati headquarters experience. We must not invent sections; we must include only if posting has real specific content. All these sections have content. Now we need to extract content verbatim (preserve all substantive information). Do not summarize away detail. So we need to copy sentences exactly? Probably we can keep them as is, but we need to format into

or

. We must not invent or summarize away detail. So we should keep the original wording. Let's extract. About the role: The first paragraph up to "What’s in this for you?" maybe. Original: "The Medpace Analytics and Business Intelligence team is growing rapidly and is focused on creating a trusted, data-driven foundation across the enterprise. We build scalable solutions leveraging data pipelines and reusable data products that ingest, transform, standardize, and serve data from operational systems for analytics, applications, and decision-making. As a Business Intelligence Intern, you will hold a highly visible role focused on modernizing data flows, improving data quality and reliability, and helping migrate fragmented data assets toward a governed single source of truth in partnership with leaders and technical teams across Medpace." That's about the role. We'll put that in

. Now Benefits: "What’s in this for you?" bullet list: - Work in a collaborative, fast paced, entrepreneurial, and innovative workplace. - Build production-grade data pipelines and trusted data products used by analysts, applications, leaders, and teams across the enterprise. - Develop your craft in Python and SQL by designing, testing, deploying, and monitoring maintainable workflows—not just one-off scripts or notebooks. - Gain business and data domain context by partnering across Medpace to consolidate fragmented sources into scalable, governed, and reusable data solutions. Also "Other Employee Benefits" section: - Competitive compensation programs that recognize and reward performance - Comprehensive health, wellness, retirement, and PTO benefits - Office based culture with occasional WFH that provides flexibility for eligible positions after training - Company-sponsored social events and intramural sports - Cincinnati Headquarters Experience: A modern corporate campus designed to support collaboration and productivity, Multiple on-site dining options in the heart of Madison Square, Free on-site parking, Convenient access to on-site 24-7 fitness and wellness facilities We could combine these into Benefits section as list items. Now Responsibilities: The heading "Responsibilities What’s involved?" then paragraph: "We are looking for a full-time Business Intelligence Engineer to add depth to our growing team by designing and building data pipelines, shared data models, and production-ready data products in Python and SQL. This role partners closely with data engineering, analytics, operations, finance, and other technical teams to understand source systems, define trusted business logic, and deliver reliable datasets that can serve as the enterprise system of record for reporting and downstream applications. An ideal candidate brings strong programming and data fundamentals and is excited to build reliable, maintainable data systems at scale. You enjoy tracing data from source to consumption, resolving ambiguity in definitions, designing reusable models, and implementing controls that make data accurate, discoverable, secure, and observable. You are eager to learn enterprise practices such as version control, automated testing, orchestration, deployment, lineage, monitoring, and operational ownership. We are looking for team members who are intensely curious, thrive on complex problems, and prefer durable platform solutions over short-term fixes." Then "What you bring to the table – and why we need you!" list: - Design, build, test, and maintain scalable batch and event-driven data pipelines using Python, SQL, and modern orchestration patterns. - Ingest and integrate data from enterprise applications, databases, files, APIs, and cloud platforms into standardized data layers. - Develop reusable, well-documented data products and dimensional or analytical models that support reporting, analytics, applications, and AI use cases. - Help migrate legacy and duplicative data assets toward a governed single source of truth with consistent definitions, ownership, and business rules. - Implement automated data quality checks, reconciliation controls, schema validation, lineage, logging, alerting, and performance monitoring. - Partner with business and technical stakeholders to document source-to-target mappings, translate requirements into data contracts, and define acceptance criteria. - Optimize pipeline performance, reliability, and cost while supporting secure access, privacy, and appropriate data governance. - Write clean, tested, documented code; participate in peer reviews; and contribute to Git-based development, CI/CD, and release practices. - Investigate pipeline failures and data discrepancies, perform root-cause analysis, and implement durable corrective actions. - Use modern engineering tools, including AI-assisted development tools where appropriate, to accelerate delivery while maintaining quality, security, and human review. We'll combine all these as responsibilities list. Now Qualifications: Heading "Qualifications" then list: - Pursuing a Bachelor's or Master's Degree in Computer Science, Data Engineering, Software Engineering, Information Systems, Business Analytics, or a related degree. - Proficiency in Python and SQL, with a solid foundation in data structures, debugging, modular design, and maintainable code. - Understanding of relational databases, data warehousing, data modeling, ETL/ELT patterns, and data quality concepts. - Familiarity with Git, automated testing, CI/CD, and software development lifecycle practices, or a strong willingness to learn. - Strong analytical and problem-solving skills, attention to detail, and clear written and verbal communication. - Preferred: experience with cloud data platforms and services, especially Microsoft Azure and/or Snowflake, including object storage, managed databases, compute, and role-based access. - Preferred: exposure to data engineering and orchestration tools such as Azure Data Factory, Fabric, Databricks, dbt, Airflow, or comparable technologies. - Preferred: familiarity with dimensional modeling, metadata, data catalogs, lineage, data contracts, observability, or master/reference data management. - Preferred: experience with APIs, containerization, Infrastructure as Code such as Bicep, ARM, or Terraform, and deploying data workloads in cloud environments. - Ability to work office-based in Cincinnati, OH. We could separate required vs preferred but we can keep as list. Now Skills: Could extract specific skills like Python, SQL, Git, Azure, Snowflake, Azure Data Factory, Fabric, Databricks, dbt, Airflow, APIs, containerization, IaC (Bicep, ARM, Terraform). But these are already in Qualifications. Might be redundant to have Skills section. However we have allowed Skills heading; we could put them there if we want. But we must not create thin sections; we already have Qualifications with details. Might be better to not create Skills section to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we can omit Skills. Thus we will have About the role, Responsibilities, Qualifications, Benefits. Now we need to output only HTML fragment, no /, no markdown fences. We'll produce:

About the role

...

Responsibilities

• ...
...

Qualifications

• ...
...

Benefits

• ...
...

Make sure to preserve all substantive information. Ensure we don't omit any details. Let's copy the exact sentences. About the role paragraph: exactly as above. Now Responsibilities: we need to include the paragraph before the list as part of responsibilities? The paragraph describes the role; we can include as a

before the list or incorporate into list items. The instruction: Use

for prose. So we can have a

for the introductory paragraph, then

for the list items. Thus:

Responsibilities

We are looking for a full-time Business Intelligence Engineer to add depth to our growing team by designing and building data pipelines, shared data models, and production-ready data products in Python and SQL. This role partners closely with data engineering, analytics, operations, finance, and other technical teams to understand source systems, define trusted business logic