About the role
As Principal Architect for SAP AI Partnership, you will own the technical architecture and operational integrity of the Tricentis ↔ SAP integration that powers the SAP-channel distribution of Tricentis portfolio capabilities. You are the principal Tricentis-side counterpart to SAP's Engineering & Architects and SAP's Partner Co-Innovation Management organization, jointly responsible for the contract surface between the two platforms. The SAP partnership is strategically critical to Tricentis. This role is not only about hardening today's integration—it is about continuing co-innovation with SAP so we can expand AI, agentic, and quality capabilities across the channel and grow SAP-sourced business. This role is anchored in the SAP Solution Extension (SolEx) perimeter—the framework through which Tricentis delivers on BTP, including private-cloud and FedRAMP-constrained deployments. SolEx is SAP's invitation-only, premium-qualified partner framework: Tricentis products in this perimeter are co-branded, resold, and supported by SAP as if they were SAP's own mission-critical solutions, and they are held to SAP's premium-qualification standards for testing, integration, and lifecycle management. Beyond the core AI provisioning stack, you will shape how Tricentis engages across the full SolEx and BTP surface: SAP Cloud ALM (CALM) integrations (including patterns comparable to qTest and Quality Agent–driven experiences), Joule expansion, and new solution concepts that extend the partnership. The Tricentis products in the SolEx perimeter that you will architect across are: SAP Enterprise Continuous Testing by Tricentis (ECT) — underlying Tricentis product: Tosca. SAP Enterprise Performance Testing by Tricentis (EPT) — underlying Tricentis product: NeoLoad. SAP Change Impact Analysis by Tricentis (CIA) — underlying Tricentis product: SeaLights & LiveCompare. SAP Joule ↔ Tricentis AI — own the co-innovation architecture that exposes Tricentis AI capabilities within SAP Joule (skills, agents, tools, grounding, and tenant/entitlement context), aligned with the shared SolEx AI provisioning, metering, and qualification model. Because of the SolEx commercial model, your architectural decisions are not purely technical. Choices about schemas, identifiers, provisioning sequences, metering granularity, and certificate lifecycles directly affect SAP's ability to sell, qualify, support, and bill the products — and therefore directly affect the joint customer experience and the partnership itself. This role exists because the SAP-channel offering crosses an unusually large number of system boundaries — SAP for Me, SAP Cloud ALM, Central Business Configuration (CBC), BTP (including private cloud and FedRAMP deployments), SAP AI Core, SAP Joule, SAP Unified Metering, Salesforce, the Tricentis Licensing API, Tricentis AI Services, the LLM Gateway, AI consumption telemetry (AI Units on the SAP side, AI Credits on the Tricentis side), the Tricentis Data Lake, and AI consumption & utilization reporting dashboards — and currently lacks a single accountable architect across that surface. You will be that architect. You will define, document, operate, and continuously harden the end-to-end flow, and you will be the single technical point of contact for SAP on partnership questions of architecture, schema, certificates, billing, qualification, and onboarding. You will operate at the seam between engineering, business intelligence, product management, finance, and an external strategic partner. You must be equally credible writing a JSON schema, reviewing an mTLS certificate exchange, debating Cloud Events payload structure with SAP, and explaining the relationship between BTPAE credits (purchased by the customer on the SAP side), AI Units (the SAP-facing billing currency), and AI Credits (the Tricentis-side internal currency) to stakeholders and executives in both organizations. What You Will Lead 1. End-to-End SAP/Tricentis AI Integration Architecture Own the reference architecture for AI expansion, agentic AI development support, and the operational flows that connect Tricentis portfolio capabilities to SAP's channel, qualification, and billing models. Own the reference architecture for the full AI provisioning and metering flow: Salesforce purchase capture → Licensing API entitlement propagation → SAP for Me feature enablement → CBC webhook activation → AI entitlement check → BTP subaccount creation under the Tricentis Global Tenant → AI Core model deployment → LLM Gateway request routing → dual-currency consumption capture (AI Units for SAP-side billing, AI Credits for Tricentis-side tracking) → SAP Unified Metering submission → Tricentis Data Lake → Reporting & Consumption dashboards. Define and version the contract with SAP Unified Metering—Cloud Events payload structure, AI Feature IDs as billing triggers—and enforce naming discipline at the source rather than catching rejections in production. Own the implementation and operational health of webhooks for CBC feature activation/deactivation notifications, including certificate rotation, endpoint registration, and tenant-routing logic behind a single centralized endpoint. Resolve the tenant-model edge cases the standard architecture does not handle cleanly: MSPs and customers with multiple tenant IDs against the same product, customers on legacy product versions outside the current SAP catalog, and the relationship between the ECT/EPT/CIA product tenant and the AI-feature subaccount under the Tricentis BTP global account. Maintain architectural coherence across the SolEx product family — ECT (Tosca), EPT (NeoLoad), and CIA (SeaLights/LiveCompare) — for the shared AI feature stack. AI capabilities introduced in any one product must follow a consistent provisioning, metering, and entitlement model, and must not create per-product divergence in the SAP-facing contract or in SAP's support and qualification expectations. Own the SAP Joule ↔ Tricentis AI architecture end to end: skills, agents, tools, grounding, entitlement boundaries, and release alignment with SAP's Joule roadmap. Shape SAP Cloud ALM (CALM) integration patterns for Tricentis quality capabilities—including CALM-native experiences comparable to qTest and Quality Agent–driven workflows—so quality data and AI-assisted insights flow cleanly between CALM and the Tricentis portfolio. Drive agentic AI architecture on the SAP channel: tool/skill contracts, orchestration boundaries, safe grounding and tenant context, and how agent workloads map to metering and qualification. 2. SAP Co-Innovation Partnership The SAP partnership is one of Tricentis's most important go-to-market motions. You will be the technical leader who keeps co-innovation moving—translating roadmap ambition into architectures SAP can qualify, sell, and support. Serve as the principal technical point of contact for SAP Partner Co-Innovation Management and the SAP AI Engineering and Architects organization. Mirror their cadence, terminology, and documentation standards. Coordinate with SAP on BTP services consumed by the integration (AI Core, Generative AI Hub, Integration Suite, Unified Metering), private-cloud and FedRAMP deployment constraints, the SAP Joule ↔ Tricentis AI experience (skills, agents, and entitlement boundaries), SAP Cloud ALM integration, AI Feature ID lifecycle, and shared technical roadmap items affecting either side's release plans. Drive resolution of cross-company technical issues at the architect layer: schema validation rejections, certificate and endpoint mismatches, C-User / GitHub access for SAP-hosted documentation and environment onboarding, AI Core cloud-provider selection, and customer-mapping disputes. Maintain the Tricentis-side technical documentation set that translates SAP terminology and Tricentis terminology bidirectionally, and that survives turnover on either side. Think ahead of today's integration: propose and socialize new SAP-solution concepts that expand Tricentis's footprint in the channel, not only maintain the paths already in flight. What You Bring Required 10+ years in platform integration architecture, with at least one prior role bridging two enterprise software vendors or operating at a hyperscaler partner-engineering boundary. Demonstrated authority to make binding architectural decisions across organizational boundaries, not merely recommend them. Working understanding of the SAP Solution Extension (SolEx) program — premium qualification standards, joint roadmap mechanics, co-branding and resale implications — and an instinct for when an architectural decision crosses into commercial or qualification territory. Working knowledge of SAP BTP (global account / subaccount hierarchy, AI Core tenancy model, Integration Suite, private-cloud and FedRAMP deployment patterns) sufficient to debate provisioning sequencing with SAP engineers. Direct experience with at least one provider-side metering and entitlement stack — SAP Unified Metering, AWS Marketplace metering, Azure consumption metering, GCP marketplace, Stripe Billing, or equivalent — and demonstrated experience reconciling usage telemetry across two or more billing currencies (e.g., raw consumption vs. purchased credits, partner-side vs. end-customer-side units). Hands-on with webhook implementation including authentication mechanisms (e.g. mTLS), certificate lifecycle, Cloud Events, and strict JSON schema validation. Comfortable reading and writing webhook contracts as the primary engineering artifact. Agentic AI development skills: designing tool/skill interfaces, orchestration and grounding patterns, entitlement-aware agent context, and how agentic workloads connect to metering, residency, and partner qualification
