Risk Analysis Specialist II
Bank of America · Jersey City, NJ · 1 mo ago
AnalystFull-time
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 that have real specific content. The posting includes: description paragraphs, responsibilities list, required skills, desired skills, skills list, shift info (Shift: 1st shift, Hours per week: 40). No explicit Benefits, Pay, Schedule beyond shift/hours. Schedule could be derived from shift/hours? The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Shift and Hours per week, which is schedule info. So we can include a Schedule section with that info. Benefits not mentioned, so omit. Pay not mentioned, omit.
We need to use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: description paragraphs, responsibilities list, required skills, desired skills, skills list, shift info (Shift: 1st shift, Hours per week: 40). No explicit Benefits, Pay, Schedule beyond shift/hours. Schedule could be derived from shift/hours? The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Shift and Hours per week, which is schedule info. So we can include a Schedule section with that info. Benefits not mentioned, so omit. Pay not mentioned, omit.
We need to use for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. No Job ID etc.
We need to preserve all substantive information. Remove boilerplate like EEO etc. There's none.
We need to include sections: About the role (maybe from first paragraph?), Responsibilities, Requirements (maybe required skills?), Qualifications (maybe education/experience?), Skills (maybe list of skills), Schedule (shift/hours). Could combine Required Skills and Desired Skills into Requirements? But we have separate sections: Requirements, Qualifications, Skills. The instruction: use headings for those if content exists. We need to decide mapping.
The posting includes: "Required Skills:" list, "Desired Skills:" list, then "Skills:" list (maybe a summary). Also earlier: "Bachelors or Masters in computer science, system analysis, Information Systems or related field. 1-3+ years of experience with Data Sourcing, Data Wrangling, Data Engineering or similar role" etc. That's qualifications.
Thus we can have:
About the role
... (the introductory paragraph about Bank of America purpose and culture).
Responsibilities
- ... each responsibility line.
Qualifications
Bachelors or Masters in computer science, system analysis, Information Systems or related field. 1-3+ years of experience with Data Sourcing, Data Wrangling, Data Engineering or similar role.
Requirements
Strong process/systems analysis, design and documentation. Strong analytical, critical thinking, and problem-solving skills. Ability to monitor tight deadlines and adapt to unexpected requirement changes. Strong Understanding of Risk Management and Data Management Principles. Experience in Product Management: Ability to visualize functionality within a product, work with cross functional teams to deliver, market the product, create Road Shows/Office Hours, and onboard the users. Experience in Project Management - Create concise project plans - Delivery Management - JIRA advanced user - Presentation Skills. Business and Data Analysis Skills - Create BRDs/DRDs - SQL Skills - Technical skills (Python etc) is a plus - Data Quality/Profiling Awareness - Data Lineage Awareness. Business Analytics - Tableau Experience - Any BI Tool Experience. Finance/Risk Domain Experience. Stakeholder management and Communication Skills.
But that's long; maybe better to split into list. The instruction: use - for any list of duties/requirements/benefits. So we can make a list for Requirements.
Similarly Skills section: we have "Skills:" list: Attention to Detail, Business Intelligence, Data and Trend Analysis, Risk Analytics, Risk Management, Adaptability, Collaboration, Continuous Improvement, Data Visualization, Project Management, Business Acumen, Issue Management, Regulatory Relations, Stakeholder Management, Technical Documentation. Could be a list.
Desired Skills also could be part of Requirements or separate? Could be included in Requirements as desired? But we already have Requirements; maybe we treat Desired Skills as part of Requirements or separate "Preferred Qualifications". But we don't have a heading for Preferred. Could add to Requirements as bullet points marked desired? But instruction: preserve all substantive information; we can include Desired Skills as part of Requirements or maybe as a separate section "Preferred Skills". However only allowed headings are those listed; we could use "Requirements" for required and desired combined, or we could add a "Skills" section for the skill list and treat Required/Desired as part of Requirements. Let's think.
We have sections: About the role, Responsibilities, Qualifications, Requirements, Skills, Schedule.
We need to avoid filler. Ensure each heading has substantive content.
Let's extract content:
About the role: first paragraph up to "Join us!" Actually there is a repeated "Job Description:" line. The first block: "At Bank of America, we are guided by a common purpose...". That's about the company and culture. We'll put that.
Responsibilities: list after "Responsibilities:" includes many bullet-like sentences. We'll make each as
- .
Qualifications: education and experience line: "Bachelors or Masters in computer science, system analysis, Information Systems or related field. 1-3+ years of experience with Data Sourcing, Data Wrangling, Data Engineering or similar role."
Requirements: the list under "Required Skills:" (the long list). We'll make each bullet.
Skills: the list under "Skills:" (the short list). We'll make each bullet.
Schedule: "Shift: 1st shift (United States of America) Hours Per Week: 40". We'll put in
.
We should also include maybe "Desired Skills" as part of Requirements or maybe as a separate "Preferred Qualifications" but not allowed headings. Could incorporate into Requirements as bullet points marked desired? But we already used Required Skills for requirements. Could add a separate section "Preferred Skills" but not in allowed list. The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive list; but likely we should stick to those. It didn't forbid other headings, but says use those for section headings. Safer to stick to those. So we can incorporate Desired Skills into Requirements or Skills. Perhaps we can add them under Requirements as bullet points with note "(desired)". But we need to preserve all info; we can just add them as additional bullet points under Requirements without marking. That would lose distinction but still preserve content. Might be acceptable.
Alternatively we could create a separate "Skills" section that includes both required and desired skills? But we already have Skills list separate. Could merge desired skills into Skills section. The Skills list currently includes things like Attention to Detail etc. Desired skills include familiarity with Trading etc, programming languages, databases, research new data technologies. Those are also skills. So we could add them to Skills list. That would preserve all.
Thus Skills section will contain both the enumerated skills list and the desired skills items.
Let's compile.
First, About the role paragraph: combine the initial paragraph(s) before the second "Job Description:" line. The text:
"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!"
That's the about.
Now Responsibilities: list after "Responsibilities:" includes:
- Supports the development and execution of reporting to allow Risk and business partners to effectively identify and manage risk
- Analyzes trends and supports the data design, portfolio trends, loss trends, and portfolio dynamics to ensure alignment with business strategies
- Provides analytical support on various product strategic initiatives affecting multiple Risk functions and lines of business to ensure company goals are met
- Participates in the development of database production processes and performance reports for senior management, using data mining and other advanced analytical techniques to aggregate data
- Supports with responding to complex ad-hoc requests for information from both internal and external parties
- Provides support on cross-functional efforts to remediate data quality issues
- Monitors the outputs of controls and investigates alerts from the control checks
We'll make each
- .
Qualifications: "Bachelors or Masters in computer science, system analysis, Information Systems or related field. 1-3+ years of experience with Data Sourcing, Data Wrangling, Data Engineering or similar role."
Requirements: list from "Required Skills:" includes many items separated by periods. Let's split each sentence as bullet.
List:
- Bachelors or Masters in computer science, system analysis, Information Systems or related field. (but that's already in qualifications; maybe we shouldn't duplicate. Actually Required Skills starts after that line? The text: "Required Skills: Bachelors or Masters in computer science, system analysis, Information Systems or related field.1-3+ years of experience with Data Sourcing, Data Wrangling, Data Engineering or similar roleStrong process/systems analysis, design and documentation.Strong analytical, critical thinking, and problem-solving skills.Ability to monitor tight deadlines and adapt to unexpected requirement changes.Strong Understanding of Risk Management and Data Management PrinciplesExperience in Product Management: Ability to visualize functionality within a product, work with cross functional teams to deliver, market the product, create Road Shows/Office Hours, and onboard the usersExperience in Project Management - Create concise project plans - Delivery Management - JIRA advanced user - Presentation SkillsBusiness and Data Analysis Skills - Create BRDs/DRDs - SQL Skills - Technical skills (Python etc) is a plus - Data Quality/Profiling Awareness - Data Lineage AwarenessBusiness Analytics - Tableau Experience - Any BI Tool ExperienceFinance/Risk Domain ExperienceStakeholder management and Communication Skills."
It seems they omitted spaces after periods. We need to parse.
We'll separate by periods and capital letters? Let's manually list:
1. Bachelors or Masters in computer science, system analysis, Information Systems or related field.
2. 1-3+ years of experience with Data Sourcing, Data Wrangling, Data Engineering or similar role
3. Strong process/systems analysis, design and documentation.
4. Strong analytical, critical thinking, and problem-solving skills.
5. Ability to monitor tight deadlines and adapt to unexpected requirement changes.
6. Strong Understanding of Risk Management and Data Management Principles
7. Experience in Product Management: Ability to visualize functionality within a product, work with cross functional teams to deliver, market the product, create Road Shows/Office Hours, and onboard the users
8. Experience in Project Management - Create concise project plans - Delivery Management - JIRA advanced user - Presentation Skills
9. Business and Data Analysis Skills - Create BRDs/DRDs - SQL Skills - Technical skills (Python etc) is a plus - Data Quality/Profiling Awareness - Data Lineage Awareness
10. Business Analytics - Tableau Experience - Any BI Tool Experience
11. Finance/Risk Domain Experience
12. Stakeholder management and Communication Skills.
We'll make each bullet.
Now Skills list: after "Skills:" line: "Attention to DetailBusiness IntelligenceData and Trend AnalysisRisk AnalyticsRisk ManagementAdaptabilityCollaborationContinuous ImprovementData VisualizationProject ManagementBusiness Ac
- for any list of duties/requirements/benefits. Use
for prose. We must not repeat job title as heading. No Job ID etc. We need to preserve all substantive information. Remove boilerplate like EEO etc. There's none. We need to include sections: About the role (maybe from first paragraph?), Responsibilities, Requirements (maybe required skills?), Qualifications (maybe education/experience?), Skills (maybe list of skills), Schedule (shift/hours). Could combine Required Skills and Desired Skills into Requirements? But we have separate sections: Requirements, Qualifications, Skills. The instruction: use headings for those if content exists. We need to decide mapping. The posting includes: "Required Skills:" list, "Desired Skills:" list, then "Skills:" list (maybe a summary). Also earlier: "Bachelors or Masters in computer science, system analysis, Information Systems or related field. 1-3+ years of experience with Data Sourcing, Data Wrangling, Data Engineering or similar role" etc. That's qualifications. Thus we can have:
About the role
... (the introductory paragraph about Bank of America purpose and culture).
Responsibilities
- ... each responsibility line.
Qualifications
Bachelors or Masters in computer science, system analysis, Information Systems or related field. 1-3+ years of experience with Data Sourcing, Data Wrangling, Data Engineering or similar role.
Requirements
Strong process/systems analysis, design and documentation. Strong analytical, critical thinking, and problem-solving skills. Ability to monitor tight deadlines and adapt to unexpected requirement changes. Strong Understanding of Risk Management and Data Management Principles. Experience in Product Management: Ability to visualize functionality within a product, work with cross functional teams to deliver, market the product, create Road Shows/Office Hours, and onboard the users. Experience in Project Management - Create concise project plans - Delivery Management - JIRA advanced user - Presentation Skills. Business and Data Analysis Skills - Create BRDs/DRDs - SQL Skills - Technical skills (Python etc) is a plus - Data Quality/Profiling Awareness - Data Lineage Awareness. Business Analytics - Tableau Experience - Any BI Tool Experience. Finance/Risk Domain Experience. Stakeholder management and Communication Skills.
But that's long; maybe better to split into- list. The instruction: use
- for any list of duties/requirements/benefits. So we can make a list for Requirements. Similarly Skills section: we have "Skills:" list: Attention to Detail, Business Intelligence, Data and Trend Analysis, Risk Analytics, Risk Management, Adaptability, Collaboration, Continuous Improvement, Data Visualization, Project Management, Business Acumen, Issue Management, Regulatory Relations, Stakeholder Management, Technical Documentation. Could be a list. Desired Skills also could be part of Requirements or separate? Could be included in Requirements as desired? But we already have Requirements; maybe we treat Desired Skills as part of Requirements or separate "Preferred Qualifications". But we don't have a heading for Preferred. Could add to Requirements as bullet points marked desired? But instruction: preserve all substantive information; we can include Desired Skills as part of Requirements or maybe as a separate section "Preferred Skills". However only allowed headings are those listed; we could use "Requirements" for required and desired combined, or we could add a "Skills" section for the skill list and treat Required/Desired as part of Requirements. Let's think. We have sections: About the role, Responsibilities, Qualifications, Requirements, Skills, Schedule. We need to avoid filler. Ensure each heading has substantive content. Let's extract content: About the role: first paragraph up to "Join us!" Actually there is a repeated "Job Description:" line. The first block: "At Bank of America, we are guided by a common purpose...". That's about the company and culture. We'll put that. Responsibilities: list after "Responsibilities:" includes many bullet-like sentences. We'll make each as
- .
Qualifications: education and experience line: "Bachelors or Masters in computer science, system analysis, Information Systems or related field. 1-3+ years of experience with Data Sourcing, Data Wrangling, Data Engineering or similar role."
Requirements: the list under "Required Skills:" (the long list). We'll make each bullet.
Skills: the list under "Skills:" (the short list). We'll make each bullet.
Schedule: "Shift: 1st shift (United States of America) Hours Per Week: 40". We'll put in
. We should also include maybe "Desired Skills" as part of Requirements or maybe as a separate "Preferred Qualifications" but not allowed headings. Could incorporate into Requirements as bullet points marked desired? But we already used Required Skills for requirements. Could add a separate section "Preferred Skills" but not in allowed list. The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive list; but likely we should stick to those. It didn't forbid other headings, but says use those for section headings. Safer to stick to those. So we can incorporate Desired Skills into Requirements or Skills. Perhaps we can add them under Requirements as bullet points with note "(desired)". But we need to preserve all info; we can just add them as additional bullet points under Requirements without marking. That would lose distinction but still preserve content. Might be acceptable. Alternatively we could create a separate "Skills" section that includes both required and desired skills? But we already have Skills list separate. Could merge desired skills into Skills section. The Skills list currently includes things like Attention to Detail etc. Desired skills include familiarity with Trading etc, programming languages, databases, research new data technologies. Those are also skills. So we could add them to Skills list. That would preserve all. Thus Skills section will contain both the enumerated skills list and the desired skills items. Let's compile. First, About the role paragraph: combine the initial paragraph(s) before the second "Job Description:" line. The text: "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!" That's the about. Now Responsibilities: list after "Responsibilities:" includes: - Supports the development and execution of reporting to allow Risk and business partners to effectively identify and manage risk - Analyzes trends and supports the data design, portfolio trends, loss trends, and portfolio dynamics to ensure alignment with business strategies - Provides analytical support on various product strategic initiatives affecting multiple Risk functions and lines of business to ensure company goals are met - Participates in the development of database production processes and performance reports for senior management, using data mining and other advanced analytical techniques to aggregate data - Supports with responding to complex ad-hoc requests for information from both internal and external parties - Provides support on cross-functional efforts to remediate data quality issues - Monitors the outputs of controls and investigates alerts from the control checks We'll make each
- . Qualifications: "Bachelors or Masters in computer science, system analysis, Information Systems or related field. 1-3+ years of experience with Data Sourcing, Data Wrangling, Data Engineering or similar role." Requirements: list from "Required Skills:" includes many items separated by periods. Let's split each sentence as bullet. List: - Bachelors or Masters in computer science, system analysis, Information Systems or related field. (but that's already in qualifications; maybe we shouldn't duplicate. Actually Required Skills starts after that line? The text: "Required Skills: Bachelors or Masters in computer science, system analysis, Information Systems or related field.1-3+ years of experience with Data Sourcing, Data Wrangling, Data Engineering or similar roleStrong process/systems analysis, design and documentation.Strong analytical, critical thinking, and problem-solving skills.Ability to monitor tight deadlines and adapt to unexpected requirement changes.Strong Understanding of Risk Management and Data Management PrinciplesExperience in Product Management: Ability to visualize functionality within a product, work with cross functional teams to deliver, market the product, create Road Shows/Office Hours, and onboard the usersExperience in Project Management - Create concise project plans - Delivery Management - JIRA advanced user - Presentation SkillsBusiness and Data Analysis Skills - Create BRDs/DRDs - SQL Skills - Technical skills (Python etc) is a plus - Data Quality/Profiling Awareness - Data Lineage AwarenessBusiness Analytics - Tableau Experience - Any BI Tool ExperienceFinance/Risk Domain ExperienceStakeholder management and Communication Skills." It seems they omitted spaces after periods. We need to parse. We'll separate by periods and capital letters? Let's manually list: 1. Bachelors or Masters in computer science, system analysis, Information Systems or related field. 2. 1-3+ years of experience with Data Sourcing, Data Wrangling, Data Engineering or similar role 3. Strong process/systems analysis, design and documentation. 4. Strong analytical, critical thinking, and problem-solving skills. 5. Ability to monitor tight deadlines and adapt to unexpected requirement changes. 6. Strong Understanding of Risk Management and Data Management Principles 7. Experience in Product Management: Ability to visualize functionality within a product, work with cross functional teams to deliver, market the product, create Road Shows/Office Hours, and onboard the users 8. Experience in Project Management - Create concise project plans - Delivery Management - JIRA advanced user - Presentation Skills 9. Business and Data Analysis Skills - Create BRDs/DRDs - SQL Skills - Technical skills (Python etc) is a plus - Data Quality/Profiling Awareness - Data Lineage Awareness 10. Business Analytics - Tableau Experience - Any BI Tool Experience 11. Finance/Risk Domain Experience 12. Stakeholder management and Communication Skills. We'll make each bullet. Now Skills list: after "Skills:" line: "Attention to DetailBusiness IntelligenceData and Trend AnalysisRisk AnalyticsRisk ManagementAdaptabilityCollaborationContinuous ImprovementData VisualizationProject ManagementBusiness Ac