📸 Team Snapshot

Team Mission

Our goal is to use modern tools and technologies in combination with open collaboration to engineer a mental health platform which truly helps people while providing a diverse and respectful working environment which combines a love of technology, personal development, and challenges from which we can grow.

Core Responsibilities

Team Blue works on various technological initiatives across mobile, web, and backend engineering. These cover our three core services:

the patient platform for the course itself
the therapist platform for course coaches
the back office platform for coach management and course design

Team Structure

Team Size: 9

Roles: 1x Engineering Manager, 1x Senior Product Manager, 1x QA Engineer, 2x Frontend Engineers, 2x Backend Engineers, 2x Mobile Engineers

Role	Description
Engineering Manager	Manages the people and processes of Team Blue, and acts as the main liaison and sparring partner of the Product Manager
Product Manager	Drives the direction of the features and the timeline for their implementation
Software Engineers	Write and ship code to deliver features, bug fixes, and technical initiatives
QA Engineer	Oversees quality-based initiatives such as testing and release planning, plus acts as the main liaison between support and engineering

In addition to our official team, we also collaborate closely with our user expert Nina and UX/UI designer Jade.

Tech Stack: We primarily use TypeScript with React for web and React Native for mobile. Our backend is almost entirely in NodeJS, with some services being transitioned to TypeScript and one service written in Ruby. Other tools and services we use: Bitbucket, Figma, MongoDB, Selenium, Sentry.

💞 Team Dynamics

How We Collaborate

Collaboration Tools

Jira for sprint backlog, tickets, board, etc.
Slack for day-to-day messaging and most communication
Google Meet for meetings and virtual get-togethers
Miro for brainstorming and retrospectives

Meeting Cadence

2-week sprints, ending on Tuesdays: this includes a one-hour retrospective on demand (when at least two team members want one). The next day (Wednesday) we do our sprint and release planning with our Product Manager, Tanja.
Standup is 3x a week (Mon, Weds, Fri) in a virtual meeting, and 2x a week (Tues, Thurs) async via Slack.
Quarterly meetings are held at the end of the prior quarter to cover the next quarter’s priorities and general plan for completion.
Fortnightly product alignment meetings (where we’re at with designs, user needs, upcoming features, etc.) and technical backlog refinements.

Core Values and Code of Conduct

Our five core values are:

Honesty and Openness
People over Processes, and Processes over Rules
Adaptability
Results-Driven
Growth Mindset

Code of Conduct

We as a team are inclusive and embracing of team members from all backgrounds, beliefs, orientations, genders, working hours, and more.
We as a team agree to respond to messages in a timely manner, taking into account working hours and timezones.
We as a team will communicate problems early, and be open about our challenges, workload stressors, and blockers.
We as a team commit ourselves to openly asking for assistance, regardless of our level or the apparent level of the question. We will not let “I should already know this” interfere with asking for help. (aka the “Anti-Imposter Syndrome Clause”)
We as a team dedicate ourselves to openly sharing ideas, no matter how small.
We as a team commit to listening first and evaluating later: we do not immediately dismiss any idea or opinion.
We as a team are open to adapt our processes to the needs of the current team members. We believe that processes should enable freedom for effective work, instead of limiting team members' options or capacity.
We as a team acknowledge that although features are fun to write, that bugs, triage tickets, and changes will always come up. We therefore aim to be flexible by retaining capacity both in the sprint and in our personal workload for unexpected situations.
We as a team strive to help each other reach our sprint goals, be it through open advice, pair programming, debugging, code reviews, or emotional support.
We as a team dedicate ourselves to creating opportunities to expand our skills and learn from each other, including through dedicated learning days with presentations on what we discover.

Fun Facts and Team Bonding

Team Building Activities

Monthly teambuilding workshop to cover ideas like values, priorities, communication, etc.
2x a year in-person participation in the HelloBetter summer and winter parties in Berlin: we really enjoy bringing our international team together for these events!
Tuesday afternoons we have a virtual gaming session for any team member who wants to join