DB2 Data Modeler
About the role
- 10+ years of relevant experience in data modeling, data architecture, or related data disciplines.
- Demonstrated hands-on experience modeling data in DB2 environments.
- Experience developing conceptual, logical, and physical data models using tools such as SAP Power
- Designer or comparable platforms.
- Strong understanding of relational database design, SQL, and complex data structures.
- Experience with data dictionaries, metadata management, data discovery, data lineage, and authoritative data sources.
- Ability to interpret business requirements and translate them into practical data models and technical solutions.
- Experience with data pipelines, ingestion, retrieval, and distributed data systems.
- Strong analytical, problem-solving, communication, and stakeholder collaboration skills.
- Financial services or capital markets experience, especially market risk or counterparty credit risk.
- Familiarity with risk and P&L data, SRPL, FRTB, or related regulatory initiatives.
- Candidates local to New York or New Jersey.
- Experience with Oracle, Sybase, Impala, Kudu, Iceberg, or Hadoop-based platforms.
- SQL performance tuning and scripting experience using Python, Shell, or Perl.
- Experience with Apache Kafka and Apache Spark.
- Familiarity with Agile delivery, DevOps practices, testing, and technology risk controls.
- Core SkillsDB2 Data Modeling
- Data ArchitectureSQLPowerDesignerData Dictionaries
- Data Lineage
- Data Quality
- Data Engineering
- Market Risk
- Solution Design
- Stakeholder Collaboration
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
