Risk and Controls Lead (contract)

We need to output HTML fragment with sections: About the role? The posting includes a paragraph about BNY culture at start. That could be "About the role" or maybe "About the company". The instruction: use

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 (the page already shows it) and 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 decide which sections to include based on content. Content: - Intro paragraph about BNY culture: "At BNY, our culture allows us to run our company better and enables you to grow and succeed..." This is about the company; could be "About the role" or maybe "About BNY". The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "About the role" for that intro. - Job Summary: "We are seeking a Risk and Controls Lead to support execution of key workstreams within the SOX and ICFR program. This role is responsible for leading assigned reviews end-to-end, including risk assessments, walkthroughs, controls testing, documentation refresh, issue tracking, and stakeholder coordination. This is a 4-month contract opportunity with potential for longer-term consideration based on business need and performance. The role follows a hybrid schedule with a 4-day in-office requirement in Pittsburgh, PA." This includes schedule info (hybrid schedule with 4-day in-office requirement). Also contract duration. Could be part of "About the role" or separate "Schedule". Since schedule is mentioned, we could create a Schedule section. However we need to ensure we only create Schedule if posting actually states them. It does: hybrid schedule with a 4-day in-office requirement in Pittsburgh, PA. So we can include Schedule section. - Key Responsibilities: a list of bullet points (though they are in paragraph with colon headings). We need to turn into

  • . The responsibilities include many items: SOX / ICFR Workstream Ownership, Risk Assessment & Control Identification, Controls Testing, Documentation Management, Stakeholder Coordination, Issue Management & Remediation, Audit Partnership, Management Reporting, Team Support & Coaching. Each has description after colon. We can make each as a list item with the heading bold? But we just need to output
    • for any list of duties/requirements/benefits. So we can create a Responsibilities section with
      • each item. - Qualifications: list of qualifications (5+ years experience, strong understanding, proven experience, strong auditing background, ability to manage multiple workstreams, strong written and verbal communication, Bachelor’s degree, Proficiency with Microsoft Office). Also Preferred Experience list. Could be separate sections: Requirements (maybe Qualifications) and Skills? The instruction allows headings: Requirements, Qualifications, Skills. We need to decide mapping. We have "Qualifications:" heading in posting. Then bullet list of qualifications. Then "Preferred Experience:" heading with list. Could treat "Qualifications" as required qualifications, and "Preferred Experience" as maybe "Skills" or "Preferred Qualifications". But we have limited headings; we could combine both under Qualifications (required) and maybe Skills for preferred? However the instruction says prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. But we need to check if Pay and Benefits are present. Pay: "Pay Rate Range 48 - 60 USD hourly". That's specific pay info. So we should include Pay section. Benefits: "Benefits Information Optional benefits offering include medical, dental, vision and retirement benefits via Tundra Technical Solutions." That's benefits info. So include Benefits section. Schedule: we have hybrid schedule with 4-day in-office requirement in Pittsburgh, PA. So include Schedule. We also have contract duration: 4-month contract opportunity with potential for longer-term consideration. That could be part of About the role or Schedule? Might fit in About the role. We need to avoid duplication. Also need to remove boilerplate like "Applications will be accepted on an ongoing basis..." etc. Also remove "Additional Notes", "Why Join Us" maybe? The "Why Join Us" section includes some prose about opportunity; that could be part of About the role or maybe a separate section like "About the role". But we already have About the role with intro; we could incorporate that "Why Join Us" content into About the role as well. However we must preserve all substantive information; we can't discard it. So we need to include that content somewhere. The "Why Join Us" paragraph: "This is an opportunity to join a team focused on strengthening execution quality across critical SOX and ICFR reviews. You will work closely with experienced leaders and stakeholders across Finance, Technology, and audit functions while gaining exposure to key financial reporting controls in a regulated environment. The team is looking for someone who can quickly contribute, execute testing with discipline, and help elevate overall quality. At BNY, our culture speaks for itself, check out the latest BNY news at: BNY Newsroom BNY LinkedIn Here’s a few of our recent awards: America’s Most Innovative Companies, Fortune, 2025 World’s Most Admired Companies, Fortune 2025 “Most Just Companies”, Just Capital and CNBC, 2025". This includes some fluff but also substantive info about opportunity, working with leaders, exposure, culture, awards. We should keep it. Could be part of About the role or maybe a separate section like "About the team". But we only have allowed headings; we could put it under About the role as well. We also have "Additional Notes" about contract via Tundra Technical Solutions, not full-time employment, contact Tundra for inquiries. That's metadata; we could fold into a short

        maybe under About the role or maybe drop? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it." This is minor metadata about contract via Tundra; we could include a short paragraph after About the role maybe. We also have "Benefits Information Optional benefits offering include medical, dental, vision and retirement benefits via Tundra Technical Solutions." That's benefits. We need to ensure we don't include boilerplate like "Applications will be accepted on an ongoing basis." That's application instruction; remove. Also remove "Please note that this is not a full-time employment opportunity." That's maybe metadata but could be kept? It's about contract nature; maybe we can keep in About the role. We need to output only HTML fragment. Let's structure:

        About the role

        At BNY, our culture allows us to run our company better and enables you to grow and succeed. As a leading global financial services company at the heart of the global financial system, we influence nearly 20% of the world’s investible assets. Every day, our teams harness cutting-edge AI and breakthrough technologies to collaborate with clients, driving transformative solutions that redefine industries and uplift communities worldwide. Recognized as a top destination for innovators and champions of inclusion, BNY is where bold ideas meet advanced technology and exceptional talent. Together, we power the future of finance – and this is what is all about. Join us and be part of something extraordinary.

        We are seeking a Risk and Controls Lead to support execution of key workstreams within the SOX and ICFR program. This role is responsible for leading assigned reviews end-to-end, including risk assessments, walkthroughs, controls testing, documentation refresh, issue tracking, and stakeholder coordination. This is a 4-month contract opportunity with potential for longer-term consideration based on business need and performance. The role follows a hybrid schedule with a 4-day in-office requirement in Pittsburgh, PA.

        This is an opportunity to join a team focused on strengthening execution quality across critical SOX and ICFR reviews. You will work closely with experienced leaders and stakeholders across Finance, Technology, and audit functions while gaining exposure to key financial reporting controls in a regulated environment. The team is looking for someone who can quickly contribute, execute testing with discipline, and help elevate overall quality. At BNY, our culture speaks for itself, check out the latest BNY news at: BNY Newsroom BNY LinkedIn Here’s a few of our recent awards: America’s Most Innovative Companies, Fortune, 2025 World’s Most Admired Companies, Fortune 2025 “Most Just Companies”, Just Capital and CNBC, 2025.

        Please note that this is a contract assignment with Tundra Technical Solutions to provide services to Bank of New York (BNY). This is not a full-time employment opportunity. Candidates selected for this role will be engaged as contractors for the specified duration of the project. For any inquiries regarding the terms of the contract or engagement, please contact Tundra Technical Solutions directly.

        Then Responsibilities section:

        Responsibilities

        • SOX / ICFR Workstream Ownership: Own end-to-end delivery of assigned SOX and ICFR reviews, including planning, walkthroughs, testing, issue tracking, and reporting against program milestones
        • Risk Assessment & Control Identification: Perform and coordinate risk assessments to identify significant processes, key controls, and changes in systems, products, or business activities impacting financial reporting risk
        • Controls Testing: Evaluate the design and operating effectiveness of key SOX manual controls through evidence review, exception analysis, and clear documentation of conclusions
        • Documentation Management: Lead refreshes of narratives, risk and control matrices, flowcharts, and control inventories to ensure documentation remains current, complete, and audit ready
        • Stakeholder Coordination: Work closely with control owners, Finance, Technology, and business partners to schedule walkthroughs, obtain evidence, resolve questions, and complete testing on time
        • Issue Management & Remediation: Identify control gaps or weaknesses, assess potential impact, support remediation planning, and validate corrective actions
        • Audit Partnership: Serve as a key liaison for internal and external auditors, providing high-quality support and clear communication throughout the audit lifecycle
        • Management Reporting: Prepare concise updates on progress, risks, issues, and remediation status, escalating matters where appropriate
        • Team Support & Coaching: Provide day-to-day guidance to junior team members on testing methodology, documentation standards, and stakeholder engagement
        Qualifications section:

        Qualifications

        • 5+ years of experience in SOX testing, internal audit, external audit, finance controls, controllership, or risk and controls roles
        • Strong understanding of SOX, ICFR, internal controls, and financial reporting processes in a regulated environment
        • Proven experience conducting controls testing, leading walkthroughs, documenting processes, evaluating exceptions, and producing high-quality working papers
        • Strong auditing background with the ability to independently execute testing once shown the process
        • Ability to manage multiple workstreams and deadlines with strong analytical, organizational, and execution skills