StoryTime| From Content Writer to Data Engineer: A Path I Never Planned

StoryTime| From Content Writer to Data Engineer: A Path I Never Planned

If you’d asked me in college what I’d become after graduation, I’d have probably said:
“Maybe a Python content writer… definitely not a developer.”

I wasn’t into competitive programming.
I was somewhere between a “basic coder” and a “kuch toh aata hai” coder.
But life — and career — had different plans for me.

It All Started with GeeksforGeeks

My journey began in 4th semester, thanks to one of my favorite professors who encouraged me to give content writing a shot.
And with a little help from a good friend, I submitted 2-3 Python-related articles to GeeksforGeeks as a sample.

✅ They liked it.
✅ I got the internship.
✅ And just like that, my journey started as a Python content writer.

I worked there till my final semester — and even got promoted to a content reviewer intern for 3-4 months.

My College Life Looked Like This:

  • Writing articles on Python Language during weekends and holidays
  • Working with 2-3 other content writing platforms
  • Doing a WordPress internship in 6th semester
  • Building a chatbot in my final year project (using Python, of course)

So naturally, I started imagining myself as a Python content writer post-college.

Developer? Nahi bhai. Not my thing.

From Writer to Engineer — Wait, What?

Then came September 2020 — the COVID batch era.
I joined an MNC as a Software Engineer. But honestly? I had no clue which domain I’d be placed into.

Turns out — it was Big Data.

A 5-week training was planned through WebEx…
but due to urgent project needs, I had to join after just 2 weeks.

And that too — the tech stack was:

  • Scala
  • Shell scripting
  • GCP etc.

I went from Python articles to staring at Scala code thinking —
“Yeh kaise ho gaya?”

Fast Forward 4 Years Later…

I’ve been working as a Big Data Developer for the last 4 years now.

In the beginning, I knew nothing — but I tried. I learned.
Every task I was assigned became a chance to grow.

And surprisingly — I’ve started enjoying this domain.

Today, I work on large-scale data systems, understand pipelines — and yes, I still use Python now and then… just in a very different way.

What This Journey Taught Me

You don’t need to have it all figured out. Your path might surprise you.

It’s okay to not be a coder-coder. You just need curiosity, consistency, and courage.

The first job doesn’t define you. But it can transform you.

So if you feel lost in your journey — or worried that you’re not a perfect fit for a role — remember,
I started by writing about Python Language. Now I’m Big Data Engineer.

And this… was just one story.

More stories soon. Until then — keep learning, keep pivoting, and never say “this isn’t for me” too early.

Thanks for reading! 🙂

 

Leave a Reply

Your email address will not be published. Required fields are marked *

? Need further clarification or have any questions? Let's connect!

Connect 1:1 With Me: Schedule Call


If you have any doubts or would like to discuss anything related to this blog, feel free to reach out to me. I'm here to help! You can schedule a call by clicking on the above given link.
I'm looking forward to hearing from you and assisting you with any inquiries you may have. Your understanding and engagement are important to me!

This will close in 20 seconds