Infosys—IT& Data D&A architect

Job description

Description: 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 Requirements: 1. Role purpose Data & Analytics (D&A) 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 D&A 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 D&A 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. 2. Main mission 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. Responsibilities: 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 Skills: 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