Global AML Operations - Data Engineer
Bank of America · Pennington, NJ · 1 mo ago
Information TechnologyFull-time
We need to output HTML fragment with sections: h3 headings for sections present: About the role? Actually we have a job description with multiple paragraphs. We need to extract sections: maybe "About the role" from first paragraph describing Bank of America purpose. Then "Responsibilities" from bullet list. Then "Skills" from list. Then "Qualifications" maybe separate Required Qualifications and Desired Qualifications? Could combine? The instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section ONLY when posting has real, specific content. So we need sections: About the role (first paragraph). Responsibilities (list). Skills (list). Qualifications (maybe Required Qualifications and Desired Qualifications combined). Also maybe "Shift" and "Hours Per Week" could be Schedule? The posting includes Shift: 1st shift (United States of America) Hours Per Week: 40. That's schedule info. So we can create a Schedule section with that info. Benefits? Not mentioned. Pay? Not mentioned. So omit.
We must not repeat job title as heading. No Job ID. Remove boilerplate.
We need to preserve all substantive information. So we need to include the paragraphs about Bank of America purpose etc. Also the second "Job Description:" paragraph about developing and delivering data solutions. Also the third "Job Description This role is responsible for designing..." etc. Actually there are overlapping sections. We need to combine content without duplication.
Let's parse the given text:
First block: "Job Description: 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!"
Second block: "Job Description: This job is responsible for developing and delivering data solutions to accomplish technology and business goals and initiatives. Key responsibilities include performing code design and delivery tasks associated with the integration, cleaning, transformation, and control of data in operational and analytical data systems. Job expectations include working with stakeholders and Product and Software Engineering teams to aid with implementing data requirements, analyzing performance, and researching and troubleshooting data problems within system engineering domains."
Then "Responsibilities:" list (multiple lines). Then "Skills:" list.
Then "Line Of Business Job Description This role is responsible for designing, developing, implementing, and supporting data and reporting solutions for AML. ..." This seems another description.
Then "Responsibilities:" list (different). Then "Required Qualifications:" list. Then "Desired Qualifications:" list. Then "Skills:" list (different). Then "Shift: 1st shift (United States of America) Hours Per Week: 40"
We need to combine all responsibilities and skills without duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should include all responsibilities from both lists, but avoid duplicate lines if they are identical? There may be overlapping but we can keep both; but better to merge unique items. However we must not lose any detail. If we merge, we might lose some nuance if duplicates are identical; merging identical lines is okay as it's not losing info. But if they are slightly different, we need to keep both.
Let's extract responsibilities from first list (after first "Responsibilities:"): It appears as a single paragraph with line breaks? Actually it's a sentence with line breaks? Let's copy:
"Works across development teams to contribute to the story refinement and delivery of data requirements through the delivery life cycle
Leverages architecture components in solution development, codes solutions to integrate, clean, transform, and control data in operational and analytical data systems per acceptance criteria
Builds processes supporting data transformation, data structures, metadata, data quality controls, dependency, and workload management and defines and builds data pipelines and complex data sets to enable data-informed decision making, identifying and raising risks at all stages of the data engineering process
Develops and executes test plans to produce quantitative results, contributes to existing test suites including integration, regression, and performance, analyzes test reports, identifies test issues and errors, and triages underlying causes
Drives complex information technology projects to ensure on-time delivery and adheres to team delivery and release processes
Identifies, defines, and documents data engineering requirements, communicating required information for deployment, maintenance, support, and business functionality
Works with technology partners and a diverse set of stakeholders to identify and close gaps in data management standards adherence, negotiates paths forward, and helps identify and communicate solutions to complex data problems leveraging knowledge of information systems, techniques, and processes"
That's 7 bullet points.
Second responsibilities list (under AML description):
"Design, develop, test, and maintain data pipelines, reporting solutions, and data products supporting AML processes.
Build and enhance data integrations, workflows, and automation solutions to improve efficiency and data quality.
Develop scalable and reusable data components that support multiple applications and use cases.
Support the day-to-day operation of AML data platforms, including issue resolution, monitoring, and performance optimization.
Analyze data requirements and translate business needs into technical solutions.
Perform data analysis, validation, reconciliation, and quality checks to ensure accuracy and completeness.
Troubleshoot production issues and implement sustainable solutions to prevent recurrence.
Participate in code reviews and testing activities to ensure solution quality and adherence to development standards.
Contribute to platform resiliency, performance tuning, and disaster recovery testing activities.
Create and maintain technical documentation, operational procedures, and support materials.
Support Agile delivery process.
Identify opportunities to improve processes, automation, and overall platform efficiency."
That's 12 bullet points.
We should combine them into a single
- list, preserving all. Ensure no duplication: some items may be similar but not identical; we keep both.
Now Skills: first skills list after first responsibilities: "Skills: Analytical ThinkingApplication DevelopmentData ManagementDevOps PracticesSolution DesignAgile PracticesCollaborationDecision MakingRisk ManagementTest EngineeringArchitectureBusiness AcumenData QualityManagementFinancial ManagementSolution Delivery Process Line Of Business"
That seems messed up: no spaces. Let's parse: "Analytical ThinkingApplication DevelopmentData ManagementDevOps PracticesSolution DesignAgile PracticesCollaborationDecision MakingRisk ManagementTest EngineeringArchitectureBusiness AcumenData Quality ManagementFinancial ManagementSolution Delivery Process Line Of Business"
Probably each skill separated by missing space. We need to split into individual 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, Line Of Business.
Second skills list after desired qualifications: "Skills: Data EngineeringData IntegrationSQL DevelopmentData Pipeline DevelopmentETL / ELT DevelopmentWorkflow AutomationData Quality ManagementApplication DevelopmentCloud Data TechnologiesPerformance OptimizationProduction SupportTroubleshootingAgile DeliveryAnalytical ThinkingCollaborationSolution ImplementationProcess Improvement"
Split: Data Engineering, Data Integration, SQL Development, Data Pipeline Development, ETL / ELT Development, Workflow Automation, Data Quality Management, Application Development, Cloud Data Technologies, Performance Optimization, Production Support, Troubleshooting, Agile Delivery, Analytical Thinking, Collaboration, Solution Implementation, Process Improvement.
We need to combine both lists, preserving all, avoid duplicates. Duplicates: Data Quality Management appears in both; Application Development appears both; Analytical Thinking appears both; Collaboration appears both. We'll keep one each.
Now Qualifications: Required Qualifications list (bullet points). Desired Qualifications list.
We need to output a Qualifications section (maybe combine required and desired). Could separate into Required Qualifications and Desired Qualifications as subheadings? But instruction only lists generic headings; we could use "Qualifications" heading and include both required and desired within
- maybe with notes? But we need to preserve all detail; we could include two subheadings inside? Not allowed? Only h3 for section headings; we could have multiple h3 sections: "Required Qualifications" and "Desired Qualifications". The instruction says use h3 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 use "Required Qualifications" and "Desired Qualifications" as h3 headings? Might be okay. However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are the allowed headings; we should stick to those. So we should have a single "Qualifications" section containing both required and desired qualifications. We can differentiate within list maybe by adding text like "Required:" but that may be extra. Better to just list all qualifications; but we need to preserve distinction? The instruction says preserve ALL substantive information; not necessarily preserve the labeling of required vs desired. If we merge, we lose that distinction. Could we include a note inside
before list? Eg
Required qualifications:
then- then
- ...
Desired qualifications:
then another- . That preserves info. That's allowed: we can have paragraphs inside the section. So we can have a Qualifications section with two paragraphs and two lists.
Now About the role: we need to include the first big paragraph about Bank of America purpose. Also maybe include the second "Job Description: This job is responsible for developing and delivering data solutions..." and third "Line Of Business Job Description..." as part of About the role? Actually those are also job description specifics. Could treat them as part of About the role or maybe separate sections like "Job Overview". But instruction only lists certain headings; we could put all descriptive prose under About the role. That seems okay.
Thus About the role section will contain multiple paragraphs: the Bank of America purpose paragraph, the "This job is responsible for developing..." paragraph, the "Line Of Business Job Description..." paragraph. Ensure we keep all.
Now Responsibilities section: combine both lists.
Skills section: combine both lists, deduplicate.
Qualifications section: include required and desired qualifications with paragraphs.
Schedule section: include shift and hours.
Now we must not include boilerplate like EEO etc. There's none.
Now output HTML fragment: start with
About the role
then paragraphs...
. ThenResponsibilities
Skills
- ...
Qualifications
Required qualifications:
- ...
Desired qualifications:
- ...
Schedule
Shift: 1st shift (United States of America); Hours per week: 40.
maybe combine. Make sure to preserve all details exactly as given, preserving punctuation. Let's extract exact text for About the role paragraphs. Paragraph1: "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
- maybe with notes? But we need to preserve all detail; we could include two subheadings inside? Not allowed? Only h3 for section headings; we could have multiple h3 sections: "Required Qualifications" and "Desired Qualifications". The instruction says use h3 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 use "Required Qualifications" and "Desired Qualifications" as h3 headings? Might be okay. However they said "Use