I would say these terms are not exclusive of each other. Like Parallelogram, square, rectangle. All 3 of your descriptions would be different types of Backend E

I would say these terms are not exclusive of each other. Like Parallelogram, square, rectangle. All 3 of your descriptions would be different types of Backend Engineers to me, with focuses on systems or data (or both) or something else. Sometimes the storage team is focused on generically keeping storage working while another team actually works on the "big data" applications, but often these teams design and plan very hand-in-hand. > But when you give a data engineer a problem, they are sure to suggest an ETL pipeline in Hadoop Maybe someone who sees Hadoop as their only hammer but IMO a "good" data engineer would go "How much data? 300MB? And you need to run this how often? Once? You're sure just once? Like really sure? Okay here is a bash script."