It's interesting to note, that when I was first called a DE - it was just software engineer in the data domain.
As in writing full software, that happen to focus on data.
Just 6 years ago I would be tinkering with PrestoDB code, looking at optimizing the scheduler and building Hadoop extensions.
Between that and today the field swung to people who came from BI, with considerably less software engineering background. To the point that just 2 years ago, when applying for DE roles I would be confused why majority of my screening questions came in the form of "how well do you know SQL".
Today I do the same as I did 3-4 years ago, but I am no longer a data engineer.
As in writing full software, that happen to focus on data.
Just 6 years ago I would be tinkering with PrestoDB code, looking at optimizing the scheduler and building Hadoop extensions.
Between that and today the field swung to people who came from BI, with considerably less software engineering background. To the point that just 2 years ago, when applying for DE roles I would be confused why majority of my screening questions came in the form of "how well do you know SQL".
Today I do the same as I did 3-4 years ago, but I am no longer a data engineer.