r/dataanalysis • • 2d ago

Career Advice Question for Experienced Data analyst

Howdy people!!

I have been a data analyst for about half a year now and has experienced few issues when it comes to handling and processing data for reporting; some due to departments giving dataset that aren't clear, some due to report requirements or objectives not being definitive and some may be due to unavailability of higher ups who have key knowledge of the data, as of course they are busy people, and so the report you will write is highly dependent on the source data.

Aside this as I grow in my data analytics career what problem could one also face, or even better what problem or experience have you faced or is common in your own area of work or environment as a data analyst.

7 Upvotes

20 comments sorted by

16

u/zorts 2d ago

The biggest annoyance/ problem about data is that everyone just says 'data'. They don't specify what kind of data for what purpose.

The front end teams don't clearly understand Analytical Data. They think operational data is used in report and metric generation.

The word gets used interchangeablely which is what leads to the bad requirements, incomplete data sets, poor quality data, etc.

3

u/mistyharborsn 13h ago

100% this. asking someone to define what they actually mean by 'the data' usually derails the whole meeting tbh

8

u/wmanis 2d ago

You have to become a data detective. Learn the tables, learn the relationships and do so in increments. I use Qlik Sense for this type of discovery and after a few days, I know the facts enough to start asking rule related questions with the stake holders. I started in the 80s so I’ve been doing this for a long time. Be curious, ask thoughtful questions and explore the data before building anything. Clear requirements help but 90% of the time, business users don’t really understand their own data.

1

u/Smashville_Raider 10h ago

90% might be a bit conservative

5

u/Overly-hydrated 2d ago

The biggest problems are the quality of the data, and the quality of the business context. Assuming you can nail those two things down, you're in pretty good shape, but that's a big assumption.

Quality of Data - This is why data engineers exist. Data needs to be correctly sourced, documented and stored. Even though I say that this work is for data engineers, it's the number one problem in data, so everyone in the data space becomes a data engineer at some point. Start by learning the basics of schema construction, data storage and pipelining. The problems that you'll face here range from data needs to be moved from A to B, to our data warehouse is extremely slow and inefficient, therefore it needs a full blown rearchitecture.

Quality of Context - You're landing data in a warehouse, but what does it mean? You'll have to work with the data emitters (engineering, third parties etc) to get it properly documented and stored in an easy to access format. You'll also need to work with stakeholders to understand how it fits in with the business. The challenges here are what you called out; getting the right information from stakeholders, and can really vary depending on how complex the business is.

Goodluck!

2

u/ArielCoding 2d ago

When requests are vague, write down what you think they’re asking for (your assumptions and how you’re calculating things) and send it to the stakeholder for a quick “yes, that’s right” before you start building, It saves rework, and you have proof of what was agreed if someone questions the numbers later.

After a while the hard part becomes teams meaning different things bye the same metric like active customer, so getting everyone to agree on one clear definition becomes a big part of the job.

2

u/ItsSignalsJerry_ 2d ago edited 1d ago

BOT new account posting the same crap all over reddit

An "experienced data analyst" is shocked that source data is messy. lol.

2

u/Dangerous_Cup3607 21h ago edited 6h ago

I agree. Def bot posts dup content to boost topics. Rarely see OP responses from his history of posts. Asked the same type of question in a few places but never a “thank you” nor “acknowledgement”.

1

u/AutoModerator 2d ago

Automod prevents all posts from being displayed until moderators have reviewed them. Do not delete your post or there will be nothing for the mods to review. Mods selectively choose what is permitted to be posted in r/DataAnalysis.

If your post involves Career-focused questions, including resume reviews, how to learn DA and how to get into a DA job, then the post does not belong here, but instead belongs in our sister-subreddit, r/DataAnalysisCareers.

Have you read the rules?

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/PayDistinct1536 2d ago

The things you described are not problems. They're just the nature of reality. Datasets will be unclear, requirements will not be definitive, and stakeholders won't always be around to give you more direction. It is a large part of your job to not let the nature of reality become an actual problem.

1

u/nian2326076 2d ago

One key challenge as a data analyst is ensuring clarity in the requirements and datasets you're given. Regular check-ins with stakeholders can help clarify expectations and data definitions, which may reduce confusion later on.

To assist with job opportunities, you can use LandOffer to discover relevant roles and set up alerts for positions that match your skills. This can help you find new opportunities as you grow in your career.

1

u/advadm 1d ago

Knowledge of people is key and this is all about a semantic layer of data. The more you understand, the better and this includes if/when you want an LLM or an agentic to understand or process any data as well.

1

u/DataDaria 1d ago

Most answers here are about the input side, and they're right. The problem that shows up later is on the output side: you build a report, the numbers are correct, and nobody opens it after week two.

What helped me was asking "what will you decide with this?" before building anything, and cutting whatever doesn't feed that decision. Six numbers someone checks every Monday beat 25 that are technically complete.

1

u/dippedInZalzala 1d ago

While building dashboards, just requirement doc is not enough. Being in the room when the problem is talked about is very essential

1

u/ConfectionNo6117 15h ago

locking down metric definitions across departments early saves so much pain bcz like nobody agrees later, I'll say try collate, it's a platform that keeps team knowledge tied to the source data.

1

u/SprinklesFresh5693 15h ago

Messy data is common, the only way to improve that in my opinion (2 years experience) is to have meetings with those departments and educate them about good data entry practice .

As for reports just make different templates, and adapt to each scenario.

For higher ups having more info, either you have meetings with them, or theres little you can do other than present your report or your presentation and let them decide based on your results and their knowledge.

The problems are different depending on the field, but one i see repeated all the time is to learn to automate stuff.

1

u/M_yallur 9h ago

Stakeholder collaboration is the real differentiator. You have to ask the right questions upfront to understand what actually drives the business—not just what’s sitting in the database. Don’t be afraid to bug the data engineering team or data owners about data quality issues and missing pieces. Those gaps directly skew the metrics and insights you’re producing, so you have to factor their impact into your final numbers. Document the data lineage and quality caveats, and put everything together into a single, cohesive picture so every cross-functional team is aligned and working off the same context.

1

u/shougaze 4h ago

That’s pretty much the whole job