Developer

Purpose

Heal-3, a workplace mental health and wellbeing company, is building
Thrive
an early-warning and peer-support platform for first responders. It helps identify changes in wellbeing early—before issues turn into injuries or crises.

The pilot will combine three forms of data:

1. Physiological data
   from Garmin wearables (sleep, stress, recovery).
2. Self-reported data
   from SMS check-ins.
3. Peer-support data
   from conversations between participants and peer mentors, all handled securely through Twilio.

The goal is to learn:

• What changes indicate strain or recovery,
• How mentors can respond in real time, and provide effective support and resources
• Which supports (community, therapy, education) are most effective in times of stress and strain.

2. Assumptions & Responsibilities (for External Developers)

Heal-3 will provide:

• An existing cloud environment (AWS or Azure) configured by our internal lead developer (including servers, networking, DNS, SSL, PostgreSQL, Redis).
• A base code repository and tech stack or Python backend + frontend).
• Access to required third-party accounts and credentials (Garmin Health API, Twilio, etc.).
• High-level data model guidance and code review, plus responsibility for deployment to production.

External contractor is responsible for:

• Implementing one or more of the components below (Twilio inbox, Garmin data integration, dashboard) within the provided codebase and environment.
• Writing clean, documented code and basic tests (unit or integration where appropriate).
• Providing clear setup/usage notes so Heal-3's internal developer can integrate and deploy.

External contractor is
not
responsible for:

• Provisioning servers, DNS, Nginx, SSL, or database infrastructure.
• Designing full production architecture or long-term scaling strategy

SCOPE OF WORK (3 Components — Developer May Do a Portion or All)

COMPONENT 1 — Twilio Texting + Centralized Peer Mentor Inbox

(Peer mentors communicate with firefighters based on their Garmin trends)

Goal

Create a Twilio-powered SMS system allowing peer mentors to send and receive messages with firefighters, in one centralized, secure inbox.

Important to note:
While the MVP will rely on Twilio SMS for communication, the long-term roadmap includes the creation of an internal messaging layer and in-app messaging interface that stores all message data within our own database. This will enable indexing, search, and future AI/ML-driven pattern detection (e.g., sentiment analysis, linguistic trends, and crisis prediction). The contractor should design the current messaging components in a flexible way that supports migration to this future architecture.

Key Tasks

• Set up one Twilio phone number (STOP/HELP compliance).
• Add 3–5 reusable text templates for mentors.
• Enable two-way SMS communication.
• Build a simple web interface showing message threads per firefighter.
• Create a basic admin/search view.
• No separate mentor login required—backend filtering manages visibility.
• Provide documentation and instructions.

COMPONENT 2 — Garmin Daily Data Integration + Cloud Backend (AWS or Azure)

(Firefighters connect their Garmin watches; mentors later see this data in the dashboard)

Goal

Allow firefighters to securely connect their Garmin accounts and sync data, stored in the backend running on the App Host, with PostgreSQL and Redis on the Database Host.

Key Tasks

• Set up AWS or Azure backend (EC2/Lambda, RDS/PostgreSQL, S3).
• Set up backend on
  App / Container Host
  (AWS/Azure EC2 or equivalent)
• Connect backend to PostgreSQL (Database Host)
• Connect backend to Redis (Database Host)
• Integrate Garmin OAuth
• Integrate Garmin Health API (daily summaries)
• Build a simple "Connect your Garmin" OAuth2 page for firefighters.
• Integrate the standard Garmin Health API (daily, not real-time) for:
• Sleep summary
• Stress
• HRV
• Resting heart rate
• Body Battery (if available)
• Clean and store data with correct timestamps.
• Provide a short system diagram (Garmin → Cloud → Dashboard).
• Include documentation and test cases.

COMPONENT 3 — Peer Mentor Dashboard (Web-Based)

(Peer mentors view wellbeing trends from firefighter Garmin data)

Goal

Build a web dashboard deployed on the App Host, reachable via Nginx on the Ingress Host, pulling data from Postgres and Redis on the Database Host.

Key Tasks

• Create dashboard served from
  App Host behind Nginx
• Connect dashboard to:
• PostgresSQL – description of data source
• Redis – transactional register and metadata
• Elastic – indexed data for ranking critical flags indicating crisis
• Support Admin + Peer Mentor role views:
• Admin → sees all firefighters
• Peer mentor → sees only their assigned firefighters
• Trend toggles for
  7 / 14 / 28 days
  .
• Display Garmin wellbeing fields:
• Sleep
• Stress
• HRV
• Resting heart rate
• Body Battery
• Include "loading" and "no data yet" states.
• Prioritize simplicity and human interpretation (no AI scoring yet).
• Transactional logging of data ingested globally by app
• Server-side logging and error mechnism

Ideal Developer / Team Profile

• Garmin Health API or similar wearable API experience
• AWS/Azure expertise
• Twilio API implementation
• "app name" API development and data exposure mechanism
• Backend development in or Python equivalent
• front-end development
• Strong documentation and security best practices