Software Engineering Intern
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include any of those headings if content exists. We have content for About the role. We have Requirements: "About You:" includes student, coding languages, willingness, etc. Also "Requirements" appears after "you're in Requirements". Actually the text: "If you have an affinity for card games, you're in Requirements About the Role:" weird formatting. Likely "Requirements" heading then list: You're a Computer Science or Software Engineering student who has coded in Java, JavaScript/TypeScript, HTML5, CSS, MySQL, and React; You are willing to work hard, be a team player, and want to learn and grow; You like to have fun, play games, and eat snacks. If you have an affinity for card games, you're in. So we can extract those as requirements.
Qualifications: Not separate; maybe same as requirements. Could treat qualifications as same? But we need to only include if real specific content. There's no explicit "Qualifications" heading. Could skip.
Skills: Could be derived from the coding languages list: Java, JavaScript/TypeScript, HTML5, CSS, MySQL, React. Could be a Skills section.
Benefits: There's a Benefits section with bullet list: 1 on 1 Mentorship, 401(k) Match, Fizzy Fridays, Catered Recognition Lunches, Unlimited Coffee and Espresso, Ping Pong Table, Lincoln's Best Places to Work Winner.
Pay: The posting says "Our internships are paid and our wages are competitive." That's not specific numbers. According to rule: never emit Pay section unless posting actually states them (specific). It says "competitive" but not a number. That's vague; we should not include Pay section because it's not specific. Similarly Schedule: The posting gives dates: May 17th, 2027 - August 13th 2027. That's schedule. So we can include Schedule section with that info.
We must not include placeholder like "commensurate with experience". So we skip Pay.
We need to output HTML fragment only, no /. Use for headings, - for lists,
for prose.
We need to preserve all substantive information. Let's gather:
About the role: list of duties.
Requirements: list of student background, coding languages, willingness, fun, card games.
Skills: list of languages: Java, JavaScript/TypeScript, HTML5, CSS, MySQL, React.
Benefits: list as given.
Schedule: May 17th, 2027 - August 13th 2027 (maybe also mention paid internships run from those dates). Could also mention that it's paid internship.
We could also include a short paragraph about the internship being paid and competitive wages? But we decided not to include Pay section. Could include a prose paragraph under About the role or elsewhere about paid nature. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the statement about paid internships and competitive wages somewhere. Could be placed in a
under a generic section? But we only have defined headings; we could add a
under About the role or maybe under a separate section like "Overview". However we must only use the allowed headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those. We could put the paid info in a
under About the role or Benefits? Probably under About the role as a prose before the list.
Similarly, we have info about the internship being paid and wages competitive. We'll include that as a
under About the role.
Also we have info about "Our internships are paid and our wages are competitive. We'll treat you like a regular employee and expect you to act like one. We think the best learning opportunities come through experience and mentorship, so you'll be provided with both. Learn, grow, explore your talents, and be taught some valuable skills. We're a small company and we're looking for interns that want an opportunity to make major contributions to our small teams." That's more about expectations; could be placed under About the role as prose.
We need to avoid duplication. Let's structure:
About the role
Our paid internships run from May 17th, 2027 - August 13th 2027 and offer competitive wages. You'll be treated like a regular employee, gain experience and mentorship, and have the opportunity to make major contributions to our small teams.
- Code high-volume and scalable software
- Create web applications and back-end services using a variety of coding languages
- Investigate and resolve software issues/bugs
- Partner closely with cross functional teams in design, product, and other business functions
Requirements
- Computer Science or Software Engineering student
- Experience coding in Java, JavaScript/TypeScript, HTML5, CSS, MySQL, and React
- Willing to work hard, be a team player, and want to learn and grow
- Enjoys having fun, playing games, and eating snacks
- Affinity for card games is a plus
Skills
- Java
- JavaScript/TypeScript
- HTML5
- CSS
- MySQL
- React
Benefits
- 1 on 1 Mentorship – paired with a mentor from day one for real‑world projects, feedback, and career development
- 401(k) Match – company contributes to your retirement savings
- Fizzy Fridays – games, snacks, and fizzy beverages at 3:30 PM each Friday
- Catered Recognition Lunches – free monthly lunch and recognition
- Unlimited Coffee and Espresso – cappuccinos, lattes, black coffee, pour‑over options
- Ping Pong Table – friendly competition breaks
- for lists,
for prose. We need to preserve all substantive information. Let's gather: About the role: list of duties. Requirements: list of student background, coding languages, willingness, fun, card games. Skills: list of languages: Java, JavaScript/TypeScript, HTML5, CSS, MySQL, React. Benefits: list as given. Schedule: May 17th, 2027 - August 13th 2027 (maybe also mention paid internships run from those dates). Could also mention that it's paid internship. We could also include a short paragraph about the internship being paid and competitive wages? But we decided not to include Pay section. Could include a prose paragraph under About the role or elsewhere about paid nature. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the statement about paid internships and competitive wages somewhere. Could be placed in a
under a generic section? But we only have defined headings; we could add a
under About the role or maybe under a separate section like "Overview". However we must only use the allowed headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those. We could put the paid info in a
under About the role or Benefits? Probably under About the role as a prose before the list. Similarly, we have info about the internship being paid and wages competitive. We'll include that as a
under About the role. Also we have info about "Our internships are paid and our wages are competitive. We'll treat you like a regular employee and expect you to act like one. We think the best learning opportunities come through experience and mentorship, so you'll be provided with both. Learn, grow, explore your talents, and be taught some valuable skills. We're a small company and we're looking for interns that want an opportunity to make major contributions to our small teams." That's more about expectations; could be placed under About the role as prose. We need to avoid duplication. Let's structure:
About the role
Our paid internships run from May 17th, 2027 - August 13th 2027 and offer competitive wages. You'll be treated like a regular employee, gain experience and mentorship, and have the opportunity to make major contributions to our small teams.
- Code high-volume and scalable software
- Create web applications and back-end services using a variety of coding languages
- Investigate and resolve software issues/bugs
- Partner closely with cross functional teams in design, product, and other business functions
Requirements
- Computer Science or Software Engineering student
- Experience coding in Java, JavaScript/TypeScript, HTML5, CSS, MySQL, and React
- Willing to work hard, be a team player, and want to learn and grow
- Enjoys having fun, playing games, and eating snacks
- Affinity for card games is a plus
Skills
- Java
- JavaScript/TypeScript
- HTML5
- CSS
- MySQL
- React
Benefits
- 1 on 1 Mentorship – paired with a mentor from day one for real‑world projects, feedback, and career development
- 401(k) Match – company contributes to your retirement savings
- Fizzy Fridays – games, snacks, and fizzy beverages at 3:30 PM each Friday
- Catered Recognition Lunches – free monthly lunch and recognition
- Unlimited Coffee and Espresso – cappuccinos, lattes, black coffee, pour‑over options
- Ping Pong Table – friendly competition breaks