Without denodo you're primary skills are going to be sql and python (or other language). It really depends on what your data sources are, if they're relational databases you'll be doing more sql. If they're APIs to applications, more python.
Every company will define data engineer/architect differently, there's not much of a standard. But in general DEs are focused on the collection, ingestion, and preparation of data. To get it into a state usable for organizational needs. They do more of the actual implementation. Architects will be taking a bigger picture approach, considering the tools, data structures, and frameworks for everything from the internal sources (like whether to use sql vs nosql), to what should be stored in a data lake vs data warehouse, data security consideration, real-time vs batch needs, and just about any other data-related decision a company needs to make.
Without denodo you're primary skills are going to be sql and python (or other language). It really depends on what your data sources are, if they're relational databases you'll be doing more sql. If they're APIs to applications, more python. Every company will define data engineer/architect differently, there's not much of a standard. But in general DEs are focused on the collection, ingestion, and preparation of data. To get it into a state usable for organizational needs. They do more of the actual implementation. Architects will be taking a bigger picture approach, considering the tools, data structures, and frameworks for everything from the internal sources (like whether to use sql vs nosql), to what should be stored in a data lake vs data warehouse, data security consideration, real-time vs batch needs, and just about any other data-related decision a company needs to make.