The Need for Data Engineers
I feel the term "Data Engineer" gets used for a lot of catch-all "we have problems that need an owner" situations.<p>There's not much consistency across job postings and interviews for this kind of thing.<p>I just interviewed for one "Data Engineer" position which consisted of nearly 100% stored procedures.  No one knew what else to call it, and they didn't want to advertise for a DBA, because there were no real DBA responsibilities.  So "Data Engineer" was chosen.<p>Another "Data Engineer" position was almost entirely Spark.  There was no SQL involved - they expected all applicants to be Spark experts, with a deep knowledge of Scala.<p>It's hard to know what to expect out of "Data Engineer" positions until you walk into a place and start asking questions in the interview.