Domain Architect, Applications and Integration

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, Applications and Integration owns the ecosystem roadmap, architecture standards, and design review operations for integration of middleware, API governance, custom applications, and cross-platform interoperability in Global Commercial Business Technology Services. API contracts, agentic patterns and registry, event schemas, and integration patterns published here bind the CRM estate, the content estate, the field operations estate, and every interface into the enterprise data platforms.  Responsibilities: Advance program objectives and resolve high-impact technical issues.  Advise on and validate sophisticated programs and analyses, orchestrate cross-functional technical efforts, and provide recommendations on ambiguous technical questions. Adjudicate interface ownership when two teams build competing APIs for the same entity, and rule on point-to-point versus middleware versus native platform integration.  Manage design reviews and enforce architecture compliance.  Lead Domain Review Board reviews for integration and custom application initiatives and serve as the standing integration reviewer for cross-domain reviews, where this domain's findings recur most often. Participate in weekly project request intake, review solutions against the architecture review standards, and coordinate remediation with named owners and dates.  Lead cross-functional training and translate strategy into blueprints . Train and develop training materials for delivery teams on API design standards, event schema contracts, and the integration playbook so patterns are applied consistently rather than reinvented, and resolve design conflicts across domain boundaries. This includes active upskilling for internal talent and developing hiring standards.  Drive continuous improvement of architecture frameworks.  Iterate integration standards from real interface failures and review findings, benchmarking against the enterprise API standards set by Enterprise Architecture. Own integration platform version currency and end-of-life positions, including API version deprecation exposure and legacy ETL retirement. Maintain the cross-domain dependency tracker.  Own technical strategy for major, complex programs.  Own the integration architecture workstream of major programs, including the global cross-domain integrations: API specifications, event schemas, agentic ecosystems, and service level agreements between all adjacent commercial systems.  Own the applications and integration ecosystem roadmap.  Publish and maintain the multi-year roadmap for integration middleware and the custom application estate: target integration platform posture, evaluate and promote evolution of our integration and ESB and ETL platforms and offerings.  Establish and operate API governance.  Own API design standards, versioning and deprecation policy, contract-first development, catalog and discoverability, security patterns, and the criteria that make an interface reusable rather than project-specific. Author reference integration architectures covering synchronous API, asynchronous and event-driven, batch and file, and platform-native integration, with clear guidance on when each applies.  Own the data platform interface contracts . Own the commercial side of every interface with data and AI platforms. Negotiate and document the contract, hold the federation-over-copy rule so commercial systems consume mastered data by reference, and escalate genuine conflicts through governance rather than resolving them by exception. Run interface rationalization and build, buy, or wait analysis.  Identify and resolve duplicate interfaces: multiple APIs for the same entity, overlapping pipelines, and point-to-point connections that should be mediated. Run this as a standing program rather than a project; it is the most direct duplicate-capability reduction lever in the portfolio. Lead build, buy, or wait evaluations with supporting total cost of ownership analysis.  Own custom application and automation standards, vendors, and mentorship.  Set design, integration, security, and supportability standards for the custom application estate, including handover requirements for externally built applications, and own commercial workflow automation and RPA governance. Serve as primary architecture relationship owner for established ESB, ETL, and interoperability, running the quarterly strategic review cadence and governing external and third-party connectivity. Provide architectural direction and mentorship to product and application architects and to solutions architects. 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 focused on integration architecture or API platform architecture at enterprise scale.  Deep architectural experience with at least one enterprise API management or integration platform (MuleSoft, Apigee, or equivalent), including API gateway design, policy enforcement, and platform operations.  Demonstrated command of enterprise integration patterns across styles: synchronous API, asynchronous messaging and event-driven, batch and file, and platform-native integration, with the judgment to select between them rather than defaulting to one.  Experience establishing API governance in an organization that did not have it: design standards, contract-first practice, versioning and deprecation policy, and a catalog that teams actually use.  Demonstrated experience rationalizing duplicate or overlapping interfaces across teams without stopping their release schedules, and working understanding of the boundary between integration architecture and data platform architecture, including system-of-record discipline and master data consumption by federation.  Demonstrated experience authoring and publishing architecture standards, reference architectures, or roadmaps that delivery teams actually adopted, and leading architecture review (DRB, ARB, or equivalent) as a governance p