Lead Software Engineer, AI Agents & Orchestration

We need to output only HTML fragment, using

h3 for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. We need to parse the posting. First paragraph: "Creating Peace of Mind by Pioneering Safety and Security At Allegion, we help keep the people you know and love safe and secure where they live, work and visit. With more than 40 brands, 14,000+ employees globally and products sold in 130 countries, we specialize in security around the doorway and beyond. Additionally, Allegion is proud to be recognized with the 2026 Gallup Exceptional Workplace Award (GEWA) for the third consecutive year, earning distinction in both the employee engagement and strengths categories. This year, Allegion also received Gallup’s With Distinction honor — a designation reserved for a select group of organizations that go above and beyond in building exceptional workplace cultures." That's about the company, could be "About the role"? Actually "About the role" is typical heading for description of role. But we have a section "Why This Role Is Important To Us" and "Why Work for Us?" etc. We need to decide which sections to include. We need to map content to headings: About the role (maybe summary), Responsibilities (What You Will Do), Requirements (What You Need To Succeed), Qualifications (maybe same as Requirements?), Skills (maybe preferred?), Benefits (What You'll Get From Us), Pay (Compensation), Schedule (maybe hybrid work model details). We must only include sections if posting has real specific content. Let's extract: About the role: Could be the initial description: "Lead Software Engineer, AI Agents & Orchestration ... As part of the Global Software Solutions Engineering team, you will operate at the intersection..." That's more like role description. Could be placed under About the role. Responsibilities: "What You Will Do" bullet list. Requirements: "What You Need To Succeed" bullet list (education, experience, etc.) Qualifications: maybe same as Requirements? Could combine? But we need separate sections only if content distinct. Could treat Requirements as mandatory, Qualifications as preferred? The posting has "Preferred:" list under What You Need To Succeed. So we could have Requirements (mandatory) and Qualifications (preferred). Or we could have Skills section for technical skills. Benefits: "What You’ll Get From Us" list. Pay: "Compensation" section with salary range. Schedule: hybrid work model details: "This role offers the benefits of our dynamic hybrid work model—combining in-person collaboration for meaningful moments with the flexibility of remote work. Since hybrid arrangements can vary based on the needs of the individual, team and business, your talent acquisition partner will provide specific hybrid details about this role. We are committed to fostering a healthy work-life balance..." Also later: "While this is the current structure and we currently have no plans to change, we reserve the right to make changes to the hybrid schedule as needed at the Company’s discretion." That's schedule info. Thus we can include Schedule section. Now we must not include boilerplate like EEO, legal, etc. Remove duplicated lines, application instructions, etc. Also remove "Apply Today!" etc. We need to preserve all substantive information. So we need to include the content from each section, but we can format as

• for lists,

  for prose. We must not invent or summarize away detail. Must preserve all specifics. Let's extract each section's content precisely. First, About the role: The initial paragraph(s) before "Why This Role Is Important To Us". Let's capture: "Creating Peace of Mind by Pioneering Safety and Security At Allegion, we help keep the people you know and love safe and secure where they live, work and visit. With more than 40 brands, 14,000+ employees globally and products sold in 130 countries, we specialize in security around the doorway and beyond. Additionally, Allegion is proud to be recognized with the 2026 Gallup Exceptional Workplace Award (GEWA) for the third consecutive year, earning distinction in both the employee engagement and strengths categories. This year, Allegion also received Gallup’s With Distinction honor — a designation reserved for a select group of organizations that go above and beyond in building exceptional workplace cultures. Lead Software Engineer, AI Agents & Orchestration We are seeking a Lead Software Engineer, AI Agents & Orchestration with strong software engineering skills and demonstrated experience building and operating production generative AI systems to help build the AI operating system across Software Engineering functions. As part of the Global Software Solutions Engineering team, you will operate at the intersection of Software Engineering, Artificial Intelligence, Agentic Systems, Data Engineering, and Enterprise AI Governance. This role is responsible for designing, engineering, and operationalizing scalable AI orchestration frameworks that transform software application data into intelligent, auditable, and secure business outcomes. This role requires strong capabilities in both AI Engineering and Data Engineering. You will design data insights, orchestrate multi-agent workflows, develop Retrieval-Augmented Generation (RAG) systems, integrate enterprise knowledge sources, and establish the governance and observability capabilities required to operate AI safely within a security critical -environment." But note the job title appears again; we should not repeat job title as heading, but we can keep it in prose? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid it in prose. However we might want to avoid duplication but it's okay. But we might want to start About the role with a summary: maybe combine the first paragraph about Allegion and then the role description. We'll keep as is. Now Responsibilities: "What You Will Do" list: - Own the technical vision and architecture for major portions of the AI Workload Orchestration Platform - Design and engineer AI orchestration frameworks that coordinate multiple models, agents, tools, APIs, and GSS SW applications. - Develop agent-to-agent and human-in-the-loop workflows that automate complex operational and analytical processes. - Lead implementation of AI context engineering strategies and AI agent architectures. - Build reusable orchestration patterns that enable rapid deployment of AI-enabled business capabilities. - Design and develop scalable data pipelines supporting AI, analytics, and agentic workflows. - Build enterprise data products optimized for AI consumption. - Develop reusable AI platform components supporting multiple use cases and business domains. - Implement MLOps and LLMOps deployment, monitoring, versioning, and governance capabilities. - Implement Responsible AI guardrails, governance controls, and model risk management processes. - Build AI observability, evaluation, telemetry, and performance measurement solutions. - Design and implement RAG architectures for GSS SW products in collaboration with Enterprise teams. - Lead cross-team architecture reviews and drive alignment across infrastructure, SW Application and Enterprise teams. We need to keep each as

• . Now Requirements: "What You Need To Succeed" includes: - Bachelor's degree in Computer Science, Data Engineering, Information Systems, Artificial Intelligence, or equivalent practical experience. - 5–7 years of experience in Data Engineering, AI Engineering, Machine Learning Engineering, Software Engineering, or related disciplines. - Strong experience developing large-scale data pipelines and distributed data-processing solutions. - Experience with Python, SQL, APIs, workflow automation, and cloud-native architectures. - Proven experience designing, deploying, and maintaining RESTful APIs and web services at scale - Strong communication and stakeholder collaboration skills. - Track record of independently driving projects from concept through production deployment - This role requires strong systems thinking, cross-team influence, and a long-term view of platform scalability, reliability, and developer experience. Then "Preferred:" list: - LangGraph, Semantic Kernel, CrewAI, AutoGen, LangChain, or similar frameworks. - Databricks, Snowflake, Spark, Kafka, Delta Lake, Iceberg, and Airflow. - Experience with vector databases, semantic search, and enterprise RAG platforms. - Experience implementing MLOps, LLMOps, AI observability, and evaluation frameworks. - Knowledge of Responsible AI, data governance, and model risk management. - Experience with FastAPI, React, and Azure Cosmos DB or similar technology stacks. - Strong understanding of AWS and or Azure Cloud Platforms. We could treat the first block as Requirements (mandatory) and the Preferred as Qualifications or Skills. The instruction: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. We could have: - Requirements: mandatory bullet list. - Qualifications: preferred bullet list (or maybe combine with Skills). - Skills: maybe technical skills list (like Python, SQL, etc.) but that overlaps. Better to follow typical pattern: Requirements (education, experience), Qualifications (preferred experience/skills), Skills (maybe technical skills). But we have overlapping. Given the instruction: "Prefer a few substantive sections over many thin ones." So we might combine Requirements and Qualifications into one section? But we need to follow headings only if real content. Could have Requirements (mandatory) and Qualifications (preferred) as separate sections if both have content. That's two sections. Skills: maybe we could extract technical skills from both lists, but that would be duplicate. Better to not create Skills if it would be thin or duplicate. Thus we will have: - About the role (prose) - Responsibilities (ul) - Requirements (ul) - mandatory - Qualifications (ul) - preferred - Benefits (ul) - What You'll Get From Us - Pay (p) - compensation range - Schedule (p) - hybrid work model details Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now we need to strip out boilerplate: The sections like "Why This Role Is Important To Us", "Why Work for Us?" we need to incorporate their content into appropriate sections. The "Why This Role Is Important To Us" paragraph: It talks about Allegion GSS accelerating adoption of AI-enabled capabilities etc. That could be part of About the role or Responsibilities? It's more about why role important. Could be included in About the role as additional prose. Similarly "Why Work for Us?" includes career growth statements, values, etc. That could be part of Benefits? Actually Benefits already covers tangible benefits. The "Why Work for Us?" is more about culture, could be part of About the role or maybe a separate section but we don't have a heading for culture. Could incorporate into About the role as additional prose. We must preserve all substantive information, so we need to include that content somewhere. Let's extract "Why This Role Is Important To Us" paragraph: "Allegion GSS is accelerating the adoption of AI-enabled capabilities to improve operational efficiency, enhance platform assets, cybersecurity resilience, strengthen quality, and deliver intelligent experiences across the software product portfolio. As a Lead AI Orchestration Engineer, you will help establish the AI execution layer that enables secure collaboration between various software applications, large language models, internal knowledge repositories, agentic workflows, governance controls, and human decision makers. At Allegion, we are driven by a bold vision: redefining safety while empowering our employees to thrive. When you join our team, you become part of a culture that values innovation, purpose, and excellence. This role offers the benefits of our dynamic hybrid work model—combining in-person collaboration for meaningful moments with the flexibility of remote work. Since hybrid arrangements can vary based on the needs of the individual, team and business, your talent acquisition partner will provide specific hybrid details about this role. We are committed to fostering a healthy work-life balance and building meaningful connections, ensuring you have the tools, resources, and support needed to excel in any environment. Together, we’ll unlock your potential and create a lasting impact. While this is the current structure and we currently have no plans to change, we reserve the right to make changes to the hybrid schedule as needed at the Company’s discretion." Note that hybrid work model details appear here also; we will capture schedule details from this. Now "Why Work for Us?" paragraph: "Allegion is a Great Place to Grow your Career if: You're seeking