You know, if someone had told me a few years back that I'd become a technical writer, I probably would've laughed it off. I mean, I was an engineer—wiring circuits, testing components, doing all the hardcore tech stuff. Writing? That was just a hobby, something I did for fun, never thought it could be part of my job. But life had other plans (thankfully!).
It wasn't always smooth sailing. Actually, it was more like driving on a bumpy road with potholes you can't dodge.
I graduated in 2019 with a degree in Electronics Engineering and landed my first job as a technician. Eventually, I worked my way up to an engineer's role. And while I was proud of what I was doing, a little voice inside me kept whispering, "This isn't it. This isn't where you belong."
And then, as if by magic, I stumbled upon a page about technical writing. My mind was blown. Wait… you can actually combine tech and writing? Why didn't anyone tell me this before?
I dove into research mode (because, engineer habits die hard), and the more I read, the more it made sense. I was already doing the technical part—documenting processes, creating test procedures, writing reports. Why not do it the right way? I started practicing by writing product documentation, editing user manuals, and soon after, earned my technical writing certification. That was it. I was hooked.
Truth is, deep down I always knew I wouldn't stay an engineer forever. I loved writing. And now? Now I know for sure—writing is where I belong.
Of course, the decision to quit my engineering job was terrifying. I knew the risks—I had bills, responsibilities, and no guarantee this writing thing would work.
But sometimes, you've got to take the leap.
I started freelancing, picking up small writing gigs. Guess what? It worked. And from there, I moved to contract roles, bigger projects, and more freelance work. Every time I finish an article, a manual, or a proposal, it feels like a piece of me heals. That's the magic of writing—it keeps you grounded and alive.
At first, I was scared. How would I write for industries I barely knew—software, IT, finance? But you know what?
Once I understood the basics of the product, the words just flowed.
I realized, I was more capable than I ever gave myself credit for. And that realization? Game changer.
Technical writing isn’t just about manuals. It’s SOPs, release notes, proposals, user guides—you name it.
To write them well, you need to keep learning. I made learning my mantra. There’s always something new—a tool, a format, a style.
I once heard, “If you think you’re the smartest person in the room, you’re probably in the wrong room.”
That stuck with me. Always be open to learning, stay curious, and stay humble.
People think writing is easy. You just sit and type, right?
Wrong. Writing—especially technical writing—needs focus, creativity, and a clear mind. Some days, I stare at the screen, and nothing comes out.
And that’s okay. Writing is a process. It needs time, space, and the right environment. Be kind to yourself on those off days.
Technical writing isn’t just about writing—it’s about understanding your audience, simplifying the complex, and ensuring clarity.
Research, communication, editing, critical thinking—these are your tools. And the more you use them, the sharper they get.
Whatever you write is a mirror of you as a writer. Your voice, your style, your values—they all shine through your words.
I always make sure my writing is not just easy to read, but also valuable and authentic. Play with words, but always respect the reader’s time and intelligence.