Summer 2027 Clinical Trials Feasibility & Proposals Internship

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: "Our corporate activities are growing rapidly, and we are currently seeking an office-based Intern to join our Feasibility and Proposals team for the Summer of 2027." That's about the role. Then responsibilities list. Then qualifications list. Then "Medpace Overview" maybe about company, not required. Then "Why Medpace?" includes purpose-driven work, collaborative culture, continuous growth & development, other employee benefits, Cincinnati headquarters experience. Those could be Benefits? They talk about benefits: competitive compensation, health, wellness, retirement, PTO, office based culture with occasional WFH, company-sponsored social events, etc. Also Cincinnati headquarters experience: modern campus, dining, parking, fitness. Those are benefits/perks. There's no explicit Pay or Schedule. So we should not create Pay or Schedule sections. We should include sections: About the role, Responsibilities? Actually "About the role" heading for intro paragraph. Then Responsibilities. Then Qualifications (maybe includes education, skills). Could also have Skills separate but we can combine. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We need to decide which sections to include based on content. We have responsibilities content. Qualifications content includes education, skills, abilities. Could split into Qualifications and Skills but we can keep Qualifications covering both. Benefits content includes compensation, health, wellness, retirement, PTO, WFH, social events, campus amenities. So we can have Benefits section. No Pay or Schedule. Also maybe "About the role" includes the intro paragraph. Also "Medpace Overview" maybe not needed as it's company description; could be omitted as not required heading. But we could include as "About the company" but not in list. Better to follow instruction: only include sections when posting has real specific content for it. The posting includes Medpace Overview, Why Medpace?, etc. Those are not exactly the headings list but could be considered Benefits or About the company. However we should not invent headings not in the list. The list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: About the role -> intro paragraph. Responsibilities -> list. Qualifications -> education and requirements. Skills -> maybe we could separate skills like MS Office, communication, language. But we already have those in qualifications. Could still create Skills section with those specifics. Benefits -> compensation, health, wellness, retirement, PTO, WFH, social events, campus amenities. No Pay or Schedule. We must not repeat job title as heading. No Job ID. Remove boilerplate like application instructions (the "What To Expect Next" part). Also remove EEO etc. There's none. We must preserve all substantive information. So we need to include all details from responsibilities, qualifications, Medpace overview, why Medpace, benefits, Cincinnati headquarters experience. Ensure we don't lose any. Let's extract: Intro: "Our corporate activities are growing rapidly, and we are currently seeking an office-based Intern to join our Feasibility and Proposals team for the Summer of 2027." Responsibilities (as bullet points): - Become familiar with ICH-GCP guidelines, industry regulations, and Medpace systems; - Provide day to day departmental support activities as necessary; Examples include site outreach, visual development in PowerPoint, and proposal finalization and delivery - Coordinate and provide summary for departmental meetings/conference calls as and when required; - Maintain database/spreadsheets and compile reports as necessary to facilitate tracking/documentation of departmental activities; - Conduct quality control reviews of departmental documents as necessary; - Support other departments on ad hoc projects; and - Perform other administrative tasks as needed. Qualifications: - High school diploma or equivalent; - Bachelor's degree in progress, in a Life Sciences field; - Knowledge of MS Word, Excel, and PowerPoint; - Knowledge and organizational skills to perform day-to-day departmental support activities (i.e., shipping, archiving, filing, departmental meeting minutes); - Demonstrated ability to maintain applicable database systems; - Demonstrated ability to adequately communicate (written and oral) with other employees as necessary; - Local language skills and an excellent level of English. Medpace Overview (company description): - Medpace is a full-service clinical contract research organization (CRO) providing phase l-lV clinical development services to the biotechnology, pharmaceutical, and medical device industries. - Mission: accelerate the global development of safe and effective medical therapeutics through the advancement of clinical research. - Leverage in-country regulatory and therapeutic expertise across all major therapeutic areas including oncology, cardiology, metabolic, endocrinology, central nervous system, and anti-viral and anti-infective. - Headquartered in Cincinnati, Ohio, employ more than 6,500 people across 40+ countries. Why Medpace? (includes purpose-driven work, collaborative culture, continuous growth & development, other employee benefits, Cincinnati headquarters experience). We'll parse: Purpose-Driven Work: - Work alongside physicians, scientists, and industry-leading experts committed to advancing the global development of medical therapeutics through clinical research excellence Collaborative Culture: - Contribute to an interactive team environment that empowers decision making, creative thinking, and continuous learning through open communication and mutual trust. - Leadership throughout Medpace is both accessible and approachable Continuous Growth & Development: - Office based environment with on-site mentors - Defined career paths with clear advancement opportunities - Industry renowned onboarding and training programs designed to accelerate professional development - Ongoing training and continuous learning opportunities throughout your career - An environment that encourages employees to influence change, contribute ideas, and grow quickly Other Employee Benefits: - 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 should not include "What To Expect Next" (application instructions). Also remove any duplicated lines. Now produce HTML:

About the role

Our corporate activities are growing rapidly, and we are currently seeking an office-based Intern to join our Feasibility and Proposals team for the Summer of 2027.

Responsibilities

• Become familiar with ICH-GCP guidelines, industry regulations, and Medpace systems;
• Provide day to day departmental support activities as necessary; Examples include site outreach, visual development in PowerPoint, and proposal finalization and delivery
• Coordinate and provide summary for departmental meetings/conference calls as and when required;
• Maintain database/spreadsheets and compile reports as necessary to facilitate tracking/documentation of departmental activities;
• Conduct quality control reviews of departmental documents as necessary;
• Support other departments on ad hoc projects; and
• Perform other administrative tasks as needed.

Qualifications

• High school diploma or equivalent;
• Bachelor's degree in progress, in a Life Sciences field;
• Knowledge of MS Word, Excel, and PowerPoint;
• Knowledge and organizational skills to perform day-to-day departmental support activities (i.e., shipping, archiving, filing, departmental meeting minutes);
• Demonstrated ability to maintain applicable database systems;
• Demonstrated ability to adequately communicate (written and oral) with other employees as necessary;
• Local language skills and an excellent level of English.

We could also add Skills section but we already covered. Might add Skills separate: but we have knowledge of MS Office etc. Could still add Skills but risk duplication. The instruction: prefer a few substantive sections over many thin ones. So we can keep Qualifications covering skills.

Benefits

• 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
• 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 might also include continuous growth & development as part of Benefits? It's more about development. Could be part of Benefits or maybe a separate section like "Development Opportunities". But not in list. Could incorporate into Benefits as bullet points. However we have not included those points: on-site mentors, defined career paths, renowned onboarding, ongoing training, environment encourages influence change. Those are substantive. Should we include them? They are under "Continuous Growth & Development". They are benefits of working there. Could be placed under Benefits as well. The instruction: include a section ONLY when posting has real specific content for it. We have content for growth & development. Could add a section "Development Opportunities" but not in allowed headings. Could we treat it as part of Benefits? Benefits heading is for compensation, health, etc. But we could still include those under Benefits as they are benefits. However the list of allowed headings includes Benefits, not Development. So we can put them under Benefits. That would be okay. Thus Benefits bullets: add: - Office based environment with on-site mentors - Defined career paths with clear advancement opportunities - Industry renowned onboarding and training programs designed to accelerate professional development - Ongoing training and continuous learning opportunities throughout your career - An environment that encourages employees to influence change, contribute ideas, and grow quickly We should also include Purpose-Driven Work and Collaborative Culture maybe under Benefits or maybe under a separate section like "Culture". Not in list. Could incorporate into Benefits as well, but might be stretching. However we have to preserve all substantive information. If we omit them, we lose info. So we need to include them somewhere. Since only allowed headings are those, we could put them under Benefits as they are part of employee experience. Or we could create a section "About the company" but not allowed. The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The e.g. suggests those are examples, but we should likely stick to those. It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the allowed headings. So we should not create other headings. So we must fit all content under those headings. Thus we need to distribute all content among About the role, Responsibilities, Qualifications, Skills, Benefits. Possibly Requirements (maybe same as Qualifications). We can use Requirements for qualifications like education, etc. And Skills for specific abilities. But we can also just use Qualifications and Skills. Let's decide: - About the role: intro paragraph. - Responsibilities: list. - Requirements: education (high school diploma, bachelor's in progress life sciences). - Qualifications: maybe knowledge of MS Office, organizational skills, database maintenance, communication, language skills. - Skills: maybe same as