My First Blog as a Data Scientist: Why Starting with Purpose Matters
Everyone starts somewhere, but the problem is—we often want it to look perfect from day one. When I began my journey into data science, I wasn't overwhelmed by algorithms or tools. I was overwhelmed by the idea that I needed to know everything before I could say, “I belong here.” But over time, I learned something crucial: curiosity is more powerful than perfection.
This blog isn't a tutorial or a success story. It's a reflection. As someone fresh in the field, this is my space to unpack what it's like stepping into a domain filled with buzzwords but grounded in real-world problems.
The "Why" Behind My Journey
Data Science isn't just about models or dashboards—it's about asking the right questions. That realization came to me when I started analyzing how businesses make decisions. The real trigger wasn’t a flashy AI project; it was a simple sales data sheet I saw during an internship. It had stories hidden inside it—unspoken problems, missed patterns, ignored potential. That was the hook.
Coming from a background in Computer Science with an interest in business operations, data science felt like the bridge where logic meets value. It gave structure to my thinking and direction to my curiosity.
Skill vs. Domain: An Ongoing Misunderstanding
Let’s address the elephant in the room: domain knowledge. I’ve personally experienced rejections just because I didn’t “belong to the domain.” Even when I proved my adaptability and shared how quickly I pick things up, the response was the same: “Sorry, you don’t have BFSI/Healthcare/E-commerce experience.”
Here’s my honest take: domain knowledge is useful—but not foundational. What’s foundational is your ability to understand business needs, think critically, translate requirements into solutions, and keep communication flowing across teams.
Domain is a canvas. Skills are your brush. And if a Business Analyst or Data Scientist can’t articulate client needs, that’s a valid reason to question their fit. But rejecting someone solely due to unfamiliarity with a specific industry? That’s short-sighted.
The best professionals I’ve met say: “Hire for skill. Train for domain.” That mindset builds long-term teams.
Working Across Teams: A Data Scientist is Never Alone
One of the biggest misconceptions is that data scientists only work with code and reports. In reality, you’re the one connecting the dots between multiple departments.
I’ve seen how a data-driven mindset helps:
-
Sales teams understand why conversions drop
-
Marketing teams fine-tune targeting strategies
-
Web teams improve funnel performance
-
Product teams measure feature impact
-
Customer support teams understand sentiment
-
Finance teams forecast better
-
Operations teams reduce waste and improve efficiency
Being a data scientist doesn’t mean sitting quietly behind Jupyter notebooks. It means being curious enough to ask why things work the way they do—and bold enough to suggest how they can work better.
That’s where the magic happens—not just in code, but in collaboration.
What I’ve Learned So Far (And Still Learning)
My journey so far has taught me some things that are worth sharing, especially if you're just getting started:
-
Focus on problem-solving, not just tools
-
You don’t need a PhD to ask intelligent questions
-
Document your thought process—future-you will thank you
-
Learn by building, not just watching tutorials
-
Communication will take you further than any library
-
The best answers often come after the dumbest questions
And perhaps most importantly: Consistency is underrated. You don’t have to be a genius every day. But if you show up, learn, reflect, and apply—growth becomes inevitable.
The Reason This Blog Exists
I didn’t write this to showcase knowledge. I wrote it to remind myself—and others—that the first step always feels awkward. Your code will break. Your dashboard will crash. Your model accuracy will suck. But that doesn’t make you any less of a Data Scientist. It makes you a real one.
I’m Rahul Sihag, and this is my first blog as a Data Scientist—not because I’ve “arrived,” but because I’ve started. And that matters more.
