If you need data infra or data strategy help, then feel free to set-up a free consultation! - calendly.com/seattledataguy/30-minute-meeting-requirements-yt
One of your best videos! Communication is key. As a manager, what I thought I wanted wasn't always what I needed. Conversely, I once had a dev team that didn't understand why it was unacceptable for two internal sales reports to give different answers to the same question -- due to time zone differences. To them, it was just a UI display issue and therefore 'no big deal'. Meanwhile, the Board is like, "why do these reports have different sales figures for Q1". (ugh)
As always, very useful video! Now I’ve been near 2 year in my DE career and I totally agree with you. Most important thing of your work is to understand the business needs so that you can gather better requirements and definitely make your work easier, more clear and more accurate
Those are excellent points. Communication with a business becomes substantially more straightforward when one understands the domain, is familiar with the terminology and abbreviations, and has knowledge of the business processes and KPIs. This not only accelerates communication but also fosters the development of trust and relationships. Therefore, it might be valuable for a data engineer or analyst to cultivate expertise in specific areas or spheres.
This is informative. Thanks! DE business/communication skills will take someone so far. Building data initiatives or projects that deliver business value, by tight collaboration with stakeholders on the process will ensure the endeavor as a success. Early on, Im trying to learn this business sense like spiderman's spider sense lol.
Thanks for the video's, @seattledataguy! I have been a Business Analyst for 4 years, and im training to be a Data Engineer now. Do you think recruiters and hiring managers are gonna think "ooo Wow, he was a business analyst!", or am I going to really have to sell that point?
You will still likely need to sell your technical side. Yes its great that you have BA experience! But starting out its important to be able to do the technical work and eventually start translating requirements
I had my first requirements gathering session as a Data Engineer this month. I started it off by saying "What are your data sources and what graphs do you currently make with it?" and they just looked at me like I was speaking a different language. I realised pretty quickly I needed to change my approach, so I showed them a video of the system we were building for the company and how it all works, and it was a lot easier after that. We started whiteboarding all the work they did until we had a full model of the data. I thought it was as fun as building the actual pipeline. Do you ever measure the effectiveness that your work has on the business? If so, how?
Hi, Can you maybe recommend some book/s that touch topic of best practices when designing ETL? - doesn't really matter what tool, just general concepts of do/don't - I know this may vary depending on the use case, but still wanted to ask if something like this even exists, there are plenty of courses that teach tools, but don't really touch on what should you avoid, I Think something like this would be helpfull for people who starts with ETL,
