SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
DocPlanner Group is the world's largest healthcare platform, connecting 24 million patients with 280,000 doctors across 13 countries through brands like ZnanyLekarz, Doctoralia, MioDottore, DoktorTakvimi, and jameda. The company operates marketplaces, SaaS, and AI tools that help doctors, clinics, and hospitals work more efficiently.
In this role, you will architect and own the structure of DocPlanner's product knowledge base, serving as the bridge between engineering, product, customer support, and AI systems. You will define how product knowledge is organized, maintained, and delivered across multiple AI assistants (Kraken for customers and Noa for doctors) and the Help Center.
Key responsibilities include:
**Structuring Product Knowledge**: Define the content model for all DocPlanner product knowledge—how topics are organized, what metadata and labels are used, and what belongs in internal versus external knowledge bases. Set quality standards ensuring every fact is traceable to its source.
**Extracting Knowledge from Code**: Work directly in GitHub with read access to the monorepo and other repositories. Understand feature logic and special cases by reading code, then translate that into clear, reviewable documentation. Improve automated knowledge generation over time to reduce manual verification needs. Establish the rule that all new or changed features are documented from code on day one.
**Migrating Existing Knowledge**: Review the current internal knowledge base article by article, deciding what to move to the new structure, rewrite, replace with code-generated content, or archive. Propose a prioritized work plan based on usage frequency and change velocity, then lead the team through the migration.
**Teaching New Workflows**: Transform the team from writing articles to verifying facts. Create working guides, examples, and training sessions. Build skills in writing self-contained facts, reviewing generated content, spotting knowledge gaps, working with repository-based content, and testing AI assistant answers. Serve as the go-to expert when the team has questions.
**Capturing Non-Code Knowledge**: Identify knowledge types not in code (market differences, plan variations, UI wording, patient-facing content, screenshots). Design repeatable processes with Product Managers, Product Marketing, and Product Experts to capture this information. Run review loops with feature owners, preparing facts in formats non-technical stakeholders can quickly confirm or reject.
**Maintaining Currency**: Define how knowledge stays current with dozens of releases monthly—what triggers updates, who gets alerted, and response timelines. Alert the Help Center team when releases invalidate published content, with enough precision they can fix it without re-reading entire articles.
**Cross-Functional Collaboration**: Work with Product Experts (who feed and test the knowledge base), the Help Center team (who publish customer-facing content), AI assistant owners (Kraken and Noa), and Engineering (for repository access and code changes needed to support knowledge extraction).
**Requirements**:
- 4 to 7 years of experience in technical writing, documentation engineering, knowledge management, developer experience, solutions engineering, or comparable field, with real ownership (not a first role in the field)
- Genuine comfort with Git and GitHub: branches, pull requests, reading diffs, navigating large unfamiliar codebases, and reading code well enough to understand rules and edge cases (no need to be a software engineer, but must work independently with repositories)
- Experience designing content structures: small self-contained pieces, labels, metadata, and standards you defined and enforced across teams
- Experience with documentation living in repositories: versioned, reviewed, and built like code
- Working understanding of how AI assistants use content: retrieval mechanisms, why well-written articles can produce poor answers, and how to test assistant output
- Proven ability to get busy experts to review facts quickly and design formats that enable fast review
- Experience teaching teams new workflows and making change stick through guides, examples, training, and patience
- Independence to build a novel role with no precedent: define scope, defend boundaries, and surface risks early
- Professional English (written and spoken); Spanish, Portuguese, Polish, or Italian a plus
