Domain Architect, Salesforce Ecosystem

About AbbVie AbbVie's mission is to discover and deliver innovative medicines and solutions that solve serious health issues today and address the medical challenges of tomorrow. We strive to have a remarkable impact on people's lives across several key therapeutic areas including immunology, oncology, and neuroscience - and products and services in our Allergan Aesthetics portfolio. For more information about AbbVie, please visit us at  www.abbvie.com . Follow @abbvie on  LinkedIn,   Facebook ,  Instagram ,  X  and  YouTube. The Domain Architect, Salesforce Ecosystem owns the ecosystem roadmap, architecture standards, and design review operations for every Salesforce platform in Global Commercial Business Technology Services, governing approximately 32 critical applications post-migration. The role is the primary architecture relationship owner for Salesforce and is accountable for driving decisions for Salesforce technology adoption, such as Data 360, Agentforce, AgentExchange, and Headless 360.  Responsibilities: Advance program objectives and resolve high-impact technical issues.  Advise on and validate system architecture designs, orchestrate cross-functional technical efforts, shape implementation strategies, and provide recommendations on ambiguous technical questions. In this domain: rule on Salesforce org strategy and connected-org questions, for example, steering decisions on Sales Cloud versus Service Cloud versus Health Cloud boundaries, and on where a capability belongs when Salesforce ships a native alternative to something AbbVie already runs.  Manage design reviews and enforce architecture compliance.  Lead Domain Review Board reviews for all initiatives touching Salesforce, classify review tier through weekly project request intake reviews, evaluate solution designs against the Architecture Review Checklist, and coordinate remediation plans with the Salesforce application teams. Own the Salesforce sections of the standards library and report review quality metrics.  Drive continuous improvement of architecture frameworks.  Iterate the Salesforce reference architectures and packaged deployment standards as the platform evolves, analyzing review feedback and benchmarking against Salesforce reference patterns and the Forward Deployed Engineering Partner Network. Own end-of-life and version currency positions, including managed package and API version deprecation exposure.  Own technical strategy for major, complex programs.  Own the Salesforce architecture workstream of large implementation programs: platform design patterns, integration contracts, migration sequencing, sunset sequencing, and cutover criteria. Define technical approach and success criteria, establish quality standards, and coordinate multidisciplinary teams and external partners to standards-aligned delivery.  Own the Salesforce ecosystem roadmap and cloud boundary decisions . Publish and maintain the multi-year Salesforce roadmap: cloud-by-cloud target state, release adoption posture, org strategy, and the sequence in which commercial capabilities consolidate onto the platform. Define and defend the boundaries between orgs, with the data model and licensing consequences of each decision stated. Reconcile the roadmap quarterly against the Salesforce vendor roadmap.  Author the Salesforce Standards Library.  Own data model conventions, integration patterns, packaging and deployment standards, environment and sandbox topology, security and sharing model patterns, and platform limits governance. Onboard Salesforce application teams to the standard delivery pipeline with the packaged deployment standard in force.  Govern agent and AI capability on the platform.  Own the evaluation and admission path for Agentforce agents, AgentExchange listings, and MCP tool exposure so the marketplace does not become an ungoverned procurement channel. Define what gets built, what gets installed, and what gets rejected, and enforce the constraint that Agentforce agents operate exclusively within the Salesforce platform. Hold the Data 360 boundary: authoritative mastering stays upstream in the enterprise data estate.  Own the Salesforce vendor relationship and rationalization decisions . Serve as primary architecture relationship owner for Salesforce: run the quarterly strategic review cadence, track the release stream and product direction, and surface roadmap misalignment with the cost of waiting stated. Identify duplicate capability inside the Salesforce estate and lead build, buy, or wait evaluations with supporting total cost of ownership analysis; a decision to wait must be time-boxed with a named re-evaluation trigger. Provide dotted-line technical leadership and cross-domain coordination.  Provide architectural direction and mentorship to the Salesforce Platform Architect and to solutions architects in delivery organizations, and participate in Platform Architect hiring. Own the Salesforce side of the integration seams to content platforms, to integration middleware, and to the enterprise data estate.  Lead competitive evaluation of new Salesforce capability. Lead technical assessment of new Salesforce products and of AgentExchange and marketplace offerings using the RFP Playbook where a competitive evaluation applies.  Required: Bachelor's degree in Computer Science, Information Systems, Engineering, or a related field with 9 years of experience; OR Master’s Degree with 8 years of experience; OR PhD with 4 years of experience. Respective years of progressive experience in enterprise, domain, or solution architecture, with demonstrated experience architecting on the Salesforce platform at enterprise scale.  Deep architectural depth across multiple Salesforce clouds, including at least two of Sales Cloud, Service Cloud, Health Cloud, Marketing Cloud, Commerce Cloud, or Data Cloud, with demonstrated command of the Salesforce data model, sharing and security model, platform limits, and governor constraints.  Demonstrated experience with Salesforce org strategy: multi-org versus single-org trade-offs, connected orgs, environment and sandbox topology, and the licensing and data model consequences of each.  Experience with Salesforce release management and packaged deployment (managed or unlocked packages, source-driven development, CI/CD for Salesforce). Experience migrating a Salesforce estate from one CI/CD toolchain to another is directly relevant.  Experience architecting a CRM platform migration or consolidation program, including coexistence patterns between an incumbent and a target platform.  Demonstrated experience authoring and publishing architecture standards, reference architectures, or roadmaps that delivery teams actually adopted, and leading architecture