How I Became a Content Writer at Groveus

How I Accidentally Became a Content Writer (And Why I Don't Regret It)

Funny thing about career paths; nobody actually plans them the way they turn out. Mine definitely didn't go how I expected, and if you had told me during my college days that I would end up writing website content for a living, I probably would've laughed, said "that's not a real job," and gone straight back to debugging whichever code broke that day.

I'm Anil, and I write content at Groveus. But "content writer" wasn't ever the plan. It just; happened. And honestly, it's one of those things that makes more sense looking backward than it ever did looking forward.

The Coding Chapter That Didn't Quite Click

I did my BSc. in Computer Science, which if you've been anywhere near that degree means a lot of late nights arguing with compilers, googling error messages that make no sense, and nodding along in recursion lectures while quietly wondering if the function is calling itself or if I am losing my mind. The whole point of the degree is the logic underneath everything: how an app actually runs, what's happening behind a website when you click a button, that kind of thing.

Here's the honest part, though: I never quite found my rhythm with it. Not because I couldn't do it - I could, and I did, but something about sitting deep in code just never clicked the way it seemed to for other people around me, the ones who looked genuinely happy at 2 AM fixing a null pointer exception. I could follow the logic. I just didn't love living inside it all day.

What I did like was solving problems. Turns out that's a bigger category than "writing code," and I didn't realize that yet.

Around second year, I came across UI/UX designing, and something shifted. This felt different - less about making a machine execute instructions correctly, more about making something actually make sense to a human being looking at it. Where should this button go? Why is this flow confusing? What happens if someone's in a hurry and just wants to find the price.

I got properly into it. Spent the rest of my remaining college time leaning into that side of things instead of development. It gave me the sense of satisfaction that I used to look for while solving problems through coding, minus the part where I felt like I was fighting the tool the whole time.

What I didn't realise at the time was that every website interface I designed had another important part that I had barely thought about; the actual words and content on the page. . I was putting content on websites the entire time without realizing that "putting words on a website" and "writing content that works" are two completely different skills. I thought I was just filling in blanks. Turns out I was doing a rough, unpolished version of a job that people actually specialize in.

I had no idea that was even a real skill until Groveus happened.

Where It Actually Clicked: Groveus

Joining Groveus is where the picture is filled in. I walked in not really knowing what content writing even meant as a discipline. I figured it was just "write some sentences, put them where the design team says." Honestly, it seemed reasonable to me. Turns out, I was wrong.

What I actually learned is that content isn't decoration sitting on top of a website, it's doing real work. The words on a page decide whether the page even shows up when someone searches for it. That's the SEO piece nobody tells you about until you're the one writing a city-specific service page for the fifteenth time and realizing every sentence is quietly pulling weight for readers, but also for search engines deciding whether your page deserves to exist on page one.

Writing "plumbing services in [city]" content sounds simple until you're actually doing it. You've got to say something real, sound like an actual business and not a template, work in the right phrases naturally, and somehow not repeat yourself across fifty city pages that are all, structurally, the same page. That's a specific kind of puzzle. Turns out I liked this puzzle. It was kicky too, same problem-solving brain from the coding days and the design days, just aimed at a completely different target.

The Rollercoaster Ride

I won't pretend this has been some smooth, straight-line glow-up story, because it hasn't. It genuinely felt like a rollercoaster - the good kind, mostly, but occasionally the kind where you question your life choices, and spend the whole day wondering whether you are even on the right path or not. Going from "I don't know what content writing even is" to actually understanding how a single paragraph can move a page up in rankings, or how tone changes depending on who's reading; that took time, several rewrites, and a fair number of drafts.

Turns Out Every Draft Teaches Me Something

Content writing taught me way more than I expected. Not just about writing. City pages, for instance; describing the same service across different cities without just swapping the name and calling it a new page. Rough lesson at first, not gonna lie.

Digging into topics I barely knew anything about made me a faster learner, fast. And editing my own drafts taught me something I didn't expect: not every sentence deserves to stay, we have to polish content as much as we can to keep it crisp and relevant. SEO added structure, keywords, actually understanding what people type into Google before they land on a page.

Somewhere between researching, writing, rewriting and wondering, it hit me. I wasn't just getting better at writing. I was getting better at researching, thinking, brainstorming through ideas, solving problems which was the whole package.