Position: Technical Writer
Company: Openware
Experience required: 2y
Category: Other
English level: fluent
Published: 2021-04-01T00:00:00+03:00

Required skills:
— 2+ years of experience as a technical writer 
— Experience in writing technical product documentation;
— Experience in writing User Guides;
— Experience in working with Confluence and Jira;
— Work experience within Agile and Waterfall methodologies;
— Advanced written and spoken English;
— Excellent cross-functional communication skills, requiring close interaction with Product Owners, UX/UI Designers, QA, Developers, and non-technical Stakeholders;
— Knowledge of IT industry, ability to quickly learn new domain terminology and concepts
— Ability to understand complex business and system requirements;
— Blockchain and trading knowledge would be a plus;
— Self-motivated and ability to work in a fast-paced environment.

RESPONSIBILITIES:

As a technical writer you will be preparing a set of documents for our internal use and for documentation portal
— Set up technical documentation for existing and developing products from scratch
— Communicate with development teams and stakeholders to identify information needs
— Keep track of ongoing products development and keep the documentation up-to-date
— Write API reference docs, architecture designs and diagrams etc.
— Address the gaps in cross-teams products knowledge
— Participate in requirements research and document new features and epics
— Quickly grasp complex technical concepts and make them easily understandable in text and pictures
— Document existing and new functionality by working with POs and Stakeholders throughout the development lifecycle, using development artifacts (User Stories, UML Use Cases and Activity Diagrams), and interviewing SMEs
— Create detailed user documentation for use within the application such as operating instructions and User Guides
— Ownership of product documentation, suggesting improvements and areas for expansion
— Gather feedback on deliverables as revise as new issues arise
— Review all customer-facing documentation to ensure it meets expected style and standards