CCaaS x AI, Manager, Technical Transformation

We need to output HTML fragment with sections: About the role? The posting includes description of work you'll do, responsibilities, qualifications, skills, benefits/pay, schedule? There's a wage range and mention of discretionary annual incentive program. Also travel requirement. Also recruiting end date. Also team description. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include a section only when posting has real, specific content for it. So we need to decide which sections have content. - About the role: Could be the introductory paragraph about Deloitte Sales & Service team and role description. That seems appropriate. - Responsibilities: The "Work you'll do" bullet points (though not bullet list but sentences). We can extract responsibilities. - Requirements: Might be the qualifications required? Actually "Qualifications Required" list. Could be Requirements. - Qualifications: Could be the "Qualifications Required" and "Preferred". Might be overlapping. But we need separate sections for Requirements and Qualifications? The instruction says use those headings if content exists. We can treat "Requirements" as mandatory qualifications, and "Qualifications" as preferred? Or we could combine. But we need to avoid thin sections. Let's see content: There's "Qualifications Required" with bullet list of required qualifications. Then "Preferred" list. So we could have a section "Requirements" for required qualifications, and "Qualifications" for preferred? Or maybe "Skills" for the list of skills (ability to work independently etc). There's a list of skills after "A successful candidate would possess these skills:" which is a list of soft skills. That could go under Skills. - Benefits: There's mention of discretionary annual incentive program, travel up to 50%, limited immigration sponsorship maybe. Also maybe benefits not detailed. Could include "Benefits" section with those items. - Pay: There's wage range $144,00 to $241,000 (typo). Also mention of discretionary annual incentive program. So we can have Pay section. - Schedule: Not mentioned besides travel up to 50% (which is not schedule). No explicit schedule like full-time, remote etc. So we should not create Schedule section. We must not repeat job title as heading. No Job ID etc. We need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like recruitment end date? That's substantive? It's metadata but maybe we can fold into a short p. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Recruiting end date is minor metadata; we can include in a short p at top maybe. We need to output only HTML fragment, no markdown fences. Let's structure:

Recruiting for this role ends on December 31, 2026.

Then

About the role

with paragraph(s) describing team and role overview. Then

Responsibilities

with

• items derived from "Work you'll do" sentences. Then

  Requirements

  with
  • for required qualifications. Then

    Skills

    with
    • for the list of abilities. Then

      Qualifications

      maybe for preferred qualifications? But we already used Skills for soft skills; Qualifications could be preferred qualifications. However we might combine required and preferred under Qualifications? But we already used Requirements for required. Let's keep Qualifications for preferred. Then

      Benefits

      with
      • for travel up to 50%, limited immigration sponsorship, discretionary annual incentive program. Then

        Pay

        with paragraph about wage range and discretionary annual incentive program (maybe mention that it's subject to rules). Ensure we don't repeat. We must not include filler like "commensurate with experience". Not present. Check for duplication: The wage range sentence also mentions discretionary annual incentive program; we might mention it in Pay only. Now extract content precisely. About the role: The first paragraph: "CCaaS x AI Manager, Technical Transformation Our Deloitte Sales & Service team empowers organizations to build deeper relationships with customers through innovative strategies, advanced analytics, Generative AI, transformative technologies, and creative design. We can enhance customer experiences and drive sustained growth and customer value creation and capture, through customer and commercial strategies, digital products and innovation, marketing, commerce, sales, and service. We are a team of strategists, data scientists, operators, creatives, designers, engineers, and architects. Our team balances business strategy, technology, creativity, and ongoing managed services to solve the biggest problems that affect customers, partners, constituents, and the workforce" That's a lot. We'll put that as paragraph(s). Could split into two paragraphs for readability but not required. Responsibilities: From "Work you'll do" paragraph: "As a Technical Manager, you will lead the architecture, engineering, and delivery of cloud-based contact center and Generative AI solutions. You will work across business, functional, and technical stakeholders to design secure, scalable solutions using AWS and cross-platform CCaaS capabilities-from technical strategy and architecture through build, testing, deployment, and production support. Lead technical delivery for CCaaS and Contact Center AI transformations, guiding teams from solution design and architecture through implementation, testing, deployment, and production support.Design scalable AWS-based solutions using Amazon Connect, Lex, Bedrock, Lambda, API Gateway, S3, DynamoDB, and CloudWatch, incorporating Generative AI patterns such as RAG, agent/tool calling, knowledge grounding, and guardrails.Translate client requirements into technical architectures, integration designs, delivery plans, testing strategies, and secure cloud solutions spanning CCaaS, CRM, WFM, analytics, knowledge management, and enterprise platforms.Partner with client executives, architects, engineers, and operations leaders to resolve technical decisions, manage delivery risks, support proposals and estimates, and mentor Deloitte practitioners." We need to split into sensible list items. Could break by sentences. Let's create list items: - Lead the architecture, engineering, and delivery of cloud-based contact center and Generative AI solutions. - Work across business, functional, and technical stakeholders to design secure, scalable solutions using AWS and cross-platform CCaaS capabilities, from technical strategy and architecture through build, testing, deployment, and production support. - Lead technical delivery for CCaaS and Contact Center AI transformations, guiding teams from solution design and architecture through implementation, testing, deployment, and production support. - Design scalable AWS-based solutions using Amazon Connect, Lex, Bedrock, Lambda, API Gateway, S3, DynamoDB, and CloudWatch, incorporating Generative AI patterns such as RAG, agent/tool calling, knowledge grounding, and guardrails. - Translate client requirements into technical architectures, integration designs, delivery plans, testing strategies, and secure cloud solutions spanning CCaaS, CRM, WFM, analytics, knowledge management, and enterprise platforms. - Partner with client executives, architects, engineers, and operations leaders to resolve technical decisions, manage delivery risks, support proposals and estimates, and mentor Deloitte practitioners. Now Requirements (required qualifications): List from "Qualifications Required": - 8+ years of experience in technology consulting, software engineering, cloud architecture, or enterprise solution delivery, including 4+ years designing, building, deploying, and supporting AWS solutions in production. - Experience designing and implementing cloud-based contact center solutions using platforms such as Amazon Connect, Genesys, NICE CxONE, or Five9, including Generative AI capabilities such as LLMs, RAG, agent/tool calling, conversational AI, or automation. - Experience with AWS integration and cloud-native architectures, APIs, event-driven solutions, data flows, enterprise security controls, CI/CD, automated testing, source control, Agile/Scrum, and SDLC governance. - Bachelor's degree in Computer Science, Engineering, or equivalent work experience. - Ability to travel up to 50% on average, based on the work you do and the clients and industries/sectors you serve. - Limited immigration sponsorship may be available. Note: Travel and immigration sponsorship maybe better under Benefits but they are in qualifications required. We'll keep them under Requirements as they are listed there. Now Skills: list from "A successful candidate would possess these skills:": - Ability to work independently and collaborate as part of a team - Effective written and verbal communication skills - Meticulous attention to detail and quality of work product - Ability to build and sustain professional relationship - Ability to lead projects or workstreams - Ability to manage and prioritize multiple tasks in a fast-paced and dynamic environment - Strong interpersonal skills and professional demeanor - Ability to meet deadlines - Ability to provide clear guidance to others Now Qualifications (preferred): list from "Preferred": - Production delivery experience with Amazon Connect, Amazon Lex, and Amazon Bedrock (including streaming patterns, security, monitoring/operations). - Experience implementing enterprise controls: IAM, network segmentation (VPC), secrets management (Secrets Manager/KMS), and observability (CloudWatch). - Cross-platform exposure to Google Gemini (API/Vertex AI) and/or Dialogflow, including tool calling, safety controls, quotas/limits, and platform trade-offs. - Experience leading Contact Center AI use cases end-to-end (design through adoption) and partnering with contact center operations leaders on change management and KPI realization. - Strong understanding of SDLC methodologies (Agile, SCRUM, RUP, other) Now Benefits: we could include travel up to 50% and limited immigration sponsorship and discretionary annual incentive program. But travel and immigration already in Requirements; maybe we should not duplicate. Better to keep them only once. Since they appear under Qualifications Required, we could keep them there and not duplicate in Benefits. Benefits could be just discretionary annual incentive program. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine travel and immigration under Benefits and remove from Requirements? But they are explicitly listed under Qualifications Required; moving them might be considered omitting detail? We could keep them in Requirements and also mention in Benefits? That would duplicate. Better to keep them only once. Since they are part of qualifications required, we keep them under Requirements. Benefits then only discretionary annual incentive program. That's a bit thin but still substantive. Could also include "discretionary annual incentive program" as benefit. Pay: wage range and mention of discretionary annual incentive program (but we already mentioned in Benefits). To avoid duplication, we could mention pay range only, and note that incentive program is separate benefit. But the text says: "You may also be eligible to participate in a discretionary annual incentive program, subject to the rules governing the program, whereby an award, if any, depends on various factors, including, without limitation, individual and organizational performance." That's a benefit. So we can put that under Benefits. Pay section just wage range. Thus: Pay: paragraph: "A reasonable estimate of the current range is $144,00 to $241,000." (Note typo: missing a zero after 144? It's $144,00 to $241,000. We'll keep as is.) Now we must not include boilerplate like "The wage range for this role takes into account ..." That's explanatory but still substantive? It's describing how range determined. Might be considered boilerplate? It's not cookie/legal/EEO. It's about compensation methodology. Might be okay to keep but could be considered filler. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This is not those. It's about compensation methodology; could be kept but it's somewhat generic. However we need to preserve ALL substantive information; not invent or summarize away detail. The sentence explains that the range takes into account factors etc. That's substantive? It's generic but still part of posting. I'd keep it maybe as part of Pay section. But we must avoid filler like "commensurate