Lead Domain Architect (Investment & Operations)

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We need to parse the job description. Given text: "Job Description Must Have Technical/Functional Skills 15+ years in Asset Management and Investment Operations with deep expertise across trade lifecycle, reconciliation, corporate actions, performance, reporting, compliance and investment data management. Strong understanding of operating models, business architecture, target state transformation and process reengineering within asset management firms. Experience identifying and prioritizing AI, GenAI and Agentic AI opportunities across investment operations value chains. Working knowledge of Anthropic Claude/Other LLMs, Agentic AI patterns, enterprise AI adoption and business process transformation. Ability to translate business requirements into domain architectures, capability maps, business cases and implementation roadmaps. Experience partnering with enterprise architects, AI architects and engineering teams to define future state solutions. Strong stakeholder management, workshop facilitation and requirements elicitation skills. Experience in regulated financial services environments with focus on governance, controls and risk management. Roles & Responsibilities Lead engagement with business stakeholders, operations leaders and enterprise architects to identify and prioritize AI transformation opportunities. Assess end-to-end investment operations processes and define high-value Agentic AI use cases. Facilitate discovery workshops, value-stream assessments and business process reviews. Translate business needs into domain requirements, capability models, target operating models and AI implementation roadmaps. Act as the bridge between business stakeholders, AI architects, data teams and engineering teams. Define Human + AI Agent operating models across investment operations functions. Develop business cases, value realization frameworks, KPIs and adoption strategies. Support PoCs, MVPs and production deployments by providing domain leadership and business validation. Ensure proposed solutions align with governance, control, risk and regulatory requirements. Generic Managerial Skills, If any Executive stakeholder management and influencing skills. Strong communication and presentation skills across business and technology audiences. Ability to lead cross-functional teams and drive consensus across diverse stakeholders. Strong analytical thinking, problem solving and decision-making capabilities. Experience managing transformation initiatives, governance forums and change programs. Ability to mentor domain consultants and business analysts. TCS Employee Benefits Summary Discretionary Annual Incentive. Comprehensive Medical Coverage: Medical & Health, Dental & Vision, Disability Planning & Insurance, Pet Insurance Plans. Family Support: Maternal & Parental Leaves. Insurance Options: Auto & Home Insurance, Identity Theft Protection. Convenience & Professional Growth: Commuter Benefits & Certification & Training Reimbursement. Time Off: Vacation, Time Off, Sick Leave & Holidays. Legal & Financial Assistance: Legal Assistance, 401K Plan, Performance Bonus, College Fund, Student Loan Refinancing. Salary Range: $150,000 - 170,000 a year Qualifications: BACHELOR OF COMPUTER SCIENCE" We need to extract sections: About the role (maybe the initial description), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for: - About the role: The initial paragraph(s) describing the role: "15+ years in Asset Management..." etc. Could be considered "About the role". We'll put that in a

. - Responsibilities: The "Roles & Responsibilities" block: bullet list of duties. - Requirements: Possibly the "Generic Managerial Skills" block? Actually those are skills. But we have "Qualifications: BACHELOR OF COMPUTER SCIENCE". Also there is "Must Have Technical/Functional Skills" earlier. Might treat that as Skills. - Skills: The technical/functional skills list: 15+ years experience, deep expertise, etc. Also the managerial skills. - Benefits: The TCS Employee Benefits Summary block. - Pay: Salary Range: $150,000 - 170,000 a year. - Schedule: Not mentioned; we should not include Schedule section. We must not repeat job title as heading. No Job ID. We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We must not include filler like "commensurate with experience". Not present. We need to use

• for any list of duties/requirements/benefits. So for responsibilities, requirements, skills, benefits we should use lists. We need to decide what goes where. Let's parse content: Technical/Functional Skills (Must Have): - 15+ years in Asset Management and Investment Operations with deep expertise across trade lifecycle, reconciliation, corporate actions, performance, reporting, compliance and investment data management. - Strong understanding of operating models, business architecture, target state transformation and process reengineering within asset management firms. - Experience identifying and prioritizing AI, GenAI and Agentic AI opportunities across investment operations value chains. - Working knowledge of Anthropic Claude/Other LLMs, Agentic AI patterns, enterprise AI adoption and business process transformation. - Ability to translate business requirements into domain architectures, capability maps, business cases and implementation roadmaps. - Experience partnering with enterprise architects, AI architects and engineering teams to define future state solutions. - Strong stakeholder management, workshop facilitation and requirements elicitation skills. - Experience in regulated financial services environments with focus on governance, controls and risk management. That's a list. Roles & Responsibilities: - Lead engagement with business stakeholders, operations leaders and enterprise architects to identify and prioritize AI transformation opportunities. - Assess end-to-end investment operations processes and define high-value Agentic AI use cases. - Facilitate discovery workshops, value-stream assessments and business process reviews. - Translate business needs into domain requirements, capability models, target operating models and AI implementation roadmaps. - Act as the bridge between business stakeholders, AI architects, data teams and engineering teams. - Define Human + AI Agent operating models across investment operations functions. - Develop business cases, value realization frameworks, KPIs and adoption strategies. - Support PoCs, MVPs and production deployments by providing domain leadership and business validation. - Ensure proposed solutions align with governance, control, risk and regulatory requirements. Generic Managerial Skills: - Executive stakeholder management and influencing skills. - Strong communication and presentation skills across business and technology audiences. - Ability to lead cross-functional teams and drive consensus across diverse stakeholders. - Strong analytical thinking, problem solving and decision-making capabilities. - Experience managing transformation initiatives, governance forums and change programs. - Ability to mentor domain consultants and business analysts. Qualifications: - BACHELOR OF COMPUTER SCIENCE Benefits: - Discretionary Annual Incentive. - Comprehensive Medical Coverage: Medical & Health, Dental & Vision, Disability Planning & Insurance, Pet Insurance Plans. - Family Support: Maternal & Parental Leaves. - Insurance Options: Auto & Home Insurance, Identity Theft Protection. - Convenience & Professional Growth: Commuter Benefits & Certification & Training Reimbursement. - Time Off: Vacation, Time Off, Sick Leave & Holidays. - Legal & Financial Assistance: Legal Assistance, 401K Plan, Performance Bonus, College Fund, Student Loan Refinancing. Pay: - Salary Range: $150,000 - 170,000 a year. Schedule: none. We need to decide sections: About the role (maybe combine the initial description before "Roles & Responsibilities"? Actually the initial part is "Job Description Must Have Technical/Functional Skills ..." which is essentially the skills. But we already have Skills section. The "About the role" could be a brief summary: maybe we can combine the first paragraph as an overview. But we have no explicit overview besides the skills. However we could treat the first paragraph as "About the role". But we also have a Skills section; we might duplicate content. Better to treat the initial paragraph as "About the role" and then have separate Skills section for more detailed skill list? But the initial paragraph includes many skill bullets; it's essentially the same as the skills list. To avoid duplication, we could make "About the role" a short prose summarizing the role, but we don't have that. The instructions: "Prefer a few substantive sections over many thin ones." So we could combine the technical/functional skills and managerial skills into a single "Skills" section, and have "About the role" as a brief prose from the first sentence? But we don't have a separate overview. Maybe we can treat the initial paragraph as "About the role" and then have separate sections for Responsibilities, Qualifications, Benefits, Pay. And we can embed the skills within About the role? But the instruction says use
  • for any list of duties/requirements/benefits. So if we have a list of skills, we should put them in a list under Skills section. So we need a Skills section. Thus we need About the role: maybe we can write a short paragraph summarizing the role: "The role focuses on leading AI transformation in asset management investment operations, requiring deep expertise in trade lifecycle, reconciliation, corporate actions, performance, reporting, compliance, and investment data management, along with experience in AI, GenAI, Agentic AI, and stakeholder management." But that would be summarizing, which might be considered inventing detail? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." Summarizing could be considered summarizing away detail? It's ambiguous. Safer to not create an About the role section if we don't have distinct overview content separate from skills. However the instruction says "include a section ONLY when the posting has real, specific content for it". If we don't have a distinct overview, we could omit About the role. But typical job postings have an "About the role" paragraph. Here the initial part is essentially the skills. Could we treat that as About the role? It's specific content: "15+ years in Asset Management and Investment Operations with deep expertise across trade lifecycle, reconciliation, corporate actions, performance, reporting, compliance and investment data management. Strong understanding of operating models, business architecture, target state transformation and process reengineering within asset management firms. Experience identifying and prioritizing AI, GenAI and Agentic AI opportunities across investment operations value chains. Working knowledge of Anthropic Claude/Other LLMs, Agentic AI patterns, enterprise AI adoption and business process transformation. Ability to translate business requirements into domain architectures, capability maps, business cases and implementation roadmaps. Experience partnering with enterprise architects, AI architects and engineering teams to define future state solutions. Strong stakeholder management, workshop facilitation and requirements elicitation skills. Experience in regulated financial services environments with focus on governance, controls and risk management." That is a substantive block. We could treat that as About the role (a paragraph). Then we still need Skills section? But that would duplicate. Perhaps we can treat that block as About the role (prose) and then have Skills section for the managerial skills? But the managerial skills are also skills. Could split: technical/functional skills in About the role, managerial skills in Skills. But the instruction says use
    • for any list of duties/requirements/benefits. The technical/functional skills are a list; we could still put them in a list under About the role? But About the role is supposed to be prose per instruction: "Use

      for section headings ... Use

      • for any list of duties/requirements/benefits, and

        for prose." So if we have a list, we should use

        • . So About the role should be prose, not a list. So we need to convert the list into prose? That would be summarizing. Might be okay if we keep the same information but in prose form, not inventing. We could turn each bullet into a sentence separated by commas or semicolons within a paragraph. That preserves all detail, just changes format. That is allowed? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." Converting bullet list to prose preserves detail, not summarizing away. So we could do that. Thus we can have About the role as a

          containing the sentences from the technical/functional skills block. Then we can have Skills section for the managerial skills (Generic