These job descriptions are examples. Looking for work?

Find JobsFind Jobs

Technical Writer

0 people like this description

We are looking for some additional vendor resources that could help us with the development, writing and editing of technical engineering content for case studies and white papers. In EE we support the engineering workforce to bring them knowledge and information they can use to improve their performance. Our specific topic areas include services engineering and agile engineering practices.

• Publishing artifacts: Vendor will publish to the Engineering Repository an average of at least two “artifacts” per week. An ‘artifact’ is defined as a community sourced documented practice or process. Artifacts may be a part of the scenario-focused engineering collection, program management collection or emerging additional collections as these are defined. Topics shall include but not be limited to: project management, business development, design thinking, and program management capabilities. A starting contact within the teams as well as editorial guidance. “Publishing” includes completing all phases of the harvesting process: Locating, Intake, Interviews, Drafting, Iterating, Publishing and Promoting artifacts. Vendor will identify whether a given artifact or practice should be included in the repository, gather information on how it was developed, used, and valued as well as challenges overcome and recommended uses. Vendor will obtain and publish the actual artifacts, and then announce publication to relevant L&D teams. Summaries will adhere to content spec delivered. Vendor will deliver summaries to prior to publishing, with notification by email. Vendor will also forward the “okay to publish” permission from the artifact submitter. Assignments and priorities on artifacts (or teams to harvest artifacts from) will be decided on at least a monthly basis. For the PM collection: Vendor will participate in scrum meetings as necessary to plan and track artifact development priorities and status. Vendor will deliver assignments as each is completed. Completion status reports will be sent and reviewed on a weekly basis and completion rate monthly.

• Maintaining backlog: Vendor will keep current a running, prioritized backlog of all EE repository artifacts in all states of publishing. Backlog will be stored in a central location accessible to all team members. Vendor will modify backlog structure as needed to support additional repository efforts or updates to the overall repository publishing system. Vendor will solicit monthly feedback on backlog contents from repository and collection owners.
• Coaching other artifact publishers: As the repository effort expands, more knowledge engineers (KE) will be publishing their own artifacts. Vendor will assist with onboarding efforts by: walking new KEs through the publishing process, responding to support requests on the publishing process, reviewing newly published artifacts for presentation and content consistency, and providing feedback to KEs on same. Vendor may also directly edit and clean up other artifacts as necessary to improve readability and keep a consistent look and feel across repositories.

• Influencing repository documentation: Vendor will function as a subject matter expert in reviewing and providing content input to the repository playbook authored.

Vendor will assist in informing the KE community on the contents of the repository by:
• Recommending artifacts: Vendor will respond to KE requests for artifact recommendations on specific topics for specific projects. These projects may include (but are not limited to) learning paths, meetup events, and course development or cross-publishing to other repository efforts.

• Leading a “What’s fresh” meeting series: Vendor will schedule and host a biweekly meeting to present latest published artifacts to other KE publishers and repository vendors.

These job descriptions are examples. Looking for work?

Find JobsFind Jobs