Knowledge Architect
Posted 5 Oct 2026
Advertised as “Knowledge Architect and Product Enablement Expert”
BranchFactor Summary
The original posting with the fluff stripped out
- Expected experience
- 4–7 yrs
- Management level
- People management
- Employment
- Hybrid
- Contract
- Full-time
- Visa sponsorship
- Not offered
No salary listed for this role.
Company Description
At Docplanner Group, we’re on a mission to help people live longer, healthier lives. As the world’s largest healthcare platform, each month, we connect 24 million patients with 280k doctors across 13 countries (through brands like ZnanyLekarz, Doctoralia, MioDottore, DoktorTakvimi, and jameda). Our marketplaces, SaaS and AI tools simplify daily tasks and help doctors, clinics and hospitals work more efficiently, so they can focus on what really matters: caring for their patients.
Learn more about our products here: pro.doctoralia.es
Why join us?
📊 Real impact – We help doctors help patients. Your work truly makes a difference.
📈 At scale, yet agile – 3,000+ employees, but still fast, flexible, and hands-on.
✨ Shape the future, sustain growth – Make a difference now and build for long-term success.
What you will own
The structure of our product knowledge
-
Define and keep the content model for Docplanner product knowledge: small self-contained facts, how topics are organised, which labels and metadata we use, and what belongs to the internal knowledge base versus the external one for customers and doctors.
-
Set the quality standard. Every fact carries a reference to where it came from (repository, file, place in the code), so anyone can check it again later instead of trusting it blindly.
-
Choose one structure that works for both assistants, Kraken for customers and Noa for doctors, so we do not end up maintaining the same knowledge twice.
Getting knowledge out of the code
-
Work directly in GitHub with read access to the monorepo and the other repositories. Find where the logic of a feature really lives, read it well enough to understand the rules and the special cases, and turn it into clear output that other people can review.
-
Improve the way we generate this output, so that over time fewer facts need a person to confirm them. Simplifying is key.
-
Protect one rule: every new or changed feature is generated from the code from day one. Older content is only redone when a release touches it, or when it is one of the most used topics in Kraken and in Customer Care. We are not going to rewrite the whole knowledge base in one big project.