r/analytics • • Sep 01 '26 Bravo

Discussion Phrases heard in analytics meetings, translated

930 Upvotes

"Can we get visibility into this?" - I will not act on this information. I want it to exist near me, like a plant.

"The data doesn't feel right." - The data contradicts what I already told my boss.

"Interesting." - I stopped listening at slide two.

"Can you make it more actionable?" - I don't know what I want. Iterate until I recognize it.

"We're a data-driven organization." - We have dashboards.

"We need to be more data-driven." - We also don't open them.

"Quick question." - Project.

"Super quick question." - Two projects and a definition fight.

"Can we add AI to this?" - I attended a webinar.

"What's our AI strategy here?" - I attended two webinars.

"Directionally accurate." - Wrong, but in a direction I like.

"Single source of truth." - My source. Of my truth.

"Let's align on definitions first." - This meeting will not survive. Nor will the next one. See you in Q3.

"Can you pull this real quick? Shouldn't take long." - I have already promised it to someone.

"Great analysis! Let's discuss next steps." - This will never be mentioned again.

"Great analysis! Really great work." - This will never be mentioned again, but warmly.


r/analytics • • Sep 16 '23

Career Advice My career change is official as of today. From Social Worker to Data Analyst

904 Upvotes

Applied to about 35 jobs. Interviewed 6 places Got 1 offer.

My career change started in 2019 when I went back to school for Business Analytics. When I first went back I felt inadequate in my first few semesters but by the end I felt more confident than ever. The job I have been working isn't data related at all so in order to make it look like I had Data Analytics experience I started incorporating data in the job on my own. I did this for 2 years and as of today that same job that was non data related is now 50% data and 50% social work.

Once I graduated I interviewed for 5 entry level data jobs and was denied by them all. I somehow landed an interview for a senior Data analyst role and did very well in the interview because I focused more on showing that I could communicate more than showing I knew SQL, Python and Excel. Turns out that's what they were looking for and the fact that I came off as a learner. I was offered the role and immediately went from $70k to $135k base.

I'm still completely shocked that I was able to land this job but I'm extremely excited about the things I will be learning.

To Those still trying to break in....keep grinding 🤙🏾


r/analytics • • Apr 16 '21

A guide to learning data analysis skills

899 Upvotes

Disclaimer: I am a Data & Insights Lead at a big tech company. I also have a small blog where I write about data skills for marketers with technical tutorials and articles on how to transition into data analysis. This post is from an article on that blog (I don't want to self-promote here but you can find the blog link in my bio or just leave a comment and I'll send it to you).

Hey all

This is the introductory post for an in-depth series on what data analysis skills to learn if you want to start, specialize or transition into data analysis.

tl;dr

  • Don’t focus solely on technical skills, but on translating data into business value.

  • Learn tool-agnostic skills.

  • Know the basics before learning advanced skills.

  • Have proficiency in spreadsheets, basic stats, and basic data viz. Also, learn how to connect data analysis with business decisions.

  • If you want to further go down the data analysis route add SQL, dashboarding, and data storytelling to this.

  • Want to become an expert data analyst? Learn Python and ETL tools.

Not sure which data analysis skills to learn? You are not alone.

A question I frequently see here (and get myself) is what skills you should learn when you want to get started with data analysis. Especially when you don’t have a technical background in math, statistics, or computer science and want to transition into data analysis from another role it’s hard to understand what skills you should learn.

Usually, when this question gets asked the answers mention seemingly random skills without any clear guidance on what is important and in which order you should learn the skills.

Similar to many other in-demand professional fields data analysis is a field that’s been ravaged by spammy information and bad ebooks, and it’s difficult to know where to start and what’s worth learning.

Wouldn’t it be great if there would be a clear guide or framework showing the exact learning path you should follow when it comes to data analysis? Detailing what you should know when it comes to the different skills?

A couple of years ago I was in a similar position when I wanted to transition from being a marketing consultant into data analysis. I was overwhelmed by all the skills, courses, and paths I could learn and take.

Based on that experience and being in the field now for a couple of years I wanted to create a skill development framework that gives you clear guidance on what skills to learn, how in-depth, and in which order when you want to get started with data analysis.

I am always open to suggestions and improvements to the framework! Looking very forward to any feedback and input to make the framework even better for beginners!

Three misconceptions when it comes to data analysis skills

Before we dive into the framework and talk about what data analysis skills you should learn exactly there are usually two misconceptions that come up among the answers when somebody asks what data analysis skills they should learn:

First, the recommendations focus too much on technical skills

E.g. “learn PowerBI, SQL, R, etc.”

The best technical skills don’t matter if you can’t translate your data analysis into business value, i.e. business decisions. You did your analysis in Google Sheets but saved the company hundreds of thousands in costs? Well, congrats! Nobody (and I mean nobody) in upper management will ask what cool technologies and coding libraries you used.

And this is also your biggest strength as somebody with a marketing/business background: You have strong business acumen. You know what matters for the business and what provides value. Play that strength by positioning yourself as somebody in between the data and the business world. That’s how you can compete easily against those with a purely technical background, by providing business value (that’s what I did when I transitioned). And that’s also why I focus so much on teaching a data analysis framework that gives you a structured framework for translating data into business outcomes.

Second, the recommended skills focus on specific tools

E.g. “learn Tableau, Google Analytics, etc.”

Yes, those are probably some of the most used tools out there. However, chances are that at every job you will have at least some tools for website analytics, dashboards, or whatever that are not mainstream.

So rather than learning the ins and outs of a specific tool (also on the job, you can still always Google any challenge you encounter…) learn agnostic skills which you can transfer to different tools.

For example, instead of knowing every detailed feature in Tableau, rather learn what makes a good dashboard, how it should be structured, and how it provides value to the audience (relating directly back to what I wrote above). Rather treat Tableau as a vehicle to learn (and show) those things than learning it for its own sake.

This makes you a lot more flexible when it comes to looking for new job opportunities and you don’t risk getting stuck when a new market leader among the tools emerges.

Third, too advanced skills are recommended

E.g. “learn Python, R, etc.”

I bet a dollar to a doughnut that every time somebody asks in a community “I want to transition into data analysis. What should I learn?” there will be at least one answer saying “Python”. Often followed by “If you want to be taken seriously in data analysis spreadsheets and SQL won’t be enough”.

Do you want to hear an industry secret? It’s not true. Even seasoned analysts often won’t use Python that much. Rather SQL and spreadsheets are often the bread and butter of many analysts and data analytics organizations. Of course, Python has many unique advantages and a rightful place in any technology professional’s toolkit for certain specialized advanced use cases. But more often than not it’s used by individuals and organizations to appear “advanced” and more “glamorous”.

This ties in directly with what I said above about the first misconception: If your analysis provides business value, nobody cares which technologies you used. Don’t start at the top and begin learning Python in a course just for the sake of it. Instead of wasting time learning theoretical concepts, think about how you can apply your analytical skills the fastest. Start with the fundamental skills and use them already to drive actual value for the business (and as such to build an analytical portfolio for yourself).

Now, let’s get finally started with the learning framework!

The Data Analysis Skill Pyramid

The Data Analysis Skill Pyramid is a framework to give you a clear learning path on what to learn when it comes to data analysis - without wasting time on nonessential things. It will help you to decide which data analysis skills to prioritize depending on your goals: No matter if you are a marketer who wants a future-proof skill to work more data-driven and to stand out among peers or if you want to transition into data analysis as a career path.

It’s a system that you can use to teach yourself data analysis in only a few months by focusing on the right things.

How the framework is structured

All the skills in the pyramid are ordered along two axes:

The horizontal axis shows you if a skill is rather a soft skill or a technical skill. For some skills, there won’t be a clear distinction between soft and technical as they provide communication tools (e.g. data visualization). However, in general, the more to the right as skill is placed the more it is a soft skill, and the more to the left it is a technical skill.

The vertical axis gives some guidance on how much scale and quality you will be able to provide with the respective data analysis skills. Scale means in this context automating things, reaching larger audiences, and being able to work with larger data sets. Depth means that you can access more data and do more sophisticated analysis which you couldn’t with lower-level skills. More on that down below.

The pyramid is divided into three stages representing beginner, intermediate, and advanced data analysis skills respectively. Below gives you an overview of what each stage stands for.

Step 1: Beginner skills (One-off analysis)

This stage is all about doing simpler to intermediate one-off analysis without a lot of automation. At this stage, you should focus on learning how to translate business challenges into data analysis projects, i.e. how to turn data into actionable insights into business decisions.

Learn a data analysis framework and process to connect your data analysis with business value and to focus on the right data and which data analysis methods to use. This teaches you what to do and you can start learning the how.

As such become a spreadsheets wizard and know the ins and outs of Excel or Google Sheets (doesn’t matter which one). Have some understanding of applied stats and modeling. (You don’t need a Ph.D. here. Again, applicability > in-depth theoretical knowledge.) And know some basic data visualization to communicate your analysis findings (e.g. in spreadsheets or on slides).

Including some general business acumen, those five skills are it to get a foot in the door and to have a basic set of data analysis skills.

Don’t get me wrong. You can already have a tremendous impact by knowing them. Again, in the end, it doesn't matter what technologies or techniques you use, the only thing that matters is the value your analysis creates for the business. You saved your business $100k by doing some marketing channel optimization analysis in a spreadsheet? Great! Nobody will care if you used Google Sheets for it...

Step 2: Intermediate skills (Improving impact)

This stage is about working more independently, autonomously, and having more impact.

You basically have three options to improve your impact with your data analysis:

  1. You can use more data that you didn’t have access to before (and/or do more advanced analysis with it).

  2. You can reach a larger audience with your analysis.

  3. You convince other stakeholders better with your data analysis.

The skills in this stage will help you with all three things.

SQL will help you to get more data autonomously (and the developers will thank you for not taking up their time anymore). As such it will help you to be more flexible with the kind of data sources you can use and how you can manipulate the data you pull. Also, you can start automating first things.

Dashboards are the natural successor to the basic data visualization of stage one. They allow you to reach large audiences at scale vs. the one-off charts you might create with slides or sheets.

Data Storytelling is an important one in any business or marketing context. If you want to have an impact you have to convince other people. Nothing better for this than an awesome presentation or pitch. This is a catalysator for the insights you generate with more technical skills. Again, you can have a tremendous impact no matter the technology you use if your outcome is directly linked to business objectives. Data well presented in a well-structured and action-oriented slide deck provides you with the leverage for this.

Step 3: Advanced skills (Automation)

I wasn’t completely honest with you, there is actually a fourth option to having more impact with data analysis: Doing more of it.

And the best way of doing this by automating things. ETL tools refer to tools that extract, transform, load data from one or more data sources into an output that represents the data differently from the source or in a different context than the source. ETL tools let you build data pipelines that allow ongoing data analysis. They’ll automatically pull data from data sources, format it, store it somewhere, and give you output such as dashboards.

With coding languages such as Python or R, you can automate things even further or do more complex analyses such as with machine learning.

So, should you learn all the skills in the framework?

It really depends on your goals. If you want to become an expert data analyst then probably yes. If you are a marketer who wants to stand out among peers, then you probably won’t need all the skills from the top of the pyramid. Either way, no matter the goal: Start at the bottom and work towards the top.

To sum this up, let’s work through an example on how a typical learning path could look like:

Let’s say you are a marketer and want to learn some data analysis skills. What should you learn?

If you are completely new to data analysis start at the bottom. Master stage one to be able to do a one-off analysis. If you want to become a better data (analysis) driven marketer you should make sure that you can check off all the skills listed in that stage.

As such as a marketer you should already have some decent business acumen. Continue with learning a data analysis framework to have a bullet-proof process to make your analysis valuable and to translate your analysis into business decisions. Afterward continue with basic data viz, applied stats, and spreadsheets. Ideally, you learn those at the same time and in a marketing context to make sure you don’t only learn theoretical concepts but know how to apply them in practical use cases right away. Again you learn everything as a means to an end to provide business value rather than for its own sake.

Only after you have mastered stage one continue on your learning path towards stage two. As I believe data storytelling is so important as it is a catalysator and leverage for everything else you do when it comes to the more technical aspects of data analysis I recommend starting with that one before continuing with SQL.

Are the skills of stage three useful for a marketer? Yes, of course. However, are they necessary? Probably not...

The skills from stage three have some diminishing returns when considering investing time there. Consider those skills either when you want to become a data analyst or later on in your learning path if you want to specialize or dive deeper into data analysis. As you can see it really depends on your goals here. Either way, if you are just starting don't make learning Python your priority for now.

What’s next?

The next parts of this series go more in-depth with the individual skills in each stage. As such we will start with stage one in the next part and I’ll detail what exactly you should know when it comes to beginner data analysis skills to get the fundamentals in that stage covered.

I'll post them here as well.


r/analytics • • Aug 06 '25

Discussion I went from Data Analyst to Head of Data in 4 years. AMA.

838 Upvotes

For context, I quit my consulting job with nothing lined up about 5 years ago. The only skills I had from that role were SQL, Tableau, and some company-specific applications. I met a guy out in New York who was the CEO of a fast-growing startup and asked if he needed a data guy. I flew in for 5 in-person interviews and got the job. I used my SQL and Tableau skills, added Python and Excel, and was promoted to Lead Data Analyst after 1 year and more recently to Head of Data after making some large contributions to the company’s culture and top line.

We were acquired by our top investor group and now I mostly do data analyst mentoring on the side. I’ve seen countless mistakes that people make both in the application process and after being hired. I’d love to answer some questions for you all!

EDIT: Lots of great questions here, so I'll share some of my high-level answers. Hope they help!

Application Process:

  1. Email the hiring manager directly after submitting your application. You can find their email on RocketReach.

  2. Think about how you can contribute to the company before you join. What does their data team likely do all day? Come up with ways you can help and share them with the hiring manager.

  3. Have numbers on your resume. Even if they're estimates, include them. Hiring managers want to see A) you made an impact and B) that you understand true impact is quantifiable.

  4. Practice your interview answers but do NOT memorize them. Allow yourself to be genuine in the moment. Use AI apps like Vocal Image to improve your communication skills if needed. The goal is to speak at a steady pace while enunciating, making eye contact, smiling, projecting, and breathing. When in doubt: SLOW. DOWN.

  5. See if you can connect with a recruiter, tell them your story and skillset, and have them share your resume with their clients. They’re great advocates if they’re on your side.


r/analytics • • Dec 16 '25

Question How do you approach large-scale text analysis when results must be GDPR-safe?

832 Upvotes

I’m interested in how people here handle large volumes of open-ended text (surveys, feedback, qualitative data) when privacy and compliance actually matter.

Many LLM-based pipelines are fast, but in practice I’ve seen teams struggle with anonymization, reproducibility, explainability, and EU/GDPR constraints, especially when results are shared with non-technical stakeholders.

What approaches have worked for you?

Custom NLP pipelines, prompt-based workflows, hybrid rule + ML systems, or something else?


r/analytics • • Mar 10 '26 Heartwarming Bravo

Discussion No one else to tell.. just got a huge promotion.

812 Upvotes

Coming up on 5 years at my current company, 6 YOE.

Just made director, and got a huge pay raise! Salary at 118k, and a bonus that brings TC to 160k/year.

Track thus far:

Year 1: Data Analyst - 51k

Company change..

Year 2: Data Analyst - 64k

Year 3: Senior Data Analyst - 80k - Performance based promotion

Year 4: Senior Data Analyst - 88k - 10% raise for performance

Year 5: Senior Manager - 103k - New team

Year 6: Director - 118k + 40k Bonus - Performance based

Just hype. No team, no direct reports, just me and the grind.

Edit: love all the haters :)


r/analytics • • Mar 21 '25

Discussion Guys, it finally happened

752 Upvotes

I started at a new company recently. My task was to create a Power BI dashboard for the VP to find opportunities. After weeks of back-and-forth, the dashboard went live in February.

My manager said all was going well. And then today I got an email from the VP: “could export some actionable data to Excel?”


r/analytics • • May 07 '21

I've had a dreamy analytics career and am getting out of the game. Here's some of what I've learned.

643 Upvotes

I've had a pretty thrilling analytics career for the past 7 years, working with Tesla for 4 years across almost the whole business, building a BI infrastructure for a Kenyan fintech startup, a couple adtech startups before that, and I may be getting out of the game. Since mentoring new analysts was my favorite part of the job, I thought I'd get some of my learnings into writing before they disappear from my memory.

When working in operations, I found that statistics and advanced modeling were highly overrated. There's a tendency for everyone to learn more advanced tech, but simplicity is really the key to all things analytics. I was interviewing for new hires in Kenya and saw hundreds of people applying with data science degrees and certificates, but almost no one knew Excel and very few knew SQL, it was all Python and R, which is great, but for startups, fancy models aren't that useful.

Simplicity is the key to everything, it helps with:

  • Stakeholders understanding the data

  • Speed in building dashboards and models

  • Lower maintenance costs

Advanced statistical models however, only work in scenarios where both of the below are true:

  • The future and the past are (nearly) identical

  • You don't have control over the inputs

If I see that 30% of Americans die of heart disease, but I stop eating unhealthily and start exercising every day, that statistic becomes less useful to me, because I can mitigate it. Instead I'm looking at cause and effect and using that to my advantage

However, with aneurysms, I don't know how to mitigate anything, so I am subject to the statistical chance, rather than having control through a solid understanding of cause & effect.

At Tesla, nothing was expected to be outside of our control. This is really where Elon shines, because for him nothing is outside of his control. But if we had a machine that wasn't performing to spec, and engineers couldn't get it to perform, Elon was able to step in and say "we don't need to use that machine, let's simplify the process".

You might think that something like weather is outside of your control, but we can control that too, either through adding outdoor structures or irrigation to be less reliant on rainy or sunny days. Choosing to be reliant on outside factors is a choice, and has all the associated costs/benefits that need to be taken into account.

When relying on statistics, you are actively choosing not to have any control over the input. Statistics work great for self-driving cars, where the outside world is inherently outside your control, or for human behavior where you aren't in control of the customer's behavior.

But for internal business processes, be it supply chain, service processes, workflows, layout, waste, etc, these can all be controlled, and that's where a great analyst has the power to deliver huge returns.

Once someone built a great model trying to predict which cars would be late coming off the assembly line, my goal was to highlight issues causing delays and improve our speed in fixing them. By the time his model was ready, the data was old, so it was never any use, and instead of predicting which cars were slow to come off the line, we just solved the problem. “The easiest way to predict the future is to build it” kind of thinking.

At Tesla my title was Operations Analyst, which meant everyone thought of me as a data guy, but I thought of myself as an operations guy. When I see outliers, they're not merely a random fluctuation or an anecdote. Instead I go in deeply to understand how the outlier became an outlier, and I try to create more, or less of them, depending on whether the customer journey was better or worse for the individual.

For any readers of Nassim Taleb (highly recommend all his books, the best on risk/probability anywhere), you'll already know that a lot of the world doesn't follow normal distributions, and there's lots of incidents where the opaqueness of a model inspire reverence for it rather than the assumption of the model being simply a guide, as it should be.

When I was building a plan for hiring 3,000+ headcount for Service, we experienced a lot of funkiness to the numbers. Some highly overperforming locations and some very underperforming. When building a simple model that could be adjusted on the fly, I was able to have conversations with outliers and learn things like "Oh 3 of our technicians aren't working in the shop, they're providing diagnostic support virtually", or "actually those 3 interns we have are actually full time technician apprentices", which I was simply able to update things on the fly. Because we could always see the inputs and their relevant outputs, and have conversations about the nuances, we weren't prescribing rules from an ivory tower, but building towards their true needs, since what happens in Norway may be vastly different from the way Hong Kong operates.

So when establishing business processes, the goal should be simplicity and clarity. Once it's clear everyone understands how things work intimately, then moving to a more advanced model is okay, but for building, simplicity is key.

The other great reason for simplicity, is the reduced maintenance. If each dashboard you build requires 5% of build time in regular maintenance, then once you have 20 dashboards, you will be fully occupied by maintenance. If you can reach 0% maintenance, then you can build indefinitely, similar to how particle colliders require superconductors to approach light speed, maintenance free dashboards give you a huge runway to keep problems solved, rather than being a glorified tech support contributor.

Which brings me to speed. Having a reliable Business Intelligence framework, that covers the main parts of the business in one or a few primary tables, allows you to get away from queries and into the true dashboard building phase. When I was at the agriculture fintech, we were able to build one master customer table, on the granularity of each farmer/season, that had maybe 150-200 columns, and is now the one stop shop for nearly all analytical questions. It is used by all the engineers, the CTO and CEO, and allows for quick answers to basically everything about sales and loans. It provides a reliable source of truth at very quick access, and is invaluable for high access, high speed, and high trust analytics.

We used a tool called dbt for building this system, which I highly recommend, as it is open source and has a great community on Slack for answering questions, but regardless, the end result of single sources of truth is huge.

But when interfacing with different teams for their data needs, I'd recommend being more an operations engineer. Helping them design operations to be efficient, to have proper incentive alignment, to highlight potential blindspots, to mitigate risks and to cap downsides of anything. Charlie Munger of Berkshire Hathaway says to spend 99% of your time understanding incentives. Nassim Taleb says that all that matters in risk is capping downside, so make sure if the potential is there for something to slip through the crack and cause major issues, you have a way to float those to the surface before they get real bad.

If you can do this, you'll have a more fun time in your role, as you'll be seen as a magician, who everyone will want to come to for all their answers. You'll be able to see lots of parts of the business and increase your experience and domain knowledge, and you'll be less stressed because you'll have fewer fires to put out and a more trustworthy data source to work with.

I hope some of you who are just getting your feet wet find this helpful or interesting.


r/analytics • • Jul 24 '25

Support I miss my junior days as an analyst…

626 Upvotes

Back when I was an individual contributor, things were simple. I opened my laptop, drank my monster energy, and dove into a dashboard. My biggest challenge was figuring out why the campaign table had 14 different definitions of “spend.” Life was beautiful.

Now I spend most of my time managing “stakeholder expectations,” navigating the political landscape like I’m playing 4D chess with people who’ve never opened a dashboard but have strong opinions about color palettes and KPI definitions.

I used to optimize media mix models. Now I optimize the wording in Teams messages so I don’t step on toes. I used to A/B test landing pages. Now I A/B test how direct I can be in a meeting without someone getting concerned about my tone. I used to ask “What does the data say?” Now I ask, “how are we going to bs the talking points this week”

Sure, I make more money now. I have a nicer title, I’m in meetings with leadership, and my calendar is a Tetris board of strategy sessions, alignment check-ins, and recurring “quick syncs” that never end quickly. But I don’t touch data anymore. My brain doesn’t light up solving a tough query. It flickers nervously trying to remember which VP is quietly feuding with which other VP.

Somewhere along the way, the craft got buried under the politics. And yes, I chose this path. I wanted to grow. But I can’t help missing the days when I had zeal. When I opened up a Jupyter notebook and felt excitement, not existential dread.

Now I just forward emails and write one-pagers with sentences like “We’re working cross-functionally to ladder insights up to the business goals.”

God help me.

Anyone else feeling this?


r/analytics • • Aug 03 '26

Question Company is banning Excel

624 Upvotes

I work for a healthcare company, and this week, out of nowhere, they instituted a policy that data can not be exported or stored in Excel format. There are no alternatives in terms of exporting reports in any other format. They said if we need information, we can just view the data within the EHR, and use their very rudimentary tools to manipulate the data within their system. I’m not really sure where this leaves me and 90% of the people I work with. Has anyone ever dealt with something like this? If so, are there any workarounds?


r/analytics • • Mar 04 '25

Discussion Coding interviews are out of control

616 Upvotes

When I entered the job market as a business analyst 8 years ago, it was just a conversation asking about my experience, what I've done for projects.

When I interviewed for a data analyst role four years ago, again, just the conversation, showed them some projects I worked on, some samples of my dashboards I'd created...

Now, It's the hunger games. I'm out here doing python, SQL, Tableau exercises in real time sharing my screen... It's very very stress inducing and as an introvert, I'm honestly not good at this, it's really hard on me. Like, I have tried training myself to be okay with this and to be more receptive to it. But it just sucks you know? 5 years I have spent in the job market with exceptional performance, and only to get interrogated and treated like a child who can't be trusted.

I honestly don't know how I'm going to get through the next few months looking for my next role with how stress inducing and difficult it is to find anything these days and all the hoops you got to jump through


r/analytics • • Mar 06 '25

Discussion PSA: Data Analytics job market is very poor

608 Upvotes

I don’t want to discourage people trying to make a career switch— but, right now is a terrible time for entry level data analytics jobs and tech in general. You’ll be competing with those who were laid off from prestigious big tech companies amongst many others in smaller firms.

I was recently laid off in January and have 6-8 years of relevant experience in Analytics, Python, SQL, and R. It’s been a struggle… most of the jobs I’m applying for require 2-3 years of experience and I have received 2 callbacks for jobs out of 100+ applications so far. If your degree is outside of statistics, data science, computer science, or some quantitative / analytics program, (🙋‍♂️) it’s going to be difficult.

I’m posting this so you can set your expectations if you struggle to find a job at first. If you’re in it for the long haul, awesome— keep your current role and apply like no other. But, I wouldn’t expect it to come easily or in the short term.

A quick tip: focus on one industry and have case studies you can use relevant to that industry (insurance, healthcare, SaaS, finance, etc.). Most of these companies are looking for experience in their industry. A major part of analytics is understanding the environment you’re operating in— far beyond code and charts.

There are some other factors, too. On-site jobs are easier to get. Remote work is very competitive, and depending on what state you live in they might not consider you off of that alone.

I hope this helps shed some light on the current market, I’m free to answer any questions you may have.


r/analytics • • Dec 11 '24

Discussion Director of Data Science & Analytics - AMA

589 Upvotes

I have worked at companies like LinkedIn, Pinterest, and Meta. Over the course of my career (15+ years) I've hired many dozens of candidates and reviewed or interviewed thousands more. I recently started a podcast with couple industry veterans to help people break in and thrive in the data profession. I'm happy to answer any questions you may have about the field or the industry.

PS: Since many people are interested, the name of the podcast is Data Neighbor Podcast on YouTube


r/analytics • • Feb 07 '26

Discussion I helped my girlfriend improve her invoices in Excel and it blew her mind

588 Upvotes

My girlfriend's been creating invoices in Excel for her family's business that's overseas. But I realized it was taking her hours to create each invoice (she would have to translate all the factory info from Chinese/English, take basic calculations each time, and re-type a lot of fields. So I mentioned to her a while back that she would save so much time if she just created a template that automated the legwork of the process, but she didn't seem convinced.

Well, yesterday, we finally sat down to look at it, and I made some pretty basic changes: a data-dump sheet in the background linked to the front-facing invoice, the translate() function to take out the manual translation process, and rounding/ceiling functions to clean everything up. Basically, it cut the process down from hours to what I imagine is an hour max for each invoice.

The funny part is that she was absolutely blown away each time I used one of these functions - apparently, she always associated Excel with being not very capable and for old people. I told her that we were barely scratching the surface of what Excel can do (I'm not even good with Excel lol) and that blew her mind even further.

Recently, I've been trying to explain to her the concept of frontloading work to save time in the long-run, and I'm hopeful this illustrated it. Anyways, this was just a little win that made me happy, so wanted to share! :)


r/analytics • • Oct 24 '24 Helpful

Discussion Just got a job!

511 Upvotes

Just signed an offer for 85k for a data analyst role at a big company! Just wanted to share this as a testimonial aimed to those out there trying to break into the field. With determination and self-belief, you can do it too.


r/analytics • • Sep 23 '25

Question Does anybody else enjoy injecting random UTM parameters into company websites? NSFW

463 Upvotes

Sometimes when I open links with UTM parameters like?utm_source=substack&utm_medium=email, I like to swap the terms with values like source=xhamster and medium=video. Does anybody else have the same guilty pleasure? And for those actively working in analytics - what do you do to prevent this from showing up during your next all hands meeting reviewing acquisition performance?


r/analytics • • Feb 20 '26

Support If I build one more "urgent" dashboard that gets zero views, I’m going to lose my mind.

435 Upvotes

Context: I am the marketing analyst for a massive, global company. They have thousands of employees, endless layers of middle management, and a bottomless appetite for "data-driven insights" that nobody actually looks at.

I’m hitting a wall, and I need to vent/get some advice before I just start sitting on my hands until its asked for 3 times.

Here is the weekly cycle:

  • I get a frantic ping at 4:00 PM on a Tuesday. "We need a deep dive on X. We needed this yesterday for a leadership sync."

  • I drop everything, pivot, clean the messy data, build the visualizations, provide some insights on the results, and send it over.

  • No "thanks," no follow-up questions, nothing.

  • Two weeks later, the person who "needed it yesterday" is ASKING FOR THE SAME THING. It's demoralizing.

How do you guys handle this?

I’ve tried the "value-based" approach where I ask what decision this data will drive before I build it, but they just give me some corporate buzzwords about "visibility."


r/analytics • • Jun 12 '26

Discussion Tableau is horrible.

431 Upvotes

Look, in 2004 — a few years after I was born — I’m sure Tableau was quite groundbreaking. But it’s an absolutely unacceptable piece of software at this point. Keep in mind that Tableau is charging about $700-$500 per creator license according to some sources. At this price point, you could use something open source like Superset, Metabase or Redash which will accomplish most of what organizations need for nearly $50 per license.

Tableau at this point seems to be an industry standard primarily because of its affiliation with its parent company — Salesforce. There’s no end to how many dashboards I see that are inconsistent in terms of quality, spacing, and design even from the same company.

Tableau is hyper-focused on customization when most dashboards and BI layers require standardization. It feels like a product made for boutique dashboard design. And yeah, there are cool things you can do with it like make a flower graph or some other esoteric visualization. But those visualizations are unnecessary for the modern business. Sure, you can merge 8 datasets from disparate sources if you want - but seriously - why would you ever want to merge someone's Excel document on OneDrive with your production SQL query?

If you're an organization large enough to afford Tableau, you can afford better upstream data engineering. Simple.

The most important issue with Tableau is that data analysts are no longer dashboard designers. I’m a data engineer, a BI user, and an ad-hoc analysis deliverer. Not a dashboard designer. Sure, I want sensible views for my stakeholders, but those should take no more than 5 minutes to create and populate. Tableau is fast, but I promise that I've created dashboards in less than 1 minute using some of these other tools at a cheaper cost. Tableau cannot do that. You will spend hours on dash boarding, creating several sheets, trying to mash them up into a dashboard, setting up the Tableau Cloud, or whatever else.

The goal of any tech organization is to automate away most of the unnecessary work. You cannot automate Tableau. You can't access Tableau dashboards as code in a way that allows you to mass update every Tableau dashboard to change the name of a few metrics all at once.

I could go on and on about specifics about Tableau, but the price point, the difficulty of use, the impossible navigation of their Server and Cloud products, the lack of open source modification...


r/analytics • • Mar 21 '25

Discussion Job offer!!!!!!!

392 Upvotes

Just wanted to share that I have finally received a job offer! Analyst position working with marketing data. Super stoked 😤.


r/analytics • • Oct 29 '25

Discussion Please read this if you are thinking of becoming data analyst...

386 Upvotes

FIRSTLY I want to preface this by saying this is going to be a bit of a rant - a lot of what I'm saying has already been said on this sub but I just want to get some things off my chest.

Don't get me wrong, there are perks to being a DA, especially early career. Depending on how you play it you can have the flexibility to jump into various different career paths : data science, SWE, data engineer etc. I also love how it gives you opportunities to bridge the gap between stakeholders and tech.

I've been working at my current company for a year and a half and while I am grateful I have a job given the current job market there are a few things that are REALLY weighing on me a lot:

1. Be wary!! Data Analyst = Excel/Dashboard Jockey (sometimes)

So much of my workload is QAing spreadsheets**,** adhoc mindless data requests, updating PowerPoints and fixing dashboards. It's reached a point where sometimes I want to scream, leave my job and become a plumber or elevator technician (which apparently aren't bad options according to reddit).

I'm looking for other data analyst positions and I see a lot of other "senior" positions that are exactly the same responsibilities. I've learned to ALWAYS ask about the job requirements in detail and in person, so many data analyst positions are not what they seem.

2. It's easy to fall behind the technology curve

The staple DA tech stack would be SQL, Power BI and maybe some cloud. You may get some opportunities to branch out but I look at friends in DS or SWE who are constantly picking up new skills in ML/Model Building etc. and it feels like I'm falling behind.

A big part of this is that my company outsource a lot of technical work externally and I've found it really hard to get involved in anything more technical than building a Power BI dashboard. Beware of companies that outsource all/most of their technical work because you will have limited progression!!

3. People don't want data analysis, even when they need it

From my experience a lot of companies are not interested in seeing the bigger picture. They have their KPIs which they want to meet and they are only really interested in those metrics. You could build a state of the art model that gives a holistic view into your company's performance and models future strategies that will save millions but senior leadership will not be interested because it is not a dashboard visual of 5 to 10 KPIs that they need to meet by the end of the year. It's this tunnel vision that drives me crazy sometimes.

OK rant over. I realise a lot of these points are related to company culture and will vary from job to job, honestly I hope a lot of people have had a different experience working as a data analyst! If so please do share.


r/analytics • • Apr 21 '21

Google Analytics Google Data Analytics Certificate

384 Upvotes

I started my 1-week free trial on Sunday. I had decent background knowledge of data analytics, excel, and sql. The 8 course certificate has been pretty painless so far, and I will finish the 5th course tomorrow. The “6 month course” is probably more like a 1 to 2 month course for anyone taking the training seriously. I’m mostly excited for courses 6, 7, 8 to get some background in Tableau and R and do the project.

I’m posting this for people interested in the certificate. It’s nothing crazy hard and even if you have no background, the videos and hands on activities do a great job teaching. I would say this is 100% an entry level certificate. I think it would be pretty good for anyone like me trying to make a career change and looking to get their foot in the door.

Let me know if you have any questions about the certificate.


r/analytics • • Sep 30 '25

Discussion If you're considering a career in analytics: Go big or go home!

379 Upvotes

As someone who has been in a perpetual state of pursuing data analytics as a career since 2014, here is my honest, bleak, and unadulterated opinion on the prospects in this field.

If you think that data analytics will be anything like what you learned in a Google certification program or bootcamp, think again. Being a data analyst is no longer exclusively about providing insights through dashboards or reports. Companies seemingly want someone who understands the full tech stack backwards and forwards and who has deep understanding of ETLs, building pipelines, data architecture, etc. Basically they all want a data engineer who can also do the dashboards and reports.

Unlike other career fields that have a natural progression from junior to senior level roles, the career ladder in data analytics is all but flat these days. Unless you're a data engineer or data scientist who does it all, you're going to struggle finding employment as a run of the mill DA or BI analyst who focuses on reports and dashboards. Those jobs don't really exist anymore as many companies want someone who apparently does everything. The field has been largely consolidated and frankly I don't think we're ever going back, especially with the advent of AI.

Unless you go work for a company that capitalizes off user data and generates revenue from the data, you're likely always going to work on a skeleton crew where you're the only one doing what you do, and treated like a luxury item that most companies don't have the budget for. When times are good, the field may be thriving. But as soon as times get tough, DA teams are usually one of the first orgs to be cut. You will spend most of your time competing for scrap resources with other teams and trying to validate your existence. Validating the reason for my being has been 95% of my job working as a data/BI analyst.

Everyone wants you to be a master of their DA platforms but managers are hesitant to take chances on you if you did similar work elsewhere on a different platform. In other words, good luck crossing over if your last platform was Tableau but the company you're applying to exclusively uses Microsoft and PowerBI. Perhaps one of the most frustrating aspects of this field is that everyone uses different tools, but hiring managers don't think you're smart enough or clever enough to figure out their tools. I run into this issue SO BLEEPING MUCH!

In good faith, I can no longer recommend this field due to the lackluster career prospects it offers in relation to other fields. If you like numbers and data, but want stability and an actual career path that provides opportunities for career growth, I would personally point you towards something like accounting or finance. There will be ample jobs at most organizations in either of these areas, and there are actual career paths that one can work their way up by gaining more experience and/or additional credentials. This is sadly not the case for most DA roles I've held in the past.

Good luck!


r/analytics • • Mar 17 '25

Support My first python code 1500 lines to automate my daily boring task.

370 Upvotes

I recently joined a company as an operations executive. While my initial goal was to work as a data analyst, securing this role was challenging due to my non-technical background. As the saying goes, "Beggars can't be choosers," so I accepted the opportunity.

Upon joining, I noticed that many tasks were being done manually, even though they could easily be automated using basic Excel formulas. For example, my colleagues were manually counting and transferring filtered data from one sheet to another. While I was impressed by their speed and efficiency with Excel shortcuts, the process still seemed time-consuming and prone to errors. With the help of ChatGPT, I created an Excel formula to automate this task, making it about 10 times faster and more accurate. However, my team leader didn’t seem pleased with my initiative. He has extensive experience with Excel and is usually the go-to person for troubleshooting, so I suspect he may have felt undermined.

It’s been 17 days since I joined, and my primary responsibility is to review daily data in an Excel file (around 50,000 rows x 11 columns) and compare it with a master file. The expectation is to complete this task within an hour, which feels unrealistic given the volume of data. So far, I’ve managed to do it in about 1.5 hours. To streamline this process, I spent my entire weekend writing a 1,600-line script with the help of AI, which automates most of the task by defining ranges and conditions.

While I’m proud of the effort I’ve put in, I can’t help but feel that the company doesn’t fully appreciate the value I’m bringing. The pay doesn’t seem commensurate with the level of work I’m doing, and the lack of holidays (like Holi) has been disappointing. I’m also concerned that if they find out about the script, they might simply assign me more tasks instead of acknowledging the efficiency I’ve created.


r/analytics • • Jan 06 '25

News Got my first Analyst job!

366 Upvotes

Just got my first job in analytics! Some background I have been doing a little bit of data analysis for a relative who owns a small business. Nothing crazy, not a lot of data but I used Excel, sql and powerBi to analyze it and to refine my skills. After getting my degree in CS I have been applying to jobs for 4-5 months and it finally happened!

Keep pushing!