Jobs · Management · Georgia

Co-Op, Operations Planning & Performance - Data and AI Enablement (Summer 2027)

Delta Air Lines · Atlanta, GA · 1 mo ago
ManagementPart-time
We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to parse the posting. The posting includes: - Overview & Key Responsibilities: description of ODAE team, core functions, co-op will work closely with analytics professionals in operation supporting cross-divisional focus areas (list). Also note about alternating semesters, full-time work schedule (but schedule details not given? It says "The full-time work schedule for this role, while remaining actively enrolled in an approved undergraduate curriculum, is as follows" but then no schedule provided. So schedule content is missing; we should not create Schedule section because no specific schedule given. - What You Need To Succeed (Minimum Qualifications): list of qualifications: enrolled in undergrad program in certain fields, available for three alternating semesters for full-time work, ability to report in-person to Delta’s World Headquarters (Atlanta, GA) or willing to relocate each semester (housing stipends will be provided to students who meet the minimum criteria), team oriented, basic understanding of data management & enablement functions, proficiency with Python or other similar tools, proficiency in SQL and ETL/ELT patterns, proficiency in Microsoft Office Suite and data analysis tools and concepts, strong organizational, project management, and verbal/written communication skills essential, willingness/ability to adapt quickly and learn new skills required, consistently prioritizes safety and security, embraces diverse people, possesses high school diploma or equivalent, at least 18 years old and authorization to work in US. - What Will Give You a Competitive Edge (Preferred Qualifications): working knowledge of and/or experience with cloud-based solutioning (i.e. Azure, AWS, GPC, etc.) We need to map to sections: About the role (overview), Responsibilities (maybe the core functions and tasks), Requirements (minimum qualifications), Qualifications (maybe preferred?), Skills (maybe list of skills), Benefits (maybe housing stipends mentioned), Pay (not mentioned), Schedule (not given). We should only include sections with real content. We have overview: "How You'll Help Us Keep Climbing (Overview & Key Responsibilities)" includes description. So we can have

About the role

with paragraph(s) summarizing overview. Responsibilities: The core functions and the co-op will work closely with analytics professionals supporting cross-divisional focus areas (list). So we can list responsibilities as
  • ... each bullet. Requirements: Minimum qualifications list. Qualifications: Preferred qualifications (cloud experience). Could also include "team oriented" etc but those are in minimum. We'll put preferred under Qualifications. Skills: Could list specific technical skills: Python, SQL, ETL/ELT, Microsoft Office, data analysis tools, etc. But those are already in minimum qualifications. Might be redundant. However we can still create a Skills section if we have specific skill list not covered elsewhere. The posting mentions proficiency with Python or other similar tools, proficiency in SQL and ETL/ELT patterns, proficiency in Microsoft Office Suite and data analysis tools and concepts, strong organizational, project management, verbal/written communication skills. Those could go under Skills. But we already have them in Requirements. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine qualifications and skills into one section? But we have headings defined: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include. We have content for About the role, Responsibilities, Requirements (minimum qualifications), Qualifications (preferred), Benefits (housing stipends). Skills could be derived from the same list but maybe we can omit Skills to avoid thin sections. However we have specific technical skills that could be placed under Skills. But we already have them in Requirements; moving them to Skills would duplicate. Better to keep them under Requirements (or Qualifications). Since we have both minimum and preferred, we could have Requirements for minimum, Qualifications for preferred. Skills maybe not needed. Benefits: housing stipends mentioned. Also maybe "housing stipends will be provided to students who meet the minimum criteria". That's a benefit. So we can have Benefits section. Pay: not mentioned, so omit. Schedule: not specific, omit. Thus output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. Now we need to preserve all substantive information, not invent or summarize away detail. Must not omit details like list of cross-divisional focus areas, core functions, etc. We need to format as HTML fragment: use

    for headings,

    for prose,

    • for lists. We must not include job title heading, no Job ID, no boilerplate. Let's extract details. Overview & Key Responsibilities paragraph: "The Operations Data & AI Enablement (ODAE) team is seeking highly motivated and curious individuals who are excited to leverage data to improve the operations. DAE enables the Operations Planning & Performance (OP&P) organization by designing modern data foundations & building data pipelines that improves data quality, accelerates insights, and empowers faster, smarter decision‑making across the business. We create human-centered data and AI foundations that empower OP&P; through intuitive design, governed structures and embedded intelligence; that unlocks speed & ease to analyze operational problems. The ODAE Team Has 3 Core Functions Data Foundations - design and steward reliable, well‑governed data foundations that enable analytics and AI at scale AI Strategy & Tooling - embed AI and data toolkits into analytical products and workflows to drive innovation, productivity, and faster insights Data Enablement Delivery - design and maintain high-quality data assets & pipelines to enable the right analytics at the right time The Co-Op will work closely with analytics professionals in the operation supporting the following cross-divisional focus areas: Aircraft Performance Planning - managing aircraft and gate to gate operations and performanceAirport Performance Planning - improving airport processes and managing performanceCrew Performance Planning - improving Pilot and Flight Attendant operations and performance efficiencyDisruption Containment - tracking flight metrics, weather, day-of flight analysesOperations Digital & Decision Science – developing decision science tools and digital product solutionsOperations Performance - managing centralized operations and competitive performance analysesOperations Schedule and Planning - optimizing aircraft schedule and resource availability to maintain peak on-time performanceProcess & Competitive Analysis - improving system processes & evaluating key metrics against our competitors in the airline industry Students are required to complete three alternating semesters of work and school; all rotations must be completed before the student's graduation. Note: Students are not permitted to work part-time hours and should refrain from taking classes and working as a co-op in the same semester. The full-time work schedule for this role, while remaining actively enrolled in an approved undergraduate curriculum, is as follows" We need to preserve all that. However the schedule line ends with "is as follows" but no schedule given; we should not invent. We can keep that sentence as is? It says "The full-time work schedule for this role, while remaining actively enrolled in an approved undergraduate curriculum, is as follows". That's a statement but no schedule. It's not substantive detail; it's placeholder. According to rules: 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. This sentence is filler; we could either keep it as part of overview paragraph (since it's in the overview text) but it's not substantive. However we must preserve ALL substantive information; we can keep it as part of the overview paragraph because it's in the original text, but it's not substantive. The instruction says preserve ALL substantive information; does not require preserving filler. It says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not exactly boilerplate but it's incomplete. Might be considered filler. Safer to keep it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we can omit non-substantive filler. The line "The full-time work schedule for this role, while remaining actively enrolled in an approved undergraduate curriculum, is as follows" is not substantive because no schedule follows. So we can omit it. However it's part of the overview paragraph; if we omit, we might be removing some text but it's not substantive. I'd omit it. Now responsibilities: we have core functions and cross-divisional focus areas. We'll list them as bullet points. We need to ensure we don't duplicate. Let's list core functions: - Data Foundations: design and steward reliable, well‑governed data foundations that enable analytics and AI at scale - AI Strategy & Tooling: embed AI and data toolkits into analytical products and workflows to drive innovation, productivity, and faster insights - Data Enablement Delivery: design and maintain high-quality data assets & pipelines to enable the right analytics at the right time Cross-divisional focus areas (list each with dash): - Aircraft Performance Planning - managing aircraft and gate to gate operations and performance - Airport Performance Planning - improving airport processes and managing performance - Crew Performance Planning - improving Pilot and Flight Attendant operations and performance efficiency - Disruption Containment - tracking flight metrics, weather, day-of flight analyses - Operations Digital & Decision Science – developing decision science tools and digital product solutions - Operations Performance - managing centralized operations and competitive performance analyses - Operations Schedule and Planning - optimizing aircraft schedule and resource availability to maintain peak on-time performance - Process & Competitive Analysis - improving system processes & evaluating key metrics against our competitors in the airline industry Also note about alternating semesters: "Students are required to complete three alternating semesters of work and school; all rotations must be completed before the student's graduation. Note: Students are not permitted to work part-time hours and should refrain from taking classes and working as a co-op in the same semester." This is more about requirements (minimum qualifications). We'll include under Requirements. Now Minimum Qualifications list: - Enrolled in an Undergraduate program in pursuit of a bachelor’s degree in computer science, Analytics, Economics, Industrial Engineering, Information Systems, or similar 4-year degree program - Available for three alternating semesters for full-time work - Ability to report in-person to Delta’s World Headquarters (Atlanta, GA) or willing to relocate each semester (housing stipends will be provided to students who meet the minimum criteria) - Team oriented and highly supportive of continuous improvement methodologies - Basic understanding of data management & enablement functions: ETL/ELT pipelines, relational database fundamentals, modeling concepts, etc. - Proficiency with Python or other similar tools and programming languages - Proficiency in SQL and ETL/ELT patterns - Proficiency in Microsoft Office Suite and data analysis tools and concepts - Strong organizational, project management, and verbal/written communication skills are essential - Willingness/ability to adapt quickly and learn new skills are required - Consistently prioritizes safety and security of self, others, and personal data. - Embraces diverse people, thinking, and styles. - Possesses a high school diploma, GED, or high school equivalency. - Is at least 18 years of age and has authorization to work in the United States. Note: The housing stipends mention is also a benefit; we could keep it under Benefits but also mention in qualifications. We'll keep it under Benefits to avoid duplication. However the sentence includes "housing stipends will be provided to students who meet the minimum criteria". That's a benefit. We'll keep it under Benefits. Now Preferred Qualifications: - Working knowledge of and/or experience with cloud-based solutioning (i.e. Azure, AWS, GPC, etc.) Now Benefits: housing stipends (maybe also mention that they are provided to students who meet minimum criteria). Could also include any other benefits? Not mentioned. Thus Benefits section:

      Housing stipends will be provided to students who meet the minimum criteria.

      Now we need to ensure we don't repeat the job title as heading. Not needed. Now output HTML fragment. We'll structure:

      About the role

      ... overview paragraph (without

Similar jobs