Data Architects Vs Data Engineers - Is There A Difference? 

Yeah as Lead Data Engineer I am trying to avoid this reclassification as I really love not only to design, but also to develop the stuff

In my opinion that's how someone ought to become a data architect. You should be a senior (or lead) data engineer first. When hiring someone as a data architect who hasn't worked as a data engineer himself you might end up with the architect taking decisions that aren't aligned with the needs of the engineers which slows down the entire project. Software architects aren't data architects.

I don't have complete control of that. Googles new rules now state that they can show ads whenever they want and if you chose not to collect the youtube payout then they'll just take all of it.

Happy to help

Great suggestion! I actually am working on an article on the topic so it might be a good idea to make a video part as well!

Widely educated and experienced data architects and data-focused enterprise architects tend to focus more on improving and automating data business processes. Enterprise architect might collect information, draft blueprints, and manage changes to a) business architecture, b) data architecture, c) application architecture, d) technology architecture. Examples of blueprints might be a) business process and task workflow models, b) data asset to system mappings and concept models, c) data platform reference model and data warehouse implementation architecture, d) technology standards handbook and datawarehouse technology architectures. When I have done these, its typical that you have or it is useful to mix a few levels together. For example, bundle application architecture and technology architecture to a same blueprint or business and data architecture. In practice, the same Visio- or ppt-diagram includes application level items (Dynamics CRM, Azure data lake, PowerBI reports) and technologies (REST API between CRM and Azure, MS Stack as enterprise standard, DAX syntax in reports etC). Or combine business process items (sales, contracting, customer service, etc) to data layer (entities like consumer customer, sales product, service contract etc) to map their relations. Depending on the skills and background of the architect, they might work more on strategic level focusing on high level resources, policies and practices or more on operational and technical level like modeling logical data models and gathering detailed requirements for software projects. According to my experience, data engineers do not really work directly with business, draft business blueprints and take part of organizational implementation tasks - business layer. Unless organization quite a small and the same person has to be enterprise architect, data engineer and data analyst at the same time. In general, data engineers are most likely not expected to design business processes or strategies, for example.

Yeah! I actually have a video on this, the courses are still relevant - ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-kW8_l57w74g.html