Back-End Software Engineer Intern

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. We must not repeat job title. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. We need to parse the posting. Content: - Intro paragraph: "Awardco is reimagining the workplace..." etc. That's about the company, maybe "About the role"? Actually "About the role" could be description of role? The posting includes mission, etc. Could treat as "About the role" or maybe "About the company". But we only have headings list; we can use "About the role" for introductory description. - Then: "Our development team is very lean..." etc. That's also about role. - Then: "This internship has a target start date in April or May 2027 with an anticipated end date in August or September 2027 with the potential to extend. This is a full-time summer internship. We currently have multiple product/engineering internships open at the moment. Please only apply to the internship that aligns most with where you want to pursue your career.* Our recruiting team will be reviewing applications during the month of October 2026." That's metadata about schedule maybe. Could go under Schedule? It includes start/end dates, full-time summer internship. That's schedule info. Also "Please only apply..." is application instruction - should be removed. "Our recruiting team will be reviewing applications during the month of October 2026." That's also application instruction? Might be considered timeline but could be kept as schedule? It's about recruiting timeline, not work schedule. Probably remove as application instruction. - Then: "What you will do:" list: managing development of new features, changes to existing code, improving overall product performance by optimizing existing workflows and code blocks. Expect dynamic, display leadership, bring fresh ideas, enthusiastic to take on new problems. Then bullet list: Design and implement new features for our existing web application; Continue to maintain and iterate on released features by implementing and following key metrics; Peer code review. That's responsibilities. - Then: "What you will bring:" list: Currently pursuing a bachelor's degree in Computer Science or related technical field; Experience in a general purpose programming language including but not limited to: C, C++, C#, Java, JavaScript, Go, or Python; Interest and ability to learn other programming languages; Experience working with data structures and algorithms; Currently located or willing to relocate to Lindon, UT area; Authorization to legally work in the US; Working proficiency in verbal and written English. That's qualifications/requirements/skills. Could split: Requirements (education, location, work auth, language proficiency) and Skills (programming languages, data structures, ability to learn). But we can combine. - Then: "Starting Pay: $25/hr" => Pay section. - Then: "Why join Awardco?" list of benefits: revolutionary product, fastest growing companies, Great Place to Work certified, etc. That's benefits. - Then EEO boilerplate etc to remove. - Disclaimer about email domain etc - remove as boilerplate. Thus sections: About the role: intro paragraphs (company mission, development team lean, internship timeline? maybe timeline goes to Schedule). Let's decide: About the role could include mission and description of team and that it's a full-time summer internship with start/end dates? But schedule section could hold start/end dates. However we need to avoid thin sections. Perhaps we combine schedule info into About the role? But we have a Pay section definitely. Benefits section definitely. Responsibilities section definitely. Requirements/Qualifications/Skills we need to decide. We could have sections: About the role, Responsibilities, Requirements, Benefits, Pay. Schedule: we have start/end dates and full-time summer internship. That's specific. Could be its own section Schedule. But we already have info about timeline in About the role maybe. However we need to follow instruction: include a section ONLY when posting has real, specific content for it. The posting does have specific start/end dates and full-time summer internship. So we should include Schedule section. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. We must not include Skills if we cover in Requirements. Could combine Requirements and Skills into one Requirements section. But we have separate headings list; we can choose to include Requirements and maybe Skills if we want. But better to avoid thin sections. We'll put all candidate qualifications under Requirements. Now we need to format:

About the role

then

...

for prose. For lists use

• . We must preserve all substantive information, not invent or summarize away detail. So we need to keep all details from the posting, but we can rephrase? We must not invent or summarize away detail. We can keep the same sentences but maybe combine into paragraphs. Must not omit any substantive info. Let's extract all substantive info: From intro: - Awardco is reimagining the workplace to be more rewarding, supportive, and fun for everyone. - As one of the fastest growing companies in the employee experience industry, our mission is to help employees love what they do, love where they work, and get recognized for their efforts—especially our own employees! - And as winners of Glassdoor's Best Places to Work, Best in Brightest in the Nation, and Great Place to Work, we do much more than talk the talk. - Our development team is very lean. - Lean software development (agile development) is an essential methodology for our development processes, and each member of our team is trained in agile software development methods and is capable of leading a team that adheres to these processes. - This internship has a target start date in April or May 2027 with an anticipated end date in August or September 2027 with the potential to extend. - This is a full-time summer internship. - We currently have multiple product/engineering internships open at the moment. - Please only apply to the internship that aligns most with where you want to pursue your career.* (application instruction - remove) - Our recruiting team will be reviewing applications during the month of October 2026. (application instruction - remove) Now responsibilities: - The Awardco engineers are responsible for an array of duties, including managing the development of new features, changes to our existing code, and improving overall product performance by optimizing existing workflows and code blocks. - We expect our development team to be dynamic, display leadership qualities, bring fresh ideas to improve the product, and be enthusiastic to take on new problems as we continue to expand the recognition and incentive industry. - Design and implement new features for our existing web application - Continue to maintain and iterate on released features by implementing and following key metrics - Peer code review Now qualifications: - Currently pursuing a bachelor's degree in Computer Science or related technical field - Experience in a general purpose programming language including but not limited to: C, C++, C#, Java, JavaScript, Go, or Python - Interest and ability to learn other programming languages - Experience working with data structures and algorithms - Currently located or willing to relocate to Lindon, UT area - Authorization to legally work in the US - Working proficiency in verbal and written English Pay: - Starting Pay: $25/hr Benefits (Why join Awardco?): - We have a revolutionary, client-approved product. - One of the fastest growing companies in the nation: 3x Inc. 500, 2x Deloitte Technology Fast 500, 2x Mountain West Capital Network Fast 100, 3x Fast 50 (Utah Business), and 3x UV50 Fastest Growing Companies (BusinessQ), to name just a few. - Great Place to Work certified, ranked in Inc. Best Workplaces, one of the Best and Brightest companies to work for, and ranked on the Salt Lake Tribune's Top Workplaces. - Backed by renowned investors, both local and national. We must not include EEO etc. Now schedule section: we have target start date April or May 2027, anticipated end date August or September 2027 with potential to extend, full-time summer internship. Also we have multiple product/engineering internships open (maybe not needed). We'll include start/end dates and full-time summer. Now we need to output HTML fragment only. Structure:

  About the role

  ... (combined intro paragraphs)

  Responsibilities

  • ... each duty

  Requirements

  • ... each qualification

  Benefits

  • ... each benefit

  Pay

  Starting Pay: $25/hr

  Schedule

  Target start date: April or May 2027; anticipated end date: August or September 2027 with potential to extend. This is a full-time summer internship.

  We must ensure we didn't miss any substantive info: The line "We currently have multiple product/engineering internships open at the moment." is substantive but maybe not needed for any section. Could be included in About the role as note. But we removed it as maybe not essential? It's substantive info about availability. Should we preserve? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that line somewhere. Could add to About the role paragraph: "We currently have multiple product/engineering internships open at the moment." That is substantive. Also "Our recruiting team will be reviewing applications during the month of October 2026." That's also substantive but maybe considered application instruction? It's about recruiting timeline, not work. Might be considered metadata but still substantive. However we are told to remove application instructions. That line is about when they review applications, which is part of application process. Likely considered application instruction, so we can remove. The line about multiple internships open is not an instruction, it's info about the role. So we should keep. Also "Please only apply to the internship that aligns most with where you want to pursue your career.*" is instruction, remove. Thus About the role paragraph should include: Awardco reimagining..., mission, winners, development team lean, agile, multiple product/engineering internships open, maybe also mention that it's a full-time summer internship? But we moved schedule to its own section. Could still mention it's a full-time summer internship in schedule section. It's okay to not duplicate. Now ensure we didn't lose any bullet points from responsibilities: we have three bullet points plus the preceding sentences about managing development etc and expectations. We should include those as list items as well? The instructions: Use
  • for any list of duties/requirements/benefits. The preceding sentences are not a list but prose. We can keep them in

    before the list or incorporate them as list items. Better to keep them as prose paragraph then list for the specific duties. But we must preserve all substantive info. So we can have a

    describing responsibilities: "The Awardco engineers are responsible for an array of duties, including managing the development of new features, changes to our existing code, and improving overall product performance by optimizing existing workflows and code blocks. We expect our development team to be dynamic, display leadership qualities, bring fresh ideas to improve the product, and be enthusiastic to take on new problems as we continue to expand the recognition and incentive industry." Then a

    with the three specific duties. Similarly for requirements: we could have a

    intro? Not needed. We'll just list each as

    • . Now benefits: we have four bullet points; we can list each as
    • . Now schedule: we have a

      with the details. Now pay: