Vice President – Global Markets APS Settlements
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. 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.
Key sections:
- Business Overview: description of team.
- Candidate Success Factors: performance drivers (Results and Impact, Leadership and Collaboration, Client, Customer and Stakeholder Focus, Compliance Culture and Conduct). This could be considered "Qualifications" or "Skills"? Might be "Candidate Success Factors" but not in list. Could treat as "Qualifications" or "Skills". The instructions say we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings.
We have:
- Business Overview: could be "About the role" or maybe "About the team". Use "About the role" heading.
- Candidate Success Factors: could be "Qualifications" or "Skills". It's about performance drivers, maybe "Qualifications". We'll put under "Qualifications".
- Responsibilities: list of duties.
- Minimum Required Qualifications: list of technical qualifications.
- Preferred Qualifications: list.
- FINRA Registrations Required: N/A etc. That's not substantive; we can drop.
- Salary range: "The expected starting salary range for this position is between $145,000 to $195,000 annually." That's Pay info. So we need a Pay section.
- Benefits: description of benefits package. So Benefits section.
- About BNP Paribas: company overview. Could be "About the role"? Already used. Could be "About the company"? Not in list. Could be omitted? The instruction says include a section ONLY when posting has real, specific content for it. We have content about company. Could map to "About the role"? But that's already used for Business Overview. Maybe we can have two sections: "About the role" (Business Overview) and "About the company" not allowed heading. Could we use "About the role" for both? Might be redundant. Perhaps we can treat the company overview as part of "About the role" as well, but that might be mixing. Better to have separate sections: "About the role" (Business Overview) and "About the company" not a permitted heading; maybe we can omit it because not in allowed list? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exhaustive? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we should not create other headings like "About BNP Paribas". So we may need to incorporate that content elsewhere, maybe under "About the role" as a description of the company context. Or we could drop it? But we must preserve ALL substantive information. So we need to include it somewhere. Could add a paragraph under "About the role" after the business overview.
Thus:
About the role
Business Overview: The North American Application Support Settlements Stream owns the end-to-end support and continuous improvement of every settlement related application used by the U.S. and Canadian Prime Brokerage businesses.
About BNP Paribas: BNP Paribas is a leading bank ...
But that mixes two topics. Might be okay.
Alternatively, we could have "About the role" for Business Overview and then another heading like "About the company" but not allowed. So we combine.
Now Candidate Success Factors: we can put under "Qualifications" as a list of performance drivers.
Responsibilities: list.
Minimum Required Qualifications: list.
Preferred Qualifications: list.
Pay: salary range.
Benefits: description.
We should not include sections like Schedule (not present). Requirements maybe same as Qualifications? We'll use Qualifications for both minimum and preferred? Could separate into "Minimum Required Qualifications" and "Preferred Qualifications" but headings must be from list; we could use "Qualifications" for minimum and maybe "Skills" for preferred? But better to keep one Qualifications section containing both minimum and preferred, maybe split with subheadings? Not allowed subheadings? Could use to differentiate. But we need to preserve all info. Could do:
Qualifications
Minimum Required Qualifications
but h4 not allowed? Not specified. Might be okay but risk. Safer to keep as with bold? But we must not invent headings not in list. Could use inside . That's okay.
Thus:
Qualifications
Minimum Required Qualifications:
- SQL – writing, tuning, and extracting settlement data.
...
Then Preferred Qualifications:
...
Similarly for Responsibilities.
Now Candidate Success Factors: maybe under "Skills"? Could be "Skills". We'll put under "Skills" heading.
Thus sections:
- About the role (Business Overview + company overview)
- Skills (Candidate Success Factors)
- Responsibilities
- Qualifications (minimum + preferred)
- Pay
- Benefits
Check if any other content: "While the description above describes our ideal candidate, we encourage applicants to apply even if they do not fully meet the complete list of qualifications noted." That's generic encouragement; could be considered boilerplate? Might be considered application instruction? It's not a direct instruction to apply, but it's encouraging. Might be considered boilerplate; we can drop.
Also "FINRA Registrations Required: N/A Not Applicable ..." drop.
Now ensure we don't repeat job title.
Now produce HTML.
We need to ensure we use - for any list.
We'll produce:
About the role
The North American Application Support Settlements Stream owns the end-to-end support and continuous improvement of every settlement related application used by the U.S. and Canadian Prime Brokerage businesses.
BNP Paribas is a leading bank in Europe with an international reach across the US, EMEA and APAC. It has a presence in 65 countries, with nearly 190,000 employees. The bank employs over 3,500 people in offices in the US across 10 states including New York, Jersey City, Chesterbrook, PA, San Francisco, Boston, Chicago, Denver, Miami, and Washington, DC. BNP Paribas has built a strong and diversified presence to support its client base. We continue to grow and strengthen our commitment to the US market through our Corporate & Institutional Banking activities. We are one of a few non-US banks to offer a full value chain for our clients, from trading to financing, and clearing and custody in the US with the international footprint and capacity to deliver both globally and locally. Leveraging the strength of our European roots, our network can support clients in virtually every region of the world, enabling more connectivity and efficiency wherever our clients conduct business. We take pride in our expertise and our ability to adapt while constantly looking ahead to create a more sustainable world. As an international company with a global footprint, the unique cultures and viewpoints of our team members are an integral part of the fabric of BNP Paribas. We are a company with a purpose - to be a responsible and sustainable global leader. We aim to create an environment where our employees feel empowered to drive change, make an impact and be true to themselves. We employ talented individuals from a wide variety of backgrounds, locally and globally, and are inspired by our employees who help us in cultivating a diverse, equitable and inclusive workplace through initiatives such as our Diversity, Equity & Inclusion (DEI) Leadership Forum and Employee Resource Group (ERG) communities. We strive to be a workplace where all team members can grow and thrive and offer robust training, development, and mentoring opportunities to make that vision a reality. Our leaders are deeply committed to DEI and highly accessible to our employees, consistently soliciting feedback on how we can continue to support our employees to reach their highest potential.
Now Skills:
Skills
- Results and Impact: Able to influence peers and team; demonstrates good judgement when making decisions of high complexity and impact; exercises appropriate autonomy in the execution and delivery of work; responsible for driving outcomes, which have meaningful effect on team or department.
- Leadership and Collaboration: Creates trust with colleagues; acts in leadership capacity for projects, processes, or programs.
- Client, Customer and Stakeholder Focus: Able to build relationships with a mix of colleagues and clients; interacts regularly with management and department leaders; demonstrates the ability to influence stakeholders at the team level.
- Compliance Culture and Conduct: Takes full responsibility for personal actions and demonstrates courage in facing problems and conflicts; perceived as a person of high moral character; upholds corporate values and displays high ethical standards.
Now Responsibilities:
Responsibilities
- Direct daily triage, root‑cause analysis, and resolution of incidents across Calypso, XSP, and all in‑house settlement tools logged in ServiceNow.
- Ensure 2nd‑line specialists receive clear, well‑documented work‑packages and that escalations follow the defined matrix.
- Conduct weekly post‑mortems for high‑impact incidents; drive corrective‑action plans that reduce repeat occurrences.
- Perform regular SoD and EoD reviews and remediation.
- Ensure communication handover of issues between regions.
- Supervise daily break‑reconciliation reviews, start‑of‑day, intraday, and end‑of‑day health checks on Calypso, XSP, and supporting in‑house utilities.
- Own the regional monitoring framework (Autosys, custom scripts, Dynatrace dashboards) and continuously improve alerting and automation.
- Identify repetitive support tasks across the settlement stack and develop Shell/Python/SQL scripts (or RPA bots) to automate monitoring, reconciliation, and batch‑job validation.
- Track and report efficiency gains (time, cost, error reduction).
- Serve as NA’s primary liaison with the Global Settlement‑Support Team.
- Coordinate ticket, job‑schedule, and change hand‑offs with EMEA and APAC support centers for Calypso, XSP, and all proprietary tools.
- Participate in global governance forums (Incident Review Board, Change Advisory Board).
- Produce weekly/monthly KPI dashboards (availability, incident trends, MTTR, automation coverage) for senior leadership.
- Maintain up‑to‑date SOPs, run‑books, and knowledge‑base articles in ServiceNow and internal wikis for each platform.
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. 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. Key sections: - Business Overview: description of team. - Candidate Success Factors: performance drivers (Results and Impact, Leadership and Collaboration, Client, Customer and Stakeholder Focus, Compliance Culture and Conduct). This could be considered "Qualifications" or "Skills"? Might be "Candidate Success Factors" but not in list. Could treat as "Qualifications" or "Skills". The instructions say we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. We have: - Business Overview: could be "About the role" or maybe "About the team". Use "About the role" heading. - Candidate Success Factors: could be "Qualifications" or "Skills". It's about performance drivers, maybe "Qualifications". We'll put under "Qualifications". - Responsibilities: list of duties. - Minimum Required Qualifications: list of technical qualifications. - Preferred Qualifications: list. - FINRA Registrations Required: N/A etc. That's not substantive; we can drop. - Salary range: "The expected starting salary range for this position is between $145,000 to $195,000 annually." That's Pay info. So we need a Pay section. - Benefits: description of benefits package. So Benefits section. - About BNP Paribas: company overview. Could be "About the role"? Already used. Could be "About the company"? Not in list. Could be omitted? The instruction says include a section ONLY when posting has real, specific content for it. We have content about company. Could map to "About the role"? But that's already used for Business Overview. Maybe we can have two sections: "About the role" (Business Overview) and "About the company" not allowed heading. Could we use "About the role" for both? Might be redundant. Perhaps we can treat the company overview as part of "About the role" as well, but that might be mixing. Better to have separate sections: "About the role" (Business Overview) and "About the company" not a permitted heading; maybe we can omit it because not in allowed list? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exhaustive? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we should not create other headings like "About BNP Paribas". So we may need to incorporate that content elsewhere, maybe under "About the role" as a description of the company context. Or we could drop it? But we must preserve ALL substantive information. So we need to include it somewhere. Could add a paragraph under "About the role" after the business overview.
Thus:
About the role
About the role
Business Overview: The North American Application Support Settlements Stream owns the end-to-end support and continuous improvement of every settlement related application used by the U.S. and Canadian Prime Brokerage businesses.
About BNP Paribas: BNP Paribas is a leading bank ...
But that mixes two topics. Might be okay. Alternatively, we could have "About the role" for Business Overview and then another heading like "About the company" but not allowed. So we combine. Now Candidate Success Factors: we can put under "Qualifications" as a list of performance drivers. Responsibilities: list. Minimum Required Qualifications: list. Preferred Qualifications: list. Pay: salary range. Benefits: description. We should not include sections like Schedule (not present). Requirements maybe same as Qualifications? We'll use Qualifications for both minimum and preferred? Could separate into "Minimum Required Qualifications" and "Preferred Qualifications" but headings must be from list; we could use "Qualifications" for minimum and maybe "Skills" for preferred? But better to keep one Qualifications section containing both minimum and preferred, maybe split with subheadings? Not allowed subheadings? Could useto differentiate. But we need to preserve all info. Could do:
Qualifications
Minimum Required Qualifications
but h4 not allowed? Not specified. Might be okay but risk. Safer to keep as with bold? But we must not invent headings not in list. Could use inside . That's okay.
Thus:
Minimum Required Qualifications:Qualifications
Preferred Qualifications:
- ...
Similarly for Responsibilities.
Now Candidate Success Factors: maybe under "Skills"? Could be "Skills". We'll put under "Skills" heading.
Thus sections:
- About the role (Business Overview + company overview)
- Skills (Candidate Success Factors)
- Responsibilities
- Qualifications (minimum + preferred)
- Pay
- Benefits
Check if any other content: "While the description above describes our ideal candidate, we encourage applicants to apply even if they do not fully meet the complete list of qualifications noted." That's generic encouragement; could be considered boilerplate? Might be considered application instruction? It's not a direct instruction to apply, but it's encouraging. Might be considered boilerplate; we can drop.
Also "FINRA Registrations Required: N/A Not Applicable ..." drop.
Now ensure we don't repeat job title.
Now produce HTML.
We need to ensure we use
- for any list.
We'll produce:
About the role
The North American Application Support Settlements Stream owns the end-to-end support and continuous improvement of every settlement related application used by the U.S. and Canadian Prime Brokerage businesses.
BNP Paribas is a leading bank in Europe with an international reach across the US, EMEA and APAC. It has a presence in 65 countries, with nearly 190,000 employees. The bank employs over 3,500 people in offices in the US across 10 states including New York, Jersey City, Chesterbrook, PA, San Francisco, Boston, Chicago, Denver, Miami, and Washington, DC. BNP Paribas has built a strong and diversified presence to support its client base. We continue to grow and strengthen our commitment to the US market through our Corporate & Institutional Banking activities. We are one of a few non-US banks to offer a full value chain for our clients, from trading to financing, and clearing and custody in the US with the international footprint and capacity to deliver both globally and locally. Leveraging the strength of our European roots, our network can support clients in virtually every region of the world, enabling more connectivity and efficiency wherever our clients conduct business. We take pride in our expertise and our ability to adapt while constantly looking ahead to create a more sustainable world. As an international company with a global footprint, the unique cultures and viewpoints of our team members are an integral part of the fabric of BNP Paribas. We are a company with a purpose - to be a responsible and sustainable global leader. We aim to create an environment where our employees feel empowered to drive change, make an impact and be true to themselves. We employ talented individuals from a wide variety of backgrounds, locally and globally, and are inspired by our employees who help us in cultivating a diverse, equitable and inclusive workplace through initiatives such as our Diversity, Equity & Inclusion (DEI) Leadership Forum and Employee Resource Group (ERG) communities. We strive to be a workplace where all team members can grow and thrive and offer robust training, development, and mentoring opportunities to make that vision a reality. Our leaders are deeply committed to DEI and highly accessible to our employees, consistently soliciting feedback on how we can continue to support our employees to reach their highest potential.
Now Skills:Skills
- Results and Impact: Able to influence peers and team; demonstrates good judgement when making decisions of high complexity and impact; exercises appropriate autonomy in the execution and delivery of work; responsible for driving outcomes, which have meaningful effect on team or department.
- Leadership and Collaboration: Creates trust with colleagues; acts in leadership capacity for projects, processes, or programs.
- Client, Customer and Stakeholder Focus: Able to build relationships with a mix of colleagues and clients; interacts regularly with management and department leaders; demonstrates the ability to influence stakeholders at the team level.
- Compliance Culture and Conduct: Takes full responsibility for personal actions and demonstrates courage in facing problems and conflicts; perceived as a person of high moral character; upholds corporate values and displays high ethical standards.
Responsibilities
- Direct daily triage, root‑cause analysis, and resolution of incidents across Calypso, XSP, and all in‑house settlement tools logged in ServiceNow.
- Ensure 2nd‑line specialists receive clear, well‑documented work‑packages and that escalations follow the defined matrix.
- Conduct weekly post‑mortems for high‑impact incidents; drive corrective‑action plans that reduce repeat occurrences.
- Perform regular SoD and EoD reviews and remediation.
- Ensure communication handover of issues between regions.
- Supervise daily break‑reconciliation reviews, start‑of‑day, intraday, and end‑of‑day health checks on Calypso, XSP, and supporting in‑house utilities.
- Own the regional monitoring framework (Autosys, custom scripts, Dynatrace dashboards) and continuously improve alerting and automation.
- Identify repetitive support tasks across the settlement stack and develop Shell/Python/SQL scripts (or RPA bots) to automate monitoring, reconciliation, and batch‑job validation.
- Track and report efficiency gains (time, cost, error reduction).
- Serve as NA’s primary liaison with the Global Settlement‑Support Team.
- Coordinate ticket, job‑schedule, and change hand‑offs with EMEA and APAC support centers for Calypso, XSP, and all proprietary tools.
- Participate in global governance forums (Incident Review Board, Change Advisory Board).
- Produce weekly/monthly KPI dashboards (availability, incident trends, MTTR, automation coverage) for senior leadership.
- Maintain up‑to‑date SOPs, run‑books, and knowledge‑base articles in ServiceNow and internal wikis for each platform.