Jobs · Finance · New Jersey

J. P. Morgan Wealth Management - Regulatory Programs and Monitoring Associate

JPMorganChase · Jersey City, NJ · 4 wk ago
On-siteFinanceFull-time
The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use
  • for lists of duties/requirements/benefits, and

    for prose - Do NOT repeat the job title as a heading (page already shows it) - 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 - 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") - 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 Now, let me parse the job posting: 1. First paragraph: "Join a team at the forefront..." - This is an "About the role" or introductory prose. 2. Second paragraph: "As an Associate on the Regulatory Program and Transformation Monitoring Team..." - More about the role. 3. Third paragraph: "In addition to monitoring responsibilities..." - More about the role. 4. "Job Responsibilities" - list of bullet points (12 items) 5. "Required Qualifications, Capabilities, And Skills" - list of bullet points (10 items) 6. "Preferred Qualifications, Capabilities, And Skills" - list of bullet points (7 items) 7. "About Us" - prose about Chase 8. "About The Team" - prose about Consumer & Community Banking division Also there's a paragraph about total rewards package, benefits, equal opportunity employer, etc. That's boilerplate EEO/benefits description. The rules say: remove EEO/equal-opportunity boilerplate. Also "never create Pay/Schedule/Benefits sections unless the posting actually states them". The posting does mention "We offer a competitive total rewards package including base salary determined based on the role, experience, skill set and location. Those in eligible roles may receive commission-based pay and/or discretionary incentive compensation... We also offer a range of benefits and programs to meet employee needs, based on eligibility. These benefits include comprehensive health care coverage, on-site health and wellness centers, a retirement savings plan, backup childcare, tuition reimbursement, mental health support, financial coaching and more. Additional details about total compensation and benefits will be provided during the hiring process." This is generic boilerplate, not specific to this role. The rules say: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state them but in a generic way. However, the rule says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". This is generic filler. I think we should not include a Benefits/Pay section because it's not specific to this role. The posting says "Additional details about total compensation and benefits will be provided during the hiring process." So it's not specific. Also the EEO statement is boilerplate, remove. The "About Us" and "About The Team" are company/team descriptions. Should we include them? The rules say "Preserve ALL substantive information". They are substantive about the company and team. But they are not typical sections like "About the role", "Responsibilities", etc. The allowed headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "About Us" and "About The Team" are not in that list. However, the rule says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests those are examples, not exhaustive. But we should only include sections when the posting has real, specific content for it. The posting has "About Us" and "About The Team" sections. They are specific to the company and team. I think we can include them as sections, maybe "About the Company" and "About the Team". But the rule says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings. However, the instruction: "include a section ONLY when the posting has real, specific content for it". The posting does have "About Us" and "About The Team". So we can include them. But note: the job description starts with "Job Description" then "Join a team...". That's the role description. Then "Job Responsibilities". Then "Required Qualifications, Capabilities, And Skills". Then "Preferred Qualifications, Capabilities, And Skills". Then "About Us". Then "About The Team". Then boilerplate. We need to map to appropriate headings. Let's decide: - "About the role" for the introductory paragraphs (first three paragraphs). - "Responsibilities" for the Job Responsibilities list. - "Requirements" for Required Qualifications (or "Qualifications"? The rule says "Requirements, Qualifications, Skills". We have Required and Preferred. Could combine into "Qualifications" with sub-lists? But the rule says use
    • for any list. We can have two subsections: "Required Qualifications" and "Preferred Qualifications". But the heading examples include "Requirements" and "Qualifications". Might be better to have "Required Qualifications" and "Preferred Qualifications" as separate sections with h3? Or combine under "Qualifications" with two lists. The rule says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we can't have "Required Qualifications" and "Preferred Qualifications". But to keep it simple, maybe have "Qualifications" heading and then two sub-lists with maybe

      ? But the rule only mentions

      for section headings. It doesn't mention

      . Safer to use

      for each major section. The posting has two distinct qualification sections. I'll make them separate sections: "Required Qualifications" and "Preferred Qualifications". That seems appropriate. - "About the Company" for "About Us". - "About the Team" for "About The Team". But the rule says "Prefer a few substantive sections over many thin ones." Having many sections is okay if they have content. Now, the boilerplate about total rewards, benefits, EEO, etc. should be removed. Also, there is no Job ID or requisition number in the posting. Good. Now, let's write the HTML. Structure:

      About the Role

      Join a team at the forefront of regulatory programs and transformation, where you'll help drive effective execution, strengthen ongoing monitoring, and support initiatives that enhance a strong risk and control environment. This role offers the opportunity to collaborate across teams, provide meaningful insights, and contribute to programs that support sustainable business practices and regulatory commitments.

      As an Associate on the Regulatory Program and Transformation Monitoring Team, you will support the development, execution, and ongoing management of regulatory monitoring solutions. You will help produce oversight reporting, identify and escalate observations, coordinate follow-up activities, and support enhancements to processes, controls, reporting, and governance.

      In addition to monitoring responsibilities, you will support regulatory programs and projects across the broader team. You will apply foundational project-management disciplines to help organize work, track deliverables, coordinate stakeholders, identify risks and dependencies, and communicate progress. The role is well suited for someone who has basic project-management experience, demonstrates strong organizational and follow-through skills, and is interested in developing the capabilities necessary to independently manage projects or workstreams over time.

      Responsibilities

      • Support regulatory monitoring activities by developing an understanding of the processes, procedures, controls, and technology used to meet regulatory requirements.
      • Partner with monitoring owners and stakeholders to design, develop, and maintain dashboards, reports, controls, and other solutions that identify potential gaps or weaknesses in regulatory frameworks.
      • Analyze data and business processes to identify trends, themes, challenges, and improvement opportunities, and communicate observations clearly.
      • Produce accurate and timely reporting that enables senior management and control partners to oversee the effectiveness of regulatory operating processes.
      • Identify and escalate monitoring observations, coordinate follow-up activities, track items through resolution, and support corrective actions as needed.
      • Execute monitoring lifecycle activities and governance checkpoints using appropriate process improvement, organizational design, change management, communication, and training strategies.
      • Develop and maintain procedures, job aids, process documentation, training materials, monitoring roadmaps, and required records.
      • Support regulatory programs, projects, and workstreams by maintaining project plans, milestone schedules, trackers, action logs, decision logs, and related materials.
      • Coordinate project meetings, prepare agendas and supporting materials, document decisions and action items, and follow up with stakeholders on commitments.
      • Monitor project milestones, deliverables, dependencies, risks, issues, and outstanding decisions, and escalate concerns in a timely manner.
      • Deliver project updates and status reporting while coordinating across business, functional, and control partners to resolve open items and maintain progress against agreed objectives.

      Required Qualifications

      • Three or more years of relevant experience in project management, regulatory programs, process improvement, controls, compliance, supervision, operations, data analytics, or a related field.
      • Foundational knowledge of project-management disciplines, including project planning, milestone and action tracking, meeting coordination, status reporting, risk and issue identification, and stakeholder follow-up.
      • Demonstrated ability to organize multiple priorities, maintain accurate project or monitoring documentation, and follow assignments through completion.
      • Strong analytical and logical-thinking skills, with the ability to understand data, identify trends and themes, and evaluate complex business processes.
      • Ability to communicate information clearly and concisely, both verbally and in writing, for audiences ranging from working teams to senior stakeholders.
      • Strong attention to detail, sound judgment, intellectual curiosity, and a willingness to ask questions and learn.
      • Ability to work collaboratively across business, functional, and control groups and build effective relationships with stakeholders.
      • Ability to operate effectively in a dynamic environment, manage changing priorities, and bring structure to ambiguous assignments.
      • Willingness to learn and apply the team's project-management methodologies, governance practices, and tools.
      • Proficiency with Microsoft Office, including Excel and PowerPoint, with the ability to learn additional project, reporting, data, and workflow tools as needed.

      Preferred Qualifications

      • Bachelor's degree or equivalent relevant experience.
      • Experience in financial services, regulatory change, risk, controls, compliance, supervision, operations, or a related environment.
      • Experience supporting projects or workstreams involving multiple business and functional stakeholders.
      • Experience preparing dashboards, management reporting, procedures, process flows, presentations, or governance materials.
      • Familiarity with wealth management, brokerage, banking, or related financial-services products and operating models.
      • Interest in building deeper expertise in wealth management, regulatory programs, monitoring, and project management.

      About the Company

      Chase is a leading

Similar jobs