Technical Writer

About the Role

We have three published user guides covering our Finance, HR and Summary Page products. Keeping those accurate as the product changes is the steady part of the job. On top of that, we ship new products and modules that need guides written from scratch, and we need someone owning the words inside the product itself.

This is a judgement role. We need someone who decides what things are called, catches what is wrong before a customer does, and takes responsibility for what we publish.

What they will do

Documentation

- Keep the three existing guides accurate and current with each release, and write the release notes.
- Write new user guides from scratch when we launch a new product or module.
- Build out the sections we are missing: troubleshooting, error references, and walkthroughs of real workflows.
- Keep screenshots current with the interface and correctly placed.
- Sign off that published documentation is factually accurate. We operate under SOC 2 and HIPAA, so this matters.

​​Product copy

- Write and review interface copy: labels, buttons, empty states, error messages, tooltips, onboarding and notifications.
- Copy testing. Walk recent screens before release and flag copy that is unclear, inconsistent, or untrue for the state it appears in.
- Decide naming and terminology when product introduces something new,



and make sure the same term is used in the interface, the guides and the API.
- Own the style guide and terminology glossary. Keep them current and enforce them.

Understanding the product

- Use the product properly and regularly. You cannot document or name what you have not used.
- Learn the finance and HR domain well enough to tell when a description is wrong, not just badly worded.

Required Skills

- Several years writing end-user documentation for enterprise or B2B software.
- UX writing or content design experience. This is not a documentation-only role.
- US English, and a working sense of what reads naturally to a US audience.
- Comfortable in Markdown and Git, reviewing changes in pull requests rather than in Word.
- Experience owning a style guide and a terminology glossary, not just following one.
- Precise. A large part of this job is catching the error before the customer does.

How we will assess A short paid exercise in two parts. First, a set of release changes plus the existing guide section they affect, and our style guide, and we ask for the updated section and the release notes. Second, screenshots of two new screens, and we ask for the interface copy and anything you would question. We are looking at accuracy, consistency with the style guide, and what you choose to challenge.

📌 Technical Writer (Pune)
🏢 Hobasa
📍 Pune