AI Platform Engineer / Architect - VP
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must output only HTML fragment, no /, no markdown fences.
Let's extract content.
Mission paragraph: "Our mission is to develop a firmwide Artificial Intelligence (AI) Development Platform that aligns with the firm's Technology principles and drives efficiency and consistency, controls, security and strong governance and promotes innovation, enabling teams to build applications that leverage AI capabilities and accelerate the adoption of AI across our businesses. This role is for a platform engineering specialist who will help build a firmwide AI Development Platform and drive adoption of AI capabilities throughout the enterprise. We have multiple focus areas across the platform and are looking for energetic, multi-disciplinary candidates who are eager to contribute to providing scalable, secure, enterprise-wide solutions for the firm."
That's About the role.
Responsibilities: Under "What You'll Do In The Role Below is a sample of potential responsibilities depending on product / focus area" then bullet list lines (each sentence). Let's list them:
- Develop tooling and self-service capabilities for deploying AI solutions for the firm leveraging Kubernetes/OpenShift, Python, authentication solutions, APIs, REST framework, etc
- Develop Terraform modules and Cloud architecture to enable secure AI cloud service deployment and consumption at scale
- Have a platform mindset and build common, reusable solutions to scale Generative AI use cases using pre-trained models as well as fine-tuned models.
- Leverage Kubernetes/OpenShift to develop modern containerized workloads
- Integrate with capabilities such as large-scale vector stores for embeddings.
- Author best practices on the Generative AI ecosystem, when to use which tools, available models such as GPT, Llama, Hugging Face etc. and libraries such as Langchain.
- Analyze, investigate, and implement GenAI solutions focusing on Agentic Orchestration and Agent Builder frameworks.
- Author and publish architecture decision records to capture major design decisions and product selection for building Generative AI solutions. Inclusive of app authentication, service communication, state externalization, container layering strategy and immutability.
- Ensure AI platform are reliable, scalable, and operational; (e.g. blueprints for upgrade/release strategies (E.g. Blue/Green); logging/monitoring/metrics; automation of system management tasks)
- Participate in all team's Agile/ Scrum ceremonies.
- Participate in team's oncall rotation in build/run team model
We'll put these as
- .
Requirements: Could be "What You'll Bring To The Role" includes education, experience, etc. We'll split into Qualifications (education/experience) and Skills (technical). But we can also combine. However instruction: prefer few substantive sections over many thin ones. We could have Qualifications (education + years experience) and Skills (technical). But we also have Benefits and Pay.
Let's extract qualifications:
- Bachelor's or Master's degree in Computer Science or related field, or equivalent job experience
- 8+ years of experience in software engineering, design and development
- Strong hands-on Application Development background in at least one prominent programming language, preferably Python Flask or FAST Api.
- Broad understanding of data engineering (SQL, NoSQL, Big Data, Kafka, Redis), data governance, data privacy and security.
- Experience in development, management, and deployment of Kubernetes workloads, preferably on OpenShift.
- Experience with designing, developing, and managing RESTful services for large-scale enterprise solutions.
- Experience deploying applications on Azure, AWS, and/or GCP using IaC (Terraform)
- Hands-on experience with multiprocessing, multithreading, asynchronous I/O, performance profiling in at least one prominent programming language, preferably python.
- Ability to articulate technical concepts effectively to diverse audiences.
- Excellent communication skills.
- Demonstrated ability to work effectively and collaboratively in a global organization, across time zones, and across organizations
- Demonstrated experience in DevOps, understanding of CI/CD (Jenkins) and GitOps.
- Knowledge of DevOps and Agile practices.
- Nice to have Practitioner of unit testing, performance testing and BDD/acceptance testing.
- Understanding of OAuth 2.0 protocol for secure authorization.
- Proficiency with Open Telemetry tools including Grafana, Loki, Prometheus, and Cortex.
- Good knowledge of Microservice based architecture, industry standards, for both public and private cloud.
- Good understanding of modern Application configuration techniques.
- Hands on experience with Cloud Application Deployment patterns like Blue/Green.
- Good understanding of State sharing between scalable cloud components (Kafka, dynamic distributed caching).
- Good knowledge of various DB engines (SQL, Redis, Kafka, etc) for cloud app storage.
- Experience building AI applications, preferably Generative AI and LLM based apps.
- Deep understanding of AI agents, Agentic Orchestration, Multi-Agent Workflow Automation, along with hands-on experience in Agent Builder frameworks such Lang Chain and Lang Graph.
- Experience working with Generative AI development, embeddings, fine tuning of Generative AI models.
- Understanding of ModelOps/ ML Ops/ LLM Op.
- Understanding of SRE techniques.
That's a lot; many are skills. We could separate Qualifications (education + years experience) and Skills (the rest). But we might have too many sections. Perhaps combine Qualifications and Skills into one "Requirements" section with lists. However instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include multiple of those if they have real content. We need to avoid filler.
We have content for About the role, Responsibilities, Requirements (maybe education+experience), Qualifications (maybe degree?), Skills (technical), Benefits, Pay.
But we risk duplication. Let's think: The posting includes "What You'll Bring To The Role" which includes education, experience, and many skills. We could split into Qualifications (education + years experience) and Skills (technical and soft skills). That seems reasonable.
Thus:
About the role
mission paragraph
Responsibilities
- ... each responsibility
Qualifications
- Bachelor's or Master's degree in Computer Science or related field, or equivalent job experience
- 8+ years of experience in software engineering, design and development
Skills
- Strong hands-on Application Development background in at least one prominent programming language, preferably Python Flask or FAST Api.
... etc (list all skill items). We'll need to include all skill items from the list.
But we must be careful not to include duplicate items that also appear in qualifications. We already used degree and years experience; we won't repeat them.
Now Benefits: Under "What You Can Expect From Morgan Stanley" there are two similar paragraphs repeated. We need to extract benefits description: "We are proud to support our employees and their families at every point along their work-life journey, offering some of the most attractive and comprehensive employee benefits and perks in the industry." Also mention "We have a track record of innovation and passion for unlocking new opportunities, we help our clients raise, manage and allocate capital." That's more about firm, not benefits. The benefits paragraph: "We are proud to support our employees and their families at every point along their work-life journey, offering some of the most attractive and comprehensive employee benefits and perks in the industry." Also later repeated similar. We'll include that as benefits.
Pay: "Expected base pay rates for the role will be between $155,000 and $215,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"
Schedule: Not present, so omit.
We must remove boilerplate like EEO, navigation, etc. The repeated paragraphs about mission, values, etc are somewhat boilerplate but contain some substantive info about firm values and benefits. We need to keep substantive info but remove duplicated lines. The posting has duplicated "What You Can Expect From Morgan Stanley" twice with similar content. We'll keep one copy of the benefits paragraph and maybe the firm description? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The firm description about mission, innovation, etc may be considered boilerplate but also part of "About the role"? Actually the mission paragraph is at start; later there is a paragraph about "In the Technology division, we leverage innovation..." and later about Morgan Stanley history. Those might be considered boilerplate but they provide context about firm. Are we to keep them? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep substantive info about firm's mission, technology division, history, values, etc as they are substantive. However we must avoid duplication. There are two similar paragraphs about Morgan Stanley values and benefits repeated. We'll keep one.
Thus About the role could include the mission paragraph plus maybe the technology division paragraph? But the mission paragraph already covers role. The technology division paragraph: "In the Technology division, 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." That's substantive about firm. Could be part of About the role or maybe a separate section? Not required. We could incorporate into About the role as additional paragraph.
Similarly the history paragraph: "Since 1935, Morgan Stanley is known as a global leader in financial services, always evolving and innovating to better serve our clients and our communities in more than 40 countries around the world." That's also substantive.
We could include those in About the role as extra paragraphs.
But we must not repeat duplicated lines. The later repeated "What You Can Expect From Morgan Stanley" includes similar content about values and benefits; we will keep one.
Thus final HTML:
About the role
Our mission is to develop a firmwide Artificial Intelligence (AI) Development Platform that aligns with the firm's Technology principles and drives efficiency and consistency, controls, security and strong governance and promotes innovation, enabling teams to build applications that leverage AI capabilities and accelerate the adoption of AI across our businesses. This role is for a platform engineering specialist who will help build a firmwide AI Development Platform and drive adoption of AI capabilities throughout the enterprise. We have multiple focus areas across the platform and are looking for energetic, multi-disciplinary candidates who are eager to contribute to providing scalable, secure, enterprise-wide solutions for the firm.
In the Technology division, 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.
Since 1935, Morgan Stanley is known as a global leader in financial services, always evolving and innovating to better serve our clients and our communities in more than 40 countries around the world.
Responsibilities
- Develop tooling and self
for prose. We must output only HTML fragment, no /, no markdown fences. Let's extract content. Mission paragraph: "Our mission is to develop a firmwide Artificial Intelligence (AI) Development Platform that aligns with the firm's Technology principles and drives efficiency and consistency, controls, security and strong governance and promotes innovation, enabling teams to build applications that leverage AI capabilities and accelerate the adoption of AI across our businesses. This role is for a platform engineering specialist who will help build a firmwide AI Development Platform and drive adoption of AI capabilities throughout the enterprise. We have multiple focus areas across the platform and are looking for energetic, multi-disciplinary candidates who are eager to contribute to providing scalable, secure, enterprise-wide solutions for the firm." That's About the role. Responsibilities: Under "What You'll Do In The Role Below is a sample of potential responsibilities depending on product / focus area" then bullet list lines (each sentence). Let's list them: - Develop tooling and self-service capabilities for deploying AI solutions for the firm leveraging Kubernetes/OpenShift, Python, authentication solutions, APIs, REST framework, etc - Develop Terraform modules and Cloud architecture to enable secure AI cloud service deployment and consumption at scale - Have a platform mindset and build common, reusable solutions to scale Generative AI use cases using pre-trained models as well as fine-tuned models. - Leverage Kubernetes/OpenShift to develop modern containerized workloads - Integrate with capabilities such as large-scale vector stores for embeddings. - Author best practices on the Generative AI ecosystem, when to use which tools, available models such as GPT, Llama, Hugging Face etc. and libraries such as Langchain. - Analyze, investigate, and implement GenAI solutions focusing on Agentic Orchestration and Agent Builder frameworks. - Author and publish architecture decision records to capture major design decisions and product selection for building Generative AI solutions. Inclusive of app authentication, service communication, state externalization, container layering strategy and immutability. - Ensure AI platform are reliable, scalable, and operational; (e.g. blueprints for upgrade/release strategies (E.g. Blue/Green); logging/monitoring/metrics; automation of system management tasks) - Participate in all team's Agile/ Scrum ceremonies. - Participate in team's oncall rotation in build/run team model We'll put these as
- .
Requirements: Could be "What You'll Bring To The Role" includes education, experience, etc. We'll split into Qualifications (education/experience) and Skills (technical). But we can also combine. However instruction: prefer few substantive sections over many thin ones. We could have Qualifications (education + years experience) and Skills (technical). But we also have Benefits and Pay.
Let's extract qualifications:
- Bachelor's or Master's degree in Computer Science or related field, or equivalent job experience
- 8+ years of experience in software engineering, design and development
- Strong hands-on Application Development background in at least one prominent programming language, preferably Python Flask or FAST Api.
- Broad understanding of data engineering (SQL, NoSQL, Big Data, Kafka, Redis), data governance, data privacy and security.
- Experience in development, management, and deployment of Kubernetes workloads, preferably on OpenShift.
- Experience with designing, developing, and managing RESTful services for large-scale enterprise solutions.
- Experience deploying applications on Azure, AWS, and/or GCP using IaC (Terraform)
- Hands-on experience with multiprocessing, multithreading, asynchronous I/O, performance profiling in at least one prominent programming language, preferably python.
- Ability to articulate technical concepts effectively to diverse audiences.
- Excellent communication skills.
- Demonstrated ability to work effectively and collaboratively in a global organization, across time zones, and across organizations
- Demonstrated experience in DevOps, understanding of CI/CD (Jenkins) and GitOps.
- Knowledge of DevOps and Agile practices.
- Nice to have Practitioner of unit testing, performance testing and BDD/acceptance testing.
- Understanding of OAuth 2.0 protocol for secure authorization.
- Proficiency with Open Telemetry tools including Grafana, Loki, Prometheus, and Cortex.
- Good knowledge of Microservice based architecture, industry standards, for both public and private cloud.
- Good understanding of modern Application configuration techniques.
- Hands on experience with Cloud Application Deployment patterns like Blue/Green.
- Good understanding of State sharing between scalable cloud components (Kafka, dynamic distributed caching).
- Good knowledge of various DB engines (SQL, Redis, Kafka, etc) for cloud app storage.
- Experience building AI applications, preferably Generative AI and LLM based apps.
- Deep understanding of AI agents, Agentic Orchestration, Multi-Agent Workflow Automation, along with hands-on experience in Agent Builder frameworks such Lang Chain and Lang Graph.
- Experience working with Generative AI development, embeddings, fine tuning of Generative AI models.
- Understanding of ModelOps/ ML Ops/ LLM Op.
- Understanding of SRE techniques.
That's a lot; many are skills. We could separate Qualifications (education + years experience) and Skills (the rest). But we might have too many sections. Perhaps combine Qualifications and Skills into one "Requirements" section with lists. However instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include multiple of those if they have real content. We need to avoid filler.
We have content for About the role, Responsibilities, Requirements (maybe education+experience), Qualifications (maybe degree?), Skills (technical), Benefits, Pay.
But we risk duplication. Let's think: The posting includes "What You'll Bring To The Role" which includes education, experience, and many skills. We could split into Qualifications (education + years experience) and Skills (technical and soft skills). That seems reasonable.
Thus:
About the role
mission paragraph
Responsibilities
- ... each responsibility
Qualifications
- Bachelor's or Master's degree in Computer Science or related field, or equivalent job experience
- 8+ years of experience in software engineering, design and development
Skills
- Strong hands-on Application Development background in at least one prominent programming language, preferably Python Flask or FAST Api. ... etc (list all skill items). We'll need to include all skill items from the list. But we must be careful not to include duplicate items that also appear in qualifications. We already used degree and years experience; we won't repeat them. Now Benefits: Under "What You Can Expect From Morgan Stanley" there are two similar paragraphs repeated. We need to extract benefits description: "We are proud to support our employees and their families at every point along their work-life journey, offering some of the most attractive and comprehensive employee benefits and perks in the industry." Also mention "We have a track record of innovation and passion for unlocking new opportunities, we help our clients raise, manage and allocate capital." That's more about firm, not benefits. The benefits paragraph: "We are proud to support our employees and their families at every point along their work-life journey, offering some of the most attractive and comprehensive employee benefits and perks in the industry." Also later repeated similar. We'll include that as benefits. Pay: "Expected base pay rates for the role will be between $155,000 and $215,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" Schedule: Not present, so omit. We must remove boilerplate like EEO, navigation, etc. The repeated paragraphs about mission, values, etc are somewhat boilerplate but contain some substantive info about firm values and benefits. We need to keep substantive info but remove duplicated lines. The posting has duplicated "What You Can Expect From Morgan Stanley" twice with similar content. We'll keep one copy of the benefits paragraph and maybe the firm description? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The firm description about mission, innovation, etc may be considered boilerplate but also part of "About the role"? Actually the mission paragraph is at start; later there is a paragraph about "In the Technology division, we leverage innovation..." and later about Morgan Stanley history. Those might be considered boilerplate but they provide context about firm. Are we to keep them? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep substantive info about firm's mission, technology division, history, values, etc as they are substantive. However we must avoid duplication. There are two similar paragraphs about Morgan Stanley values and benefits repeated. We'll keep one. Thus About the role could include the mission paragraph plus maybe the technology division paragraph? But the mission paragraph already covers role. The technology division paragraph: "In the Technology division, 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." That's substantive about firm. Could be part of About the role or maybe a separate section? Not required. We could incorporate into About the role as additional paragraph. Similarly the history paragraph: "Since 1935, Morgan Stanley is known as a global leader in financial services, always evolving and innovating to better serve our clients and our communities in more than 40 countries around the world." That's also substantive. We could include those in About the role as extra paragraphs. But we must not repeat duplicated lines. The later repeated "What You Can Expect From Morgan Stanley" includes similar content about values and benefits; we will keep one. Thus final HTML:
- Develop tooling and self
About the role
Our mission is to develop a firmwide Artificial Intelligence (AI) Development Platform that aligns with the firm's Technology principles and drives efficiency and consistency, controls, security and strong governance and promotes innovation, enabling teams to build applications that leverage AI capabilities and accelerate the adoption of AI across our businesses. This role is for a platform engineering specialist who will help build a firmwide AI Development Platform and drive adoption of AI capabilities throughout the enterprise. We have multiple focus areas across the platform and are looking for energetic, multi-disciplinary candidates who are eager to contribute to providing scalable, secure, enterprise-wide solutions for the firm.
In the Technology division, 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.
Since 1935, Morgan Stanley is known as a global leader in financial services, always evolving and innovating to better serve our clients and our communities in more than 40 countries around the world.
Responsibilities