Wells Fargo

Principal Engineer - Data Engineering Architect

India · Work style not stated · Full time

Apply on the employer’s site ↗See how well you match this job

You apply directly with the employer. ROLIVA does not submit applications from this page and is not the employer.

About the role

Description from the employer’s posting. Check the employer’s page for the current version.

  • EmployerWells Fargo
  • LocationIndia
  • Work styleWork style not stated
  • Employment typeFull time
  • Employer posted

About This Role

Wells Fargo is seeking a Principal Engineer / Architect ( Data Engineering )to define and advance the data information strategy, information models, data sourcing standards, and data enablement roadmap across Enterprise Risk, Audit, and Finance Technology.

This is a horizontal architecture role supporting multiple business and technology domains, including Financial Risk, Non-Financial Risk, Finance, Treasury, Regulatory Reporting, Internal Audit, Independent Testing, Model Risk, and Financial Crimes.

The role will shape how enterprise information is identified, defined, sourced, modeled, governed, integrated, and made consumable across ERAFT. The role will establish common information models, semantic standards, authoritative-source guidance, reusable data products, and architecture patterns that enable consistent reporting, analytics, regulatory traceability, and artificial intelligence use cases.

Show full description

The ideal candidate brings a strong combination of information architecture, enterprise data architecture, financial-services and banking domain knowledge, data governance, sourcing strategy, semantic modeling, integration design, analytics enablement, and stakeholder leadership. This individual must be able to work independently, influence decisions across business and technology teams, and translate complex business, regulatory, and technology requirements into practical and scalable data architecture.

In This Role, You Will

  • Act as an advisor to leadership to develop or influence applications, network, information security, database, operating systems, or web technologies for highly complex business and technical needs across multiple groups
  • Lead the strategy and resolution of highly complex and unique challenges requiring in-depth evaluation across multiple areas or the enterprise, delivering solutions that are long-term, large-scale and require vision, creativity, innovation, advanced analytical and inductive thinking
  • Translate advanced technology experience, an in-depth knowledge of the organizations tactical and strategic business objectives, the enterprise technological environment, the organization structure, and strategic technological opportunities and requirements into technical engineering solutions
  • Provide vision, direction and expertise to leadership on implementing innovative and significant business solutions
  • Maintain knowledge of industry best practices and new technologies and recommends innovations that enhance operations or provide a competitive advantage to the organization
  • Strategically engage with all levels of professionals and managers across the enterprise and serve as an expert advisor to leadership.

Required Qualifications:

  • 7+ years of Engineering experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education
  • 7+ years of experience in data architecture, information architecture, enterprise architecture, information modeling, or data-platform design.
  • 7+ years of experience supporting banking, financial services, finance, risk, audit, regulatory reporting, compliance, or control-related domains.

Desired Qualifications:

Data Information Strategy and Architecture

  • Define and own the data information strategy and target-state information architecture across ERAFT.
  • Develop current-state, target-state, and transition-state architectures covering information domains, data sourcing, information models, metadata, lineage, data products, semantic access, integration, and consumption.
  • Define canonical information models and common business concepts that can be reused across Risk, Finance, Audit, regulatory reporting, analytics, and AI use cases.
  • Establish standards and artifacts for conceptual and logical data models, taxonomies, ontologies, business glossaries, source-to-target mappings, data flows, data lineage views, and semantic relationships.
  • Align ERAFT information architecture with enterprise data, metadata, privacy, security, retention, records-management, and regulatory standards.
  • Define architecture principles that enable common information to be understood and reused while allowing justified domain-specific extensions.
  • Produce architecture specifications, decision records, reference models, roadmaps, standards, and executive-level recommendations.
  • Develop POC’s and demos to supplement architecture materials.

Data Sourcing Strategy

  • Define reusable data sourcing strategies across ERAFT business and technology domains.
  • Identify authoritative systems of record, systems of reference, authoritative distribution sources, and trusted consumption sources for critical enterprise information.
  • Establish criteria for selecting the appropriate sourcing approach, including direct-source integration, authoritative data products, APIs, event streams, batch feeds, data warehouses, data lakes, data virtualization, federated queries, and metadata-driven ingestion.
  • Define sourcing patterns for structured, semi-structured, and unstructured information.
  • Partner with source-system owners, data owners, and data stewards to assess data availability, ownership, quality, lineage, refresh frequency, historical coverage, access restrictions, and regulatory obligations.
  • Determine whether information should be physically ingested, virtually accessed, indexed, summarized, referenced, or exposed through a governed data product.
  • Reduce duplicate sourcing, unnecessary data movement, point-to-point integration, and inconsistent transformation logic.
  • Define data contracts that document schema, semantics, quality expectations, service levels, usage constraints, and change-management responsibilities between producers and consumers.

Information Modeling and Semantic Alignment

  • Develop and maintain enterprise and domain-level information models across ERAFT.
  • Standardize business concepts, definitions, relationships, taxonomies, and metrics across Risk, Finance, Audit, and related regulatory domains.
  • Define semantic relationships among customers, accounts, products, transactions, legal entities, positions, risks, controls, models, obligations, issues, findings, evidence, business processes, reports, and organizational structures.
  • Partner with business data owners and governance teams to approve common definitions and resolve semantic conflicts.
  • Support subject-area taxonomy alignment, conceptual modeling, glossary analysis, ontology evaluation, and capability mapping.
  • Define semantic-layer patterns that separate business meaning from physical data structures and technology implementations.
  • Evaluate ontology and knowledge-graph approaches where they improve cross-domain discovery, traceability, impact analysis, aggregation, or AI-enabled access.
  • Promote reuse of common information concepts while preserving appropriate business context for individual domains.

Data Governance, Quality, Metadata, and Lineage

  • Define information-governance requirements for ERAFT data products, platforms, and solutions.
  • Partner with data owners and stewards to establish accountability for business terms, data domains, data products, and Critical Data Elements.
  • Define data-quality expectations for completeness, accuracy, timeliness, validity, consistency, and uniqueness.
  • Establish patterns for data controls, reconciliation, validation, observability, and issue remediation.
  • Define end-to-end lineage requirements from authoritative sources through ingestion, transformation, semantic models, reports, analytics, models, AI solutions, and downstream consumers.
  • Establish metadata requirements that support discovery, reuse, impact analysis, auditability, explain ability, and regulatory response.
  • Ensure that information architecture addresses privacy, security, entitlements, data classification, retention, records management, and permitted use.
  • Promote common metadata, glossary, domain, ownership, and quality standards across on-premises, cloud, and hybrid environments.

Data Enablement, Analytics, and AI

  • Define the data foundation required to support dashboards, reports, analytics, advanced monitoring, and AI-enabled insights.
  • Partner with analytics and business-intelligence teams to define fit-for-purpose data products, semantic layers, data marts, dimensions, metrics, and reporting definitions.
  • Ensure that business metrics and analytical concepts are consistently defined, traceable to authoritative information, and reusable across domains.
  • Define information structures and metadata required for AI retrieval, grounding, context management, model inputs, evaluation, and human review.
  • Establish data-readiness criteria for AI use cases, including quality, lineage, authority, access, consent, context, explainability, and traceability.
  • Enable governed AI access to business glossaries, metadata, lineage, quality indicators, relationships, and approved enterprise knowledge.
  • Ensure that AI-enabled consumption is explainable, auditable, secured, and aligned with applicable governance expectations.
  • Promote an information-first approach in which AI solutions consume governed enterprise context rather than creating isolated copies and conflicting definitions.

Integration and Data-Platform Architecture

  • Partner with enterprise architects, application architects, platform architects, solution architects, and engineering teams to translate information architecture into implementable solutions.
  • Define patterns for APIs, event streaming, batch ingestion, ETL and ELT, files, data virtualization, federated queries, and metadata-driven connectors.
  • Ensure that platform designs support scalability, resiliency, performance, security, maintainability, and lifecycle management.
  • Align information architecture with enterprise cloud, hybrid, on-premises, analytics, and integration standards.
  • Provide data-architecture input to platform selection, vendor assessment, and build-versus-buy decisions.
  • Guide modernization from fragmented legacy data flows to governed, reusable, and interoperable enterprise capabilities.
  • Maintain a clear separation between business information architecture, logical data architecture, and physical technology implementation.

Stakeholder Management and Architecture Governance

  • Act as a trusted information-architecture adviser to business, data, technology, architecture, risk, finance, audit, compliance, and control leaders.
  • Translate business and regulatory requirements into practical information and data architecture decisions.
  • Facilitate decisions involving information ownership, authoritative sourcing, semantic definitions, quality expectations, data sharing, and consumption patterns.
  • Present data and information architecture strategies, target states, trade-offs, risks, and roadmap recommendations to senior leaders and governance forums.
  • Lead and contribute to architecture reviews, design reviews, data-governance forums, and platform decision-making bodies.
  • Independently drive architecture decisions while balancing risk, cost, regulatory requirements, delivery commitments, and long-term sustainability.
  • Document major sourcing, modeling, semantic, integration, and platform decisions through architecture decision records.
  • Identify architecture risks, dependencies, gaps, exceptions, and remediation requirements.
  • Mentor architects, data modelers, analysts, and engineers in information-architecture practices.

Job Expectations:

The Principal Engineer - Lead Architect will be expected to:

  • Experience spanning multiple Risk, Finance, Audit, Treasury, Financial Crimes, Model Risk, regulatory, or enterprise data-management domains.
  • Experience with metadata management, data catalogs, business glossaries, data lineage, data-quality platforms, data products, and data contracts.
  • Experience with semantic layers, ontologies, knowledge graphs, or enterprise information models.
  • Understanding of data mesh, data fabric, authoritative data sources, and contract-driven data distribution.
  • Experience with APIs, Kafka or event streaming, ETL and ELT, data virtualization, data lakes, lakehouse platforms, and enterprise data warehouses.
  • Experience with technologies such as Dremio, Databricks, Snowflake, Spark, Python, SQL, Neo4J, Protégé, object storage, and metadata or catalog platforms.
  • Familiarity with graph technologies, vector databases, retrieval-augmented generation, enterprise large-language-model platforms, and AI orchestration frameworks.
  • Experience defining governed data patterns for AI, including source traceability, context, lineage, human validation, explainability, and auditability.
  • Familiarity with enterprise architecture frameworks such as TOGAF or equivalent.
  • Relevant architecture, information-management, cloud, data-governance, or security certification.
  • Establish a clear and executable data information strategy across ERAFT.
  • Define reusable information models and semantic standards across Risk, Finance, and Audit.
  • Improve clarity around authoritative sources, data ownership, business definitions, and consumption patterns.
  • Promote reuse of governed data products, reference data, metadata, and integration patterns.
  • Improve the quality, traceability, explainability, and auditability of enterprise information.
  • Enable consistent reporting, analytics, regulatory use, and AI-enabled capabilities.
  • Reduce duplicate sourcing, inconsistent definitions, manual reconciliation, and fragmented data flows.
  • Translate target-state strategies into standards and patterns that application and platform teams can adopt.

Posting End Date:

18 Oct 2026

*Job posting may come down early due to volume of applicants.

We Value Equal Opportunity

Wells Fargo is an equal opportunity employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability, status as a protected veteran, or any other legally protected characteristic.

Employees support our focus on building strong customer relationships balanced with a strong risk mitigating and compliance-driven culture which firmly establishes those disciplines as critical to the success of our customers and company. They are accountable for execution of all applicable risk programs (Credit, Market, Financial Crimes, Operational, Regulatory Compliance), which includes effectively following and adhering to applicable Wells Fargo policies and procedures, appropriately fulfilling risk and compliance obligations, timely and effective escalation and remediation of issues, and making sound risk decisions. There is emphasis on proactive monitoring, governance, risk identification and escalation, as well as making sound risk decisions commensurate with the business unit’s risk appetite and all risk and compliance program requirements.

Candidates applying to job openings posted in Canada: Applications for employment are encouraged from all qualified candidates, including women, persons with disabilities, aboriginal peoples and visible minorities. Accommodation for applicants with disabilities is available upon request in connection with the recruitment process.

Applicants with Disabilities

To request a medical accommodation during the application or interview process, visit Disability Inclusion at Wells Fargo.

Drug and Alcohol Policy

Wells Fargo maintains a drug free workplace. Please see our Drug and Alcohol Policy to learn more.

Wells Fargo Recruitment and Hiring Requirements:

a. Third-Party recordings are prohibited unless authorized by Wells Fargo.

b. Wells Fargo requires you to directly represent your own experiences during the recruiting and hiring process.

Staying safe while you apply

  • Never pay to apply, interview or accept an offer. ROLIVA never asks you for payment to apply to a job.
  • Apply only through the official “Apply on the employer’s site” button, on the employer’s own site, and check that a recruiter’s email uses that employer’s own domain rather than a free email address.
  • Be cautious of an offer made with no real interview, or pressure to decide quickly or share financial details early.

Does something look wrong with this listing? Use “Report broken link” in the role details, or read ROLIVA’s full job-safety guidance ↗.

Preparing for this role with ROLIVA

  • Check the fit.

    Compare the requirements with the experience you have confirmed, including gaps.

  • Prepare honestly.

    Build interview stories and application drafts from your own evidence.

  • Keep track.

    Save the role and record your own application status and follow-ups.

Create a free workspace or log in.

Software engineer jobs in Bengaluru

ROLIVA currently lists 1203 open roles like this in Bengaluru.

Employers hiring for this

  • Hewlett Packard Enterprise87 open roles
  • Cadence67 open roles
  • Okta66 open roles
  • Databricks45 open roles
  • Renesas Electronics25 open roles

Top skills asked for

Listings whose description mentions each term. A mention is not a requirement.

At a glance

  • Employment typeFull time
  • SeniorityLead / Principal
  • Employer posted
  • Added to ROLIVA
  • Last checked

Skills in this posting

Skills ROLIVA found in the employer’s own description above. A mention is not a requirement.

SQL Python Snowflake Spark Kafka Stakeholder management

Explore similar roles

Similar jobs

Automationanywhere

Staff Engineer

India

Work style not statedFull time

Automationanywhere

Principal Engineer

India

Work style not statedFull time

Automationanywhere

Sr. Staff Engineer

India

Work style not statedFull time