AI Architect (Hybrid)
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate. Include only sections with real specific content.
We need to parse the posting.
Key info:
- About the role: description of RTX and the position. Could be a paragraph.
- Responsibilities: bullet list of "What You Will Do" items.
- Requirements: maybe "U.S. Person" requirement? Also "Security Clearance Type: None/Not Required". Also maybe "Work Location: hybrid role, eligible candidates must reside within commuting distance of ...". That could be under Requirements or maybe a separate section? But we can include under Requirements or maybe a separate "Location" but not required heading. We'll include under Requirements as prose.
- Qualifications: "You Must Have" and "We Prefer". Could be combined under Qualifications heading with sub-sections? But we only have headings defined; we can put both under Qualifications with paragraphs and lists.
- Skills: maybe not explicit separate; but we could treat technical experience as skills. However we should only include a Skills section if posting has real specific content for it. There's a list of technical experience under Qualifications; we could put that under Qualifications rather than separate Skills. Probably better to not create Skills unless explicit.
- Benefits: paragraph about total rewards package, list of some benefits.
- Pay: salary range given: 132,400 USD - 251,600 USD.
- Schedule: hybrid role description: "Hybrid: Employees who are working in Hybrid roles will work regularly both onsite and offsite. Ratio of time working onsite will be determined in partnership with your leader." Also mention work location commuting distance. Could be under Schedule.
We need to avoid filler like "commensurate with experience". Not present.
We must not include boilerplate like EEO, privacy policy, etc.
We need to preserve all substantive information.
Let's extract.
About the role: Paragraph(s) describing RTX and the position: "At RTX, the world's largest aerospace and defense company, 185,000 great minds are united by purpose and inspired to make a difference solving the world’s most complex problems. With our three market leading businesses, world-class operations and investments in research and development, we offer capabilities and opportunity no one else can. Together, we push the boundaries of known science and find new ways to connect and protect our world. Join us and help shape the future of aerospace and defense. The following position is to join our RTX Enterprise Services team: We are seeking an experienced AI Architect to define and guide the architecture of enterprise Artificial Intelligence and Machine Learning solutions across RTX. This role will partner with business units, product teams, engineering organizations, domain architects, cybersecurity, data, and enterprise technology teams to translate complex business needs into scalable, secure, and production-ready AI architectures. The ideal candidate combines deep AI/ML expertise with strong software, data, cloud, and enterprise architecture experience and has demonstrated success guiding complex technology solutions from concept through production. A key focus of this role will be identifying common needs across RTX business units and translating them into reusable enterprise AI capabilities, reference architectures, and design patterns that accelerate adoption while reducing duplication and technical complexity."
That's a good paragraph.
Responsibilities: bullet list from "What You Will Do". Items:
- Define end-to-end architectures for enterprise AI and ML solutions spanning traditional machine learning, Generative AI, agentic AI, data, applications, APIs, platforms, infrastructure, and enterprise systems.
- Partner with business and technology leaders to translate business opportunities and requirements into architecture blueprints, technical strategies, success criteria, and implementation roadmaps.
- Determine the appropriate technical approach for complex business problems, including traditional software, machine learning, Generative AI, retrieval-augmented generation, agentic AI, or combinations of these approaches.
- Develop reusable reference architectures, design patterns, standards, and technical guardrails, and identify common requirements across RTX business units that can be addressed through reusable enterprise AI capabilities.
- Architect modern AI solutions including model selection and routing, retrieval and grounding, context engineering, agent orchestration, tool use, state and memory, human-in-the-loop workflows, evaluation, observability, and secure enterprise integration.
- Define architecture patterns for AI/ML data pipelines, model serving, model lifecycle management, MLOps, deployment, monitoring, and operation across cloud, hybrid, on-premises, and restricted environments.
- Evaluate technology and platform alternatives and lead build, buy, configure, and integrate decisions considering business value, scalability, interoperability, security, performance, cost, and operational complexity.
- Lead architecture and technical design reviews, partner with enterprise architecture, cybersecurity, data, identity, privacy, and Responsible AI teams, and provide technical leadership and mentorship across engineering teams.
Also "What You Will Learn" could be considered responsibilities? It's more about learning; but we could include under Responsibilities or maybe a separate section? Not required heading. Could be included under Responsibilities as additional bullet points? Might be considered part of role description. But we can keep them as part of Responsibilities or maybe as a separate "Learning Opportunities" but not a defined heading. Safer to include under Responsibilities as bullet points? However the instruction: Use
- for any list of duties/requirements/benefits. "What You Will Learn" is not duties but could be considered part of role. Might be okay to include as list under Responsibilities? Might be stretching. Better to keep only duties list. We'll omit the "What You Will Learn" list? But we must preserve ALL substantive information. So we need to include that info somewhere. Could be under a separate heading like "What You Will Learn" but not in allowed headings. Could we treat it as part of Responsibilities? It's not duty but still substantive. Could we add a section "Learning Opportunities"? Not allowed headings. The instruction says: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It gives examples but not exclusive list. So we could add a heading like "What You Will Learn" if we want. However the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we should stick to those headings. It doesn't explicitly forbid others, but to be safe, we should use only those headings. So we need to fit the "What You Will Learn" content somewhere else, maybe under About the role or Qualifications. Could add a paragraph under About the role describing learning opportunities. That would preserve info.
Thus About the role can be expanded to include also what you will learn.
Similarly, "What You Will Learn" bullet list:
- How AI and ML technologies are applied across a global aerospace and defense enterprise spanning diverse business, engineering, manufacturing, and operational domains.
- How enterprise AI platforms and reusable architecture patterns enable AI solutions to scale across multiple business units while meeting security, data, and governance requirements.
- How Generative AI and agentic AI capabilities are evolving from experimentation into production systems that interact with enterprise data, tools, applications, and workflows.
- How AI architectures are designed across commercial cloud, hybrid, on-premises, and restricted computing environments.
- How emerging AI technologies, models, frameworks, interoperability standards, and industry practices can be evaluated and translated into practical enterprise capabilities.
- How to influence the technical direction of enterprise AI by working across business units, architecture disciplines, engineering organizations, and senior leadership.
We can incorporate these as a paragraph or list under About the role.
Now Requirements: includes U.S. Person requirement, security clearance none, work location commuting distance, maybe also "Position Role Type: Hybrid". Also maybe "U.S. Citizen, U.S. Person, or Immigration Status Requirements: This job requires a U.S. Person." Also "Security Clearance Type: None/Not Required". Also "Work Location: This is a hybrid role, eligible candidates must reside within commuting distance of Farmington, CT, El Segundo, CA, San Jose, CA, Tucson, AZ, McKinney, TX, Andover, MA, Cedar Rapids, IA, or Charlotte, NC." Also "Please ensure the role type defined below is appropriate for your needs before applying to this role." That's more instruction; we can ignore as boilerplate? It's not substantive? Might be considered meta. We'll keep location and hybrid info.
Thus Requirements section: paragraph(s) covering U.S. Person requirement, security clearance none, hybrid work location and commuting distance.
We could also include "Position Role Type: Hybrid" as part of Requirements.
Now Qualifications: includes "You Must Have" and "We Prefer". We'll create two sub-sections maybe as paragraphs with lists.
We must not invent headings like "Must Have" etc. We'll just put content under Qualifications heading, using paragraphs and lists.
We need to list the must-have qualifications:
- A University Degree in Computer Science, Artificial Intelligence, Machine Learning, Engineering, or a related STEM discipline and a minimum of 10 years of relevant professional experience, or an Advanced Degree in a related field and a minimum of 7 years of relevant professional experience.
- A minimum of 5 years of experience designing, developing, integrating, or architecting AI/ML solutions, including experience taking AI or ML capabilities beyond experimentation into production environments.
- Experience serving as a technical architect, solution architect, technical lead, or senior engineer for complex enterprise software, data, cloud, or AI/ML systems.
- Technical experience with AI/ML systems and modern AI application architectures, including Generative AI and large language models.
- Experience designing distributed systems, APIs, microservices, enterprise integrations, data pipelines, or cloud-native applications using at least one major public cloud platform.
- Experience translating business and technical requirements into architecture designs and evaluating technical, business, cost, security, and operational tradeoffs.
- Experience working with enterprise security concepts including identity and access management, authentication and authorization, data protection, application security, and secure system integration.
Now preferred qualifications list:
- Experience architecting production Generative AI, retrieval-augmented generation, agentic AI, or multi-agent systems including modern AI architecture patterns including model selection and routing, embeddings, vector and enterprise search, context engineering, structured outputs, tool calling, orchestration, memory, state, and human-in-the-loop workflows.
- Experience with emerging agent technologies and interoperability approaches such as Model Context Protocol (MCP), agent identity, secure tool integration, or similar standards.
- Experience with AI evaluation, observability, tracing, guardrails, model monitoring, Responsible AI, model governance, or production AI reliability and with traditional machine learning lifecycle capabilities including data pipelines, feature engineering, model serving, model registries, monitoring, and MLOps.
- Experience designing AI architectures across multiple models, vendors, platforms, and cloud, hybrid, on-premises, or restricted environments.
- Experience with Kubernetes, containers, CI/CD, infrastructure-as-code, and modern application deployment architectures.
- Familiarity with relevant AI risk, cloud architecture, and enterprise architecture frameworks and principles, such as NIST AI RMF, cloud well-architected frameworks, TOGAF, Zachman, or similar disciplines, and experience applying them to enterprise technology decisions.
- Demonstrated ability to lead technical discussions, influence architecture decisions across multidisciplinary teams, and communicate complex technical concepts to technical and non-technical stakeholders.
Now Benefits: paragraph about total rewards package and list of some benefits.
We have: "Whether you’re just starting out on your career journey or are an experienced professional, we offer a robust total rewards package with compensation; healthcare, wellness, retirement and work/life benefits; career development and recognition programs. Some of the benefits we offer include parental (including paternal)
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate. Include only sections with real specific content. We need to parse the posting. Key info: - About the role: description of RTX and the position. Could be a paragraph. - Responsibilities: bullet list of "What You Will Do" items. - Requirements: maybe "U.S. Person" requirement? Also "Security Clearance Type: None/Not Required". Also maybe "Work Location: hybrid role, eligible candidates must reside within commuting distance of ...". That could be under Requirements or maybe a separate section? But we can include under Requirements or maybe a separate "Location" but not required heading. We'll include under Requirements as prose. - Qualifications: "You Must Have" and "We Prefer". Could be combined under Qualifications heading with sub-sections? But we only have headings defined; we can put both under Qualifications with paragraphs and lists. - Skills: maybe not explicit separate; but we could treat technical experience as skills. However we should only include a Skills section if posting has real specific content for it. There's a list of technical experience under Qualifications; we could put that under Qualifications rather than separate Skills. Probably better to not create Skills unless explicit. - Benefits: paragraph about total rewards package, list of some benefits. - Pay: salary range given: 132,400 USD - 251,600 USD. - Schedule: hybrid role description: "Hybrid: Employees who are working in Hybrid roles will work regularly both onsite and offsite. Ratio of time working onsite will be determined in partnership with your leader." Also mention work location commuting distance. Could be under Schedule. We need to avoid filler like "commensurate with experience". Not present. We must not include boilerplate like EEO, privacy policy, etc. We need to preserve all substantive information. Let's extract. About the role: Paragraph(s) describing RTX and the position: "At RTX, the world's largest aerospace and defense company, 185,000 great minds are united by purpose and inspired to make a difference solving the world’s most complex problems. With our three market leading businesses, world-class operations and investments in research and development, we offer capabilities and opportunity no one else can. Together, we push the boundaries of known science and find new ways to connect and protect our world. Join us and help shape the future of aerospace and defense. The following position is to join our RTX Enterprise Services team: We are seeking an experienced AI Architect to define and guide the architecture of enterprise Artificial Intelligence and Machine Learning solutions across RTX. This role will partner with business units, product teams, engineering organizations, domain architects, cybersecurity, data, and enterprise technology teams to translate complex business needs into scalable, secure, and production-ready AI architectures. The ideal candidate combines deep AI/ML expertise with strong software, data, cloud, and enterprise architecture experience and has demonstrated success guiding complex technology solutions from concept through production. A key focus of this role will be identifying common needs across RTX business units and translating them into reusable enterprise AI capabilities, reference architectures, and design patterns that accelerate adoption while reducing duplication and technical complexity." That's a good paragraph. Responsibilities: bullet list from "What You Will Do". Items: - Define end-to-end architectures for enterprise AI and ML solutions spanning traditional machine learning, Generative AI, agentic AI, data, applications, APIs, platforms, infrastructure, and enterprise systems. - Partner with business and technology leaders to translate business opportunities and requirements into architecture blueprints, technical strategies, success criteria, and implementation roadmaps. - Determine the appropriate technical approach for complex business problems, including traditional software, machine learning, Generative AI, retrieval-augmented generation, agentic AI, or combinations of these approaches. - Develop reusable reference architectures, design patterns, standards, and technical guardrails, and identify common requirements across RTX business units that can be addressed through reusable enterprise AI capabilities. - Architect modern AI solutions including model selection and routing, retrieval and grounding, context engineering, agent orchestration, tool use, state and memory, human-in-the-loop workflows, evaluation, observability, and secure enterprise integration. - Define architecture patterns for AI/ML data pipelines, model serving, model lifecycle management, MLOps, deployment, monitoring, and operation across cloud, hybrid, on-premises, and restricted environments. - Evaluate technology and platform alternatives and lead build, buy, configure, and integrate decisions considering business value, scalability, interoperability, security, performance, cost, and operational complexity. - Lead architecture and technical design reviews, partner with enterprise architecture, cybersecurity, data, identity, privacy, and Responsible AI teams, and provide technical leadership and mentorship across engineering teams. Also "What You Will Learn" could be considered responsibilities? It's more about learning; but we could include under Responsibilities or maybe a separate section? Not required heading. Could be included under Responsibilities as additional bullet points? Might be considered part of role description. But we can keep them as part of Responsibilities or maybe as a separate "Learning Opportunities" but not a defined heading. Safer to include under Responsibilities as bullet points? However the instruction: Use
- for any list of duties/requirements/benefits. "What You Will Learn" is not duties but could be considered part of role. Might be okay to include as list under Responsibilities? Might be stretching. Better to keep only duties list. We'll omit the "What You Will Learn" list? But we must preserve ALL substantive information. So we need to include that info somewhere. Could be under a separate heading like "What You Will Learn" but not in allowed headings. Could we treat it as part of Responsibilities? It's not duty but still substantive. Could we add a section "Learning Opportunities"? Not allowed headings. The instruction says: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It gives examples but not exclusive list. So we could add a heading like "What You Will Learn" if we want. However the instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we should stick to those headings. It doesn't explicitly forbid others, but to be safe, we should use only those headings. So we need to fit the "What You Will Learn" content somewhere else, maybe under About the role or Qualifications. Could add a paragraph under About the role describing learning opportunities. That would preserve info. Thus About the role can be expanded to include also what you will learn. Similarly, "What You Will Learn" bullet list: - How AI and ML technologies are applied across a global aerospace and defense enterprise spanning diverse business, engineering, manufacturing, and operational domains. - How enterprise AI platforms and reusable architecture patterns enable AI solutions to scale across multiple business units while meeting security, data, and governance requirements. - How Generative AI and agentic AI capabilities are evolving from experimentation into production systems that interact with enterprise data, tools, applications, and workflows. - How AI architectures are designed across commercial cloud, hybrid, on-premises, and restricted computing environments. - How emerging AI technologies, models, frameworks, interoperability standards, and industry practices can be evaluated and translated into practical enterprise capabilities. - How to influence the technical direction of enterprise AI by working across business units, architecture disciplines, engineering organizations, and senior leadership. We can incorporate these as a paragraph or list under About the role. Now Requirements: includes U.S. Person requirement, security clearance none, work location commuting distance, maybe also "Position Role Type: Hybrid". Also maybe "U.S. Citizen, U.S. Person, or Immigration Status Requirements: This job requires a U.S. Person." Also "Security Clearance Type: None/Not Required". Also "Work Location: This is a hybrid role, eligible candidates must reside within commuting distance of Farmington, CT, El Segundo, CA, San Jose, CA, Tucson, AZ, McKinney, TX, Andover, MA, Cedar Rapids, IA, or Charlotte, NC." Also "Please ensure the role type defined below is appropriate for your needs before applying to this role." That's more instruction; we can ignore as boilerplate? It's not substantive? Might be considered meta. We'll keep location and hybrid info. Thus Requirements section: paragraph(s) covering U.S. Person requirement, security clearance none, hybrid work location and commuting distance. We could also include "Position Role Type: Hybrid" as part of Requirements. Now Qualifications: includes "You Must Have" and "We Prefer". We'll create two sub-sections maybe as paragraphs with lists. We must not invent headings like "Must Have" etc. We'll just put content under Qualifications heading, using paragraphs and lists. We need to list the must-have qualifications: - A University Degree in Computer Science, Artificial Intelligence, Machine Learning, Engineering, or a related STEM discipline and a minimum of 10 years of relevant professional experience, or an Advanced Degree in a related field and a minimum of 7 years of relevant professional experience. - A minimum of 5 years of experience designing, developing, integrating, or architecting AI/ML solutions, including experience taking AI or ML capabilities beyond experimentation into production environments. - Experience serving as a technical architect, solution architect, technical lead, or senior engineer for complex enterprise software, data, cloud, or AI/ML systems. - Technical experience with AI/ML systems and modern AI application architectures, including Generative AI and large language models. - Experience designing distributed systems, APIs, microservices, enterprise integrations, data pipelines, or cloud-native applications using at least one major public cloud platform. - Experience translating business and technical requirements into architecture designs and evaluating technical, business, cost, security, and operational tradeoffs. - Experience working with enterprise security concepts including identity and access management, authentication and authorization, data protection, application security, and secure system integration. Now preferred qualifications list: - Experience architecting production Generative AI, retrieval-augmented generation, agentic AI, or multi-agent systems including modern AI architecture patterns including model selection and routing, embeddings, vector and enterprise search, context engineering, structured outputs, tool calling, orchestration, memory, state, and human-in-the-loop workflows. - Experience with emerging agent technologies and interoperability approaches such as Model Context Protocol (MCP), agent identity, secure tool integration, or similar standards. - Experience with AI evaluation, observability, tracing, guardrails, model monitoring, Responsible AI, model governance, or production AI reliability and with traditional machine learning lifecycle capabilities including data pipelines, feature engineering, model serving, model registries, monitoring, and MLOps. - Experience designing AI architectures across multiple models, vendors, platforms, and cloud, hybrid, on-premises, or restricted environments. - Experience with Kubernetes, containers, CI/CD, infrastructure-as-code, and modern application deployment architectures. - Familiarity with relevant AI risk, cloud architecture, and enterprise architecture frameworks and principles, such as NIST AI RMF, cloud well-architected frameworks, TOGAF, Zachman, or similar disciplines, and experience applying them to enterprise technology decisions. - Demonstrated ability to lead technical discussions, influence architecture decisions across multidisciplinary teams, and communicate complex technical concepts to technical and non-technical stakeholders. Now Benefits: paragraph about total rewards package and list of some benefits. We have: "Whether you’re just starting out on your career journey or are an experienced professional, we offer a robust total rewards package with compensation; healthcare, wellness, retirement and work/life benefits; career development and recognition programs. Some of the benefits we offer include parental (including paternal)