Senior Technical Consulting Manager - Practice & Domain Overlay

Job description

To get the best candidate experience, please consider applying for a maximum of 3 roles within 12 months to ensure you are not duplicating efforts. Job Category Sales Job Details About Salesforce Salesforce is the #1 AI CRM, where humans with agents drive customer success together. Here, ambition meets action. Tech meets trust. And innovation isn’t a buzzword — it’s a way of life. The world of work as we know it is changing and we're looking for Trailblazers who are passionate about bettering business and the world through AI, driving innovation, and keeping Salesforce's core values at the heart of it all. Ready to level-up your career at the company leading workforce transformation in the agentic era? You’re in the right place! Agentforce is the future of AI, and you are the future of Salesforce. Salesforce Professional Services is building a Global Solutions CoE to create a more consistent, scalable, and predictable way to shape, scope, estimate, and deliver Professional Services (ProServe) programs. We are looking for a Practice & Domain Overlay Manager to make sure the CoE model is not generic. This role brings the required product, industry, regulatory, and domain depth into scoping and estimation so that our standards work in real customer situations. This role does not own every product or every industry. Instead, it owns the process of identifying where specialized input is needed, capturing that input into reusable patterns, and ensuring the CoE model reflects real delivery complexity. The right candidate understands how Salesforce programs vary by cloud, industry, geography, regulatory environment, and customer maturity — and can turn those differences into practical scoping and estimation guidance the field can actually use. What You Will Do 1. Identify Where Domain Expertise Is Required You will define when a deal needs additional practice or domain input during scoping. Examples: • Data Cloud program with complex source systems and identity resolution • Agentforce program with unclear automation boundaries or trust requirements • Health / Life Sciences program with regulatory or data privacy considerations • Public Sector program with procurement, compliance, or security constraints • Financial Services program with sensitive data, controls, or integration complexity • Multi-cloud program involving Sales, Service, Data, Marketing, Commerce, MuleSoft, or Industry Clouds Your job is to make these triggers explicit so the field knows when to pull in the right expertise. 2. Build Product and Industry Overlay Patterns You will create practical overlays that sit on top of the core CoE model. Each overlay should answer: • What is different for this product, industry, or domain? • What additional discovery questions are required? • What scoping assumptions should be added? • What roles or skills are typically needed? • What risks should be flagged early? • What SOW language or exclusions are required? • What delivery dependencies must be confirmed before signature? Examples of overlays: • Data Cloud readiness overlay • Agentforce scoping overlay • Regulated industry overlay • Public Sector delivery overlay • Integration complexity overlay • Migration / data readiness overlay • Multi-cloud transformation overlay • Change and adoption overlay 3. Translate Practice Knowledge Into Reusable Assets You will work with Practices and domain SMEs to convert expertise into usable CoE assets. Expected outputs: • Discovery questions • Scoping checklists • Estimation factors • Role and skill assumptions • Risk indicators • SOW assumptions and exclusions • Delivery readiness checkpoints • Reference examples from past programs This role is not about creating long documents. The goal is to create short, reusable assets that can be embedded into scoping workflows, tools, agents, and playbooks. 4. Maintain the Domain Pattern Library You will own the structure and quality of the domain pattern library. The library should include: • Product-specific scoping guidance • Industry-specific considerations • Regulatory and compliance triggers • Common risks and mitigation patterns • Standard assumptions and exclusions • Recommended SMEs / practices to engage • Reusable examples from successful programs You will ensure assets are current, easy to find, and practical enough for field use. 5. Support Better Estimation Accuracy You will help improve estimates by identifying domain-specific effort drivers. Examples: • Number and quality of data sources • Number of integrations • Number of clouds involved • Customer operating model maturity • Regulatory review requirements • Testing and validation intensity • Migration complexity • Localization / regional requirements • AI governance and trust requirements • Change manageme