Hi Connections
Teamware is hiring for Technical Writer role
Experience:10+years
Location: Noida
Interview:Face to Face interview
NP:Immediate
JD
- Understand releases end-to-end. Read and interpret product requirements, Figma designs, engineering specs, marketing collateral, and release notes to plan and write documentation.
- Plan before you write. Create content plans and gather requirements from cross-functional stakeholders — product managers, engineers, QA, and marketing.
- Write for real people. Write transparent, accurate documentation for end users and administrators — including help articles, feature guides, onboarding content, and release notes.
- Get hands-on with the product. Install and test product builds across desktop and mobile environments to verify accuracy of documented workflows.
- Work with AI, not around it. Use AI writing tools to improve efficiency and content quality, while maintaining editorial standards.
- Write in voice. Learn and apply style guide, voice and tone principles, and editorial rules consistently across all content.
- Own the review process. Manage review cycles — send drafts, incorporate feedback from multiple stakeholders, track approvals, and resolve conflicting inputs professionally.
- Think in systems, not just articles. Design content architecture — decide how topics are structured, grouped, and linked within a help environment.
- Write for the world. Write with localization in mind — clean, translation-ready sentences for a global user base.
- Measure your impact. Track content performance using documentation analytics — page views, search deflection, low-rated articles, and search-with-no-results data — to identify gaps and improve content.
WHAT YOU BRING
- Proven experience writing end-user or admin documentation for software products — not general web content or marketing copy.
- Ability to read and work from product requirements, UI specifications, Figma designs, and technical collateral.
- Understanding of the software development lifecycle — sprint cycles, code freeze, release candidates, GA milestones, and how documentation fits within them.
- Experience working within a style guide and editorial framework at a previous employer.
- Comfortable receiving and resolving feedback from multiple stakeholders with differing perspectives.
- Able to manage multiple concurrent content workstreams at different stages without losing track.
- Familiarity with documentation analytics and an understanding of how to use data to prioritize content improvements.
- Self-sufficient in a remote, cross-geographical environment — knows when to ask questions and when to move forward independently.
- Experience writing for localized or global products is a plus.
HOW YOU WORK
- Articulate communicator — can present decisions, push back on vague feedback, and hold their own with PMs and engineers.
- Global collaboration mindset — async-first, timezone-aware, leaves clear written trails so nothing gets lost across geographies.
- Curious and quick to learn — asks "why does this work this way" before writing, not after.
- Sharp attention to detail — catches UI label mismatches, version inconsistencies, and broken steps before they reach users.
- Deadline-driven — release trains don't wait. Self-prioritizes under pressure without needing to be managed.
- Comfortable with ambiguity — starts with what's available, flags gaps early, iterates as clarity arrives.
- Proactive, not reactive — identifies content needs, flags risks, and follows up without being chased.
- Open to feedback — takes editorial critique professionally, not personally.
TOOLS — GOOD TO HAVE We don't require expertise in any specific tool. Familiarity with any of the following is a plus:
Oxygen XML / DITA authoring tools
Markdown / docs-as-code workflows
Adobe Experience Manager (AEM)
Confluence / SharePoint
Jira / Workfront
Figma (reading, not designing)
AI writing tools
- Git / version control basics
If interested do share cv to
[email protected]
📌 Technical Writer (Noida)
🏢 Teamware Solutions
📍 Noida