Docplanner

Knowledge Architect and Product Enablement Expert

Region Restricted

Remote work allowed only within certain countries or regions.

Employer listed it 8 days ago · Added 4 days ago

First listed 8 days ago and still open.

Salary

Not stated

Location

Timezone

Not stated

Contract

Full-time

Experience

Mid

Remote flexibility

Region Restricted

Remote work is allowed, but the listing limits candidates to Curitiba, Remote.

What the employer says

Source listing states candidate location: "Curitiba, Remote"

What Nomaders makes of it

Nomaders could not match this to a wider region
Check the original posting

The quotes above are the employer's own words; the reading is ours. Always check the original listing and employment terms before working from another country.

About the 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.

Our current internal knowledge base

Review what we have today, article by article, and decide what happens to each part: move it to the new structure, rewrite it, replace it with output generated from the code, or archive it because it is no longer useful.

Propose the order of that work, with clear reasons based on how much each topic is used and how often it changes, and agree with the manager of the team.

Lead the team through that work. You do not do it alone. You decide the method, you explain it, you review the result, and you keep the quality consistent across markets and people .

Teaching the team to work in the new way

Bring the team from writing articles to checking facts . This is a real change in habits, and it needs to be taught.

Create the working guides, examples and short training sessions that make the new way easy to follow, and update them as the method changes.

Build new skills inside the team : how to write a small self-contained fact, how to review generated content, how to spot a knowledge gap, how to work with content that lives in a repository, and how to test an AI assistant's answers.

Requirements

·What will help you thrive?
·Experience designing content structures : small self-contained pieces of content, labels and metadata, standards that you defined and then made other people follow. Markdown, YAML or JSON as formats you use every day.
·Experience with documentation that lives in a repository: versioned, reviewed, and built like code, not kept in a folder of documents.
·A working understanding of how AI assistants use content : how they retrieve it, why a well-written article can still produce a bad answer, and how to test the answers instead of assuming they are fine.
·Proven ability to get busy experts to review facts quickly, and to design the format that makes that possible.

Benefits

·Healthcare insurance – so you can focus on what matters.
·Wellness that works for you – from gym memberships to mental health support, we’ve got you covered.
·Time off that counts – whether it’s a vacation, your birthday, or just a day to recharge, we believe in balance.
·📍 Local Perks – Depending on your location, you will be entitled to local benefits like meal vouchers (ticket restaurant), transport allowances, or extended parental leave.
·🚀 Career Growth – We’re growing, and so can you! You’ll find lots of chances to learn, develop, and explore new paths—whether within your team or through cross-functional projects.

How to apply

1Check the flexibility label above, region restricted, matches where you plan to live and work.
2Tailor your CV to the role at Docplanner, mentioning your remote working experience.
3Apply directly on the employer's careers page using the button below. Nomaders never handles your application.

Found 5d ago. Last checked today. Always confirm the details on the original posting, salary and location can change after publication.

Listing sourced from Company boards.