Why Working at Meta is Bad for Data Engineers
I have to come clean — I build data pipelines, but I’m not a Data Engineer; at least according to some top tech companies. Over the past few years at one Silicon Valley company, I’ve worked with many Data Engineers. To be more specific; varying roles who deliver work commonly aligned with data engineering, such as writing code to build data pipelines. We’re in a time period where data engineering doesn’t have a widely agreed upon definition. While some companies, such as Amazon and Meta lean on Data Engineers to define metrics, write SQL, and even build dashboards, other companies task Data Engineers with coding entire applications in languages like C++ or Java.
Based on jobs listed on metacareers.com, Data Engineers in Meta’s own terminology are typically an extension of software engineering. It is common to see listings for “Software Engineer — Data Engineering”, and less common to see titles such as “Data Engineer” or “Business Intelligence Engineer.” Meta is one of the most mature engineering cultures founded on engineering principles, and engineering can have a very specific meaning.
The bar for Data Engineers at Meta is just as high — and sometimes higher, than that of an equivalent Software Engineer at Meta
How could it be bad for Data Engineers with a company like Meta on their resume? Firstly, according to…
