Sr Data Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Remove boilerplate. Preserve all substantive info. We need to parse the job description. First paragraph: "At Bank of America, we are guided..." That's generic corporate fluff. Might be considered boilerplate? It's about culture, purpose. Might be considered "About the role"? Not exactly. The posting includes a "Job Description: What we're building" etc. The initial paragraph is generic but could be considered "About the role" or "Company overview". The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real, specific content for it. The initial paragraph is generic but still about the company and role? It's not specific to the role. Might be considered boilerplate? It's not cookie/navigation/legal/EEO etc. It's about company purpose. Could be considered "About the role". However it's vague. The instruction says: Prefer a few substantive sections over many thin ones. So maybe combine into an "About the role" paragraph. Then we have "Job Description: What we're building" which is a description of team projects. Could be part of "About the role" or separate "Responsibilities"? Actually responsibilities are listed later. So "What we're building" could be part of "About the role" or "Team overview". We'll include as part of About the role. Then "Who we're looking for" paragraph describing hybrid role. Could be part of About the role or Qualifications. Might be better as "About the role". Then "Responsibilities" heading with bullet list. We'll output

Responsibilities

then

• items. Then "Required Skills:" list. That's qualifications/requirements. Could be split into Requirements and Qualifications? The instruction includes both headings. We have Required Skills (which are qualifications). Also there is a "Nice to have:" list. That could be "Preferred Qualifications" or "Skills". There's also a separate "Skills:" list at end: Analytical Thinking etc. That's likely a list of competencies. Could be "Skills" section. Also there is "Shift: 1st shift (United States of America)" and "Hours Per Week: 40". That's schedule info. So we should include a Schedule section. Pay/Benefits: Not mentioned. So we omit those sections. We must not include Job ID etc. None present. We need to preserve all substantive info. So we need to include all bullet points from Responsibilities, Required Skills, Nice to have, Skills list, Shift/Hours. We must not invent or summarize away detail. So we need to keep each bullet as is. We need to format as
  • for any list of duties/requirements/benefits. For prose, use

    . Thus: - About the role: combine the initial fluff, "What we're building", "Who we're looking for". Could be multiple paragraphs. We'll output:

    About the role

    At Bank of America, we are guided by a common purpose to help make financial lives better through the power of every connection. We do this by driving Responsible Growth and delivering for our clients, teammates, communities and shareholders every day. Being a Great Place to Work and providing a culture of caring is core to how we drive Responsible Growth. We are intentional about fostering an inclusive workplace where every teammate has the opportunity to succeed, build a career and contribute to our shared success. This includes attracting and developing exceptional talent, recognizing and rewarding performance, and supporting our teammates’ physical, emotional, and financial wellness through affordable, competitive and flexible benefits. We value the unique perspectives individuals bring from all backgrounds and career paths - whether shaped by military service, community college education, or a wide range of work and life experiences. These journeys foster resilience, leadership and innovation, strengthening our workforce and positively impact the communities we serve. Bank of America is committed to an in-office culture that supports collaboration, engagement, and career development. Our approach includes clear in-office expectations, while providing an appropriate level of flexibility based on role-specific responsibilities and business needs. At Bank of America, you can build a successful career with opportunities to learn, grow, and make an impact. Join us!

    What we're building Our team runs a range of data and AI projects across the GPS business. A few examples: A modern, AI-ready data platform and lakehouse that supports analytics, machine learning, and generative AI across the org.AI-powered tools that give sales and product teams fast, reliable answers to product, servicing, and client questions.Models that optimize pricing and foreign-currency conversion to drive real business value.Real-time pipelines that turn raw client and servicing data into insights teams can act on.

    Who we're looking for This is a hybrid role that spans data engineering, AI product enablement, and platform architecture. You'll build and scale the data backbone behind AI at GPS: engineering AI-ready data products, helping shape platform direction, and taking solutions from idea to production. We want someone who enjoys both the hands-on craft of building strong data platforms and the bigger opportunity to influence how the organization delivers AI. Whether you lean engineer or lean strategist, there's room here to do both.

    Then Responsibilities:

    Responsibilities

    • Build the data foundation for AI. Design and deliver end-to-end pipelines and Data Lake architecture using Python, Spark, SQL, and modern ETL practices, turning large raw datasets into trusted, AI-ready data products.
    • Enable AI products through data. Work with Product Owners, Data Scientists, and business partners to move AI and GenAI solutions into production, turning business problems into reusable data capabilities.
    • Set platform standards. Define the architecture, patterns, and standards for how data and AI get built, deployed, and used across the org, with an eye on reusability, performance, and cost.
    • Engineer production-grade solutions. Apply Object-Oriented design, solid data platform concepts, and strong ETL practices to build reliable, scalable pipelines, and help shape where the team's data capabilities go next.
    • Own the data-to-insight lifecycle. Review and improve data-flow processes, understand how data gets consumed, and make sure insights reach the people who use them.
    • Champion trusted, governed data. Build Data Governance and Quality principles into your work and act as a reliable partner to stakeholders and data consumers.
    • Drive projects from idea to production. Take new concepts and deliver them across business and Enterprise IT partnerships in a fast-paced environment.
    • Keep the customer first. Anticipate needs, take initiative, and deliver solutions that work well for internal and external customers.
    Then Requirements/Qualifications: We have "Required Skills:" list. Could be under Requirements. We'll use

    Requirements

    (or Qualifications). Since we have both headings possible, we can choose Requirements for the required skills, and Qualifications for nice-to-have? Or we could combine. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Required Skills and Nice to have into a single "Requirements" section with subheadings? But we cannot add extra headings beyond the allowed ones? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those. We could have Requirements for required skills, Qualifications for nice-to-have, Skills for the competency list, Schedule for shift/hours. Thus:

    Requirements

    • Bachelor's degree in Computer Science, Management Information Systems, Finance, Statistics, or a related field required.
    • 5+ years of hands-on Data Engineering experience building and operating production-grade data pipelines and platforms.
    • Advanced SQL expertise, deep proficiency in writing, optimizing, and tuning complex SQL and stored procedures across large-scale relational and distributed datasets (query performance, window functions, partitioning, and data modeling).
    • Strong programming background in Python and Spark, with solid Object-Oriented design principles and a focus on reusable, testable, production-quality code.
    • Modern data pipeline orchestration — hands-on experience with Apache Airflow (or comparable modern schedulers) to build, schedule, and monitor reliable end-to-end ETL/ELT workflows.
    • Data Lake and modern platform architecture — strong understanding of Data Lake concepts, dimensional modeling, data virtualization, and modern data delivery methodologies (medallion/lakehouse patterns, distributed processing).
    • Experience delivering Data & AI solutions within large, matrixed organizations, with the ability to quickly assess and adopt the right sourcing and architecture strategy.
    • Strong quantitative, analytical, and problem-solving skills, paired with critical thinking and creativity.
    • Ability to build effective relationships with business and technology partners.
    • Outstanding verbal and written communication skills, with the ability to express complex technical concepts in business terms across all levels of management.
    Then Qualifications (nice to have):

    Qualifications

    • Modern data engineering & orchestration tooling such as Airflow, dbt, Spark, and CI/CD for data pipelines (Git-based workflows, automated testing, and deployment).
    • Cloud and lakehouse platforms experience with modern cloud data warehouses and lakehouse technologies (e.g., Snowflake, Databricks, Delta Lake) alongside distributed storage (HDFS, Hive, Apache Spark).
    • Advanced SQL & database platforms performance tuning and engineering across RDBMS and Big Data platforms such as Oracle Exadata, SQL Server, and Teradata.
    • ETL/ELT and streaming technologies Python, Spark, SSIS, shell scripting, and exposure to real-time/streaming frameworks (e.g., Kafka).
    • BI and data visualization Tableau (Desktop and Server), Power BI, SSRS, and SSAS.
    • AI/GenAI enablement familiarity with building data foundations that support machine learning and generative AI use cases.
    • Banking and Global Treasury transactions industry experience a plus.
    Then Skills (competency list):

    Skills

    • Analytical Thinking
    • Application Development
    • Data Management
    • DevOps Practices
    • Solution Design
    • Agile Practices
    • Collaboration
    • Decision Making
    • Risk Management
    • Test Engineering
    • Architecture
    • Business Acumen
    • Data Quality Management
    • Financial Management
    • Solution Delivery Process
    Then Schedule:

    Schedule

    Shift: 1st shift (United States of America)

    Hours Per Week: 40

    We must not include Pay/Benefits sections. Check for any duplicated lines: The initial fluff includes "Join us!" which is okay. We must not include any boilerplate like cookie/navigation/legal/EEO etc. None present. We must not repeat job title as heading. We didn't. We must not put Job ID/requisition numbers as headings. None. We must preserve all substantive information. Did we miss anything? The "What we're building" paragraph had no spaces after periods? It's okay. We included "What we're building" and "Who we're looking for" as paragraphs under About the role. We included all responsibilities bullets. We