On Monday’s episode we talking about the way to avoid the many pitfalls associated with building an all star in-house analytics and data team.
This shorty episode builds on this by talking about the important skillsets you must look for when hiring your first business intelligence engineer or visualization specialist!
To keep up with the podcast be sure to follow us on twitter @datacouturepod and on instagram @datacouturepodcast. And, if you’d like to help support future episodes, then consider becoming a patron at patreon.com/datacouture!
Music for the show: Foolish Game / God Don’t Work On Commission by spinmeister (c) copyright 2014 Licensed under a Creative Commons Attribution (3.0) license. http://dig.ccmixter.org/files/spinmeister/46822 Ft: Snowflake
Welcome to data couture, the podcast about data culture at work at home. And on the go. I’m your host Jordan bohall. If you like what you hear, be sure to subscribe lows get the latest episode. So wherever you get podcast, and if you’d like to stay up to date on everything data couture, be sure to follow us on Twitter at data couture pod. Finally, if you’d like to help support this in future episodes, consider becoming a patron of the podcast through our Patreon firstname.lastname@example.org. forward slash data couture. Now on to the show.
Welcome to Data Couture. I’m your host Jordan and once again, we’re in fabulous Las Vegas for the pickle World Conference where I’m enjoying quite a few of the sessions but also getting a chance to interview some of the top influencers in the data game. On this data bites, we’re going to be following up on Monday and Wednesday. Wednesday is episodes for how to hire a data analytics team. Now Monday, as a quick recap, we talked about all the different roles within an analytics team some of the common pitfalls as well as how to go about hiring your first analytics team at your organization. And Wednesday, we talked about the challenges, and really the type of person necessary to hire as your first database analyst. Now on this episode, we’re going to be talking about how to hire the next person, your bi engineer, your business intelligence engineer, or sometimes called a visualization engineer.
Now, we’re going to be talking about just getting your analytics team off the ground, not necessarily a mature analytics team at an organization with a mature analytics program. Instead, we’re going to be talking about that first couple of hires those first few people and the sort of skills they need to have. Now of course, every good business intelligence engineer or visualization engineer needs to be very fluent and the visualization software you’re using. If you primarily rely on say, the our programming language, then something like GFI, or if you’re a.net, or a Microsoft stack organization, then something like Power BI. Or if you’re well, it doesn’t really matter of the stack. But Tableau be very fluent in tableau, or any of the other hundred visualization software packages. Given the rather in tune and rather fluid with Power BI.
I’ll be using that as our example. Now, with Power BI, your bi engineer, visualization engineer will, of course have to know best practices when it comes to visualization and dashboarding. Also, the DAX program programming language, which is more of just a syntax, which evolved out of Excel, of course, as well as T sequel or transact SQL, which is the particular flavor of sequel from Microsoft, that Power BI uses. Clearly, I’m still on the talent of being sick. Nevertheless, those are all fairly standard fare for this kind of role. However, there’s some additional pieces that will be necessary similar to what’s going to be necessary from your first database administrator slash data engineer that you’re going to hire. That is, they’re going to have to be excellent the use of sequel for working within the data warehouse, so they can create the custom views and custom tables that they’ll need to most efficiently optimize the data visualization practices. But on top of that, and the most important, I would say would be the interpersonal skill set that ability to reach out to other users, other business units, other verticals within the organization, be able to derive the very specific requirements that will be needed.
Of course, those people in those business units won’t probably know as much about the data as your bi engineer, well, that won’t matter what will matter is their ability to pull out the need of the organization, instead of just some sort of static file they’ll be able to meet need to be able to pull out why you’re creating this automated dashboard for this group, and then come back to those people in an agile process over and over and over again, show them iterations of the dashboard until the correct product is developed for that company, or for that organization, I should say. And so that requires a lot of knowing business processes and being able to dig down and not being embarrassed to say no to folks, especially when their senior leadership or people above the particular bi engineer in the organization, being able to do so in a respectful way in a way that makes both parties happy with the end analytics product at the conclusion. Without that, without this interpersonal skill set, the one your your group won’t be particularly liked, he won’t have a good rapport with a number of folks, especially folks that you’ll rely on to act as cheerleaders so that you can build momentum for your analytics team. And furthermore, they’re just probably not going to use the product. And so this early bi engineer, this early visualization engineer is going to have to be able to train people how to use the software system, how to use the automated dashboard, as well as how to garner insights from the dashboard itself, because this is brand new. And if you’re presented with something brand new, that helps at least have a user’s manual or good documentation or someone in the best case scenario to tell you how to use the damn thing. So with that, you’re going to have to find somebody with you know, a few different skill sets and my experience, it helps to hire someone, internally, someone who knows the data, most ideally. But nevertheless, someone who’s been around long enough to really know how the business operates and has that eagerness to learn because it is a learning process to be a DI engineer, as well as the ability to interface with everyone across the organization. So if you have any comments or feedback or ways that you’ve tried this in the past, let me know in the comments down below. I’d be happy to see what everyone’s saying.
I’ll talk to you next time.
That’s it for the show. Thank you for listening. liked what you’ve heard, think consider leaving a comment or like down below. Stay up to date on everything data couture, be sure to follow us on Twitter at data couture pod, consider becoming a email@example.com forward slash data couture
music for the podcast. It’s called foolish game. God don’t work on commission by the artist spin Meister used under the Creative Commons Attribution 3.0 license,
writing, editing and production of the podcast is by
your host Jordan bohall.