Data Architecture Strategies: Data Architect vs Data Engineer vs Data Modeler

preview_player
Показать описание
The increasing focus on data in today’s organization has increased demand for critical roles such as data architect, data engineer, and data modeler. But there is often confusion and ambiguity around what these roles entail, and what overlap exists between them. This webinar will discuss these data-centric roles and their place in the data-driven organization.
Рекомендации по теме
Комментарии
Автор

20:00 Idk what that building, engineering, and architecture split means but it sounds wrong.

I think a Data Architect is a natural career progression in data engineering. It maybe called a lead engineer or principle engineer in some places. With years of experience as a Data Engineer you get a chance to work with various architecture and tools. Now with new data and challenges coming you are in the front line of architectural decision making and tools onboarding.

You are building everyday, you are engineering everyday, you are not only just building, you are building new proof of concepts, performance testing new tools, thinking what would help the most and thinking about the changing landscape of data needs and how your team can build the best solutions for it.

Yes there is dealing with business, but your not some personality interface between tech and business, you speak on behalf of tech as an expert. This requires stronger tech skills, you and business both speak English (or presumably the same language) no one needs a translator, that is not a real job. Also drawing a diagram isn't a job either, that is a 5-10 minute task if you know the system inside and out.

moazim