7 Lessons From My First Week as a Data Analyst
Your first week as a data analyst ain’t gonna be all glitter and rainbows. Get out of fantasy land.
In a perfect world, I’d be treated like a damn king – right away. I’d walk into the office with my coworkers cheering me on. And I’d be left in peace to write SQL queries for eight hours straight.
Now, that sounds like a great day to me.
But this is the real world, buddy. Life ain’t like that.
I know every job is different, but here’s what I learned during my first week as a data analyst…
This is gonna be a reality check for some of you up-and-coming data analysts.
Here’s the TL;DR of the lessons for you lazy bums:
- Don’t worry about tech skills
- Get ready for meetings galore
- Time management is key
- Brush up your people skills
- This ain’t a data portfolio project
- Good luck setting up your tools
- Domain knowledge trumps tech skills
Okay. Let’s dive in…
Tech skills? What are those?
Let’s face it…
You either became or are becoming a data analyst for one reason -- you love the skills. That’s why I’m here. I’m a sucker for a clean SQL join or a good-looking Python function. Oh how they steal my heart.
So you’re probably learning tools like Excel, SQL, Tableau, Power BI, Python, or if you’re a real wild fella, JavaScript -- hopefully not actually that last one.
But don’t expect to use these skills in your first week on the job.
It probably won’t happen.
I didn’t write a single SQL query during my first week. Still waiting now, twiddling my thumbs in the background.
Why haven’t I done it yet?
Because there’s a lot to learn about my team’s database and processes. If I don’t know the tables or data they contain, how would my boss expect me to run a critical query that the big jefe needs?
So, if you’re in a medium to large company like me, don’t expect to use those tools you’ve studied hard for immediately.
It’ll take time until you’re ready.
That’s fine. Don’t stress about it.
Meetings, meetings, and oh yeah, more meetings
Now that you know I haven’t used any of my super rad tech skills yet, what did I do every day?
Well…
Sat in a whole lot of meetings. It was freaking meetings galore.
Since summer’s ending, everyone’s done taking vacations. So teams are moving full speed, trying to catch up with everyone else.
Depending on the size of your company and the time of the year you join, your days may not be packed with meetings.
But let me tell you this…
No matter what, you’ll sit in many meetings or calls to understand your team’s responsibilities during the first few weeks. You’ll sit in the corner -- digitally or physically -- like a good boy and absorb as much company jargon as possible.
It’s gonna suck.
It’s gonna be boring.
But it’s a crucial step for you to grow fast in your role.
Time Management is the key
If you’re on a good data team, you’ll notice that your coworkers are time management superheroes.
And if you don’t believe me, here’s why you’re wrong…
People love dumping their problems onto the data team. This happens everywhere. So, your team members are swamped with work.
That’s one thing to deal with.
They also have to deal with other teams pestering them for more data.
They have to deal with project managers.
They have to deal with company leaders.
And now…
Worst of all…
They have to deal with you. You. The new data analyst who needs training.
So yeah, they’ve got a lot on their hands. But they know how to manage it.
And I suggest you start building your time management skills too.
You’ll thank me later for this one.
People Skills Matter -- A Lot
Did I mention there are a lot of meetings? Because there are.
I’ve now seen how project managers, team managers, and other associates work together. And let me tell you…
People who aren’t on your data team don’t give a damn about your technical skills. Your SQL code may be sexy. Your dashboards could be supermodels -- the most beautiful thing roaming the planet.
But do you think other teams care?
Hell no.
They don’t give a damn.
They want you to be easy to work with, and they want you to work fast.
That’s it.
Your coworkers will care more about your people skills than your technical skills.
So, if you’re a Shy-Sally, change that.
Build up your people skills and learn how to communicate with others. The Dorky World of Data isn’t built for lone wolfs.
Real-life Data Projects are Nothing Like Your Lame Portfolios
Your portfolio projects suck. Don’t feel bad. It’s the truth. And if it makes you feel better, mine suck too.
That’s because no portfolio project prepares you for what you’ll encounter in the real world. The projects are more complex than putting a couple of bar charts on a Tableau dashboard or cleaning 50 rows of data in Excel.
You’ll be working with 50,000+ rows of data daily.
You’ll work with columns you don’t understand.
And even the simplest projects aren’t solo projects. You’ll collaborate with others -- whether on or off your team. In the real world, every project has more than one person working on it.
It ain’t like what you do when learning the skills independently.
But don’t let this scare you.
While the projects will feel tremendous initially, they’re not so bad.
With time, you’ll get the hang of what’s happening.
Connecting to Tools and Getting Permissions Will Kill You
The best part about being a data analyst is working with cool tools:
- SQL Server
- Power Bi
- Tableau
- Excel
- Azure
- AWS
- JIRA
- Git
Man, the list goes on and on…
But do you know the worst part about using these tools?
It’s setting them up.
Even if you’re lucky enough to have the tools downloaded on your company laptop, you’re gonna have to gain the correct credentials and security permissions.
This will suck.
You’ll second-guess your decision to become a data analyst. You’ll think to yourself, “Oh no… Is this what working with the tools will be like every day?”
Don’t worry.
It won’t be like that.
Yeah, it’s tedious and sucks at first. You’ll talk to one too many managers and IT pros. But once you access your tools, you’ll never deal with the issue again.
I’m only telling you this because data analysts use a hell of a lot software tools. So you’re gonna feel overwhelmed getting set up.
You’ll survive.
Domain Skills Trump Technical Skills
Screw the data people on LinkedIn who talk about the glorious tech skills you use as a data analyst and nothing else. I’m guilty of this often, too. So don’t hate me for it.
But seriously…
Screw them.
I spent a lot of time my first week sitting in meetings. Did I mention that yet?
And I’ll tell you right now that I had no idea what was going on. I wasn’t just a deer in headlights. I was a deer that got hit by a freaking set of Mack Truck headlights. How’s that for an analogy?
Even with experience in manufacturing and purchasing, I didn’t understand half of what people said in meetings.
But that’s okay.
I’m in a new industry. So, I can’t compare myself to those with 5-10+ years of experience.
And odds are, your first data job will be in a new industry.
So you’ll feel like me.
If you want to cushion the blow from the Mack Truck about to hit you, study up the industry before your first day.
Learn as much as possible about your new company and study some competitors.
No matter what, you won’t know enough.
You’ll be an innocent little deer searching for its mother during meetings.
But coming prepared with domain knowledge goes a long way. It’ll help you stand out more than your tech skills ever will.
And in case anyone from my company reads this, I’m a quick learner. That Mack Truck may have hit me, but I’ll recover fast.
A Dorky TL;DR
In case you forgot 99% of what you just read, here’s the TL;DR for you again:
- Don’t worry about tech skills
- Get ready for meetings galore
- Time management is key
- Brush up your people skills
- This ain’t a data portfolio project
- Good luck setting up your tools
- Domain knowledge trumps tech skills
And look…
I’m pretty damn proud of my writing. So if you’ve made it this far, I’m gonna assume you had fun reading this post. If not and you’re still here, then leave. You’re weird for making it this far.
But if you’re a real data dork like me, let’s not make you reading my work a one-night stand.
Go follow me here on LinkedIn so you can get more juicy data stories like this.
And while you’re over on LinkedIn, send me a connection request or message with your thoughts.
Tell me if this post resonates with your experiences as a data analyst.
Or tell me if this post gives value to your journey to become a data analyst.
Anyway…
That’s it for today.
Go to my LinkedIn.
Do it.