Risk and Controls Testing Specialist
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We must include sections only when posting has real specific content. We need to map content to appropriate headings.
We have:
- About Our Team: could be "About the role"? Actually "About Our Team" is about team, not role. Could map to "About the role"? But guidelines say use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use those headings if content matches. We have "About Our Team" content: description of team. Could fit under "About the role"? Might be okay. Or we could create a custom heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples, but we should use those headings when appropriate. We can also use other headings? 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 exact headings where applicable. So we need to map content to those.
We have:
- About the role: could include "About Our Team" and "Role Overview". Combine.
- Responsibilities: "Primary Responsibilities" content.
- Requirements: "Experience Required" (Bachelor's degree etc.) plus maybe "Desired Experience" could be Qualifications or Skills.
- Qualifications: maybe "Desired Experience" (experience within banking etc.) could be Qualifications.
- Skills: maybe list of skills like Excel, PowerPoint, communication etc.
- Benefits: Not explicitly given besides "Why Join Us?" which mentions transformational journey, team growing, delivering value. Not specific benefits like health, 401k. So we should not create Benefits section unless posting actually states them. It does not list benefits, so omit.
- Pay: we have pay range: $68,400 - $114,000 Annual. So include Pay section.
- Schedule: not mentioned, omit.
- Location: could be included in a short paragraph maybe under About the role or as metadata. The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those exact headings where applicable. So we need to map content to those. We have: - About the role: could include "About Our Team" and "Role Overview". Combine. - Responsibilities: "Primary Responsibilities" content. - Requirements: "Experience Required" (Bachelor's degree etc.) plus maybe "Desired Experience" could be Qualifications or Skills. - Qualifications: maybe "Desired Experience" (experience within banking etc.) could be Qualifications. - Skills: maybe list of skills like Excel, PowerPoint, communication etc. - Benefits: Not explicitly given besides "Why Join Us?" which mentions transformational journey, team growing, delivering value. Not specific benefits like health, 401k. So we should not create Benefits section unless posting actually states them. It does not list benefits, so omit. - Pay: we have pay range: $68,400 - $114,000 Annual. So include Pay section. - Schedule: not mentioned, omit. - Location: could be included in a short paragraph maybe under About the role or as metadata. The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata, we can include in a short
maybe under About the role or separate paragraph. We must preserve all substantive information. So we need to include all details from the posting, except boilerplate. We need to output only HTML fragment, no /, no markdown fences. We'll structure:
About the role
About Our Team ... Role Overview ... Location Wilmington, Delaware, United States of America.
But we need to keep the content: About Our Team paragraph, Role Overview paragraph. We'll combine them. ThenResponsibilities
- ... each responsibility as list items.
- for list of duties/requirements/benefits. For experience required, we can make a list.
We'll create:
Requirements
- Bachelor’s degree and a minimum of 2 years' relevant work experience, or in lieu of a degree, a combined minimum of 6 years' higher education and/or work experience, including a minimum of 2 years' relevant work experience.
- Strong understanding of control testing methodologies, including control design and operating effectiveness testing.
Qualifications
maybe. List: - Experience within banking, wealth management, institutional services, financial services, audit, compliance, risk management, or operational risk functions. - Experience using Archer or other Governance, Risk, and Compliance (GRC) platforms. - Ability to adapt to change and perform effectively in a fast-paced environment. - High proficiency in Excel, PowerPoint, and the Microsoft Office Suite. - Experience collaborating with cross-functional stakeholders and providing guidance on risk and control matters. - Exceptional interpersonal, presentation, and communication skills, with a demonstrated ability to build strong relationships and influence outcomes. - Strong analytical, critical thinking, and problem-solving skills with exceptional attention to detail. - Ability to independently manage multiple priorities while meeting deadlines and quality expectations. - Ability to work effectively within a team-oriented environment where success is measured collectively. - Ability to work effectively as part of a team-oriented environment, where success is measured collectively. (duplicate? but we keep as is.) We could combine duplicates but must preserve all info; we can keep both. Now Skills: maybe we could separate skills like Excel, PowerPoint, communication etc. But we already have them in Qualifications. The instruction says use headings like Skills. We could create a Skills section for technical skills: Excel, PowerPoint, Microsoft Office Suite, Archer/GRC. But we already have them in Qualifications. To avoid duplication, maybe we put technical skills under Skills and other under Qualifications. However we must not invent sections without content. We have content for both. Let's decide: Use Qualifications for experience and background, Skills for technical and soft skills. Thus:Qualifications
- Experience within banking, wealth management, institutional services, financial services, audit, compliance, risk management, or operational risk functions.
- Experience using Archer or other Governance, Risk, and Compliance (GRC) platforms.
- Ability to adapt to change and perform effectively in a fast-paced environment.
- Experience collaborating with cross-functional stakeholders and providing guidance on risk and control matters.
- Ability to independently manage multiple priorities while meeting deadlines and quality expectations.
- Ability to work effectively within a team-oriented environment where success is measured collectively.
- Ability to work effectively as part of a team-oriented environment, where success is measured collectively.
Skills
- High proficiency in Excel, PowerPoint, and the Microsoft Office Suite.
- Strong analytical, critical thinking, and problem-solving skills with exceptional attention to detail.
- Exceptional interpersonal, presentation, and communication skills, with a demonstrated ability to build strong relationships and influence outcomes.
Pay
The pay range for this position is $68,400.00 - $114,000.00 Annual (USD). The successful candidate’s particular combination of knowledge, skills, and experience will inform their specific compensation.
Location: we can include a short paragraph maybe under About the role or separate. Since it's minor metadata, we can fold into About the role paragraph. Now About the role content: combine About Our Team and Role Overview. Let's extract: About Our Team: "The Institutional Services & Wealth Management (ISWM) Risk team serves as the First Line of Defense, partnering closely with business leaders to strengthen risk management practices and promote a culture of accountability, transparency, and continuous improvement. Within ISWM Risk, the Risk and Control Management team is responsible for identifying, assessing, monitoring, and mitigating risk through the evaluation of control design and operating effectiveness. Our team plays a critical role in maintaining a strong and sustainable control environment that enables business growth, supports strategic objectives, and ensures compliance with regulatory expectations and enterprise risk management standards." Role Overview: "The Control Testing Analyst is a key contributor within the ISWM Risk & Control Management team and is responsible for executing a risk-based control testing program that evaluates the design and operating effectiveness of controls across Institutional Services and Wealth Management (ISWM). Reporting to the ISWM Control Testing Lead, this role partners closely with control/ process owners to assess control effectiveness, identify control gaps, and strengthen the overall risk and control environment. The ideal candidate possesses hands-on experience in control testing, control design assessments, operating effectiveness testing, Risk and Control Self-Assessments (RCSA), and issue management. This individual must be highly organized, detail-oriented, and capable of independently managing multiple testing engagements while effectively communicating results and recommendations to stakeholders." We'll combine into a paragraph(s). Could be two
under About the role section, but we need to use
for prose. We can have multiple
inside the section. Thus:
About the role
The Institutional Services & Wealth Management (ISWM) Risk team serves as the First Line of Defense, partnering closely with business leaders to strengthen risk management practices and promote a culture of accountability, transparency, and continuous improvement. Within ISWM Risk, the Risk and Control Management team is responsible for identifying, assessing, monitoring, and mitigating risk through the evaluation of control design and operating effectiveness. Our team plays a critical role in maintaining a strong and sustainable control environment that enables business growth, supports strategic objectives, and ensures compliance with regulatory expectations and enterprise risk management standards.
The Control Testing Analyst is a key contributor within the ISWM Risk & Control Management team and is responsible for executing a risk-based control testing program that evaluates the design and operating effectiveness of controls across Institutional