Senior Information Developer
PowerPlan, Inc
- Atlanta, United States
- Senior Level
- 5+ years
- Bachelor's degree
- Posted
Skills
Required
- docs-as-code workflows
- Markdown
- Git branching
- pull requests
- code editor
- Code
- automated publishing pipelines
- Agile
- utilities
- fixed assets
- system and network architecture
- gas
Preferred
- component content management systems
- CCMS
- content authoring tools
- MadCap
- Flare
- Zendesk
- docs-as-code
- API documentation
- OpenAPI
- AI
The Information Developer II (Technical Writer) will design, develop, and deliver clear, concise, and effective documentation for PowerPlan’s suite of software solutions.
Responsibilities
- Documentation is currently authored in a component content management system (CCMS), MadCap Flare, and published through Zendesk, and the team is transitioning to a docs-as-code, AI-first approach in 2027.
- This individual will deliver documentation in the current CCMS and Zendesk environment while helping the team adopt Markdown, Git-based workflows, and AI-assisted authoring.
- They will support product launches and empower internal teams, external users, and the AI assistants they increasingly rely on by creating high-quality, accessible, structured content.
- Success in this role is measured by the impact documentation has on product understanding, user satisfaction, and the accuracy of the answers people and AI tools get from it.
- Research, write, and publish end-user and technical documentation for all new product releases.
- Author content in the current CCMS (MadCap Flare) and publish it to Zendesk.
- As the transition to docs-as-code progresses in 2027, author in Markdown managed in Git with pull-request review and automated builds.
- Collaborate with Product Management, UX, Training, Engineering, and QA teams to gather technical information and user stories.
- Use approved AI tools to speed up research, drafting, and editing while remaining accountable for accuracy.
- Conduct quarterly reviews of all published documentation, in the current CCMS and Zendesk and later in the new platform, for accuracy, completeness, and usability.
- Support these reviews with automated checks (style, links, and content freshness) and with usage data, search terms, support cases, and AI-assistant feedback.
- Host monthly stakeholder meetings to discuss documentation needs for assigned products.
- Contribute to the 2027 Transition from CCMS to Docs-as-Code and AI-First Documentation: Help move documentation from the current CCMS (MadCap Flare) to Markdown-based, Git-managed sources in 2027, with both environments running side by side until cutover.
- Plan and validate how content will be published to Zendesk from the new pipeline.
- Convert, clean up, and validate content, using scripts and AI-assisted conversion where appropriate, and preserve content reuse, conditional content, and metadata.
- Contribute to templates, style guidance, build and publishing pipelines, and migration documentation so the team adopts the new workflow and AI-first practices consistently.
- Meet the migration milestones set by the Manager, Information Development.
- Create AI-Ready Content and Ensure Responsible Use of AI: Write modular, consistently structured content with clear titles, concise summaries, metadata, and stable terminology so that AI assistants and retrieval systems can find and cite it accurately.
- Author and maintain prompts, agent instructions, and reusable skills that capture PowerPlan’s style, terminology, and documentation workflows.
- Test how AI tools answer questions from our documentation, and close the content gaps those tests expose.
- Review AI-assisted drafts for technical accuracy, completeness, tone, and adherence to the style guide, and confirm them with subject matter experts before publication.
- Follow company guidelines for AI use, including protection of confidential and customer information, and help the documentation team refine those practices as tools and standards evolve.
- Success Metrics Documentation delivered on or ahead of release schedules
- Migration milestones met for the 2027 transition from the CCMS to docs-as-code
- Increased product adoption and positive customer feedback, including documentation ratings and task success
Fewer support cases caused by documentation gaps
- Accuracy and freshness of published content, including quarterly review results and passing quality checks
- Accuracy of AI-assistant answers drawn from our documentation, measured against a defined set of test questions
- Uptake of new documentation tools, formats, and AI-assisted workflows
- Experience in structured, topic-based writing, including content reuse, metadata, and consistent terminology.
- Hands-on experience using generative AI tools (for example, Claude, Copilot, or ChatGPT) in documentation work, with the judgment to verify AI output for technical accuracy.
- Experience in documenting enterprise-level software applications/solutions.
- Process orientation and ability to analyze and design/build complex processes.
Requirements
- Qualifications Bachelor’s degree or equivalent.
- 5+ years of experience as a Technical Writer or in related roles.
- Experience with docs-as-code workflows (Markdown, Git branching and pull requests, a code editor such as VS Code, and automated publishing pipelines), or the demonstrated ability to learn them quickly as the team transitions in 2027.
- Executive presence through verbal and non-verbal communication (confidence, poise, and authority).
- Clear and concise writing for both technical and non-technical audiences.
- Excellent organizational and time management skills.
- Detail-oriented and comfortable in a fast-paced environment where meeting deadlines will require perseverance.
- Experience working in an Agile environment.
- Industry/domain knowledge: Accounting knowledge and the ability to apply it in an area of domain specialty.
- Examples of domains are regulated utilities, oil & gas, fixed assets, tax, and budgeting.
- Understanding of system and network architecture, system platforms, system access, database design, SQL queries, and network protocols.
- RAG, prompt engineering, and context engineering (including progressive disclosure and context-window limits); authoring and testing agent skills and instructions; Model Context Protocol (MCP) and AI-facing content formats such as llms.txt; designing content for AI retrieval; and evaluating the accuracy of AI answers drawn from documentation.
Preferred
- Skilled with component content management systems (CCMS) and content authoring tools, with a preference for MadCap Flare and Zendesk experience, and willing to learn new tools as the team transitions to docs-as-code.
- Experience in API documentation (OpenAPI, Postman, Bruno).
- Experience with docs-as-code tooling, such as static site generators (Docusaurus, MkDocs, Hugo, or Sphinx), prose and Markdown linters (Vale, markdownlint), and automated link checking in CI.
- Experience migrating content from a CCMS such as MadCap Flare to Markdown-based sources.
PowerPlan is an EOE Applicant Privacy Notice Please note that this is a hybrid role that involves a combination of onsite work from our corporate office as well as work from home. While we strive to accommodate flexible working arrangements when sensible, there will be times when onsite work is required. This could include scheduled office days, team meetings, client meetings, or special events.
