Kavitha Raja

Performing research and writing technical, information-driven material and documentation. Conducting review of the publication copy to ensure conformity with established rules. Systematizing the documents in line with the set standards pertaining to order, clarity, conciseness, style, and terminology. Gathering and evaluating the information about products from subject matter experts and observations. Used JIRA to track issues and project management.

Ensuring the delivery of high-quality documentation via paying attention to detail and meeting the requirements of end users. Studying product samples, specifications, illustrations, and working closely with product designers and developers. Creating apposite documentation for the products, transforming complex technical information in an easy, clear and concise manner which the target audience can comprehend. Used Arena PLM/QMS software to track the entire product record and bill of materials (BOM).

Developing accurate and reliable end-user documents and technical manuals. Writing easy-to-understand user interface text, online help, and developer guides. Gathering review comments from the engineers and customers, and revising the documents accordingly. Using drawings, diagrams, animation, and charts to illustrate key points in the documents. Used FrameMaker to create the Software User Manual in different languages, and SnagIT to capture the process and to create visual instructions.

Gathering and organizing end-user content requirements and technical manuals. Collaborating with various project teams to write project-specific documentation and content. Using flow charts, graphs, photographs, videos, and animations to enhance user’s understanding. Revising the documents based on the feedback from the internal teams and customer. Used PMS, named Whizible, to track the project life cycle such as work-breakdown structure (WBS), tracking bugs, timesheet, helpdesk, and dashboard.

Creating user documentation for a variety of content and maintaining the information architecture. Developing and rewriting the content provided ensuring technical verbiage is easy to understand by the layman. Proofreading, reviewing, and editing content for accurate use of grammar. Using tables, charts, graphs, and pictures for a clear understanding by the audience. Collating the feedback from the customers and incorporating the changes in the documents.

Mathematics

Physics, Mathematics, Electronics