As a data engineer, have you ever felt like you’re stuck in a rut, working on data platforms and ingestion without gaining any meaningful domain knowledge? You’re not alone. I’ve been there too, and it’s frustrating when you’re assigned tasks that don’t require any understanding of the industry you’re working in.
I used to think that working as a data engineer in a healthcare or financial company would automatically give me domain knowledge in those areas. But the reality is, it’s not that simple. You might be stuck working on data pipelines and platforms without ever getting a chance to dive deeper into the business side of things.
Data modelers, on the other hand, seem to have an easier time gaining domain knowledge. They work closely with stakeholders and have a better understanding of the business requirements. But those positions are often highly sought after and hard to get.
So, what can you do to gain domain knowledge as a data engineer? One strategy is to try to get analyst experience and combine it with your data engineering skills. This will give you a seat at the table with important stakeholders and expose you to the business side of things.
But what if you’re not given the opportunity to work on projects that provide domain knowledge? That’s a tough spot to be in. It might be time to have a conversation with your manager or look for opportunities outside of your current company.
Gaining domain knowledge takes time and effort, but it’s essential for data engineers who want to make a meaningful impact in their industry.