BRIM Technical Architect

What You'll Do:   Own the technical architecture of the SAP BRIM platform — how it is built, integrated, and kept scalable over time. You define how the Order-to-Cash (O2C) solution is structured technically: the billing and subscription models at implementation level, the integration architecture, the cross-module technical coherence, and the extensibility patterns that keep the platform upgrade-safe and maintainable as Criteo's monetization evolves.   Beyond delivery, you are a strategic thinking partner — contributing to the definition of the future billing platform: what monetization capabilities Criteo needs to build, what the platform should become, and how technical architecture choices today shape product options tomorrow.     Main missions:   Own the end-to-end technical architecture across BRIM modules, ensuring cross-module coherence at implementation level (CI, SOM, CM, CC, FI-CA) within the O2C flow   Define and own the billing and subscription model implementation: rating architecture, pricing and charging structures, contract and entitlement lifecycle at technical level.   Own the integration architecture between BRIM, S/4HANA FI and non-SAP systems — interface contracts, data flows, error handling patterns, API and event-based integration.   Ensure the platform remains extensible, upgrade-safe and Clean Core compliant — define the extensibility patterns (standard APIs, events) that govern how the ABAP Lead builds.   Translate   functional designs into implementable technical blueprints, surfacing constraints, trade-offs and platform limitations before  build  starts.   Partner with the BRIM Product Lead to help defining the future billing platform vision — translating market, business and monetization evolutions into technical architecture directions and platform investment options.   Tasks:   Define the technical implementation of monetization models: subscription structures, rating and pricing mechanics, billing cycle architecture, revenue and collection flows at system level.   Design integration patterns and interface contracts (inbound/outbound, event-driven, API-based) between BRIM and adjacent systems; own technical decisions on error handling, retry, and reconciliation.   Validate technical feasibility of functional designs produced by the Solution Architect; identify cross-module technical impacts and escalate conflicts or constraints before they reach build.   Define extensibility standards and Clean Core guardrails for the ABAP Lead: which enhancement frameworks to use, where custom code is justified, how extensions are structured to remain upgrade-safe.   Contribute to BRIM product roadmap discussions with the Product Lead: surface technical constraints, platform opportunities and build-vs-standard trade-offs that shape future product decisions."   Anticipate evolutions in Criteo's monetization model and translate them into forward-looking architecture options — new…