Senior Technical Writer

Lets be clear right out of the gate:

We’re not looking for a “person who can type words into a page.” We’re looking for that rare unicorn of a technical writer who knows that documentation is as much a product as the product itself. Someone who sees the art in clarity, the science in structure, and the satisfaction in hitting “publish” on something so good people actually thank you for it.

blueBriX

What We’re Sick Of (and You Probably Are Too)

• API docs that look like someone dumped their brain into Notepad and called it a day.
• Release notes that ramble like a bad podcast.
• “We’ll update the docs later” as an acceptable sentence.
• Teams who think writing and documentation are interchangeable.

If you’ve just nodded so hard you almost sprained your neck, keep reading.

What You’ll Actually Be Doing

(And yes, this is the part where you either get excited or close the tab.)

• Wrangling chaos — turning messy product specs, half-baked Jira tickets, and “oh yeah, I forgot to mention” Slack messages into crisp, usable documentation.
• Building API docs so clear even junior devs can build without pinging you 20 times.
• Owning the content strategy — if it’s written, you either wrote it or made it better.
• Making sure our docs and our product are always in sync (no “we’ll fix it later” excuses).
• Partnering with Product, QA, and SMEs to actually understand the tech before you explain it.
• Gathering feedback from users and iterating until the docs work as hard as the code.

You’ll Know This Role Is For You If

• You’ve stared down an undocumented API and thought, Challenge accepted.
• You’ve cut a 10-page release note down to three pages and made it better in the process.
• You get genuinely irritated when terminology isn’t consistent across a platform.
• You’ve been the person who quietly fixed the developer-written “documentation” before it saw daylight.
• You’ve muttered “Not on my watch” at bad help text.

Stuff We’ll Brag About Offering

• An on-site role in Kochi, Kerala — because leaning over someone’s desk beats waiting three hours for a chat reply.
• A team that respects your craft and knows good documentation saves everyone’s sanity.
• A gym in the office — so you can work your brain and your biceps in the same building.
• Ownership, impact, and the chance to leave your fingerprints on something that matters.

Who Shouldn’t Apply

• People who think “technical writing” means copy-pasting from Jira.
• Folks who need to be reminded what they’re working on.
• Anyone who thinks “good enough” is a compliment.

Final Word:

blueBriX is ready for you. Are you ready for us?