Principal Software Architect for SAP

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 requirements.

• Strong, precise written English. This role lives in long multi-party cross-company email threads where ambiguity creates rework; word choice and structure matter.

Preferred

Top candidates will also bring the following. These are not hard requirements, but they strongly differentiate applicants who can grow the partnership—not only operate it.

• Familiarity with SAP CBC, SAP for Me, SAP AI Core, SAP Cloud ALM, and SAP Joule (copilot skills/agents, BTP integration patterns) specifically. Prior exposure to S/4HANA or ECC integrations is useful but not the focus.

• Direct technical familiarity with the SolEx product underpinnings — Tosca (ECT), NeoLoad (EPT), LiveCompare (CIA) — sufficient to understand how each product's existing architecture constrains the shared AI integration.

• Experience operating a multi-tenant AI inference platform (per-customer model deployment, request routing, usage capture).

• Familiarity with Salesforce as the system of record for enterprise purchase capture, and with internal Licensing APIs that propagate entitlements from CRM-driven order capture to downstream operational services.

• Prior co-innovation or strategic partner integration role with a major enterprise software vendor or hyperscaler.

• Knowledge of MSP licensing, reseller/end-customer reporting splits, and multi-tenant entitlement edge cases.

• Demonstrated ability to operate across the Engineering / BI / Finance interface: can specify an API contract with the same precision as a reporting requirement, and can move between the two without losing fidelity.

• Track record of innovation leadership: having designed and driven the productionization of multiple new products on cloud infrastructure; having transformed legacy products into modern environments (cloud migration, AI migration, etc.); and examples of navigating ambiguity from partners and product teams to land executable architectures.

• Working knowledge of EU data protection and AI regulation — including GDPR (lawful basis, data minimization, DPIAs, processor/sub-processor roles, DPA expectations), EU-only deployment and data-residency constraints, cross-border transfer rules (e.g. Schrems II / SCCs), and emerging EU AI Act obligations where they affect partner integrations, metering telemetry, and customer-facing AI features in SAP-channel deployments.

Success Criteria for This Role

A successful architect will:

• Ensure the monthly SAP AI usage reporting cycle runs reliably without routine human involvement.

• Ensure new SAP-channel customers can be onboarded end-to-end without Engineering escalation and with a steadily decreasing rate of architect intervention per onboarding, including non-standard tenant configurations.

• Resolve Tricentis ↔ SAP technical issues at the architect layer rather than allowing them to escalate into executive workstreams.

• Maintain SolEx premium-qualification posture for the AI integration across ECT, EPT, and CIA on a yearly cadence and upon every major release, with zero qualification or support-model regressions attributable to architectural drift.

• Deliver successful premium qualifications (PQs) for the AI portions of ECT, EPT, and CIA on schedule, with no regressions attributable to architectural drift.

• Define or co-define at least one new SAP-channel solution concept per year that SAP can take through qualification and roadmap planning.

• Give Engineering, BI, PMO, Finance, and Sales Operations a single canonical reference architecture and a single accountable point of contact for the SAP AI integration.

Why Tricentis

Tricentis Core Values

At Tricentis, we strive for success while inspiring those around us by knowing what we need to achieve and how we'll achieve it. Our core values serve as our guiding light to drive our every action and define our ways of working so that we can create and enjoy a successful journey and reach higher heights together.

• Demonstrate Self-Awareness: Own your strengths and limitations.

• Finish What We Start: Do what we say we are going to do.

• Move Fast: Create momentum and efficiency.

• Run Towards Change: Challenge the status quo.

• Serve Our Customers & Communities: Create a positive experience with each interaction.

• Solve Problems Together: We win or lose as one team.

• Think Big & Believe: Set extraordinary goals and believe you can achieve them.

Tricentis is proud to be an equal opportunity workplace. Qualified applicants will receive consideration for employment without regard to race, color, ethnicity, gender, religious affiliation, age, sexual orientation, socioeconomic status, or physical and mental disability and other statuses protected by law.

Tricentis is proud to be an equal opportunity workplace. Qualified applicants will receive consideration for employment without regard to race, color, ethnicity, gender, religious affiliation, age, sexual orientation, socioeconomic status, or physical and mental disability and other statuses protected by law.

Tricentis is proud to be an equal opportunity workplace. Qualified applicants will receive consideration for employment without regard to race, color, ethnicity, gender, religious affiliation, age, sexual orientation, socioeconomic status, or physical and mental disability and other statuses protected by law.

Global Sanctions Compliance

We comply with all applicable global sanctions and export control laws. Candidates must not be listed on any government restricted party lists (including OFAC SDN List and U.S. Commerce Department restricted lists) and must certify that their employment would not violate any sanctions or export control regulations. Candidates must notify us of any changes to their status during the application process or subsequent employment.