Joke aside, data engineers do a wide variety of engineering work related to data. Often that's around data warehousing and business intelligence, sometimes it's work on big data streaming or storage systems, or building yet another integration for marketing.
The breadth is a challenge, which makes it fun and also hard.
Thankless work so that the analysts can turn on the faucet and get nice clean data for their fancy algorithms and models
Also bonus if you know how to run a business and give guidance on what type of house to buy before putting in pipes.
Is there any chance for someone with my profile to get a job in this? Remotely of course, as any remote job would pay times better than anything I could get in my home country. If yes, where does one learn about it more? I see Coursera has some course, but better asking from someone with your experience I guess. My approach to a job is that you do it in order to get money to fulfill whatever you enjoy in life, as long as I'm paid I'll be the best I can. Thanks
Most of the data warehouse work is data transformation and scheduling, so Apache Airflow and writing DAGs in python is a large part. For some of the larger streaming things you've got Kafka and others.
Also every cloud has it's own stack that is sometimes worth using.
A lot of the time they do ETL/ELT mostly with airflow nowadays.
Some use little more than SQL and if they're lucky something like DBT to template and schedule the queries.
A lot of SQL now runs on data warehouses of which snowflake and Google bigquery stand out, but it's SQL nevertheless.
A few lucky ones get to use Spark which is more interesting as it's written in scala or python, but from my experience 99% of the time businesses are better off training business analysts to use SQL and writing the queries in snowflake.
Another interesting area is real time data, for existing e with Kafka. This can be challenging and fulfilling except a lot of the time businesses people will tell you it's cool but they don't want the data to keep changing so could you please aggregate it every day... So you end up with an overly complicated batch system anyways.
For me the sweet spot of practicality right now is Airflow/DBT/python/snowflake.
If you want a fun language, it's really the wrong place to be.
The work can be very fun, but you must take the fun from data analysis. The best software engineering can do for you is to not get on your way (and SQL excels on this).
I'd say the people working with Spike are the unlucky ones. Because they have to focus more on their tools, and not on the analysis.