When I was trying to break into data engineering, I thought I needed to be an expert in every tool and technology under the sun. But looking back, it was a handful of unexpected skills that actually helped me land my first role.
The Overrated Skills
I spent hours upon hours learning the intricacies of distributed systems, pouring over papers on consensus protocols, and practicing my coding skills until I could solve any problem on LeetCode. But when it came down to it, these skills weren’t as crucial as I thought they’d be.
The Skills That Actually Mattered
So what did help me land my first data engineering role? Here are a few skills that might surprise you:
- Communication: Being able to explain complex technical concepts to non-technical stakeholders was essential. I had to be able to communicate with product managers, designers, and other engineers to ensure everyone was on the same page.
- Problem-solving: While coding skills are important, it was my ability to approach a problem from multiple angles and find creative solutions that impressed my interviewers.
- Data analysis: Being able to collect, process, and analyze data to inform business decisions was a critical skill. This involved working with datasets, identifying trends, and presenting my findings in a clear and concise manner.
- Collaboration: Data engineering is a team sport. I had to be able to work effectively with others, provide and receive feedback, and adapt to changing priorities.
The Takeaway
Looking back, I wish I had focused more on developing these skills and less on trying to be a master of every tool and technology. If you’re trying to break into data engineering, don’t underestimate the importance of communication, problem-solving, data analysis, and collaboration.
Further reading: Data Engineering Handbook