2027 Engineering Rotational Program

We need to output HTML fragment with sections: About the role? The posting includes description: "Our Engineering team ..." and "What You’ll Do". Also "Who We’re Looking For" includes basic and preferred qualifications. Also "Working model and hours". Also "Benefits". Also "Pay Range". Also maybe "Schedule". We need to follow rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include. We have: - About the role: maybe the introductory paragraph about U.S. Bank mission and description of engineering team. Could be "About the role" or "About the team". Use

  About the role

  with prose. - Responsibilities: "What You’ll Do" bullet list. - Requirements/Qualifications: Basic qualifications and Preferred qualifications. Could combine into "Qualifications" or separate "Requirements" and "Preferred qualifications". The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate. We have "Basic qualifications:" list and "Preferred qualifications:" list. Could put under

  Qualifications

  with subheadings? But we only allowed headings as per list; we could still include subheadings inside? Probably better to have

  Requirements

  for basic qualifications, and

  Preferred Qualifications

  maybe not in list but we can still use? The instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive; we can use other headings? It says use

  for section headings (e.g. ...). Likely we should stick to those examples but can also use others if needed. Safer to use those given. We have "Working model and hours" which could go under Schedule. We have Benefits section. We have Pay Range. Thus sections: About the role, Responsibilities, Requirements (basic qualifications), Qualifications (maybe preferred?), Benefits, Pay, Schedule. But we need to avoid thin sections. Could combine basic and preferred into one Qualifications section with two lists: Basic and Preferred. Or separate. Let's think: The posting includes "Basic qualifications:" and "Preferred qualifications:" as separate lists. We could have

  Qualifications

  with two

  maybe but not allowed? Could just have two

  headings inside? Might be okay to have Basic qualifications: etc inside the section. But instruction: Use

  • for any list of duties/requirements/benefits, and

    for prose. So we can have

    Basic qualifications:

    then
    • ... etc. Similarly for Preferred. Thus we can have a single Qualifications section containing both. Now "Working model and hours": This is schedule info: "This role requires working from a U.S. Bank location three (3) or more days per week, while having flexibility on their work location for the other working days." That's specific. So we can have

      Schedule

      with

      containing that sentence. Now Benefits: list of benefits. We'll put

      Benefits

      then
      • each benefit. Pay:

        Pay

        with

        Pay Range: $81,515.00 - $95,900.00

        . Now About the role: We need to capture the introductory mission and description of engineering team. The posting starts: "At U.S. Bank, we’re on a journey to do our best. Helping the customers and businesses we serve to make better and smarter financial decisions and enabling the communities we support to grow and succeed. We believe it takes all of us to bring our shared ambition to life, and each person is unique in their potential. A career with U.S. Bank gives you a wide, ever-growing range of opportunities to discover what makes you thrive at every stage of your career. Try new things, learn new skills and discover what you excel at—all from Day One. Job Description Our Engineering team At U.S. Bank, we deliver high performance, scalable, repeatable, and secure deliverables across the Enterprise. Our team uses technology acumen to provide input to assist with the evaluation of new technologies and contribute to the design of applications and services. Our work is structured and collaborative, with on-the-job training including construction, automation, debugging and implementation." We should keep that as prose. Possibly split into two paragraphs: first about mission, second about engineering team. Now Responsibilities: "What You’ll Do Engineering is a multi-faceted, ever-evolving field. Our Engineering Rotation Program will provide you with accelerated learning and skill development through a mix of on-the-job training, mentorship, a community of peers and advisors, and three rotations over 2.5 years to help you choose your path to a career in software or infrastructure engineering. As an Engineering Rotational Program Analyst, you will:" then bullet list: - Get hands-on experience in a variety of engineering roles across Infrastructure and Software Development supporting our many business line teams. - Enhance your engineering skills and learn the nuances of banking technology related to engineering practices. - Develop technical and business acumen through training, mentorship, and exposure to senior executives. - Build a supportive community of peers through a variety of cohort strengthening activities such as social events, volunteer days, and development workshops. We need to keep the introductory sentence before the list as prose maybe in a

        . Then the list as

        . Now Qualifications: Basic qualifications list: - Bachelor’s degree in computer science or similar majors completed in December 2026 or spring 2027. - Good understanding of engineering terms, concepts, and applications through relevant coursework or projects in computer science, software design, cloud computing and user experience. - Demonstrate proficiency in at least one programming language (i.e., Python, Java or similar). - Indicates familiarity with current and emerging technologies and develops ability to apply these technologies - Ability to start full-time rotational program on July 12, 2027. - Ability to work in-person at our U.S. Bank location in Hopkins, MN. Preferred qualifications list: - Desire to collaborate with multiple teams. - Leadership experiences in extracurricular activities. - Experience that required analytics, root cause analysis, and creative thinking. - Flexibility to work within a multi-discipline team and receive dynamic on-the-job training. We'll include both. Now Schedule: as above. Now Benefits list: need to capture each bullet: - Healthcare (medical, dental, vision) - Basic term and optional term life insurance - Short-term and long-term disability - Pregnancy disability and parental leave - 401(k) and employer-funded retirement plan - Paid vacation (from two to five weeks depending on salary grade and tenure) - Up to 11 paid holiday opportunities - Adoption assistance - Sick and Safe Leave accruals of one hour for every 30 worked, up to 80 hours per calendar year unless otherwise provided by law We should keep as list. Now Pay: as above. Now we must remove boilerplate: EEO, E-Verify, background check, disability accommodations, application instructions, etc. Also remove duplicated lines like "Posting may be closed earlier due to high volume of applicants." (appears twice). Also remove "Review our full benefits available by employment status here." (maybe considered boilerplate). Also remove "U.S. Bank is an equal opportunity employer..." etc. Also remove "The salary range reflects figures based on the primary location..." maybe keep? Actually that is about pay range but we already have pay range; the sentence about location may be considered filler but it's substantive? It says "The salary range reflects figures based on the primary location, which is listed first. The actual range for the role may differ based on the location of the role." That's extra detail about pay range; we could keep it as part of Pay section. However the instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay range, so we can include Pay section with that detail. We could include the extra sentence as prose. Similarly for Benefits: there is a sentence "Our approach to benefits and total rewards considers our team members’ whole selves and what may be needed to thrive in and outside work. That's why our benefits are designed to help you and your family boost your health, protect your financial security and give you peace of mind." That's substantive; we can include as prose before list. Now schedule: we have the sentence about working model and hours. Also maybe there is also "Working model and hours: This role requires working from a U.S. Bank location three (3) or more days per week, while having flexibility on their work location for the other working days." That's it. Now we need to ensure we don't include any application instructions like "If you are interested in applying and learning more, click on the Apply Now icon to submit your application." Remove. Also remove "If there’s anything we can do to accommodate a disability during any portion of the application or hiring process, please refer to our disability accommodations for applicants." Remove. Also remove "U.S. Bank will consider qualified applicants with arrest or conviction records for employment." etc. That's EEO/boilerplate. Now produce HTML fragment. Structure:

        About the role

        ...

        ...

        Responsibilities

        What You’ll Do Engineering is a multi-faceted, ever-evolving field. Our Engineering Rotation Program will provide you with accelerated learning and skill development through a mix of on-the-job training, mentorship, a community of peers and advisors, and three rotations over 2.5 years to help you choose your path to a career in software or infrastructure engineering. As an Engineering Rotational Program Analyst, you will:

        • Get hands-on experience in a variety of engineering roles across Infrastructure and Software Development supporting our many business line teams.
        • Enhance your engineering skills and learn the nuances of banking technology related to engineering practices.
        • Develop technical and business acumen through training, mentorship, and exposure to senior executives.
        • Build a supportive community of peers through a variety of cohort strengthening activities such as social events, volunteer days, and development workshops.

        Qualifications

        Basic qualifications:

        • Bachelor’s degree in computer science or similar majors completed in December 2026 or spring 2027.
        • Good understanding of engineering terms, concepts, and applications through relevant coursework or projects in computer science, software design, cloud computing and user experience.
        • Demonstrate proficiency in at least one programming language (i.e., Python, Java or similar).
        • Indicates familiarity with current and emerging technologies and develops ability to apply these technologies
        • Ability