Software Engineer, Intern

We need to output HTML fragment with sections: About the role? The posting includes mission statement, what you'll do, what we're looking for, what you can expect, past projects, why you'll love working here, hourly range, benefits. Also includes some metadata like graduation dates, availability windows, deadline to apply. Those are part of "What We're Looking For". We need to format using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. We need to map content to these headings appropriately. We have: - About the role: mission statement and description of team, learning opportunities, etc. Could be "About the role". Use

About the role

then

with that prose. - Responsibilities: "What You'll Do..." bullet list: Contribute to full-stack software projects by developing, testing, and maintaining features and services. Develop, release, and maintain services and/or infrastructure Lead individual project priorities, deadlines, and deliverables Contribute to code reviews and collaborate across teams to ensure quality and scalability. That's a list. - Requirements: maybe graduation date windows? Actually "What We're Looking For..." includes graduation date, pursuing degree, dedication, programming experience, availability windows, deadline to apply. Those are requirements/qualifications. Could split into Requirements (education, experience) and Qualifications (maybe skills). But we have headings: Requirements, Qualifications, Skills. We need to decide. We have programming languages: Java, Python, Kotlin, or Swift. That's Skills. We have graduation date windows: Graduating December 2027 - August 2028. That's a requirement (education timeline). Also "Pursuing a B.S. or M.S. degree in Computer Science or a related technical field (e.g. math, physics or data science)" is qualification/requirement. "Dedication to our mission..." maybe a soft requirement. Availability windows: "12 weeks of consecutive availability May 24, 2027 - August 13, 2027 June 14, 2027 - September 3, 2027". That's schedule? Actually schedule heading is for work schedule (like part-time/full-time). Could treat as Schedule. Deadline to apply: September 30, 2026. That's metadata, could be in a short p. Benefits: "Close support from your mentor and your team Working on features and projects that will have real impact for our learners and internal users A fun, mission-driven environment, where you’ll have lots of opportunities to grow as an engineer and make meaningful connections with your colleagues". That's more like What you can expect. Could be Benefits? But we also have a Benefits section later: "Language learning opportunities Catered in-house lunches, and breakfast and dinner options Company-wide Hackathon PTO and company holidays Frequent company-wide dinners, monthly celebrations, social clubs, and so much more! Connect with your recruiter on the benefits for interns at Duolingo!" That's benefits. Pay: "Hourly Range For This Internship Is $54—$56 USD". That's Pay. Schedule: maybe the 12 weeks availability windows. Past projects: could be under Responsibilities or a separate section? Not in headings list. Could be under Responsibilities as additional bullet? Or maybe under "What You Can Expect". But we have headings limited to those given; we can add other headings? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we can use others? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we should map content to those headings. Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Possibly not all needed if content missing. We have content for About the role (mission). Responsibilities (what you'll do). Requirements (education, graduation date, dedication). Qualifications maybe overlapping; but we could put degree pursuit under Requirements, and programming experience under Skills. Qualifications could be dedication to mission? Hmm. Better: Requirements: education (B.S./M.S. CS or related) and graduation window. Qualifications: dedication to mission, maybe also 12 weeks consecutive availability? Actually availability is schedule. Skills: programming languages Java, Python, Kotlin, Swift. Benefits: the list of perks (language learning opportunities, catered meals, hackathon, PTO, holidays, dinners, celebrations, social clubs). Pay: hourly range $54-$56. Schedule: 12 weeks consecutive availability windows (May 24-Aug 13 2027, June 14-Sept 3 2027). Also maybe mention deadline to apply? Could be placed in a short p under About the role or separate? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Deadline to apply is metadata, could be a short p. Also "Past projects include..." could be under Responsibilities or maybe under What You Can Expect. But we have no heading for that; we could include under Responsibilities as additional bullet points? Or maybe under About the role? Probably better to add under Responsibilities as extra bullet points (they are examples of past projects). However Responsibilities heading is for duties; past projects are not duties but examples. Could also go under "What You Can Expect" but we don't have that heading. Could we add a section "What You Can Expect"? The instruction says use h3 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. ...)". Likely they expect only those headings. Safer to stick to those. Thus we can put past projects under Responsibilities as a bullet list? Might be odd but acceptable. Let's craft:

About the role

Our mission at Duolingo is to develop the best education in the world and make it universally available. It’s a big mission, and that’s where you come in! At Duolingo, you’ll join a team that cares about educating our users, experimenting with big ideas, making fact-based decisions, and finding innovative solutions to complex problems. You’ll have limitless learning opportunities and daily collaborations with world-class minds — while doing work that’s both meaningful and fun. Join our life-changing mission to develop education for our half a billion (and growing!) learners around the world. Read our blog to learn more. 🧠

Responsibilities

• Contribute to full-stack software projects by developing, testing, and maintaining features and services.
• Develop, release, and maintain services and/or infrastructure
• Lead individual project priorities, deadlines, and deliverables
• Contribute to code reviews and collaborate across teams to ensure quality and scalability
• Past projects include: Developing a GPT-4 chat interface for one of our internal tools to streamline content creation; Integrating our A/B testing framework with our observability stack to flag experiments that introduce errors; Spanish audio lessons to improve listening comprehension; Crafting new lessons to teach Coordinates in our Math course; Porting large features to new platforms (iOS, Android, web); Dashboards and tooling for site reliability insights; Crafting new microservices from scratch

Requirements

• Pursuing a B.S. or M.S. degree in Computer Science or a related technical field (e.g. math, physics or data science)
• Graduating December 2027 - August 2028
• Dedication to our mission of universally available education

Qualifications

None specific beyond requirements; but we could leave empty? Better not to create empty section. Maybe we skip Qualifications if no distinct content. But we have dedication already in Requirements. Could we put "12 weeks of consecutive availability" under Qualifications? That's more schedule. Hmm. Alternatively we could treat Qualifications as "Programming experience in one or more of the following languages: Java, Python, Kotlin, or Swift." but that's Skills. Let's assign Skills to languages, Qualifications to dedication? Already used dedication. Could put "12 weeks of consecutive availability" under Qualifications? Not ideal. Maybe we can combine Requirements and Qualifications: Requirements: education and graduation; Qualifications: dedication and availability; Skills: languages. Let's do that. Thus:

Requirements

• Pursuing a B.S. or M.S. degree in Computer Science or a related technical field (e.g. math, physics or data science)
• Graduating December 2027 - August 2028

Qualifications

• Dedication to our mission of universally available education
• 12 weeks of consecutive availability (see Schedule for specific windows)

Skills

• Programming experience in one or more of the following languages: Java, Python, Kotlin, or Swift

Benefits

• Close support from your mentor and your team
• Working on features and projects that will have real impact for our learners and internal users
• A fun, mission-driven environment, where you’ll have lots of opportunities to grow as an engineer and make meaningful connections with your colleagues
• Language learning opportunities
• Catered in-house lunches, and breakfast and dinner options
• Company-wide Hackathon
• PTO and company holidays
• Frequent company-wide dinners, monthly celebrations, social clubs, and so much more!

Pay

Hourly Range For This Internship Is $54—$56 USD

Schedule

12 weeks of consecutive availability: May 24, 2027 - August 13, 2027 or June 14, 2027 - September 3, 2027

We also need to include deadline to apply as minor metadata: maybe a short p after Schedule or before? Could add a

Deadline to apply: September 30, 2026

after Schedule or as part of About the role? Probably after Schedule as a short p. Make sure not to include any boilerplate like EEO, fraud warning, accommodations, etc. Now output only HTML fragment. Check that we didn't repeat job title as heading. Good. Check that we didn't include any placeholder like "commensurate with experience". Not present. Check that we didn't invent content. All content derived from posting. Check that we didn't miss any substantive info: mission, responsibilities, past projects, requirements (degree, graduation, dedication), qualifications (dedication, availability), skills (languages), benefits (list), pay, schedule windows, deadline to apply. Also we included "Close support from your mentor..." etc under benefits; that was originally under "What You Can Expect". It's fine. We also included "Working on features and projects that will have real impact for our learners and internal users" etc under benefits; okay. Now produce final