Infrastructure Automation Engineer Intern

We need to output HTML fragment with sections: About Us? Actually we need to reformat job posting into clean semantic HTML. 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. Do NOT put Job ID/requisition numbers as headings. 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. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Content: - About Us: description of company. - Role Summary: description of internship. - How You Will Make An Impact: bullet list of duties. - What You Bring To The Team (Required): bullet list of requirements. - Additional Assets (Preferred): bullet list of preferred. - What We Offer: bullet list of benefits. - Additional Requirements: about office schedule. - EEO etc: remove. We need to map to sections: About the role? Possibly "About Us" could be "About the role"? Actually they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which sections we have content for. We have: - About the role: could be Role Summary (description). Could also include About Us? But "About the role" likely refers to role description. We'll put Role Summary under

About the role

. - Responsibilities: How You Will Make An Impact (list of duties). We'll put under

Responsibilities

. - Requirements: What You Bring To The Team (Required) (list). We'll put under

Requirements

. - Qualifications: maybe same as Requirements? Could combine? But we have also Additional Assets (Preferred) which could be Skills or Qualifications. We could put under

Skills

for preferred assets. Or Qualifications for required? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple sections. We need to decide what content goes where. We have: - About the role: Role Summary paragraph. - Responsibilities: bullet list of impact. - Requirements: bullet list of required qualifications. - Skills: bullet list of preferred assets (exposure to automation tools). - Benefits: bullet list of What We Offer (competitive pay, mentor program, resource groups, casual dress, social/philanthropic calendar). Also maybe 401k eligibility. - Schedule: Work schedule: 40 hours/week Monday-Friday 8am-5pm. Also program dates June 2 – August 6 (10 weeks). Location: onsite Kansas City, MO. Also mention not eligible for visa sponsorship, must be authorized to work in US. Also Additional Requirements: Employees required to be in office on a scheduled frequency. Adherence essential. That's schedule/location info. - Pay: Competitive pay mentioned under What We Offer. So we could include Pay section with that detail. But they said prefer few substantive sections over many thin ones. Could combine Pay and Benefits? But they said include a section ONLY when posting has real specific content for it. We have competitive pay mentioned; we could put under Benefits or Pay. Since they have separate headings for Pay and Benefits, we could put pay under Pay and other benefits under Benefits. However they said prefer few substantive sections over many thin ones. Might be okay to have both if content is substantive. Let's see: Pay: "Competitive pay and 401k eligibility for employee contributions." That's specific. Benefits: Mentor Program, Access to Business Resource Groups, Casual dress code, robust social and philanthropic calendar. Those are benefits. So we could have both Pay and Benefits sections. - Schedule: Work schedule and program dates, location, office requirement. So we can have Schedule section. We must not include boilerplate like EEO, accommodation statement, etc. Remove those. Also remove duplicated lines, application instructions (like deadline to apply? Actually that's part of posting; but they said remove application instructions. The deadline to apply is November 1, 2026. That's application instruction? Might be considered metadata; but they said do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. The deadline is maybe minor metadata; we could fold into a short p under About the role or Schedule? But they said remove application instructions. The deadline is an application instruction. So we should remove it. Also "Program dates: June 2nd – August 6th (10 weeks)." That's schedule info, keep. "Work schedule: 40 hours/week - Monday – Friday (8 am – 5 pm)." Keep. "Location: this onsite position will be based out of our Kansas City, MO office." Keep. "This position is not eligible for visa sponsorship. Applicants must be authorized to work in the U.S. without visa sponsorship, now or in the future." That's a requirement about work authorization; could be under Requirements? It's a requirement. We'll include. Also "Additional Assets (Preferred)" is preferred skills. Now we need to output HTML fragment only. Structure:

About the role

Role summary paragraph.

Responsibilities

• ...
...

Requirements

• ...
...

Skills

• ...
...

Pay

Competitive pay and 401k eligibility for employee contributions.

Benefits

• Mentor Program - during your time with us you will be assigned a dedicated mentor to provide career coaching and mentoring.
• Access to our Business Resource Groups (Emerging Professionals, Pride, Mosaic, Green Team, and others.)
• Casual dress code - be comfortable and express your unique self.
• A robust social and philanthropic calendar of events hosted just for Interns!

Schedule

Program dates: June 2nd – August 6th (10 weeks). Work schedule: 40 hours/week - Monday – Friday (8 am – 5 pm). Location: onsite at the Kansas City, MO office. This position is not eligible for visa sponsorship; applicants must be authorized to work in the U.S. without visa sponsorship, now or in the future. Employees are required to be in the office on a scheduled frequency; adherence to this schedule is essential to fulfilling the expectations of the role.

We need to ensure we preserve all substantive information. Let's extract exact phrasing. From posting: About Us paragraph: "American Century Investments® is a leading global asset manager with over 65 years of experience helping a broad base of clients achieve their financial goals. Our expertise spans global equities and fixed income, multi-asset strategies, ETFs, and private investments. Privately owned and independent, we focus solely on investment management. But there’s an unexpected side to us, too. We direct 40% of our dividends every year—over $2 billion since 2000—to the Stowers Institute for Medical Research. Our ongoing financial support drives the Institute’s breakthrough work and mission of defeating life-threatening diseases like cancer and Alzheimer’s. So, the better we do for our clients, the more we can do for everyone. All who work here around the globe are inspired every day by the unique difference our hard work can make in so many lives. It shows in the curiosity we bring to every initiative, the deep relationships we build with our clients, and the way we treat each other in the hallway. If you’re excited to learn more about us, we can’t wait to learn more about you." But we might not need About Us as a section; they said use headings like About the role, Responsibilities, etc. About Us could be considered "About the role"? Actually About the role is separate. The About Us is company description; maybe we could include it under About the role? But they said do NOT repeat the job title as a heading. They didn't forbid including company description. Could we include a section "About the company"? Not in list. They gave examples but not exclusive. However they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should stick to those headings. So we likely should not include About Us as a separate heading; maybe we can incorporate it into About the role paragraph? But About the role is supposed to be role summary. However we could include both company description and role summary under About the role? Might be okay but could be mixing. Better to follow their examples: we have About the role (role summary). We could omit the About Us paragraph because it's not directly about the role? But they said preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the About Us info somewhere. If we don't have a heading for it, we could put it as a

before the first heading? The instruction: Output ONLY the HTML fragment — no /. It didn't forbid having a leading paragraph without heading. It said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't say you cannot have other headings, but they gave examples. It said include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we could have a heading like "About the company" if we want, but they didn't list that as example; but it's not prohibited. However they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). This implies those are the expected headings. Safer to stick to those. We could incorporate About Us into About the role paragraph as a preamble: "About the role: [company description] Role summary..." But that might be weird. Alternatively, we could create a section "About the company" but not in examples; risk. Given the instruction to prefer few substantive sections over many thin ones, maybe we can combine About Us and Role Summary into About the role section. Let's do that:

About the role

Company description + role summary.

We need to preserve all substantive information: include company description and role summary. Let's extract role summary paragraph: "We’re looking for a motivated, tech-savvy Infrastructure Automation Engineer Intern to join our Infrastructure & Operations team, with a focus on driving automation initiatives. This internship offers hands-on experience in an enterprise IT environment, where you’ll collaborate with experienced professionals to streamline operations, improve system reliability, and reduce manual processes through innovative automation solutions. As an AI-forward organization, American Century Investments is committed to finding innovative ways to apply artificial intelligence across our technology landscape. As an Infrastructure Automation Engineer Intern, you'll have the opportunity to help shape how AI is used within enterprise IT, exploring new approaches to automation, operational efficiency, and service improvement while gaining valuable hands-on experience in a modern infrastructure environment. This program is for currently enrolled undergraduate rising seniors who will graduate in December 2027