Head of architecture seem to be more application/software architects. Once you get to enterprise architect that is normally it.
#Data architect role and responsibilities how to#
Cloud skills I would say are a must nowadays as an architect, but I still meet lots who don’t know how to deploy their solutions to the cloud or even know which resources to use and why.
You could actually go broader and learn some of the skills other architects have. And some companies think you just do analytics. I am happy doing all three, some companies expect you to do them all. In the modelling world, the enterprise conceptual data model, standards…. Able to work analytics, application, data migration … and roughly understanding how that fits into the enterprise.Įnterprise data architect - doesn’t know or need to know technical how things work.pre focused on what the business is trying to do and what Data capabilities are needed to deliver those. Solution data architect - broader skillset. Responsible for a specific system and the fine detail of how that system works. Technical Data Architect - bordering on senior data engineer. And then there are three levels in each of those. People either become data modellers or technical. And I think it really depends what you want to do as an architect. Not because the work is hard, because no one really knows what you do.ĭata architecture can be split many ways and the roles all differ. I’ve been a Data Architect for 10 years now and it is really a tough role to do.
0 kommentar(er)
