AI Enabled Modernization - Agentic Software Engineer - Vice President (Seattle, WA)

We need to output HTML fragment with sections for headings present: About the role? The posting includes "What We Do", "Your Impact", "Key Responsibilities", "Basic Qualifications", "Preferred Qualifications", "About Goldman Sachs". According to rules, we should use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content to these headings. The posting doesn't have explicit sections named exactly those, but we can infer: "Your Impact" could be About the role? Actually "About the role" is typical heading for description of role. We have "What We Do" (company description) and "Your Impact" (role impact). Could treat "What We Do" as About the role? Might be better to have sections: About the role (combining What We Do and Your Impact?), Responsibilities (Key Responsibilities), Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Skills (maybe not separate), Benefits (none), Pay (none), Schedule (none). We should only include sections when there is real specific content. No Pay/Benefits/Schedule given, so omit those. We must not repeat job title as heading. No Job ID. We need to preserve all substantive information, no boilerplate. Remove cookie/navigation/legal/EEO etc. The "About Goldman Sachs" includes some boilerplate but also substantive description of firm. We should keep that as maybe "About Goldman Sachs" but not a standard heading; maybe we can put under "About the role"? Actually "About Goldman Sachs" is company overview, could be part of "About the role" or separate section like "About the company". But rules only list specific headings; we should not create other headings. However we could include "About Goldman Sachs" content under "About the role" heading? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, but we should use those headings when appropriate. It also says "include a section ONLY when the posting has real, specific content for it". So we can create sections for those headings if we have content. We have content for About the role (description of role and impact). We have Responsibilities. We have Requirements (basic qualifications). We have Qualifications (preferred). We might not have Skills separate; but we could put skills under Qualifications. Benefits, Pay, Schedule none -> omit. Thus output:

About the role

... combine What We Do and Your Impact?

But we need to preserve all substantive information; we should not lose details. So we need to include the text from "What We Do At Goldman Sachs, our Engineers..." and "Your Impact We are seeking entrepreneurial Agentic Software Engineers..." etc. We can put them in

under About the role. Then Responsibilities: list each bullet as

• . Then Requirements: Basic Qualifications list. Then Qualifications: Preferred Qualifications list. We must not include boilerplate like "Learn more about our culture, benefits, and people at GS.com/careers . We’re committed to finding reasonable accommodation..." That's EEO/boilerplate; remove. Also remove "About Goldman Sachs" section? Actually that is company overview; but we already used About the role for role description; we could include company overview under About the role as well, but maybe better to have a separate section? Not allowed headings besides those. Could we treat "About Goldman Sachs" as part of About the role? It's not about the role but about the company. However the instruction says we can use those headings as examples; maybe we can add a section like "About Goldman Sachs" but not in list? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are typical but not exclusive? It says "use

  for section headings (e.g. About the role, ...)". Likely they expect us to use those specific headings when applicable. Since we don't have a standard heading for company overview, maybe we omit it or incorporate into About the role. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine company overview into About the role. Thus About the role will contain: What We Do paragraph, Your Impact paragraph, and maybe also a brief about Goldman Sachs? But we can include the Goldman Sachs description as part of About the role as well. Let's extract substantive content: What We Do At Goldman Sachs, our Engineers don’t just make things – we make things possible. Change the world by connecting people and capital with ideas. Solve the most challenging and pressing engineering problems for our clients. Join our engineering teams that build massively scalable software and systems, architect low latency infrastructure solutions, proactively guard against cyber threats, and leverage machine learning alongside financial engineering to continuously turn data into action. Create new businesses, transform finance, and explore a world of opportunity at the speed of markets. Goldman Sachs Engineers are innovators and problem-solvers, building solutions in Artificial Intelligence, risk management, big data, mobile and more. Your Impact We are seeking entrepreneurial Agentic Software Engineers to join a newly formed AI Agentic Systems team. This team is tasked with solving firmwide, large-scale application and infrastructure challenges by building and deploying swarms of agents. You will build systems that understand, plan, transform, and validate application modernization workflows across one of the largest and most complex technology estates in the industry. As a founding member of this team, you will help incubate a new paradigm of software engineering—moving beyond static automation to dynamic, goal-oriented agentic systems that operate across all the firm’s business units. Key Responsibilities list: - Agentic Orchestration: Design and deploy multi-agent systems (swarms) capable of autonomous planning, reasoning, and execution across distributed cloud environments. - Learning and Feedback: Build human-in-the-loop systems, evaluation frameworks, and observability mechanisms that enable continuous agent improvement. - Tool Integration: Design and build integrations with APIs, developer tooling, CI/CD pipelines, data platforms, or operational systems. - Cross-Functional Collaboration: Partner with diverse business units to identify high-impact use cases for agents, translating ambiguous business needs into technical agentic workflows. Basic Qualifications: - Software Engineering Excellence: Strong proficiency in Python, Go, Java, Javascript or similar languages with a deep understanding of distributed systems and cloud-native architecture (AWS, Azure, or internal private clouds). - Agentic Experience: Direct experience deploying and operating LLM-based agents in production environments. Familiarity with frameworks such as LangGraph, AutoGPT, or custom-built orchestration layers. - AI Evals: Experience designing benchmarks, evaluations, and quality metrics for AI systems. - Problem-Solving Domains: Proven track record of applying agentic patterns to at least two of the following: * Data Analysis: Autonomous synthesis of large-scale datasets. * Observability: Self-healing infrastructure and automated root-cause analysis. * Optimization: Dynamic resource allocation and cost management. * Planning: Multi-step task decomposition and execution in non-deterministic environments. - Entrepreneurial Mindset: Ability to thrive in a 0-to-1 environment, comfortable with ambiguity, and driven to build systems that have never existed before. Preferred Qualifications: - Demonstrated interest in emerging agentic technologies such as Multi-Agent Reinforcement Learning (MARL), and swarm intelligence, with a willingness to experiment, learn, and apply new approaches where they create practical business value. - Familiarity with Model Context Protocol (MCP), A2A and other emerging standards for agent-to-tool communication. - Strong communication skills to bridge the gap between technical agentic logic and human-centric business processes. We should not include the "About Goldman Sachs" paragraph about firm history etc. That's boilerplate? It's somewhat generic but still substantive about the firm. However it's not required; we could omit to keep sections thin. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The About Goldman Sachs paragraph is substantive about the firm. But we already have a lot; maybe we can include it under About the role as additional paragraph. It's not boilerplate like EEO; it's firm description. I'd include it. Thus About the role will have multiple paragraphs: What We Do, Your Impact, and About Goldman Sachs (the firm description). We'll keep them as separate

  tags. Now produce HTML fragment:

  About the role

  What We Do At Goldman Sachs, our Engineers don’t just make things – we make things possible. Change the world by connecting people and capital with ideas. Solve the most challenging and pressing engineering problems for our clients. Join our engineering teams that build massively scalable software and systems, architect low latency infrastructure solutions, proactively guard against cyber threats, and leverage machine learning alongside financial engineering to continuously turn data into action. Create new businesses, transform finance, and explore a world of opportunity at the speed of markets. Goldman Sachs Engineers are innovators and problem-solvers, building solutions in Artificial Intelligence, risk management, big data, mobile and more.

  Your Impact We are seeking entrepreneurial Agentic Software Engineers to join a newly formed AI Agentic Systems team. This team is tasked with solving firmwide, large-scale application and infrastructure challenges by building and deploying swarms of agents. You will build systems that understand, plan, transform, and validate application modernization workflows across one of the largest and most complex technology estates in the industry. As a founding member of this team, you will help incubate a new paradigm of software engineering—moving beyond static automation to dynamic, goal-oriented agentic systems that operate across all the firm’s business units.

  About Goldman Sachs At Goldman Sachs, we commit our people, capital and ideas to help our clients, shareholders and the communities we serve to grow. Founded in 1869, we are a leading global investment banking, securities and investment management firm. Headquartered in New York, we maintain offices around the world. We believe who you are makes you better at what you do. We're committed to fostering and advancing diversity and inclusion in our own workplace and beyond by ensuring every individual within our firm has several opportunities to grow professionally and personally, from our training and development opportunities and firmwide networks to benefits, wellness and personal finance offerings and mindfulness programs. Learn more about our culture, benefits, and people at GS.com/careers . We’re committed to finding reasonable accommodation for candidates with special needs or disabilities during our recruiting process. Learn more: https://www.goldmansachs.com/careers/footer/disability-statement.html

  But note: The last part includes "Learn more about our culture, benefits, and people at GS.com/careers . We’re committed to finding reasonable accommodation..." This is somewhat boilerplate but still part of About Goldman Sachs. Might be considered EEO/boilerplate? It's about disability statement; could be considered legal. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". The disability statement is legal/EEO. So we should remove that sentence. Also the "Learn more about our culture, benefits, and people at GS.com/careers" is maybe okay but it's a link; could be considered navigation? It's a link to careers page; maybe we should remove as it's navigation. Safer to remove the whole last two sentences. Keep the earlier part about commitment to diversity etc. That's also EEO? It's about diversity and inclusion; could be considered EEO boilerplate. The instruction says remove EEO/equal-opportunity boilerplate. So we should remove the diversity and inclusion paragraph as well. That leaves only the first two sentences: "At Goldman Sachs, we commit our people, capital and ideas to help our clients, shareholders and the communities we serve to grow. Founded in 1869, we are a leading global investment banking, securities and investment management firm. Headquartered in New York, we maintain offices around the world. We believe who you are makes you better