Data Science Internship, Summer 2027

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. Must not repeat job title. No Job ID. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Content: - About Us: description of company. Not needed as a heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include sections only if posting has real specific content for them. The posting includes "About the Role:" which is a heading. So we can have

About the role

with content from that section. - Responsibilities: The posting includes "What To Expect From The Internship" with bullet-like paragraphs. Also "As a Data Science intern, your main responsibility is to learn, but you'll learn it by doing real work." Also bullet points for first week, first month, end of internship. So we can put responsibilities under

Responsibilities

. - Requirements: The posting includes "What You’ll Bring:" with bullet list of qualifications. So we can put that under

Requirements

or maybe Qualifications. The instruction says we can have Requirements and Qualifications separate. We need to decide based on content. The "What You’ll Bring" includes enrollment, knowledge, experience, proficiency, bonus items. That could be Requirements. Could also split into Requirements (mandatory) and Qualifications (bonus). But we can just put all under Requirements. However we also have a separate "What We’ll Bring for the Internship:" which is benefits. And "What We’ll Bring to Full-time Team Members:" which is benefits for full-time (not internship). The instruction: include Benefits section only if posting actually states them. There is "What We’ll Bring for the Internship:" which lists hourly compensation, espresso bar, etc. That's benefits for internship. So we can have Benefits section. - Pay: The posting includes "Hourly compensation" under What We’ll Bring for the Internship. No specific amount. It says "Hourly compensation" but no number. That's vague; we should not include Pay section if it's just "Hourly compensation" without specifics? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Hourly compensation" but no amount. Is that considered stating? It's a mention but not specific. The instruction says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Hourly compensation" without amount is similar to not specified. So we should not create a Pay section. - Schedule: The posting includes "This is not a remote opportunity; it is 100% onsite". Also mentions flexibility for personal needs, remote weeks around major holidays. So schedule info exists: 100% onsite, flexible for personal needs, remote weeks around major holidays. That's specific enough. So we can include Schedule section. - Skills: The posting includes knowledge of machine learning, SQL, Python, etc. Could be under Skills. But we already have Requirements covering those. Could split: Requirements for enrollment, Qualifications for experience, Skills for technical. However instruction: prefer a few substantive sections over many thin ones. So maybe combine Requirements and Skills into one section? But we have headings list; we can choose to include only those with substantive content. We could include Requirements (enrollment, etc.) and Skills (technical). But that may be thin. Let's see content: "What You’ll Bring:" includes enrollment, knowledge of machine learning and statistical research, experience using SQL, proficient in programming, analysis, visualization using OOP languages (Python preferred). Bonus: enrolled in a Master’s Degree or advanced technical degree, previous work experience, experience with implementing ML solutions to production, understanding of modern scalable data science platforms. That's a mix of requirements and qualifications. Could treat as Requirements. Skills could be separate: maybe list of technical skills: Python (scikit-learn, pandas, NumPy, statsmodels), SQL, Redshift. That's mentioned in About the Role. So we could have Skills section with those. Thus we can have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule. Check each for substantive content. About the role: we have paragraph describing data team, role, tasks. Good. Responsibilities: we have bullet points for first week, first month, end of internship, plus main responsibility. Requirements: we have enrollment, knowledge, experience, proficiency, bonus items. Skills: we have technical stack: Python (scikit-learn, pandas, NumPy, statsmodels), SQL, Redshift. Benefits: we have hourly compensation (maybe skip), espresso bar, full kitchen, weekly catered lunches, snacks, beverages, everyday lunch essentials, one-of-a-kind office with comfortable work/lounge spaces and pleasant riverfront setting, opportunity to gain experience at fastest-growing financial startup, cross-functional work. Also maybe "What We’ll Bring to Full-time Team Members:" is not for internship, but could be considered benefits? Probably not for internship. We'll stick to internship benefits. Schedule: 100% onsite, flexibility for personal needs (sick children, urgent errands), coordinate official remote weeks around major holidays. Now we need to output HTML fragment only, no markdown fences. Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we must keep details like "Perpay is a certified B Corp..."? That's About Us, not required headings. Should we include About Us? Not in headings list, but we could include as a

  before sections? 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 (e.g. those). It might be okay to include other headings like

  About Us

  but they didn't list it. Safer to only include those headings if they have content. The About Us content is substantive but not under those headings. Could we wrap it in a

  without heading? Probably yes. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but to be safe we could just put About Us as a

  before the sections. However they said "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." So we can have other headings if needed, but they gave examples. I'd include About Us as a

  (no heading) because it's not one of the listed headings but it's substantive. However they might expect only those headings. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies those are the allowed headings. So we should not add other headings like About Us. Instead we could incorporate About Us content into a

  under maybe no heading? But that would be stray text without heading. Might be okay. However they said "Output ONLY the HTML fragment — no /, no markdown code fences." So we can output a series of

  and

  /

  . If we include About Us as a

  without heading, it's still HTML fragment. Probably acceptable. But to be safe, we could treat About Us as a

  About Us

  even though not in list. The instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests examples, not exhaustive list. So we can add About Us heading. I'll include it. Now we need to ensure we don't include boilerplate like EEO, equal opportunity, scam warning, etc. Remove those lines. Also remove duplicated lines, navigation, cookie, legal, etc. Now let's extract content. About Us paragraph: "Perpay is a certified B Corp and Philadelphia’s most impactful growth-stage startup. We are driven by a mission to significantly improve the financial stability of everyday Americans. For the past decade, we have established strong product-market fit and a profitable, efficient operating model across a suite of products, positioning Perpay as the premier financial partner for consumers with subprime credit. With over 500,000 customers who have utilized more than $1 billion in spending power, we are at a pivotal moment. We are scaling our operations, building new offerings, and deepening our impact. We are looking for teammates eager to join us on this journey. Our venture partners include First Round Capital and L Catterton. Products we’ve built to make an impact: Perpay Marketplace: Combines interest-free payments and modern e-commerce to reduce cost of ownership and promote healthy repayment behavior. Perpay+: Leverages Marketplace repayment history to help members monitor and build credit with all 3 credit bureaus. Perpay Credit Card: Expands access to the flexibility and benefits of a World Mastercard by removing common barriers like high security deposits and low approval odds. Our team thrives on in-person collaboration, operating from our unique center-city Philadelphia office. This comfortable "home away from home" space offers river views and fosters rapid product development, strong relationships, and career growth. The energy from achieving big wins is palpable here. While we primarily work in the office, we offer sensible flexibility for personal needs, such as sick children or urgent errands, and coordinate official remote weeks around major holidays. If you are passionate about a meaningful mission, collaboration, equity, and generous perks, Perpay is the best place to be in Philadelphia right now." We'll keep that as a

  under

  About Us

  . About the Role: "Our data team is organized across three groups: Data Engineering, Data Science, and Strategic Analytics. Data Science owns the modeling work that drives Perpay's most consequential decisions: credit decisioning, loss forecasting, marketing-mix attribution, product experimentation, and the ML systems that sit in front of our customers in real time. As a Data Science intern, your main responsibility is to learn, but you'll learn it by doing real work. During the summer of 2027, you'll leverage our expansive data sets to research, identify, and build features to train models and drive real impact. Applying your knowledge of modeling, statistical methodologies, and exploratory data analysis, you'll partner with stakeholders across Engineering, Risk, Marketing, Merchandising, and Finance and communicate solutions designed to drive company growth, getting hands-on with our stack, which includes Python (scikit-learn, pandas, NumPy, statsmodels), SQL, and Redshift. Our greatest strength is our people and we’d love for you to be one of them!" We'll put that as

  under

  About the role

  . Responsibilities: We have "What To Expect From The Internship" with bullet-like paragraphs. Also the main responsibility sentence. Let's capture: - Main responsibility: learn by doing real work. - During summer 2027: leverage data sets to research, identify, build features to train models and drive real impact. - Apply knowledge of modeling, statistical methodologies, exploratory data analysis; partner with stakeholders across Engineering, Risk, Marketing, Merchandising, Finance; communicate solutions designed to drive company growth; get hands-on with stack. - Within