IT& Data D&A architect

Role purpose Data Analytics (DA) is a strategic growth enabler. Architecture capability is organized as a Chapter that defines what the solution must look like and safeguards architectural integrity across product teams.

The DA Architecture Chapter Manager is the people-and-decision leader for architecture across a defined perimeter of products/domains. Unlike engineering, architects are not assigned full-time to a single squad: they operate transversally across several products. The role ensures data solutions are designed within the guardrails and aligned with OneSource 2.0, by applying the standards defined by the Chapter Lead - without redefining them.

Double-hatting note: Depending on the size of the perimeter, this role may be exercised as a double-hat. On a small perimeter, the Chapter Manager also performs DA Solution Architect duties (producing designs and ADRs). Once the perimeter reaches the defined threshold, the role refocuses on management and governance, and architecture production is delegated to the chapter's Solution Architects. Any such arrangement is made explicit.

Sizing note: The trigger for adding a new Architecture Chapter Manager is driven by the product/domain load, not by the number of architects. Guideline: ~1 Architecture Chapter Manager per 8-12 active products/domains, adjusted for product complexity/criticality, ADR decision density, and the number of external architects to manage. If the number of managed contractors exceeds the playbook span-of-control guideline (15-20 people), this also justifies a second Chapter Manager. Exceptions are handled via the Product Centricity GUILD.

Ensure, across the product perimeter, the coverage of architects (mostly external), their steering, and the governance of the "what" (what the solution must look like), so that product squads deliver scalable, secure and compliant data solutions - balancing delivery demand, architecture quality and cost efficiency.

A DA 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 DA Solution Architect, with cross-review, until the perimeter grows beyond the defined threshold.

MCA,ME,MSc,MTech,Bachelor of Engineering,BE,BSc,BTech

Technology->Data Management->Data Architecture

Data Analytics Unit