Data Modeler
Intersoft Data Labs · India Development Centre
Source and collection record
Last observed by our collector: . This is not a manual review or a confirmation from the employer.
Employer requisition: data-modeler
Job type and experience labels are automated discovery categories. The employer determines eligibility. Original experience wording was not retained separately; check the current employer page.
Your application evidence checklist
Mark the statements you can support after reading the employer source. This checklist stays on this page; it does not score your eligibility or submit an application.
0 of 2 checks marked. Keep unresolved requirements as questions for the employer.
Collected role description
Required Skill Set : Hands on experience with ERWIN Data Modeler and Working on the Enterprise Data Mart. Understanding Metadata Management principles ( Data Dictionary activities ). Hands on experience with Creating the ETL Mapping. Should understand impacts of model changes on databases and to validate that a model supports straight-forward requirements. Hands on experience with 3NF Data Modeling and NORMALIZED schema. Should be able to analyze business requirements to develop data models with minimal oversight. Hands on experience implementing Data Warehouse presentation layer – including design and definition of logical tables, physical sources, columns, aggregation rules. Hands on experience in writing SQL queries, views, and optimization of SQL queries. Comprehensive Knowledge of Bill Inmon’s Data Modeling Concepts (Logical and Physical) including 3NF, Supertypes, Subtypes, Abstraction, Associative entities / tables. Requires strong decision-making, organizational, planning and problem-solving skills. Nice to have : Knowledge on other Data Modeling tools like Power Designer , Visio , ER studio. Comprehensive Knowledge of Ralph Kimball’s Data Modeling Concepts including Transaction dimensions, conformed dimensions and facts, slowly changing dimension, multi-Star/ Snowflake Schema Modeling, different types of Fact tables. Implementing a virtual semantic layer (virtual star schema) using views on a multi-tiered normalized Integrated Operational Data Store is a huge plus. 3NF (Relational) Logical and Physical Modeling.