Summer 2027 Software Engineering Internship

We need to output HTML fragment only, 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 as heading. No Job ID etc. Remove boilerplate: EEO, legal, navigation, cookie, application instructions, duplicated lines. We need to preserve all substantive info. Let's parse the job description. First paragraph: "Looking to jumpstart your career at a company that offers real opportunities to flourish? Look no further than Pacific Life. We’re investing in bright, agile new talent with fresh perspectives to help us innovate and build meaningful relationships for years to come. It’s in this spirit that we are currently looking to add Software Engineering Interns to our team for Summer 2027 at a Fortune 500 company in the financial services industry." That's about the role/company. Could be "About the role" or "About Pacific Life". We'll use "About the role". Next: "As a Software Engineering Intern, you will be directly embedded in our technology teams driving Pacific Life’s digital transformation. As part of the technology organization, you will have incredible development opportunities across a variety of business and operational areas while being exposed to modern technology in an enterprise environment. Potential areas include cloud engineering, software/application delivery, integration development and information security." That's responsibilities. Then "What You’ll Do" list: bullet points: - Contribute to technology delivery and operations teams to develop and deploy solutions in an enterprise environment - Collaborate closely with technologists and other stakeholders to plan, design, implement and support digital technologies aligned to business priorities - Evaluate business needs and technology solutions to assess fit - Be exposed to and develop capability in related enterprise technologies as well as delivery practices (e.g. Agile scrum) That's responsibilities. Then "Factors for Success" list: bullet points: - Currently enrolled in a Bachelor’s or Master’s Degree in Computer Science, Software Engineering, Information Technology, or another related field. - Strong analytical, problem solving, and organizational skills with methodical approach - Excellent communication skills, with the ability to articulate technical concepts clearly - Ability to work well with others as a team and independently - Desire for learning new technologies and analytic tools; as well as modeling and quantitative techniques - Proficiency in at least one programing language such as Python, Java, C# - Good understanding of algorithms, data structures and software design principles - Familiarity with industry tools and platforms for software delivery and automation - Familiarity with at least one public cloud platform preferably AWS but will consider other major could providers such as Azure or GCP - Display a true passion and intellectual curiosity for solving business problems with code via coursework or external or personal project These are qualifications/requirements/skills. We need to decide sections: Requirements, Qualifications, Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can split into Requirements (maybe education enrollment), Qualifications (maybe degree?), Skills (technical). But we must not create thin sections. Better to combine into a few substantive sections. We have "Requirements": currently enrolled in Bachelor's/Master's in CS etc. That's a requirement. We have "Qualifications": maybe the list of skills? Actually qualifications often include education and experience. But we already used education as requirement. Could treat "Qualifications" as the list of desired qualifications (analytical skills, communication, teamwork, desire to learn). And "Skills" as technical proficiencies (programming language, algorithms, cloud, tools). That seems reasonable. Then we have Pay: "The base pay rate for this position is $25.00 per hour for undergraduates and $30.00 per hour for advanced degrees." Also "Relocation stipend available if residence is outside of 50 mile radius from office location." That's a benefit? Could be part of Benefits or Pay. Since we have Pay section, we can include pay rate there. Relocation stipend could be a benefit. Benefits: "More Reasons To Join At Pacific Life, the work we do matters. We work passionately each day to drive our company forward while enjoying job security, flexible scheduling, and great opportunities for career growth. If you’re seeking a thriving career doing the type of meaningful work that’s all too rare at a Fortune 500 Company, Pacific Life is the place for you. If you are a self-starter who appreciates creativity and individuality in your colleagues – even better. We look forward to receiving your application." Also "You belong at Pacific Life At Pacific Life, we believe you belong. We foster a culture of belonging, a space where all employees are empowered to be authentic. We embrace and celebrate diversity, create a culture of equity and inclusion, and value and respect every employee." Also "How We Help You Succeed Our Summer Internship Program has become Pacific Life’s talent pipeline for full time early career opportunities. The University Relations team ensures each intern has a well-rounded positive experience to help them reach their career goals. The Summer Program includes: Professional DevelopmentExecutive Mentorship ProgramCollaborative EnvironmentReal World WorkSocial EventsTraining and EducationNetworking and Exposure to Leadership" Also "You Can Be Who You Are We are committed to a culture of diversity and inclusion that embraces the authenticity of all employees, partners and communities. We support all employees to thrive and achieve their fullest potential." Also "What’s life like at Pacific Life? Visit Instagram.com/lifeatpacificlife" These are benefits/culture. We can create a Benefits section summarizing: job security, flexible scheduling, career growth, professional development, executive mentorship, collaborative environment, real world work, social events, training and education, networking, exposure to leadership, diversity and inclusion, belonging, etc. Also relocation stipend. We should not include boilerplate like EEO statement, Instagram link maybe okay as it's substantive? It's a link to Instagram; could be considered a benefit? Might be okay to keep as part of Benefits? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Instagram link is not boilerplate; it's a reference to culture. Might keep. We must not include duplicated lines. There's some duplicated sentences: "Designs, develops, modifies, debugs and evaluates software enhancements or new programs for new and/or existing applications used in local, networked, cloud-based or Internet-related environments." etc. That appears later in the description after "More Reasons To Join". That seems like a generic job description for a software engineer role, maybe duplicated. We need to preserve all substantive information but not duplicate. We should include that content if it's substantive and not duplicated elsewhere. However it looks like a generic description of software engineer duties, maybe not specific to internship. It might be considered boilerplate? It's not clearly boilerplate like EEO, but it's a generic description of software engineer tasks. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep it if it's substantive. However it's quite detailed and appears after the "More Reasons To Join" section. It might be part of the job description (maybe copied from a standard software engineer role). We'll include it under Responsibilities or maybe a separate section "Key Responsibilities". But we already have Responsibilities section with What You'll Do. This extra detail could be added to Responsibilities as additional bullet points. We need to avoid duplication: we already have bullet points under What You'll Do. The later paragraph includes many similar tasks: design, develop, modify, debug, evaluate software enhancements, review system requirements, develop program logic, code, test, debug, document, implement, maintain software applications, develop conversion and system implementation plans, prepare documentation, recommend changes, train users. These are more detailed responsibilities. We should include them. We must not include application instructions (like "We look forward to receiving your application.") That's maybe okay to keep as part of Benefits? It's not an instruction to apply; it's a statement. Might be okay. We must not include EEO statement at end. Now decide sections: - About the role (intro) - Responsibilities (combining What You'll Do and later detailed duties) - Requirements (education enrollment) - Qualifications (soft skills: analytical, problem solving, communication, teamwork, desire to learn) - Skills (technical: programming language proficiency, algorithms/data structures, tools/platforms, cloud familiarity, passion for solving business problems) - Benefits (job security, flexible scheduling, career growth, professional development, executive mentorship, collaborative environment, real world work, social events, training/education, networking, exposure to leadership, diversity/inclusion, belonging, relocation stipend) - Pay (hourly rates) Schedule: not mentioned; we should not create Schedule section if not present. We must not create sections with filler like "commensurate with experience". Not present. Now produce HTML. We need to use

for each section heading. Use

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

  for prose. We need to ensure we don't repeat job title as heading. Not using. We must output only HTML fragment. Let's craft. First, About the role: combine intro paragraphs. Paragraph: "Looking to jumpstart your career at a company that offers real opportunities to flourish? Look no further than Pacific Life. We’re investing in bright, agile new talent with fresh perspectives to help us innovate and build meaningful relationships for years to come. It’s in this spirit that we are currently looking to add Software Engineering Interns to our team for Summer 2027 at a Fortune 500 company in the financial services industry." That's prose. Second, Responsibilities: we need a list. We'll combine bullet points from What You'll Do and later detailed duties. List items: - Contribute to technology delivery and operations teams to develop and deploy solutions in an enterprise environment - Collaborate closely with technologists and other stakeholders to plan, design, implement and support digital technologies aligned to business priorities - Evaluate business needs and technology solutions to assess fit - Be exposed to and develop capability in related enterprise technologies as well as delivery practices (e.g. Agile scrum) - Design, develop, modify, debug and evaluate software enhancements or new programs for new and/or existing applications used in local, networked, cloud-based or Internet-related environments - Review system requirements and business processes and develop program logic for new applications or analyze and modify logic in existing applications - Interact with users to define system requirements and/or necessary modifications - Code, test, debug, document, implement, and maintain software applications using current programming language and technologies - Write code, complete programming, integrate application components, and perform testing and debugging of applications - Develop conversion and system implementation plans to ensure that system improvements are successfully deployed - Prepare and obtain approval of system and programming documentation and procedures for installation and maintenance - Recommend changes in development, maintenance and system standards - Train users in conversion and implementation of systems We could combine some similar items to avoid redundancy but keep substance. Third, Requirements: education enrollment. List: Currently enrolled in a Bachelor’s or Master’s Degree in Computer Science, Software Engineering, Information Technology, or another related field. That's a single item; could be

  but instruction says use

  • for any list of duties/requirements/benefits. If only one item, still could be
    • . Or we could use

      . Safer to use

      for prose. But requirement is a statement; we can use

      . Fourth, Qualifications (soft skills): list. - Strong analytical, problem solving, and organizational skills with methodical approach - Excellent communication skills, with the ability to articulate technical concepts clearly - Ability to work well with others as a team and independently - Desire for learning new technologies and analytic tools; as well as modeling and quantitative techniques Fifth, Skills (technical): list. - Proficiency in at least one programming language such as Python, Java, C# - Good understanding of algorithms,