Software Engineer, Intern (Summer 2027) - US

We need to output HTML fragment with sections: About the team? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real specific content. We need to preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. We need to parse the posting. Let's extract sections: - About The Team: description of DoorDash building logistics engine, looking for experienced engineers to join fast-growing engineering team to help develop 24x7 global infrastructure system that powers DoorDash's three-sided marketplace. - About The Role: description of product engineers implement and operate technological solutions to improve experiences of merchants, dashers, consumers. Also mention interns essential, 12-week Software Engineer internship, interns immersed, develop maintain ship products, directly impact business, collaborate with team to solve real problems. Applicants must be authorized to work in US; F-1 students eligible if using CPT; DoorDash does not support J-1 visas. The 2027 internship program will be hosted in person at a DoorDash office in one of the following locations; New York, San Francisco, Sunnyvale, Los Angeles and Seattle. You will have opportunity to select preferred location(s) during application process. - You’re Excited About This Opportunity Because You Will…: bullet list of items: Develop, maintain and ship technical elements with support of mentor, manager, team members; Act on feedback, coaching, mentorship; Actively learn about elements to which you contribute; Make a direct impact on our business by collaborating with your team to solve problems for our customers; Participate in intern programming - Leadership Speaker series, social events – virtually and in-person; Present your summer learnings during a final presentation at the end of the internship; You are excited about an in person summer work experience. - Here Are Some Examples Of Past Intern Projects: Collection of Summer 2024 Intern Projects Summer 2024 Intern Projects Cont. (maybe just mention that there are examples; but no specific projects listed). This may be considered placeholder? It says "Collection of Summer 2024 Intern Projects Summer 2024 Intern Projects Cont." No actual project details. Might be considered filler. Probably we should omit this section because no specific content. - We’re Excited About You Because…: bullet list: pursuing B.S. or M.S. Degree in Computer Science or equivalent, have no more than 2 years of full-time work experience, graduating between Fall 2027 to Summer 2028; available for May or June 2027 start date (internships only hosted during Summer); experience working with databases (e.g., AWS, SQL, etc.); solid understanding of algorithms and data structures; proficient experience working with at least 1 object-oriented programming language (e.g., Python, Java, Kotlin, etc.); experience writing clean code, working with version control, and doing unit testing. - Preferred But Not Required: bullet list: at least 1 previous Software Engineering internship or equivalent relevant experience; curiosity about and experience using AI-powered tools to support software development, problem solving, and learning, with understanding of how to evaluate outputs and use these tools responsibly; ability to analyze and improve efficiency, scalability, and stability of various systems; excited to develop, release and run large-scale web applications; experience with solutions for systems monitoring, live deployments, and continuous integration; experience with real-time technology problems; experience working with service-oriented architecture, writing APIs, and designing systems; participation in project or research-based technical work, hackathons, technical conferences/organization, on-campus student organization leadership, technical teaching assistant roles, relevant extracurricular activities, or other technical experience. - Compensation: includes paragraph about compensation determined based on factors, base salary localized, DoorDash offers comprehensive benefits package to all regular employees, includes 401(k) plan with employer matching, 16 weeks of paid parental leave, wellness benefits, commuter benefits match, paid time off and paid sick leave in compliance with applicable laws (e.g. Colorado Healthy Families and Workplaces Act). DoorDash also offers medical, dental, and vision benefits, 11 paid holidays, disability and basic life insurance, family-forming assistance, and a mental health program, among others. To learn more about our benefits, visit our careers page here. See Below For Paid Time Off Details For salaried roles: flexible paid time off/vacation, plus 80 hours of paid sick time per year. For hourly roles: vacation accrued at about 1 hour for every 25.97 hours worked (e.g. about 6.7 hours/month if working 40 hours/week; about 3.4 hours/month if working 20 hours/week), and paid sick time accrued at 1 hour for every 30 hours worked (e.g. about 5.8 hours/month if working 40 hours/week; about 2.9 hours/month if working 20 hours/week). The national base pay range for this position within the United States, including Illinois and Colorado. $107,400—$158,000 USD. - About DoorDash: mission statement etc. Might be considered boilerplate? It's about company mission, but could be considered substantive? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. About DoorDash is not exactly boilerplate but could be considered generic company description. Might be okay to keep? The instruction says "Prefer a few substantive sections over many thin ones." We could keep About DoorDash as a section maybe "About DoorDash". However the allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list About DoorDash or About the Team. But they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. We could still use other headings like About the Team, About DoorDash, etc. But we need to consider if they want only those headings? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we can use those headings for sections; but we could also use other meaningful headings. However they also say "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 use headings for sections like About the Team, About the Role, Responsibilities, etc. We need to decide which sections to include. The posting includes: - About The Team - About The Role - You’re Excited About This Opportunity Because You Will… (maybe could be Responsibilities? Actually it's more like what you will do; could be Responsibilities) - Here Are Some Examples Of Past Intern Projects (maybe not needed) - We’re Excited About You Because… (could be Requirements/Qualifications) - Preferred But Not Required (could be Preferred Qualifications) - Compensation (Pay and Benefits) - About DoorDash (maybe not needed) - Also there is a line about "Applicants must be authorized to work in the U.S. to be considered for this position. F-1 students are eligible if they are using Curricular Practical Training (CPT). DoorDash does not support students on J-1 visas at this time." This could be part of Requirements. We need to preserve all substantive info. So we need to include details about work authorization, location options, start date, etc. We need to avoid boilerplate like "Our Commitment to Diversity and Inclusion", "Statement of Non-Discrimination", "Pursuant to the San Francisco Fair Chance Ordinance", "Notice to Applicants for Jobs Located in NYC or Remote Jobs Associated With Office in NYC Only", "Beware of recruitment scams". Those should be removed. Also remove duplicated lines. Thus final HTML should contain sections: About the Team, About the Role, Responsibilities (maybe from "You’re Excited About This Opportunity Because You Will…"), Requirements (maybe from "We’re Excited About You Because…" plus work auth and location), Preferred Qualifications (from "Preferred But Not Required"), Benefits, Pay (maybe combine Benefits and Pay? Could separate Benefits and Pay sections). The instruction says use headings like Benefits, Pay, Schedule. We have Pay range and benefits details. So we can have a Benefits section listing benefits, and a Pay section with the salary range. Schedule: Not mentioned (internship is 12-week summer, but schedule not specified). Could we infer schedule? The posting mentions "12-week Software Engineer internship", "Internships are only hosted during the Summer", "May or June 2027 start date". Not specific schedule like full-time. Might be considered schedule info? Could add a Schedule section with "12-week full-time summer internship". But we need to avoid placeholder text like "not specified". The posting does mention it's a 12-week internship, start dates May or June 2027, hosted in person. That's substantive. So we can include a Schedule section with that info. We need to ensure we don't create sections with filler like "commensurate with experience". We have actual specifics. Now we need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

About the Team

DoorDash is building the world’s most reliable on-demand logistics engine for delivery. We’re looking for experienced engineers to join our fast-growing engineering team to help us develop a 24x7 global infrastructure system that powers DoorDash’s three-sided marketplace of consumers, merchants, and dashers.

About the Role

At DoorDash, our product engineers implement and operate technological solutions to improve the experiences of our merchants, dashers, and consumers. From creating beautiful, user-friendly flows to crafting scalable backend architectures, we strive to deliver reliable, performant technology that delights our customers. We believe interns are essential to our mission of attracting and retaining top talent. During our 12-week Software Engineer internship, interns are completely immersed in their teams and will have the opportunity to develop, maintain, and ship products. As an intern, you will directly impact our business by collaborating with your team to solve real problems for our customers.

Responsibilities

• Develop, maintain and ship technical elements with the support of your mentor, manager, and team members
• Act on feedback, coaching, and mentorship from your mentor and team members
• Actively learn about the elements to which you contribute
• Make a direct impact on our business by collaborating with your team to solve problems for our customers
• Participate in intern programming - Leadership Speaker series, social events – virtually and in-person
• Present your summer learnings during a final presentation at the end of the internship
• You are excited about an in‑person summer work experience

Requirements

• Pursuing a B.S. or M.S. Degree in Computer Science or equivalent
• No more than 2 years of full‑time work experience
• Graduating between Fall 2027 and Summer 2028
• Available for a May or June 2027 start date (internships are hosted only during the Summer)
• Experience working with databases (e.g., AWS, SQL, etc.)