Regulatory Change Management (RCM) Operational Readiness Support Analyst

We need to output HTML fragment with sections: About the role? Actually we have job description content. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We have: Job Description includes duties (Day to Day job Duties). That's responsibilities. We have Basic Qualifications (requirements). Also Nice to Have (maybe qualifications/skills). We have Travel mention, Degree. We have Pay: starting pay range $125,000-$165,000. Also mention incentive compensation. We have Benefits: list of benefits. We have Schedule? Not mentioned. No schedule info. So we should not include Schedule section. We have About the role? Could be a brief overview: maybe from first paragraph: "NTT DATA strives to hire exceptional..." but that's generic. The posting includes a description of the role in the Job Description. Could treat "About the role" as a short paragraph summarizing role. But we must not invent content. We could use the first paragraph after Job Title? The posting includes: "We are currently seeking a Regulatory Change Management (RCM) Operational Readiness Support Analyst to join our team in Warren, New Jersey (US-NJ), United States (US)." That's about the role. Also "NTT DATA strives to hire exceptional..." is generic company statement. Might be considered boilerplate? It's not specific to role. Probably we should include a short About the role using that sentence. We must not repeat job title as heading. So we will not put the title as heading. We need to include

headings for each section we include. We need to use

• for any list of duties/requirements/benefits. We need to use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We need to drop Job ID/requisition numbers as headings; fold minor metadata into short

  or drop it. So we can include a short paragraph with location maybe. Let's extract substantive content: - Location: Warren, New Jersey (US-NJ), United States (US). Could be included in About the role paragraph. - Role purpose: Support design, documentation, implementation of RCM operating processes to ensure operational readiness and successful transition to BAU. - Day to day duties list (bulleted). We'll convert each bullet to

• . - Develop and maintain RCM documentation... - Create training materials... - Assist in operational readiness assessments... - Support change enablement activities... - Partner with Compliance, Legal, Risk, Operations, and Technology teams... - Support implementation, go-live planning, and post-go-live stabilization... - Coordinate with external vendors and internal stakeholders... - Monitor and track documentation updates... - Contribute to development of auditable and sustainable RCM processes... That's duties. - Basic Qualifications: list each bullet. We need to capture each qualification bullet. Let's list them: - Minimum 3+ years of experience in Regulatory Change Management, Compliance Operations, Risk Management, Governance, or related regulatory programs. - Minimum 3+ years of experience creating and maintaining business documentation, including policies, procedures, operating models, process maps, and training materials. - Experience supporting operational readiness, business process implementation, change management, or BAU transition activities. - Strong understanding of regulatory compliance frameworks, governance structures, and operational control environments. - Experience working with cross-functional stakeholders including Compliance, Legal, Risk, Operations, and Technology teams. - Strong business writing, documentation, and communication skills with the ability to translate complex regulatory and operational requirements into clear, user-friendly documentation. - Experience supporting platform onboarding, user training, process adoption, and change enablement initiatives. - Knowledge of process improvement methodologies, workflow documentation, and operational controls. - Strong organizational skills with the ability to manage multiple deliverables, timelines, and stakeholder expectations. - Proficiency in Microsoft Office Suite, including Word, PowerPoint, Excel, and Visio or other process-mapping tools. - Travel: This position may require occasional travel for stakeholder meetings, workshops, training sessions, and program-related activities. - Degree: Bachelor’s degree in Business Administration, Finance, Risk Management, Compliance, Law, Public Policy, or a related discipline. - Nice to Have; Experience within Financial Services or other highly regulated industries. - Familiarity with Regulatory Change Management platforms, workflow tools, or GRC solutions. - Knowledge of regulatory implementation programs, compliance transformation initiatives, or enterprise governance frameworks. - Experience supporting process design, target operating model development, or control framework implementation. - Certifications related to Compliance, Risk Management, Project Management, Business Analysis, or Change Management. - Experience working with third-party vendors and enterprise technology implementation programs. We could separate Nice to Have as part of Qualifications or Skills. The instruction: Use headings for Requirements, Qualifications, Skills. We need to decide what goes where. We have Basic Qualifications (minimum). Could be Requirements. Nice to Have could be Qualifications or Skills. We also have specific skills like business writing, documentation, communication, process improvement methodologies, organizational skills, proficiency in MS Office. We could put Requirements = Basic Qualifications (minimum). Qualifications = Nice to Have (preferred). Skills = specific skill bullets (business writing, etc). But we must not create thin sections; we need substantive content. We have enough for each. Pay: we have starting pay range $125,000-$165,000, plus incentive compensation. Benefits: list of benefits. Schedule: none. About the role: we can include a short paragraph: "We are currently seeking a Regulatory Change Management (RCM) Operational Readiness Support Analyst to join our team in Warren, New Jersey (US-NJ), United States (US)." plus maybe the NTt DATA strives to hire... but that's generic; maybe we can include it as part of About the role? It's not specific to role but it's about company. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The NTt DATA strives to hire exceptional... is not exactly boilerplate but it's a generic statement about hiring. Could be considered fluff but it's substantive? It's about the company's hiring philosophy. Might be okay to include but it's not role-specific. Safer to include only the role-specific sentence. Thus About the role paragraph: "We are currently seeking a Regulatory Change Management (RCM) Operational Readiness Support Analyst to join our team in Warren, New Jersey (US-NJ), United States (US)." Now we need to output HTML fragment only. Structure:

  About the role

  We are currently seeking a Regulatory Change Management (RCM) Operational Readiness Support Analyst to join our team in Warren, New Jersey (US-NJ), United States (US).

  Responsibilities

  • Support the design, documentation, and implementation of Regulatory Change Management (RCM) operating processes to ensure operational readiness and successful transition to Business as Usual (BAU).
  • Develop and maintain RCM documentation, including policies, procedures, operating models, standards, process flows, controls, and supporting governance artifacts.
  • Create training materials, user guides, communications, and knowledge transfer documentation to support stakeholder adoption and platform onboarding.
  • Assist in operational readiness assessments, process reviews, and gap analyses to ensure governance, controls, and operating procedures are fully established prior to go-live.
  • Support change enablement activities, including stakeholder engagement, training coordination, and readiness tracking across impacted business functions.
  • Partner with Compliance, Legal, Risk, Operations, and Technology teams to translate regulatory requirements and target operating models into executable business processes.
  • Support implementation, go-live planning, and post-go-live stabilization activities for RCM processes, tools, and governance frameworks.
  • Coordinate with external vendors and internal stakeholders to ensure process documentation, workflows, system functionality, and operating procedures are aligned.
  • Monitor and track documentation updates, governance requirements, action items, and readiness milestones to support program objectives.
  • Contribute to the development of auditable and sustainable RCM processes that support regulatory compliance, governance oversight, and operational effectiveness.

  Requirements

  • Minimum 3+ years of experience in Regulatory Change Management, Compliance Operations, Risk Management, Governance, or related regulatory programs.
  • Minimum 3+ years of experience creating and maintaining business documentation, including policies, procedures, operating models, process maps, and training materials.
  • Experience supporting operational readiness, business process implementation, change management, or BAU transition activities.
  • Strong understanding of regulatory compliance frameworks, governance structures, and operational control environments.
  • Experience working with cross-functional stakeholders including Compliance, Legal, Risk, Operations, and Technology teams.

  Qualifications

  • Experience within Financial Services or other highly regulated industries.
  • Familiarity with Regulatory Change Management platforms, workflow tools, or GRC solutions.
  • Knowledge of regulatory implementation programs, compliance transformation initiatives, or enterprise governance frameworks.
  • Experience supporting process design, target operating model development, or control framework implementation.
  • Certifications related to Compliance, Risk Management, Project Management, Business Analysis, or Change Management.
  • Experience working with third-party vendors and enterprise technology implementation programs.

  Skills

  • Strong business writing, documentation, and communication skills with the ability to translate complex regulatory and operational requirements into clear, user-friendly documentation.
  • Experience supporting platform onboarding, user training, process adoption, and change enablement initiatives.
  • Knowledge of process improvement methodologies, workflow documentation, and operational controls.
  • Strong organizational skills with the ability to manage multiple deliverables, timelines, and stakeholder expectations.
  • Proficiency in Microsoft Office Suite, including Word, PowerPoint, Excel, and Visio or other process-mapping tools.

  Pay

  The starting pay range for this role is $125,000‑$165,000. Actual compensation will depend on a number of factors, including the candidate’s relevant experience, technical skills, and other qualifications. This position may also be eligible for incentive compensation based on individual and/or company performance.

  Benefits

  • Medical, dental, and vision insurance with an employer contribution
  • Flexible spending or health savings account
  • Life and AD&D insurance
  • Short and long term disability coverage
  • Paid time off
  • Employee assistance
  • Participation in a 401k program with company match
  • Additional voluntary or legally‑required benefits
  We should not include Schedule section. Check for any duplicated lines: we have not included any. Check for any boilerplate: we omitted NTT DATA description, EEO, etc. Check for any minor metadata like Job ID: we omitted. Check for Travel: we included Travel under Requirements? Actually Travel is a bullet under Basic Qualifications. We placed Travel bullet under Requirements? We didn't include Travel explicitly. Should we include Travel as part of Requirements or maybe as a separate bullet under Requirements. The Travel bullet is: "Travel: This position may require occasional travel for stakeholder meetings, workshops, training sessions, and program-related activities." This is a qualification/requirement. We should include it under Requirements (or Qualifications). Since it's a condition, we can add to Requirements list