Team Development

Team Development

This page is maintained by the 🤖Team Development

This page is still under development 😇 

Who we are?

We are a group of 25(and growing) Problem Solvers. We have gathered here at HelloBetter from different parts of the world to solve the biggest problems in mental health.

🧬 Our Engineering Culture

  • We believe in rewarding collaboration ahead of egos
  • Agility ahead of process
  • Autonomy and Ownership ahead of micro-management
  • And Patient first ahead of presumptions

🛠️ Methodologies & Principles

We follow Kanban. We introduced OKRs in early 2020 (company- team level) to bring the best alignment to all teams. They are published to all teams, with updates each month to see how we progress.

🤝 How do we work

At HelloBetter the Engineering and Product Team are working together in cross-functional teams called Squads and Chapters.

Squads are formed to tackle product and engineering initiatives, which allows its members to focus on one objective at a time. They are largely self-managed and have ownership over their workflow and rituals (such as daily stand-ups, retrospectives, and product&tech refinements).

Our squads promote cross-collaboration between different roles to develop the best solutions to our business problems.

Each squad contains the following roles: 🧑🏽‍💼  1 PM (Product Manager) 🌐  1 or more web developers 📲  1 or more mobile developers 👩🏽‍💻  1 or more backend developers 👨🏿‍💻  1 QA engineer

In addition, we have some people that are not part of a single squad but support multiple squads at once. For example, our PD (Product Designer), our Engineering Manager, and some chapter-leads attend multiple squad rituals.

Chapters at HelloBetter are made up of people working on the same platform (mobile, web, backend, QA). They align on engineering standards and address platform-specific issues.

⚙️ Architecture

Our architecture is designed for flexibility and growth, supporting a language-agnostic microservices approach with a focus on NodeJS. We create distinct platforms for patients and therapists, and a backoffice for platform management, ensuring a seamless experience for all users.


  • Programming Languages: NodeJS (major), transitioning to TypeScript, and JavaScript (ES6) for versatile development.
  • Frameworks and Tools: React for web development, React Native for mobile apps, Fastify for backend services, and tools like, frisby.js, & Detox for testing.
  • Databases and Cloud: PostgreSQL and MongoDB for our data storage needs, with TelekomCloud hosting our infrastructure, currently migrating to AWS.
For more information check our ↗️  stackshare page.


Security is at the heart of everything we do. We put a lot of effort into making sure our systems are designed as rigor as possible. Our systems are compliant with several different regulations like GDPR, MDD/MDR (Medical Device regulations) and we implement a company-wide quality management system according to ISO 13485 (QMS) and ISO 14971 (Risk) standards. In 2021, we further implemented ISO 27001 to comply with the Digital Care Act.

Apart from that, we are very active in growing a security mindset amongst engineers and all employees with our Legal Counsel helping us to balance compliance and agility.


  • Full CI/CD via Jenkins, unstable/staging/production branching scheme
  • all standardized & automated


Mostly full test coverage across projects. Developers are responsible for writing tests themselves. Integration tests are written and run continuously against testing and live environments. QA tests are written by the team continuously. Test-driven development (TDD) is deployed across almost all projects.

Development vs. maintenance

As we are building our new platform from scratch we will be 100% developing new features in the beginning. Then we 75/25, mostly development and some maintenance. As we test everything during development, the need for maintenance is smaller than usual.

Who is responsible for force majeure situations?

We have an On-call rotation in place, with DevOps/senior devs being on call.

We like the term: “You build it - You run it!”

📈 Platform usage

We will architect the platform to be able to serve more than 1 Mio patients with thousands of simultaneous users (including video streaming).

Our current addressable market contains 14 Mio people in Germany. With the new regulation, we are able to address 70+ Mio people. We assume the prevalence of psychological disorders to be at 20% of the population.

❤️ Open-Source

We are community players and deeply believe in the power of open-source. You have our full support to open-source as much of our work as possible. Although, we know that lots of companies make promises about open-sourcing stuff. Reality tells a different story and we know sometimes it can be really challenging to achieve, especially during the early stage.