A Bachelor's degree in a technical field or technical communication.
• 5+ years experience.
• A thorough understanding of the publishing process and the ability to work with raw engineering data and develop it into end-user documentation.
• Experience using Style Guides such as Chicago Manual of Style and the Microsoft Manual of Style.
• Excellent project management, organizational and planning skills.
• Ability to handle multiple projects and meet scheduled deadlines.
• Excellent ability to work either in a team environment or individually when required.
• Excellent working knowledge of desktop publishing tools such as FrameMaker, and/or on-line help systems such as Robohelp.
• Excellent communication skills.
• Excellent problem-solving skills.
• Preferable experience: Engineering or software work experience.
• Preferable characteristics: A “can do” attitude with a strong desire to get the job done well.
• Produce high quality end-user documentation and procedures for a technical audience. Work on all phases of information development from information gathering, research, and interviewing, to writing and editing.
• Produce graphics and illustrations using Visio, such as timing diagrams, block diagrams and flow charts.
• Produce paper and electronic versions of documentation using Adobe FrameMaker, and Adobe Acrobat. Deliverables may also include on-line help, user manuals and API reference guides.
• Be able to manage competing deadlines, work with the program team to meet customer and business objectives, and ensure that the documents are delivered on time, and are complete and accurate.
• Be flexible and be able to adapt to changing requirements.
• Be able to work with remote teams across several time zones such as with participating in conference calls at various times of the day.
• Attend program management status meetings in order to do such things as
• keep tabs on product development and respond to sales/engineering/test requests for documentation deliveries
• maintain high visibility of the documentation efforts.
• Be proactive in resolving bottlenecks that affect the release of documents or other objectives.
• Be responsive in communicating project status and timelines.
• Use appropriate communication vehicles to get the desired results and facilitate work on the team. For example, use direct face-to-face communication, conference calls, instant messaging, and video conferencing where it is found to be effective over email.
• Anticipate issues and be proactive and willing to educate yourself on the product to gain a deeper understanding of the information discussed among the test engineers, design engineers and the team as a whole. Be willing to ask dumb questions in the interest of learning what is relevant and going beyond simply processing content that is “delivered” to you.
• Support Design Engineers documentation efforts by training them on software tools, such as FrameMaker and Visio to improve efficiency in raw data transfer between the designer and writer.
• Demonstrate initiative to learn new technology/software.
• Apply standard practices and also work with management to find solutions in these areas where improvements are needed.
• Work through established channels to get buy-in when implementing change, while maintaining an awareness of industry practices and standards.
• Take initiative to solve problems all around that move Marvell forward, demonstrating your leadership on the program team as well as on the writing team, in such areas as:
• Introducing new tools/processes
• Mentoring other writers
• Focusing on solutions
Engineering - General