I spent three years thinking I knew what data analysts needed to learn.
SQL? Check. Python? Check. Dashboards in Tableau? Obviously. I'd read the job postings, studied the frameworks, built projects that looked impressive on GitHub. And then I hit a wall at work — and realized I'd been optimizing for the wrong things entirely.
Here's what nobody tells you when you're starting out in data: the skills that look good on LinkedIn aren't always the ones that get you hired. And the ones that do get you hired? They're not as visible. They're not as easy to portfolio. But they're what separates someone who gets callbacks from someone who gets ignored.
I want to walk you through what I got wrong, what I learned, and what actually matters in 2025 — especially if you're an Indian analyst trying to break into roles at places like Morningstar, flipkart, Amazon, or fintech startups.
What I Got Wrong About Technical Skills
When I was studying Economics at university, I thought data analysis was mostly math. Regressions, hypothesis testing, statistical theory — that's what mattered. So when I started learning SQL and Python, I approached them the same way: master the syntax, understand the logic, build complex queries.
I was partially right. And completely missing the point.
The SQL Mistake
I used to write SQL like I was trying to prove something. Nested subqueries, window functions stacked three levels deep, CTEs within CTEs. I could optimize a query to run in milliseconds instead of seconds. On Reddit, people would upvote it. I'd feel smart.
Then I joined a team where people actually ran my queries in production.
The most valuable query I ever wrote was the simplest one. Four joins, a clean GROUP BY, readable column names. A colleague ran it on the entire financial database and found a ₹2.3 crore discrepancy in quarterly reconciliation. That query got me recognized in a company all-hands. Not because it was clever. Because it worked, and someone else could understand it six months later.
Here's the thing: in 2025, the bar for SQL isn't complexity — it's clarity. Hiring managers don't care if you can write a recursive CTE. They care if you can write a query that answers a business question, runs fast enough, and your team can maintain it without calling you at midnight.
What actually matters now:
- Writing queries that are readable at first glance
- Understanding execution plans — not memorizing them, but knowing when a query will crawl
- Being comfortable with JSON, nested data, and unstructured formats (because real data is messy)
- Knowing when NOT to use SQL — when a simple API call or a spreadsheet would be faster
The Python Paradox
I learned Python because every job posting demanded it. I built a portfolio of machine learning models — clustering algorithms, time-series forecasting, neural networks. Beautiful code. Impressive GitHub repos.
I've used Python for actual production work exactly twice in three years.
Most of the time? It's pandas for data cleaning, matplotlib for quick exploration, and that's it. When something needs to be more sophisticated, the company either has specialized data engineers or they use pre-built tools like Looker or Mode.
But here's what surprised me: the Python skill that got me hired wasn't machine learning. It was automation. Writing a script to pull data from an API, clean it, and dump it into a database — that's what people actually need.
In 2025, Python matters for:
- Data cleaning and transformation (pandas, polars)
- API work and automation
- Quick analysis and prototyping
- NOT necessarily machine learning (unless you're applying to ML-specific roles)
The Visualization Trap (And Why Your Dashboards Might Be Hurting You)
Tableau. Power BI. Looker. Every analyst learns these tools.
And most dashboards are terrible.
I used to think more interactivity was better. Drill-downs, filters, color-coded heatmaps with 12 different shades. I'd spend hours perfecting a dashboard, adding animations, using gradients that would make a designer cringe. It looked impressive in demos.
Nobody actually used it.
The dashboards people actually used were boring. Simple. One metric. One clear insight. Maybe a trend line. That's it.
Here's what I learned: a dashboard isn't an art project. It's a communication tool. Your job isn't to show how much data you can display — it's to make a decision easier for someone who has 30 seconds before they go into a meeting.
In 2025, what matters is:
- Understanding your audience: Building a dashboard for a CFO is completely different from building one for a product manager. Know who's looking at it before you build it.
- Storytelling over aesthetics: Can you look at a dashboard and immediately understand what action it's recommending? If not, it's not a good dashboard.
- Automation and freshness: A beautiful dashboard that's updated manually every week is worse than an ugly one that updates every hour.
- Mobile-first thinking: If your CFO is looking at it on an iPhone in a cab on the way to Bombay airport, can they still understand what it means?
And honestly? The tool doesn't matter as much as people think. I've seen brilliant analysts do incredible work in Google Sheets. I've seen people with advanced Power BI certifications build dashboards that nobody looks at. The tool is secondary. The thinking is primary.
What Actually Gets You Hired (The Skills Nobody Teaches)
Business Sense
This one surprised me more than anything else.
When I was interviewing for my current role, I walked in thinking they'd ask me to write SQL on a whiteboard. They didn't. Instead, the hiring manager gave me a scenario: "Our payment success rate dropped 2% last quarter. Where would you start investigating?"
She didn't care about my technical answer. She cared that I asked the right clarifying questions. How much of the drop was due to the new payment gateway? Which user segments were affected? What was the time lag between the change and the metric drop?
That's business sense. And it's worth more than knowing 10 SQL functions.
In 2025, the analysts getting hired are the ones who:
- Can read a P&L statement and understand what the numbers mean
- Understand unit economics (even if they work in tech, not fintech)
- Can translate a business problem into a data question
- Know the difference between correlation and causation, and more importantly, know when their CEO doesn't
How do you build this? Read annual reports. Follow Indian startup metrics (check out Twitter threads from founders). Spend time in financial communities like r/IndianStreetBets or Zerodha's Varsity. Understand how SIPs work, how margin trading works, why Nifty moves when it does. This isn't about becoming a trader — it's about building intuition for how business works.
Communication (The Skill That Sounds Soft But Isn't)
I used to think communication meant writing well. I worked on my emails, made my writing crisp and professional.
That's not what they mean.
Communication in data analysis means: explaining a complex finding to someone who doesn't care about the methodology. It means knowing when to show a confidence interval and when to just say "we're pretty sure." It means presenting data in a way that changes behavior.
Last month, I had to present why our recommendation algorithm was biased toward certain fund categories. The numbers were clear — there was a 23% skew. But how do you make that matter to someone who just wants the daily dashboard to work?
I didn't lead with statistics. I led with: "We're recommending 23% more equity funds to women investors even when their risk profile doesn't support it. That could be a compliance issue."
Suddenly, it mattered.
This is the skill that separates good analysts from ones who are constantly frustrated that "nobody listens to data." They listen if you speak their language.
Skepticism (Not Cynicism)
This one I got from my Economics professor, actually. She used to say: "An economist's job isn't to find the answer. It's to find the right question and then be relentlessly skeptical of the first answer you find."
I used to think skepticism was about being difficult — questioning everything, playing devil's advocate, being annoying in meetings.
Real skepticism is humility. It's asking: "What could I be missing? What assumption am I making that might be wrong? Is this correlation actually correlation, or am I seeing a pattern that isn't there?"
In 2025, this is valuable because there's a lot of data now. Too much data, actually. The skill isn't finding insights — it's questioning whether the insights are real or if they're just statistical noise.
| Skill | What I Thought It Meant (Wrong) | What It Actually Means (2025) |
|---|---|---|
| SQL | Writing complex, optimized queries | Writing clear, maintainable queries that answer business questions |
| Python | Building machine learning models | Automating data pipelines and cleaning messy data |
| Dashboarding | Making beautiful, interactive visualizations | Creating tools that drive decisions and are actually used |
| Communication | Writing well and presenting professionally | Translating data into language that changes behavior |
| Business Sense | Not important; technical skills matter more | The most important — knowing which questions to ask |
What Your Portfolio Should Actually Show
Here's the uncomfortable truth: most data analyst portfolios are showcasing the wrong things.
Everyone has a project where they cleaned a public dataset (Titanic, Iris, whatever) and built a model. Everyone has a GitHub repo with beautiful notebooks. And hiring managers have seen all of them.
What they haven't seen enough of is: real problems. Messy data. Incomplete solutions. Honest write-ups about what didn't work.
If you're building a portfolio right now, here's what actually matters:
One project where something went wrong: Build something, find an issue with your approach, fix it, and document what you learned. This shows way more than a perfect project. Why? Because in the real world, things go wrong. How you handle it matters.
One project with actual data (if possible): Can you use public APIs to pull data? Scrape a website responsibly? Use your own financial data from CRED or PhonePe? Real data is messier and more interesting than cleaned datasets. Show that you can handle it.
One project where you explain why you didn't use advanced techniques: This sounds weird, but it's powerful. Document a case where you could have used machine learning but simple aggregation was better. Or where you could have built a dashboard but a CSV export made more sense. This shows you think about tradeoffs.
One project with terrible visualization, then a good one: Show your growth. Here's my first dashboard—it was awful. Here's what I learned. Here's the second version. Hiring managers love this because it shows self-awareness.
The portfolio should tell a story: you're not just technically skilled, you're thoughtful about problems. You ask questions. You consider your audience. You've made mistakes and learned from them.
The Skills That Will Matter More in 2025 Than They Do Today
Data Literacy (Not Data Science): The ability to read a dataset, spot anomalies, and ask questions. This is getting more valuable as more people work with data. The analysts who can teach others to think about data critically will be valued.
Working With Unstructured Data: JSON, text, images, logs. Traditional analysts learned SQL on clean, structured databases. In 2025, your data lives in Slack conversations, user feedback, raw logs, and API responses. Comfort with mess is a superpower.
Version Control (Git): I resisted learning Git for two years. "I'm not a developer," I'd say. Now every analyst I know uses it. Version control isn't just for engineers anymore — it's how you document your work and collaborate.
Privacy and Ethics: GDPR, data consent, algorithmic bias. These aren't side topics anymore. If you're analyzing user data, you need to understand the ethical implications. Companies are starting to care about this. A lot.
Domain Expertise: Being an analyst in fintech is completely different from being one in e-commerce or healthcare. In 2025, analysts who understand their specific domain — who read quarterly results, who understand unit economics, who know what their competitors are doing — will outpace generalists.
My Perspective
I used to think my Economics degree mattered because I understood regression analysis. I was half-right. What actually mattered was that I had a framework for thinking about systems — how incentives work, why correlations can be misleading, how to model human behavior.
My professor used to say in lectures: "The numbers don't lie, but they rarely tell the whole truth." I hated this as a student. It felt like a cop-out. Now I get it.
What surprised me most about my first three years as a data analyst wasn't the technical stuff — I picked that up. What surprised me was how often the "right" answer was the boring one. How often the finding was "we don't have enough data to be sure." How often the most valuable thing I could do was ask someone: "Are you sure that's what you're actually trying to measure?"
If I were starting over right now, I'd spend less time on Kaggle competitions and more time on understanding business. Less time perfecting visualizations and more time explaining findings clearly. I was optimizing for looking like a data analyst instead of being one.
Final Thoughts
I'm still figuring this out. Honestly. Every quarter, something changes — a new tool gets hyped, a different skill suddenly matters, someone in the industry writes a Twitter thread about what's broken with how we hire analysts, and I think: "Am I teaching people the wrong things?"
But here's what I know for sure: the analysts who get hired and stay relevant are the ones who are curious about business, skeptical of their own conclusions, and clear about what they've found. The technical skills get outdated. The way you think about problems doesn't.
If you're 22 to 35, living in India, trying to break into data analytics: you don't need to be perfect at SQL or Python or Tableau. You need to be good at asking questions and having the tools to find answers. Start there.
And if you're commuting daily like I am, reading this on the local train from Kalyan — remember that what you're learning today might be wrong tomorrow. That's not a reason to stop learning. It's a reason to stay curious.
The job market is opening up for good analysts. But "good" doesn't mean technically perfect. It means thoughtful. And that's something you can get right, starting today.
Dattatray Dagale
Data Analyst • Blogger • Mumbai
I'm a data analyst from Kalyan, Maharashtra, working at Morningstar. I write about personal finance, career growth, and everyday life for Indian millennials — the stuff I wish someone had told me earlier.
Written by Dattatray Dagale • 02 August 2026
.gif)
.png)
.png)
0 Comments