Pivoting from Product Design to Data Engineering
Context
After several years working as a product designer and researcher, I found myself increasingly drawn to the infrastructure and systems side of technology. I was considering a move into cloud engineering when an opportunity in data engineering came up.
Decision
Accept a data engineering role instead of continuing down the cloud engineering path
Alternatives Considered
Pursue cloud engineering (my original plan)
- Already studying for Azure AZ-900 certification
- Cloud skills are broadly applicable
- Closer to infrastructure and DevOps work
- Less direct connection to data — my emerging interest
- Highly competitive field
- Longer ramp-up to hands-on impact
Accept the data engineering role
- Combines infrastructure thinking with data impact
- My design background helps me empathize with data consumers
- Growing field with strong demand
- Opportunity to build tangible pipelines and platforms
- Less experience with data tools compared to cloud platforms
- Different skill set than what I was originally studying for
Reasoning
Data engineering sits at the intersection of infrastructure and impact. I get to build systems (the part of cloud engineering that excited me) while also producing something immediately useful — reliable data for analysts and business stakeholders. My product design background is an asset here: I understand the end users of data platforms and can design systems with their needs in mind.
Why This Was the Right Pivot
I originally planned to move into cloud engineering — that was the path I was studying for. But when I looked at what actually excited me about cloud work, it was the systems thinking: designing pipelines, automating processes, making infrastructure reliable.
Data engineering gave me all of that, plus something cloud engineering often doesn’t: a clear line from my work to business impact. When a pipeline delivers fresh data to a dashboard, the value is immediately visible.
What My Design Background Brings
Most data engineers come from software engineering or analytics. Coming from product design means I naturally think about:
- Who is consuming this data and what do they need?
- How can I make the data platform intuitive for non-technical stakeholders?
- Where are the pain points in the current data workflow?
This empathy for the data consumer has been surprisingly valuable.