Data Modeler

Senior Data Modeler Location: Remote Duration: 6 months (initial) with 12+ month extension Role Overview We are seeking Senior Data Modelers to support a large-scale data integration initiative following a major banking merger. This is a pure design and architecture role, not a development or engineering position. You will be responsible for defining the data schemas, structures, and quality standards required to unify disparate banking systems into a cohesive, scalable environment. Key Responsibilities • Logical & Physical Modeling: Design complex schemas that bridge legacy systems from both organizations. • Integration Mapping: Identify overlaps and gaps in data structures between the two banks (e.g., reconciling different “Customer” or “Transaction” definitions). • Data Governance: Define data quality rules, access controls, and metadata standards to ensure regulatory compliance. • Schema Evolution: Develop future-state models that support high-volume banking transactions and analytical reporting. • Collaboration: Act as the bridge between Business Analysts (requirements) and Data Engineers (implementation). Technical Profile & Tooling Options The ideal candidate should have 5+ years of experience and mastery in one or more of the following categories: Category Representative Technologies (Examples) Data Modeling Tools Erwin Data Modeler, ER/Studio, or PowerDesigner Cloud Data Warehouses Snowflake, Google BigQuery, or Amazon Redshift Transformation/Logic dbt (Data Build Tool), SQL-based views, or Data Vault 2.0 Data Quality/Catalog Collibra, Alation, or Informatica Enterprise Data Catalog Database Engines Oracle RAC, Teradata (Legacy), or PostgreSQL Required Qualifications • 5+ Years in Data Modeling: Proven track record in large-scale enterprise environments (Financial Services/Banking preferred). • Advanced SQL: Deep ability to query complex datasets to reverse-engineer existing schemas. Preferred Qualifications: • Regulatory Knowledge: Familiarity with banking-specific data standards (e.g., BCBS 239, AML/KYC data requirements). • Merger Experience: (Preferred) Previous experience in “Mapping & Gap Analysis” during corporate acquisitions or system migrations.