Role Brief

Technical Writer
Adobe | Digital Enablement & Care | Contract

Note to Vendor / Agency
This role is specifically scoped to technical and product documentation — NOT content marketing, blog writing, social media, or brand copy. Candidates whose experience is primarily in those areas may not meet the requirements for this position, regardless of title. We encourage the agency to prioritize resumes that show clear software documentation experience. Please also note: this is an open-band role. We welcome resumes across mid to senior levels of technical writing experience.

A B O U T T H E R O L E

We are looking for a Technical Writer to join our documentation team and help users understand Adobe's software products. You will translate complex product functionality into clear, accurate, and well-structured content — working directly with product, engineering, QA, and marketing teams across release cycles. The ideal candidate has experience writing end-user and admin documentation for software products, is comfortable working within an editorial system, and can independently manage content from planning through publication.

W H A T Y O U ' L L D O

• Understand releases end-to-end. Read and interpret product requirements, Figma designs, engineering specs, marketing collateral, and release notes to plan and write documentation.
• Plan before you write. Create content plans and gather requirements from cross-functional stakeholders — product managers, engineers, QA, and marketing.
• Write for real people. Write clear, accurate documentation for end users and administrators — including help articles, feature guides, onboarding content, and release notes.
• Get hands-on with the product. Install and test product builds across desktop and mobile environments to verify accuracy of documented workflows.
• Work with AI, not around it. Use AI writing tools to improve efficiency and content quality, while maintaining editorial standards.
• Write in Adobe's voice. Learn and apply Adobe's style guide, voice and tone principles, and editorial rules consistently across all content.
• Own the review process. Manage review cycles — send drafts, incorporate feedback from multiple stakeholders, track approvals, and resolve conflicting inputs professionally.
• Think in systems, not just articles. Design content architecture — decide how topics are structured, grouped, and linked within a help environment.
• Write for the world. Write with localization in mind — clean, translation-ready sentences for a global user base.
• Measure your impact. Track content performance using documentation analytics — page views, search deflection, low-rated articles, and search-with-no-results data — to identify gaps and improve content.

W H A T Y O U B R I N G

• Proven experience writing end-user or admin documentation for software products — not general web content or marketing copy.
• Ability to read and work from product requirements, UI specifications, Figma designs, and technical collateral.
• Understanding of the software development lifecycle — sprint cycles, code freeze, release candidates, GA milestones, and how documentation fits within them.
• Experience working within a style guide and editorial framework at a previous employer.
• Comfortable receiving and resolving feedback from multiple stakeholders with differing perspectives.
• Able to manage multiple concurrent content workstreams at different stages without losing track.
• Familiarity with documentation analytics and an understanding of how to use data to prioritize content improvements.
• Self-sufficient in a remote, cross-geographical environment — knows when to ask questions and when to move forward independently.
• Experience writing for localized or global products is a plus.

H O W Y O U W O R K

• Articulate communicator — can present decisions, push back on vague feedback, and hold their own with PMs and engineers.
• Global collaboration mindset — async-first, timezone-aware, leaves clear written trails so nothing gets lost across geographies.
• Curious and quick to learn — asks "why does this work this way" before writing, not after.
• Sharp attention to detail — catches UI label mismatches, version inconsistencies, and broken steps before they reach users.
• Deadline-driven — release trains don't wait. Self-prioritizes under pressure without needing to be managed.
• Comfortable with ambiguity — starts with what's available, flags gaps early, iterates as clarity arrives.
• Proactive, not reactive — identifies content needs, flags risks, and follows up without being chased.
• Open to feedback — takes editorial critique professionally, not personally.

T O O L S — G O O D T O H A V E

We don't require expertise in any specific tool. Familiarity with any of the following is a plus:

• Oxygen XML / DITA authoring tools
• Markdown / docs-as-code workflows
• Adobe Experience Manager (AEM)
• Confluence / SharePoint
• Jira / Workfront
• Figma (reading, not designing)
• AI writing tools
• Git / version control basics

K E Y W O R D S F O R R E S U M E S C R E E N I N G

When reviewing resumes, look for signals of genuine technical writing experience. Strong candidates will show keywords and experience such as:

• Technical writer / technical documentation / software documentation
• End-user documentation / admin documentation / product documentation
• Help authoring / help center / knowledge base
• Style guide / voice and tone / editorial standards
• Content plan / content architecture / information architecture
• SDLC / sprint / release notes / GA / code freeze
• Stakeholder review / feedback management / SME review
• Docs-as-code / Markdown / XML / DITA / structured authoring
• Cross-functional collaboration (product, engineering, QA, marketing)
• Localization-ready / translation / global audience
• Content analytics / page views / search deflection / content performance
• AI writing tools / content workflow automation

Adobe | For vendor/agency use only | Not for public distribution