____       __  __            ____
   / __ )___  / /_/ /____  _____/ __ \____  _____
  / __  / _ \/ __/ __/ _ \/ ___/ / / / __ \/ ___/
 / /_/ /  __/ /_/ /_/  __/ /  / /_/ / /_/ / /__
/_____/\___/\__/\__/\___/_/  /_____/\____/\___/

About engineering at BetterDoc

TL;DR: we build the best patient to physician matching product. We try our best not to be another mindless software factory.

As a leading e-health startup in Germany with over 70 employees, BetterDoc finds the right physicians for patients. Currently our service is valued by more than 10,000 happy patients per year.

Engineering at BetterDoc – the Product Development Team

To improve how we deliver our service, we are forging a domain model that enables us to represent and store quality data related to health, and use that to make well-based recommendations for the right physician.

🦸‍♀️ Our mission

BetterDoc is on a mission to always find the right doctors for patients with serious health issues. At the moment, our service is mainly provided by real medical staff like physicians and scientific researchers. They tap into our extensive physicians database and recommend specialists, based on the patient’s health issue and intent. Now we are starting to write machines to do parts of our service. Of course, medical staff is here to stay, solve complex cases, train our machines and assure quality. Think of it as a healthy human-machine symbiosis.

⚔️ Our challenge

To have a deep insight into the problems we solve for researchers, members of our call center team and other teams such as physician data administration and analytics, we organise workshops with all stakeholders to get a good and deep understanding of problems and needs. Our learnings are distilled into short briefing documents that are used to capture learnings and sketch out possible solutions.

💪 How we work

Our developers are able to work on all parts of our stack, both in the frontend and the backend, with various focus areas and strengths.

We value curiosity and learning. To support this, we experiment and learn 20% of our work time. You can, for example, invest this time to visit a conference, contribute to open source software or start your own open source project.

We are proud to trust colleagues instead of controlling them. Our team organises itself and reflects on how to improve our working mode.

We plan our work using GitHub and Trello. Projects are self-managed by teams. Management means helping teams and people: removing obstacles, helping out, creating an encouraging environment.

We work to deliver value, not to do as the spec says. Everybody is free and expected to contribute ideas on how to improve architecture, code and organisation.