Associate Director, Applied AI Engineering - PxE Consulting

We need to output HTML fragment with sections: About the role? The posting includes Role Overview, Key Responsibilities, The team, The successful candidate will possess: (maybe Qualifications), Required Qualifications, etc. We must use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. Not present. Remove duplicated lines. Remove application instructions (none). Remove minor metadata like Job ID etc (none). Must not repeat job title as heading. Must not put Job ID/requisition numbers as headings. We need to decide sections: About the role (role overview). Responsibilities (Key Responsibilities). Requirements (maybe Required Qualifications). Qualifications (maybe The successful candidate will possess:). Skills (maybe list of tech stack). Benefits (maybe discretionary annual incentive program). Pay (wage range). Schedule (maybe ability to work in local office at minimum 3 days per week, travel 0-10%). Also location requirement maybe not schedule. We must not create sections with filler like "commensurate with experience". We have actual content for Pay: wage range $130,900 to $268,700. Also mention discretionary annual incentive program. So Pay section can include that. Schedule: ability to work in local office at minimum 3 days per week, travel 0-10% average. That's schedule info. Benefits: maybe mention discretionary annual incentive program? Could also be considered benefit. But we already used that in Pay. Could also list other benefits not given. So maybe Benefits section omitted if no specific benefits besides incentive. But we could include "Discretionary annual incentive program" as benefit. However the instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state wage range and incentive program, so we can have Pay and Benefits. Benefits: discretionary annual incentive program. Also maybe mention "Must be legally authorized to work in the United States without the need for employer sponsorship" is a requirement not benefit. We need to avoid duplication. Let's extract content. Role Overview paragraph: "As an Associate Director, Applied AI Engineering , you will set the engineering vision and technical direction for the firm's enterprise solutions-mapping business capabilities to the enterprise technology landscape and defining how GenAI and agentic capabilities are built directly into the products we deliver. Leading across teams and product groups, you will stay hands-on in your craft-shaping architecture, design, and code-while driving the standards and reference architectures that engineers build against. Your leadership will be pivotal in delivering tangible value across Deloitte's product and AI investments, aligning technical solutions with business and technology strategy, and advancing Applied AI engineering across the organization. You will bring extensive engineering craftsmanship and deep expertise across software and data engineering, solution architecture, and AI/ML and GenAI, together with an exemplary track record of high-quality, outcome-focused delivery at scale. The ideal candidate is a role-model engineering leader who leads by doing -setting vision, elevating standards, developing engineers and emerging leaders, and building trusted relationships with stakeholders from engineering teams to executives." That's About the role. Key Responsibilities: a long list with bullet-like sentences but not actual bullet list. We need to convert to

• . We must preserve all substantive information; do not summarize away detail. So we need to break each responsibility into list items. The text includes headings like "Strategic Vision and Alignment:", "Advocacy and Technology Roadmap:", etc. We can treat each as a list item with its description. We'll need to parse. Let's extract responsibilities sections: - Strategic Vision and Alignment: Craft and articulate a vision for Applied AI engineering across the firm's enterprise solutions-mapping business capabilities to the enterprise technology landscape and defining how GenAI and agentic capabilities are built directly into the products we deliver-in alignment with the Business Strategy and US Deloitte Technology strategy. Collaborate with diverse stakeholders across product, engineering, experience, delivery, security, and infrastructure at all organizational levels. - Advocacy and Technology Roadmap: Advocate for, develop, and communicate the integrated Applied AI engineering, architecture, and technology strategy and its implementation roadmap to engineering teams and business stakeholders. Ensure the organization is well-informed about objectives, KPIs, maturity, compliance, and progress. Promote a culture of reuse, quality, and speed-keeping an eye on leverage of existing assets and on the inference, token, and cloud cost of what we build, to maximize outcomes and minimize total cost. - Craft Mastery and Objectives Realization: Define, measure, and drive the achievement of KPIs and NFRs spanning system performance, scalability, security, reliability, and maintainability. Establish and evolve Applied AI engineering, architecture, and AI/ML/GenAI reference architectures, standards, and best practices-including spec- and context-driven development, evaluations, AI agent orchestration, and the AI and Agentic SSDLC that carries work from discovery to production to operations with full automation and quality checks through the SSDLC lifecycle. Remain hands-on with design, architecture, and code-contributing to team and product group velocity and staying engaged with engineers across the SSDLC-while reviewing code, driving tech-debt reduction, and experimenting with new technology. - Capability Evolution and Development: As a recognized engineering leader, mentor and develop engineers and emerging engineering leaders, coaching modern Applied AI engineering practices-full-stack and micro-services, cloud-native design, AI/ML/GenAI and agentic systems, data engineering, application-level infrastructure-as-code, and advanced deployment techniques (Blue-Green, Canary, A/B testing) that minimize downtime. Lead by example through thought leadership-showcasing experiments internally, speaking at conferences, publishing whitepapers or blogs, and leading R&D collaborations, including with academia. Cultivate a growth mindset and modern engineering behaviors across the organization. - Iterative Value Delivery: Embrace an iterative and incremental approach to Applied AI product engineering, favoring action and rapid learning over extensive upfront planning. Apply a leaning-forward approach and empirical methods to navigate complexity and uncertainty, ensuring each iteration delivers value and stays aligned with customer and business goals. - Customer-Centric Problem Solving: Maintain a relentless focus on solving the most critical challenges faced by customers and users, aligning technical solutions with business outcomes. Minimize unnecessary technical complexity and avoid overengineering-features and functionality that do not add value-and drive teams toward peak performance through continuous learning and collaborative execution. - Expert Proficiency and Continuous Improvement: Possess deep expertise in modern Applied AI engineering and architecture practices, with a keen ability to identify inefficiencies and opportunities for innovation across the product lifecycle. Continuously enhance the engineering operating model to be lean, adaptable, and responsive-guiding and transforming the organization to embrace lean principles and foster a culture of innovation. - Tech/Quality Risk Management: Establish and evolve reference architectures, coding standards, and engineering and quality benchmarks that ensure robust, secure, scalable, and reliable/resilient solutions. Ensure appropriate, responsible technology adoption-developing explainable, scalable, reliable, and secure AI and agentic products-and proactively identify technical risks, developing mitigation strategies through proactive problem-solving and contingency planning. - Influential Communication: Influence, persuade, and drive decision-making across the organization. Communicate effectively in both written and verbal forms, crafting clear, structured arguments and technical trade-offs supported by evidence. - Organizational Engagement and Collaboration: Engage stakeholders at all levels-from team members to middle management to executives-building collaborative, constructive relationships and co-creating momentum and value across multiple organizational levels. We'll put each as
• . Now Requirements: maybe "The successful candidate will possess:" list: Excellent interpersonal and organizational skills, with the ability to handle diverse situations, complex projects, and changing priorities, behaving with passion, empathy, and care. That's more like Skills/Requirements. We'll treat as Requirements? Actually we have Required Qualifications separate. Qualifications: maybe "Required Qualifications" section includes bullet list of qualifications. We'll treat as Qualifications. Skills: maybe the list of technologies under Required Qualifications could be considered Skills. But we can also put them under Qualifications as part of the bullet list. However we need to follow instruction: Use sections only when posting has real specific content. We have content for Required Qualifications (education, years experience, tech stack, etc). We can make a Qualifications section with that content. Skills maybe not needed separately if we incorporate tech stack into Qualifications. But we could also make Skills section for the tech stack list. However we risk duplication. Better to have Qualifications include education and experience, and Skills include the specific technologies. But the posting lumps them together under Required Qualifications. We could split: Qualifications: education and years experience; Skills: specific tech stack. Let's see. Required Qualifications text: "Required Qualifications: A bachelor's degree in computer science, software engineering, data science, machine learning, or related discipline. Experience is the most relevant factor. 10+ years of full-stack software engineering experience with most of the following: Angular, React, NodeJS, Python, C#, .NET, Java, SQL/NoSQL, REST/SOAP/GraphQL, SSO/MFA, PyTorch, TensorFlow, LangChain, LangGraph, as well as unit and integration testing frameworks. 7+ years of experience architecting and delivering enterprise solutions on modern technology stacks (e.g., API Gateways, Message Brokers, Queuing Services, Workflow Automation & Orchestration, ETL/ELT, Event Streaming, Real-Time Data Processing, Service Mesh) and cloud-native engineering, using FaaS, PaaS, and micro-services on any of the cloud hyperscalers such as Azure, AWS, or GCP, including leveraging their AI/ML services such as Azure OpenAI, AWS Bedrock, or Vertex AI, plus application-level infrastructure-as-code and cost-aware engineering (FinOps accountability). 5+ years of experience building AI/ML and agentic applications, with hands-on GenAI experience across LLM integration (OpenAI, Anthropic, or open-source models), RAG pipelines, prompt engineering, vector databases, evaluations, and AI agent orchestration. 2+ years of experience in establishing engineering standards, including actively leading, mentoring, and guiding team members in the adoption and continuous improvement of these standards. Prior software engineering experience with the understanding of Business Context Diagrams (BCD), sequence/activity/state/entity relationship/data flow diagrams, OOP/OOD, data structures, algorithms, and code instrumentations, and AI-augmented spec-driven development. Prior experience using methodologies & tools such as XP, Lean, DevSecOps, SRE, ADO, GitHub, SonarQube, MLflow, and agentic AI frameworks (e.g. LangFuse, LangSmith, or equivalent multi-agent orchestration tools) etc. to deliver high-quality products rapidly. Ability to work in your local office at a minimum of 3 days per week Candidates must be located within a commutable distance to one of the select locations available for this role Must be legally authorized to work in the United States without the need for employer sponsorship, now or at any time in the future Ability to travel 0-10%, on average, based on the work you do and the clients and industries/sectors you serve" We need to separate schedule items (ability to work 3 days per week, travel) into Schedule section. Location requirement maybe not needed as separate section; could be part of Requirements? But we have no specific section for location; we could include in Requirements as a note. But we should not create a section for location if not requested. We'll keep location requirement within Requirements or maybe under Qualifications as a bullet. Pay: wage range and discretionary annual incentive program. Benefits: maybe discretionary annual incentive program could be benefit, but we already used in Pay. Could also list other benefits not given. So maybe we omit Benefits section. Schedule: ability to work in local office at minimum 3 days per week, travel 0-10% average. Now we need to output HTML fragment with headings

  and content. We must not include