Director, Finance Operations Tech

We need to output HTML fragment with sections: About the role? Actually the posting includes "Company Profile", "What You’ll Do In The Role", "What You’ll Bring To The Role", "What You Can Expect From Morgan Stanley". Also includes "Telecommuting permitted up to 2 days per week." That's schedule info. Also includes "Expected base pay rates for the role will be between $166,000 and $166,000 per year". That's pay info (though it's same number). Should we include Pay section? The rule: include a section ONLY when 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. Here we have specific pay: $166,000 to $166,000 per year (though it's same). That's specific. So we can include Pay section. Schedule: "Telecommuting permitted up to 2 days per week." That's schedule info. So include Schedule section. Benefits: The posting mentions "some of the most attractive and comprehensive employee benefits and perks in the industry." That's vague but still mentions benefits. However it's not specific list. The rule: prefer a few substantive sections over many thin ones. Benefits section would be thin (just a statement). Could we omit Benefits? The rule says never create Benefits sections unless posting actually states them. It does state benefits generically. But is that considered substantive? Might be considered filler. I'd lean to omit Benefits to avoid thin section. However we could include Benefits with that sentence. But the rule: "Prefer a few substantive sections over many thin ones." So maybe we omit Benefits. Also we have "What You Can Expect From Morgan Stanley" includes description of firm, values, etc. That could be About the role? Actually "About the role" is not present; we have company profile and what you can expect. Could treat "Company Profile" as About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have: - About the role: Could be company profile + what you can expect? But "About the role" is generic description of role. We have "What You’ll Do In The Role" which is responsibilities. So we can map that to Responsibilities. - "What You’ll Bring To The Role" is requirements/qualifications/skills. We need to split into Requirements, Qualifications, Skills maybe. The posting lists education requirement, years experience, and a long list of skills. We could put education and years under Requirements (or Qualifications). The list of skills under Skills. - Pay: we have base pay range. - Schedule: telecommuting up to 2 days per week. - Benefits: maybe omit. We also need to include any other sections like "Qualifications". Could combine education and experience under Qualifications. Requirements could be the years of experience? Hmm. Better: Use headings: Responsibilities, Requirements, Skills, Pay, Schedule. Also maybe About the role (company profile). Let's include About the role using company profile paragraph. Thus sections:

About the role

Company profile paragraph.

Responsibilities

• ... list of duties from "What You’ll Do In The Role"

Requirements

Master’s in Computer Science, Computer Engineering, or related field; two (2) years of experience in the position offered or as an Associate, Analyst, Software Developer, Computer Systems Engineer, or closely related occupation.

Skills

• list of skills from "What You’ll Bring To The Role" after the experience requirement.

Pay

Expected base pay rates for the role will be between $166,000 and $166,000 per year at the commencement of employment.

Schedule

Telecommuting permitted up to 2 days per week.

We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, equal opportunity, scam warning, application instructions, navigation, cookie, legal. Also remove the "To learn more about our offices across the globe, please copy and paste ..." and the EEO link. Also remove the "Expected base pay rates ... However, base pay if hired will be determined on an individualized basis and is only part of the total compensation package..." That's extra but still about pay; we can keep the first sentence about base pay range, but the rest is filler? It says "However, base pay if hired will be determined on an individualized basis and is only part of the total compensation package..." That's still pay info but somewhat generic. Might be okay to include but could be considered filler. The rule: never emit a heading followed by filler/placeholder text. The Pay section would have specific range then extra sentence. That's not filler; it's additional detail. Could keep it. But we might trim to just the range to keep concise. However we must preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep all substantive info. The extra sentence about base pay being individualized and part of total compensation is substantive. So we should include it. Thus Pay section:

Expected base pay rates for the role will be between $166,000 and $166,000 per year at the commencement of employment. However, base pay if hired will be determined on an individualized basis and is only part of the total compensation package, which, depending on the position, may also include commission earnings, incentive compensation, discretionary bonuses, other short and long-term incentive packages, and other Morgan Stanley sponsored benefit programs.

We should remove the "TBD" after that line. There's a "TBD" at end of that sentence? Actually the text: "... and other Morgan Stanley sponsored benefit programs.TBD". So there's a TBD after a period. That's placeholder; we should drop TBD. So we end before TBD. Now schedule: "Telecommuting permitted up to 2 days per week." That's it. Now responsibilities: need to extract bullet points from "What You’ll Do In The Role". It's a paragraph with many sentences. We need to turn into list items. We should preserve all substantive information; we can split by sentences or logical clauses. Let's parse: "What You’ll Do In The Role Morgan Stanley Services Group, Inc. seeks an Director, Finance Operations Risk Tech in New York, New York to conduct the architecture, design, and delivery of enterprise-scale cloud-native platforms, market data infrastructure, and Agentic solutions. Drive platform modernization efforts that improve operational efficiency, developer productivity, model governance, and business process automation across front-office, risk, and finance functions. Work cross-functional projects for strategic platform initiatives. Partner across organizations to align delivery milestones, and business priorities while ensuring measurable outcomes such as workflow automation, improved data quality, reduced operational risk, and faster time-to-market. Collaborate closely with stakeholders to define target-state architectures for official End-of-Day (EOD) market data distribution. Lead analysis of current-state processes, identify control and data-quality gaps, perform risk assessments, and develop strategic solutions while supporting enterprise cost-efficiency and scalability objectives. Define and govern architecture standards, platform frameworks, and control models supporting FRAME Policy, Daily Marking Policy requirements, market input consistency and enterprise market data governance. Establish reusable design patterns for official EOD marking, milestone management, data lineage, entitlement controls, and API-based consumption models that can be consistently extended across asset classes. Lead the implementation of FRAME on DAL, enabling Risk Technology’s FrameHub platform to provide consistent, governed, and auditable official EOD marks consumed by enterprise Risk, Valuation, and downstream processes. Oversee development of FRAME APIs, milestone orchestration, DAL persistence services, and strategic integrations that improve data availability, simplify onboarding, and accelerate decommissioning of legacy market-data infrastructure. Guide engineering teams in the development and adoption of AI/Agentic solutions. Drive delivery of intelligent agents and workflow automation capabilities for model review document generation, evaluation and scoring workflows, governance controls, and software delivery lifecycle optimization. Manage and mentor engineering teams responsible for cloud-native platforms, market data services, and AI-enabled applications. Establish best practices in software engineering, solution architecture, DevSecOps, platform reliability, observability, and AI adoption while fostering technical excellence and leadership across multiple strategic initiatives. Establish engineering governance, SDLC controls, and production management practices that improve delivery predictability, system resiliency, audit readiness. Lead modernization initiatives. Support organizational growth and balance capacity against strategic priorities, business transformation programs, modernization initiatives, and AI platform." We need to make list items. Could break each sentence as

. Ensure we keep all info. Now Skills: list from "What You’ll Bring To The Role" after experience requirement. The text: "Requires two (2) years of experience with the following skills:Object-oriented programmingWorkflow managementLarge data processingSystem integrationUser Interface developmentAutomated and user testingScriptingData structuresBusiness related software developmentSoftware development life cycleMicro-services architectureBusiness Process Model and Notation, Decision Model and Notation solutioningJava Backend DevelopmentRelational and non-relational databaseLinux/Unix app developmentAgile Project DevelopmentPython application development and data processingFunctional programmingData visualization" Note there is no punctuation between items; we need to split appropriately. Likely each skill separated by line break in original but lost spaces. We need to infer list: Object-oriented programming, Workflow management, Large data processing, System integration, User Interface development, Automated and user testing, Scripting, Data structures, Business related software development, Software development life cycle, Micro-services architecture, Business Process Model and Notation, Decision Model and Notation solutioning, Java Backend Development, Relational and non-relational database, Linux/Unix app development, Agile Project Development, Python application development and data processing, Functional programming, Data visualization. We'll create

for each. Now Requirements: includes education and experience. The text: "Requires a Master’s in Computer Science, Computer Engineering, or a related field.Requires two (2) years of experience in the position offered or as an Associate, Analyst, Software Developer, Computer Systems Engineer, or a closely related occupation". We'll combine. Now About the role: Company Profile paragraph: "Morgan Stanley is a leading global financial services firm providing a wide range of investment banking, securities, investment, and wealth management services. The Firm's employees serve clients worldwide, including corporations, governments, and individuals from more than 1,200 offices in 43 countries. In Technology, we leverage innovation to build the connections and capabilities that power our Firm, enabling our clients and colleagues to redefine markets and shape the future of our communities." We'll put that in

. Now we must ensure we don't include any boilerplate like EEO, scam warning, etc. Also remove the "To learn more about our offices across the globe, please copy and paste https://www.morganstanley.com/about-us/global-offices into your browser." and the EEO link. Also remove the "What You Can Expect From Morgan Stanley" paragraph? Actually we used that for About the role? We used company profile only. The "What You Can Expect From Morgan Stanley" includes values, benefits, etc. That could be considered Benefits section but we omitted. However we might want to include some of that as About the role? But we already have About the role as company profile. The "What You Can Expect" is more about the firm culture, values, benefits. Could be considered Benefits or About the company. Since we omitted Benefits, we could incorporate that into About the role? But we must not invent sections. The rule: include a section ONLY when posting has real, specific content for it. The "What