J

JP Morgan Chase

Runs a consumer bank and an investment bank

Principal Architect - Data

Data ManagementConfirmed live in the last 24 hours
Full-timePalo Alto, CA, USA$204.3k - $285kIn-person

About the Job

Requirements

  • Formal training or certification on architecture concepts and 10+ years of applied experience.
  • Extensive experience in data architecture, enterprise architecture, software architecture, or a comparable technical leadership role within a large, complex organization.
  • Deep working knowledge of conceptual, logical, and physical data modeling, relational design, identifiers, integrity constraints, schema evolution, and data contracts.
  • Experience designing and governing data integration patterns across application programming interfaces, event-driven architectures, streaming platforms, batch processing, replication, and analytical environments.
  • Demonstrated ability to establish common data semantics, ownership models, and canonical definitions across multiple products, systems, and business domains, including resolving conflicting definitions across teams.
  • Proven ability to turn architectural standards into implementation guidance, reusable patterns, reference designs, and delivery controls that engineering teams use.
  • Experience working with legacy systems where models, schemas, integrations, and ownership are incomplete or inconsistent, including reverse-engineering and remediation.
  • Ability to lead through influence across engineering, architecture, product, operations, risk, and senior stakeholders, and to make sound decisions in ambiguous environments with incomplete information and revise direction when delivery evidence requires it.
  • Strong written and verbal communication skills, including the ability to explain technical trade-offs to engineers and delivery, control, or operational risks to executives.

Responsibilities

  • Define the target-state data architecture for Foundational Services, establishing boundaries between systems of record, analytical data stores, caches, and derived data products, and prioritizing the highest-risk domains, systems, and integrations.
  • Develop a prioritized data architecture roadmap that moves teams from inconsistent, after-the-fact data design to model-first delivery, with a conceptual and logical model covering priority domains and critical data elements delivered within the first year.
  • Establish reusable engineering patterns for producing, sharing, moving, storing, and consuming data, including application programming interfaces, events, streaming, batch processing, and replication; prove the patterns in product delivery and improve them based on results.
  • Define and govern standards for data contracts, schema evolution, metadata management, lineage, data quality, retention, lifecycle management, and ownership; produce reference architectures, templates, decision trees, and implementation checklists for teams to adopt the patterns.
  • Lead enterprise data architecture decisions, including canonical data definitions, systems-of-record strategy, cross-product data semantics, and integration design; resolve conflicts that individual teams cannot settle independently and secure named ownership for critical data elements and cross-product interfaces.
  • Require material schema and integration changes to have an updated model, named owner, and approved data contract before implementation, and work with the Principal Data Modeler and product architects to keep logical and physical models synchronized.
  • Establish a lightweight architecture review and exception process that supports delivery while protecting critical data decisions, with clear rules and usable ways for teams to follow them.
  • Coach architects, engineers, product teams, and data owners on approved patterns and standards, and build executive alignment on architectural decisions needed to prevent local shortcuts from becoming enterprise-wide problems.
  • Assess logical-model and physical-schema alignment for priority applications, lead remediation of existing model and schema drift, including reverse-engineering where required, and report adoption, exceptions, model coverage, ownership gaps, and major integrity risks to leadership.

Desired Qualifications

  • Experience in financial services or another highly regulated, high-availability environment.
  • Experience defining systems-of-record strategy, operational versus analytical data boundaries, and data-product ownership models.
  • Experience with enterprise streaming, event-driven architecture, data platforms, metadata and lineage tooling, or data catalog capabilities.
  • Experience introducing model-first design, schema governance, or data-contract practices into an established organization.
  • Experience leading or mentoring data architects, data modelers, software architects, or engineering teams.
  • Familiarity with data classification, privacy, retention, access control, auditability, and resiliency requirements.

About the Company

JP Morgan Chase

Runs a consumer bank and an investment bank

JPMorgan Chase runs the largest bank in the United States, which serves households and small businesses as Chase and large companies, governments, and investors as J.P. Morgan. During the 2008 financial crisis it bought the failing investment bank Bear Stearns and lender Washington Mutual, and in 2023 it took over First Republic Bank after regulators seized it. Chase takes deposits and earns interest on credit cards, mortgages, and car loans, while the investment side earns fees for advising on mergers, raising money for companies, trading stocks and bonds, and managing wealth. Formed in a 2000 merger, JPMorgan Chase traces its roots to 1799 and is based in New York City.

Company size
10,001+
Company stage
IPO
Headquarters
New York City, New York
Founded
1799

Recently Posted Jobs

Explore more opportunities at JP Morgan Chase

See more jobs