IT& Data D&A architect

IT& Data D&A architect

Expertise expected – Strong data & analytics architecture expertise with hands-on credibility on modern cloud platforms (e.g. Azure: ADF, Databricks, ADLS), lakehouse and distributed data processing – Mastery of ingestion/sharing patterns, data modeling and non-functional requirements (security, scalability, resilience) – Ability to reason across a product perimeter and to arbitrate complex, high-impact architecture decisions Leadership positioning – Proven experience steering external architects and deciding autonomously within standards – Excellent communication, stakeholder management and servant-leadership skills A D&A Architecture Chapter Manager is the leader accountable, across a product perimeter, for architect coverage (mostly external), their steering, and the governance of the “what” of data solutions — owning the ADRs and chairing the Solution Design Forum — while applying (not defining) chapter standards. On a small perimeter, the role may double-hat as a D&A Solution Architect, with cross-review, until the perimeter grows beyond the defined threshold. Coverage, staffing & vendor management – Assign architects (mostly external) to products/squads based on demand, in a transversal (multi-product) mode — without dedicating an architect full-time to a single squad – Steer vendors: sourcing, scoping, deliverable quality, ramp-up/ramp-down and cost control – Anticipate architecture needs together with Product Owners and the Chapter Lead People leadership & capability building – Onboard, coach and upskill external architects; ensure continuity and knowledge transfer towards internal staff – Monitor vendor performance across the perimeter (quality, timeliness, compliance) Architecture governance (the “what”) – Accountable for solution architecture within guardrails, domain modeling and boundaries, integration patterns, solution security models and non-functional requirements – Own Architecture Decision Records (ADRs); chair the Solution Design Forum (SDF) as final decisionmaker (engineering input is consultative); escalate only strategic architecture decisions Standards adoption – Ensure solutions apply chapter standards, patterns and guardrails, and govern architectural exceptions Double-hatting (small perimeter) – Contribute directly as a Solution Architect (designs, ADRs), with cross-review to preserve the separation between producing and validating architecture decisions