Strategic context

High-risk, high-urgency platform transition, ongoing product delivery must be maintained in parallel. Timeline is compressed by approximately 3 months versus the original plan.

Transformation scope

• Migrate a legacy Java Spring Boot platform (Thymeleaf + Angular) to Rust + Flutter + React.
• Preserve functional parity for critical modules: content management, reporting, and billing.
• Run a related product line (mental health) in parallel without major delivery degradation.

Company and team overview

A Berlin-based digital health company ("Digitale Gesundheit") operating a suite of therapy and patient management products. The broader organization includes Engineering, Product/Design & Content, a Rollout team (key account managers serving ~120 clinics and ~70 therapists), and an internal business team.

Engineering team

• Team size: approximately 12 and growing.
• Experienced team: average age around mid-30s.
• Gender balance: currently ~40% female / ~60% male, improving representation of women in engineering is an explicit hiring objective.
• Strong international culture: team members from South Korea, Tunisia, Argentina, Greece, Latvia, Belarus, Russia, India, and Germany.

Product portfolio

Core platform web

The main B2B platform serving clinics and therapists.

Mental health product line launch Nov '25

Psychosomatic therapy app covering depression, anxiety, PTSD, and related conditions.

Somatic therapy app in transition

Patient-facing home app (legacy) migrating to a new somatic therapy product, covering post-surgery and physical rehabilitation (e.g. orthopaedic recovery, cardiac surgery).

Therapy management platform

Internal hub for therapists and care coordination teams.

Patient portal web + app

Patient-facing portal available as web and mobile app.

Skillset

• Production-grade service development in Rust and/or Go
• Strong non-functional requirements translation (latency, availability, correctness)
• Concurrency, resilience, observability, and incident response
• Database and caching performance optimization

Required

• 5+ years in backend engineering with measurable reliability/performance outcomes
• Strong API design and production debugging capability
• Experience operating services through incidents and continuous improvement loops

Nice to Have

• Queue/event-driven systems and stream processing
• Strong collaboration with DevOps and infrastructure teams
• Cost/performance optimization experience

Pain Points to Solve

• Latency and throughput bottlenecks
• Reliability risk during compressed delivery
• Backend velocity limits impacting migration and product tracks