Solution Architect - Application Integration

Job Details:

Job Title: Solution Architect Application Integration

Duration: 6 months and possibly longer

REMOTE

Client specifically is looking for the skills below.

1. Document the future-state architecture
   • Draw.io
   • Architecture diagrams
   • Application interaction maps
   • Integration flows
2. Coordinate across workstreams
   • SAP
   • Workday
   • ServiceNow
   • Data team
   • AI team
3. Drive meetings to closure
   • Follow-ups
   • Decisions
   • Action tracking
   • Stakeholder communication

Position Overview

The Application Integration Solution Architect will own the design and governance of system-to-system connectivity across the client application landscape. This role focuses on APIs, event-driven architectures, middleware patterns, and the Copilot Studio agent layer that connects enterprise applications to AI capabilities. As we move from isolated automations to an orchestrated, agent-driven enterprise, this architect ensures that every integration is secure, scalable, and aligned to our platform strategy.

Business Need & Strategic Drivers

• 9+ Enterprise Platforms Requiring Integration: Client application landscape includes SAP (multiple versions), Blue Yonder, Snowflake, Workday (HR), ServiceNow (workflow/tickets), Syndigo, Alation, Automation Anywhere (AP only), and the Microsoft ecosystem (Copilot Studio, Fabric, Azure AI Foundry). Each platform has its own API patterns, authentication models, and event mechanisms. A dedicated application integration architect is essential to design coherent connectivity across this landscape.
• Copilot Studio as the Agent Orchestration Layer: Microsoft Copilot Studio is our primary platform for building AI agents. These agents need to call APIs across SAP, ServiceNow, Workday, and other systems in real-time. Designing the connector architecture, API abstraction layers, and security model for agent-to-system communication requires deep integration expertise that goes beyond individual project teams.
• Legacy SAP Bridge Patterns: With Joule AI unavailable on ECC instances, the Copilot Studio + SAP RFC/API + Fabric bridge pattern is critical for extending AI capabilities to legacy systems. This is a complex integration pattern requiring API gateway design, RFC connector management, and error handling that must be architected once and reused across use cases.
• Automation Anywhere Scoping Discipline: AA is scoped specifically to AP workflows (T&E Risk Scoring, PCard Monitoring, Invoice Triage, Vendor Statements). The application integration architect ensures AA integrations remain bounded to this scope and that broader automation needs are addressed through Copilot Studio, Power Automate, and native platform capabilities.
• Basware-to-Coupa Transition Management: The ongoing transition from Basware to Coupa creates integration dependency risks for AP automation use cases. An integration architect is needed to design migration-resilient integration patterns that can pivot as the underlying procurement platform changes.
• ServiceNow & Workday Integration: ServiceNow (workflow/ticket automation) and Workday (HR) both require bidirectional integration with Copilot Studio for agent-driven experiences (e.g., ticket creation from Teams, HR self-service agents). These integrations need standardized patterns, not one-off custom builds.

Key Responsibilities

1. Design and maintain the enterprise application integration architecture, including API standards, event-driven patterns, and middleware selection
2. Architect the Copilot Studio connector framework for agent-to-system communication across SAP, ServiceNow, Workday, Blue Yonder, and other platforms
3. Define and enforce the legacy SAP bridge pattern (Copilot Studio + RFC/API + Fabric) for extending AI to ECC environments
4. Govern Automation Anywhere integration boundaries, ensuring AP-scoped usage and alignment with broader platform strategy
5. Design migration-resilient integration patterns for the Basware-to-Coupa transition and future platform changes
6. Establish API security, authentication, and access governance standards across all integration points
7. Collaborate with the AI Architect on Model Context Protocol (MCP) and agent-to-agent (A2A) integration patterns
8. Evaluate and recommend integration platform capabilities (Azure API Management, Logic Apps, Power Automate, native connectors) based on use case requirements