Under the guidance of a more senior colleague, you will be involved in creating and managing our central data models. That means you will help process new change requests for data structures and continuously improve our data models (which we manage in the PowerDesigner modeling tool). Models are not everything we have! If you are interested, you can also participate in improving the central processes that we have already created around managing our models, data modeling, and change requests. As a central data architect, you will often help other local architects in different countries and provide them with support in managing their local data models. As part of your role, you will actively collaborate with various data and other teams such as data governance, data science, data engineers and others. You will also be partially involved in activities related to central data governance, collaborating on the creation of central business glossaries and linking them to our data models. We are already dealing with data structures in several countries, but more and more countries are yet to come, and as a central data architect, you will help with gap analysis and other related tasks.
Basic knowledge of relational databases – As a data architect, you should understand the logic and meaning of tables, columns (data types), primary keys, foreign keys, composite keys, relationship tables, etc.
Basic knowledge of a modeling tool – A significant advantage is knowledge of the PowerDesigner modeling tool, but it is not a requirement. It is important for us that you know at least one modeling tool. We assume that if you are proficient with any modeling tool, learning to work with PowerDesigner should not be a problem for you.
Basic experience with data modeling – Since the data architect often needs to discuss changes to the data structures of our models, you should have demonstrable experience with data modeling at various levels of abstraction and should be familiar with best practices in data modeling (for example, naming conventions, advantages and disadvantages of normalization/denormalization and data structure patterns).
Basic experience with data analytics – As a data architect, you will often be involved in discussions about source systems and data transformation. Therefore, we expect you to have sufficient experience with data analysis and be able to ask the right questions and identify potential problems before they occur.
Basic knowledge of SQL language – In order for a data architect to be able to discuss data transformations, it is necessary to know at least SQL (or other). Therefore, we expect you to be able to work with data - you should know how to manipulate, join, filter, and modify data (or data structure).
Basic knowledge of data governance - We expect you to have a general understanding of what data governance is and what data dictionaries and business glossaries are used for.
Other - Knowledge of English and Czech language, common sense, logical reasoning, attention to detail, and the ability to independently seek solutions to problems.
Praha
