Technical Publication Engineer

Role & responsibilities

• Generate and export source files for multiple publication output types from online repositories (source files in md, xml, json, htm, indd, ai, psd, pdf, and Office formats).
• Configure and execute publish transform to build formatted outputs in various target types (online help, CHM, PDF, Word, zip).
• Evaluate source files, fix errors, extract non-editable texts, and prepare files for translation.
• Create translation projects in TMS platforms.
• Develop translated assets in Aegisub, Photoshop, Illustrator, InDesign, and Office apps using provided text translations and input files. Includes capturing localized screens from localized application GUIs.
• Validate syntax and fix errors in localized markup, markdown, and JSON files.
• Create local-language packages, import to publishing tools, and prepare local-language publishing environments.
• Configure and execute publish transforms to build formatted outputs in all languages. Includes debugging and fixing errors/warnings.
• Perform side-by-side QA of source-language and local-language output to identify errors, capture defects in bug tracking systems, implement fixes in single-source assets, and republish.
• Implement edits and corrections requested by documentation owners.
• Work is performed in online and local applications. Interaction with colleagues and client contacts occurs in multiple channels and within both your Welocalize domain and a client-contractor domain. Responsiveness and collaboration are key success factors in delivering services in this role.

Preferred candidate profile

• Documentation development in markup and markdown single-source environments.
• Setup, configure, execute of transformation engines to generate formatted output (OLH, CHM, PDF, etc.) from markup/markdown source.
• Cloud documentation management platforms with workflow automation.
• Quality assurance testing both format/layout and functional, of online and offline UA content.
• Managing single-source and output versioning in a multi-author environment.
• Managing change-orders in source files based on feedback provided against output files.
• Debugging and troubleshooting scripts used for publishing automation, in response to log errors or build failures.
• Continuous improvement mindset, always finding ways to deliver more efficiently and with less risk for errors.

REQUIREMENTS

• Bachelors degree with an engineering background.
• 1-2 years of experience in Technical Publication or a related field.
• Knowledge of installation and configuration management for the most common operating systems and platforms.
• Knowledge on encoding and fonts.
• ENG tools (EmEditor, Word, BeyondCompare etc.)
• Image tools (Photoshop, Illustrator etc.)
• Screen capture tools (SnagIT etc.)
• Github tools (Github Desktop)
• HTML Help Workshop
• Aegisub