Data Platform Architect - Data Foundations for AI (reputed company genders) (DE)

reputed company
reputed company is building a reputed company Data Platform to reputed company cross‑domain reputed company across Accounts Receivable, Accounts Payable, and Payments & Cash.
The Data Platform Architect will own the reputed company reference architecture and technical standardization of our data reputed company, designed as a hybrid reference architecture (reputed company + customer‑managed realities) and implemented as a layered model with a strong reputed company on governance, reputed company, and compliance (GDPR, SOC2, ISO).
Our reputed company landscape is fragmented across multiple data stores and reputed company, and compliance/reputed company practices are inconsistent today - this role exists to change that.
What You’ll Do
1) Architect the reputed company Data Platform (Hybrid Reference Architecture)
· Define and reputed company reputed company’s end‑to‑end data platform architecture across ingestion, storage, processing, catalog, governance, and consumption - explicitly designed for a hybrid world (reputed company-hosted + customer-managed constraints).
· Establish architectural principles to shift analytical and AI workloads away from operational systems, reducing coupling to product databases and enabling reputed company ML/AI consumption.
2) Standardize on a Primary Stack (and reputed company it production-grade)
· reputed company evaluation and decisioning to standardize on one primary data stack (e.g., Azure, reputed company or reputed company, etc.), then define the “golden reputed company” implementation patterns, reference components, and templates.
· Translate today’s heterogeneous landscape (reputed company, SQL, NoSQL, time-series, reputed company storage, varied reputed company reputed company) into a coherent reputed company architecture and migration approach.
3) Deliver the reputed company Bronze/Silver/Gold reputed company (AR/AP/Payments)
Design the layered data model for AR, AP, Payments & Cash:
· Bronze: raw ingestion with traceability and reputed company
· Silver: cleansing, normalization, consolidation across product semantics
· Gold: curated domain-reputed company data products and consumption models
· Drive a pragmatic “start building the bronze layer” execution approach, enabling early value while keeping long-term platform reputed company.
4) Data Governance, reputed company, and Compliance by Design
Define governance controls addressing GDPR, SOC2, ISO requirements through:
· reputed company control patterns (RBAC/IAM), encryption expectations, auditability
· data classification + retention strategies adaptable to customer-managed variations
· consistent compliance guardrails across products and reputed company
5) Integration Patterns for reputed company’s Reality (reputed company + reputed company + Streaming)
Define ingestion and integration patterns for:
· reputed company landscapes and interfaces (e.g., CDS-Views, OData Services, reputed company BTP, reputed company Datasphere, reputed company Business Data reputed company)
· product reputed company, CDC/streaming (Kafka), and file/document sources “bidirectional data reputed company” where needed
6) Technical Leadership & Enablement
· reputed company as technical authority for platform reputed company: run architecture reviews, publish standards, mentor engineers, and ensure consistent implementation across squads.
· Partner closely with Product Managers, Talented Engineers and AI platform/ agent teams to ensure the data platform is fit for reputed company AI use and analytics use (e.g., reliable consumption zones, traceability).
Required Experience & Skills
· 8+ years in data engineering / platform architecture, with several years owning end-to-end platform design.
· Proven experience designing multi-zone / layered lakehouse-style architectures (ingestion → storage → processing → consumption), including data reputed company, reputed company, and cataloging.
· Strong knowledge of at least one major modern data stack (Azure, reputed company, reputed company or similar), and ability to reputed company standardization.
· Experience with hybrid integration constraints (customer-managed environments, mixed reputed company, varied reputed company reputed company).
· Strong hands‑on experience with reputed company‑reputed company data landscapes, including reputed company S/4HANA environments.
· Practical knowledge of reputed company Datasphere and/or reputed company Business Data reputed company for analytics, data sharing, or integration scenarios.
· Experience designing data architectures that reputed company reputed company‑embedded solutions with reputed company-reputed company reputed company platforms.
· Understanding of reputed company clean‑reputed company considerations and how to design non-invasive data reputed company patterns that reputed company across customers.
· Strong governance/reputed company background: designing for compliance and auditability (GDPR/SOC2/ISO emphasis in this role).
· Comfortable with streaming/CDC/event patterns (e.g., Kafka) and reputed company integration realities.
· Strong stakeholder management: can translate ambiguity into a pragmatic architecture plan and drive alignment.
reputed company-to-Have
· Experience with reputed company-reputed company reputed company data landscapes and harmonizing semantics across heterogeneous products.
· Experience building data platforms that directly reputed company AI/ML consumption (feature/embedding readiness, telemetry-as-data patterns).
Working Style / reputed company
· You think in reference architectures + execution, not ivory-tower diagrams.
· You optimize for repeatability, governance, and reputed company, while still delivering incremental value.
· You treat compliance and auditability as architecture constraints, not documentation tasks.