Experience designing dimensional/star schema and normalized data models from scratch.
Experience using Erwin Data Modeler
Understanding how to work within data modeling and metadata standards frameworks (i.e. naming standards, class word standards, writing clear, concise, unambiguous definitions. This is huge as it is the most time-consuming piece of the data modeling effort but also one of the things regulators will look at in ensuring we DO understand our data and are using it appropriately. From a resume perspective, someone with experience developing modeling standards would be expected to have that knowledge, or if they explicitly call out data naming and metadata standards in their resume.
Strong communications skills, verbal and written.
have to be able to illicit information on data needs from business users who do not understand our role/goal.
must be able to speak to their design/modeling decisions (specifically to the DRB but also within the team)
must be willing/able to communicate/escalate issues found while developing their data models.
S2T mapping experience is a plus especially within marts/dimensional models as this is foundational to lineage.
Flexibility in approach to achieving goals when the “right” solution is not achievable in the short term. This is one we probably won’t see on a resume but need to get to in an interview. I have run into many people where perfection is the ONLY acceptable outcome.
Takes initiative to identify and meet with the IT and business resources necessary to refine requirements and understand data and processes completely.
Self-starter driven to move designs forward without the benefit of extensive detailed documentation.
Comfortable collaborating positively and proactively with a diverse team of modelers ranging in experience from relative novice to exceedingly experienced.
Design, model and implement data solutions meet the business needs and risk tolerance criteria of the LOB.
Ensure changes to the data environment generated by the LOB are compatible and compliant to the firm’s architectural standards.
Enforce data architectural standards via the Data Model Review Forum and participation in all LOB projects that create new data store or modify existing data stores.
Logical + Physical Data Modeling experience is a must with a minimum of 5 years’ experience, 7+ preferred.
Erwin Data Modeler experience is a must.
Hands on experience with Oracle, SQL Server, DB2 and Snowflake is preferred.
Experience with robust, operationally sound production environments is preferred.
Experience with large/very large databases is must.
Experience with large scale development projects, Internet development experience, large integration projects is a must.