Developer Writer

### The Role Developers increasingly rely on AI search, coding assistants, technical communities, and traditional search engines to find and evaluate solutions. For Apryse to earn their attention, our content must be technically accurate, easy to discover, and genuinely useful. As a Developer Writer, you will create the technical content that helps developers understand what they can build with Apryse and how to get started. You will write tutorials, how-to blogs, use-case content, code-led articles, and other documentation-adjacent resources designed to answer real developer questions. This is a hands-on individual contributor role for someone who can turn technical concepts and product capabilities into clear, practical content. You do not need to be a software engineer, but you must be comfortable reading code, working with technical subject-matter experts, and writing for an audience that values precision over marketing language. ### Responsibilities Create Technical Content Developers Can Use - Write how-to guides, technical articles, use-case content, and other documentation-adjacent resources. - Translate product capabilities and technical concepts into clear, practical content for developers and technical decision-makers. - Incorporate code samples, implementation steps, technical requirements, and relevant product details into marketing-owned content. - Create content that answers specific developer questions and helps readers evaluate, adopt, and successfully use Apryse products. - Refresh and improve existing content to strengthen its accuracy, clarity, usefulness, and discoverability. Support Developer Discoverability - Execute technical content priorities identified by the AEO Program Manager and Manager, Content. - Partner with the AEO Program Manager and SEO specialists to address gaps in AI-generated answers, coding assistants, search results, and other developer discovery channels. - Structure content so it can be easily understood by both developers and AI systems. - Apply content briefs, query research, competitive findings, and product positioning to each assignment. - Help ensure Apryse is accurately represented when developers research document-processing solutions. Collaborate Across Technical Teams - Work with Engineering, Product, Product Marketing, and Documentation to verify technical claims and product details. - Incorporate technical feedback quickly and accurately while maintaining a clear, consistent voice. - Coordinate with content owners and subject-matter experts to keep published content current as Apryse products evolve. Contribute to the Broader Content Program - Support additional Content team priorities, including ebooks, one-pagers, campaign content, sales enablement materials, and BDR programs. - Adapt technical subject matter for different audiences, channels, and stages of the buyer journey. - Contribute to a developer-focused brand voice that is credible, direct, useful, and free from unnecessary marketing language. ### Requirements - 2+ years of experience writing technical content for developers or another technical audience. - Experience creating tutorials, how-to articles, integration content, technical blogs, or documentation-adjacent resources. - Ability to read, understand, and clearly explain code samples. - Strong writing and editing skills, with an emphasis on accuracy, clarity, structure, and usability. - Ability to translate complex technical information into content that is approachable without oversimplifying it. - Comfort working across multiple programming languages and SDK environments. - Experience collaborating with engineers, product teams, documentation teams, or other technical subject-matter experts. - Strong attention to detail and the ability to incorporate technical feedback quickly. - Ability to manage multiple assignments and deliver high-quality work against agreed timelines. ### Skills & Mindset - You understand that developer trust is earned through accuracy and usefulness, not marketing claims. - You can tell when a technical explanation or code sample is incomplete, even if you are not writing production code yourself. - You are curious and comfortable asking detailed questions until you fully understand the subject. - You are an adaptable writer who can move between a technical tutorial, a use-case article, and a broader marketing deliverable. - You are comfortable receiving direct technical feedback and revising your work accordingly. - You are organized, self-directed, and able to turn a defined content brief into a polished deliverable. ### Nice to Haves - Experience writing for an SDK, API, developer-tools, infrastructure, or software company. - Experience with API or SDK documentation and developer tutorials. - Familiarity with document-processing technologies, including PDF SDKs, document conversion, data extraction, OCR, or digital signatures. - Familiarity with AEO, GEO, SEO, or writing content intended to perform in AI-generated answers. - Experience testing code samples or working with GitHub repositories. - Basic video editing or screen-recording skills for product and use-case walkthroughs. - Experience engaging with developers on 3rd party platforms including Reddit, HackerNoon, and Stack Overflow.