Jobs · Management · New York

Middle Office - Direct Lending Loan Operations Vice President

JPMorganChase · New York, NY · 1 mo ago
On-siteManagementFull-time
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only sections that have real specific content. We need to parse the job description. We have: Job Description text: includes description of role, responsibilities, required qualifications, capabilities, and skills, preferred qualifications, capabilities, and skills, About Us, About The Team. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "About Us" maybe? The instruction says we should include sections only when posting has real specific content. "About Us" is generic corporate description; maybe we should not include it as a section because it's not specific to the role? The instruction says: "Prefer a few substantive sections over many thin ones." The sections we can include: About the role (maybe from first paragraph), Responsibilities, Requirements (maybe combine Required Qualifications, Capabilities, And Skills), Skills (maybe separate?), Benefits, Pay, Schedule. But we need to see if posting actually states Benefits, Pay, Schedule. It mentions "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, paid in the form of cash and/or forfeitable equity... 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." So there is some info about benefits and pay (though not specific numbers). The instruction says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits and pay generically, so we can include Benefits and Pay sections. Schedule is not mentioned, so we should not include Schedule. We should not repeat the job title as a heading. The job title is "Vice President, Fixed Income Middle Office" maybe. Not needed. We need to output only HTML fragment, no /, no markdown fences. We need to use

for section headings. Use
  • for any list of duties/requirements/benefits, and

    for prose. We need to preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include all details from responsibilities, qualifications, etc. But we can format them as lists. We need to remove duplicated lines, boilerplate like EEO statements, etc. Also remove "About Us" maybe? The instruction says we can include sections only when posting has real specific content. "About Us" is generic but still specific to JPMorganChase. Might be considered boilerplate? It's describing the company, not role-specific. Likely we should omit it. Similarly "About The Team" maybe also generic but could be considered relevant? It describes J.P. Morgan Asset & Wealth Management. Might be considered not specific to the role. Safer to omit. Thus sections: About the role (maybe from first paragraph describing role), Responsibilities, Required Qualifications, Capabilities, And Skills (maybe combine as Requirements), Preferred Qualifications, Capabilities, And Skills (maybe as Preferred Qualifications), Benefits, Pay. We need to decide heading names: The instruction list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use those headings as appropriate. For Required Qualifications, we could use "Requirements". For Preferred Qualifications, maybe "Preferred Qualifications" but not in list; we could use "Qualifications" for required and maybe "Preferred Qualifications" as a subsection? But instruction says use those headings; we can also add other headings if needed? It 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 exclusive list. But we should prefer those. We could have "Required Qualifications" under "Requirements". And "Preferred Qualifications" maybe under "Qualifications"? But that could be confusing. Better to have "Requirements" for required, and "Preferred Qualifications" as a separate heading maybe not in list but still okay? The instruction says use those headings for section headings; it doesn't forbid other headings, but says "Use

    for section headings (e.g. ...)". Likely they expect us to use those headings where applicable. For preferred qualifications, we could still use "Qualifications" heading and include both required and preferred? But that would mix. Might be better to have "Requirements" for required, and "Preferred Qualifications" as a separate heading but still using

    . The instruction didn't forbid other headings, just gave examples. I'll include both. We need to ensure we don't include filler like "commensurate with experience". Not present. Now extract content. First paragraph: "The Fixed Income Middle Office sits at the intersection of Portfolio Management, Trading, Operations, Technology, Risk, and Controls. It provides critical trade lifecycle support, data integrity, process oversight, and operational excellence to safeguard portfolio accuracy and enable the front office to focus on investment decisions. As a Vice President on the Fixed Income Middle Office team, you will support our Private Credit / Direct Lending platform. This role is a Middle Office SME and operational point of contact for Direct Lending, providing end-to-end oversight of the trade/lifecycle process, reconciliations, issue escalation, and governance of the servicing model to ensure timely execution and strong controls as the platform scales. The Direct Lending platform is entering a ramp period with increasing deployment and borrower count, driving non-linear increases in BAU lifecycle events, reconciliations, and exception management needs. This role adds experienced coverage to preserve service levels and strengthen controls as BAU lifecycle volume, reconciliations, and exception management scales." That's the role description. We'll put under

    About the role

    with

    containing that. Next responsibilities: list after "Job Responsibilities". It's a long sentence with many items separated by periods? Actually it's: "Own and oversee lifecycle event processing and throughput during periods of high concurrency, including payments, notices, rate resets, amendments, consents, drawdowns, repayments, covenant package coordination, and delayed settlements.Provide settlement support for funding, paydowns, and fees, partnering with internal and external stakeholders to resolve breaks and exceptions.Lead cash, position, and accrual reconciliation oversight, including break investigation, escalation, closure discipline, and governance cadence.Drive exception management and escalation ownership, coordinating across Middle Office partners and stakeholders to ensure timely resolution and adherence to controls.Deliver operational inputs for reporting and client servicing, recognizing the impact of multiple vehicles on reporting variants, cutoffs, and formats.Support onboarding for new SMA, Fund-of-One accounts, new fund launches, and new product builds, including account setup, connectivity, standing instructions, reconciliation model, reporting specifications, procedures, approvals, target operating model, lifecycle playbook, controls, exception taxonomy, UAT/testing, governance signoffs, and training.Partner on material operating model changes, focusing on requirements, design, testing, runbooks, cutover, and monitoring to reduce operational risk during scale.Act as a subject matter expert for training and knowledge transfer as staffing scales, helping institutionalize best practices and consistent oversight.Execute daily oversight activities, including pipeline review, monitoring notices and inbox, lifecycle event preparation, pre- and post-cutoff reconciliation, and documentation and escalation of unresolved issues. Lead or participate in weekly oversight with the servicing provider to review pipeline, cash breaks, lifecycle events, and unresolved issues, ensuring actions are owned and followed through.Drive monthly oversight, reporting, and meeting cadence, including review of portfolio and cash accounts, document management, reconciliation outcomes, unresolved breaks, and process improvement items.Own and execute governance and controls deliverables, such as KRIs, procedures, and audit readiness, continuously enhancing procedures to support scale." We need to split into list items. Each sentence seems a responsibility. We'll create

    • for each. Now Required Qualifications, Capabilities, And Skills: after "Required Qualifications, Capabilities, And Skills". It's a paragraph: "Middle Office / loan operations experience supporting private credit and/or direct lending lifecycle processing (funding, paydowns, interest/payment support, rate resets, notices, amendments/consents).Strong reconciliation and break management expertise (cash/position/accrual), including root-cause analysis, escalation, and closure governance. Proven ability to run BAU while simultaneously executing onboarding/build work in deadline-driven ramp periods. Strong controls mindset (procedures, KRIs, audit readiness) and comfort operating in a high-accountability environment. Stakeholder management skills across operations, front office/business, and external parties (agents/custodians/vendors as applicable)." We'll split into list items. Preferred Qualifications, Capabilities, And Skills: after that: "Direct experience onboarding new operating perimeters (new clients/vehicles/products) and building scalable playbooks, controls, and exception taxonomies is strongly preferred. Experience overseeing a third-party servicing model and operating across multiple platforms during integration/transition periods is preferred." We'll list. Benefits: from About Us: "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, paid in the form of cash and/or forfeitable equity, awarded in recognition of individual achievements and contributions. 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." We need Benefits section: list of benefits. Also Pay section: maybe we separate pay info. The instruction says we can have Pay and Benefits sections. So we could put base salary and commission info under Pay, and benefits list under Benefits. Thus:

      Pay

      Base salary determined based on the role, experience, skill set and location. Eligible roles may receive commission-based pay and/or discretionary incentive compensation, paid in the form of cash and/or forfeitable equity, awarded in recognition of individual achievements and contributions.

      Benefits

      • comprehensive health care coverage
      • on-site health and wellness centers
      • retirement savings plan
      • backup childcare
      • tuition reimbursement
      • mental health support
      • financial coaching
      • and more
      We should not include "Additional details about total compensation and benefits will be provided during the hiring process." That's boilerplate; we can drop. Now About The Team and About Us we drop. Now ensure we didn't repeat job title as heading. Not. Now output HTML fragment. We need to ensure we only output the HTML, no extra text. Let's construct:

      About the role

      The Fixed Income Middle Office sits at the intersection of Portfolio Management, Trading, Operations, Technology, Risk, and Controls. It provides critical trade lifecycle support, data integrity, process oversight, and operational excellence to safeguard portfolio accuracy and enable the front office to focus on investment decisions. As a Vice President on the Fixed Income Middle Office team, you will support our Private Credit / Direct Lending platform. This role is a Middle Office SME and operational point of contact for Direct Lending, providing end-to-end oversight of the trade/lifecycle process, reconciliations, issue escalation, and governance of the servicing model to ensure timely execution and strong controls as the platform scales. The Direct Lending platform is entering a ramp period with increasing deployment and borrower count, driving non-linear increases in BAU lifecycle events

Similar jobs