Actively recruiting / 8 applicants
We’re here to help you
Juliana Torrisi is in direct contact with the company and can answer any questions you may have. Email
Juliana Torrisi, RecruiterAbout the Project
We are building a non-clinical chronic disease monitoring platform for telehealth organizations. Patients submit daily metrics (blood pressure, glucose, weight, etc.), symptom check-ins, and engagement data. The system generates simple, non-clinical alerts to help clinicians monitor patient status across multiple partner organizations.
This is a multi-tenant B2B SaaS platform built with:
- Next.js (App Router)
- Supabase (Postgres, Auth, Storage, RLS)
- n8n automation workflows
- SendGrid for messaging
- Vercel for deployment
The MVP contains no medical decision-making, AI, or diagnostic features—strictly non-clinical workflows.
Role Overview
We are seeking a highly capable Full-Stack Developer to build the full MVP end-to-end. The ideal candidate has deep experience with Supabase, particularly RLS, dynamic form rendering, and multi-tenant SaaS architectures.
If you tend to “just hardcode logic,” this project is not a fit—the system relies on a JSON-driven rules engine and strict dynamic rendering.
Required Skills
✔ Strong experience with Next.js + React
✔ Strong experience with Supabase (must have real RLS experience)
✔ Ability to build complex CRUD + forms + dashboards
✔ Experience integrating external services (e.g., SendGrid)
✔ Ability to implement multi-tenant architecture
✔ Confidence writing Postgres functions & policies
✔ Experience building production-ready web apps
✔ Strong communication & ability to follow detailed specs
If you say “I’ll just hardcode this” → you are not fit for the project.
All condition logic MUST be JSON-driven.
Nice-to-Have Skills
- Familiarity with healthcare systems
- Experience with HIPAA-level security
- Time-series data experience
- API design experience
- UI/UX sensibility
- Charting libraries
What You Will Build (MVP Modules)
- Authentication & Roles
- Supabase Auth + JWT
- User roles: superadmin, partner_admin, clinician, patient
- Multi-tenant isolation via RLS
- Role-specific UI flows
- Patient Management
- CRUD, clinician assignment, patient status (active/paused/archived)
- Consent timestamp tracking
- JSON-Driven Condition Module Engine (Core Feature)
- No condition logic hardcoded
- Superadmin pastes JSON modules
- Frontend dynamically renders:
*Metrics (labels, units, ranges)
*Check-in questions
*Education content
*Backend interprets JSON for alert rules, frequencies, targets
- Metric Submission Engine
- Bundled submissions with one submission_id
- Multiple metric rows per submission
- Numeric validation
- Check-In Engine
- Dynamically render questions
- Store responses
- Trigger symptom alerts (non-clinical)
- Alert Engine
- Out-of-range alerts
- Missed readings (via n8n)
- Symptom + engagement alerts
- Alerts are immutable, filterable, prioritized
- Clinician Dashboard
- Patient list, alerts list, filters
- Patient detail page
- Override target ranges + frequencies
- Basic charts (optional bonus)
- Patient Portal
- Submit metrics + check-ins (JSON-driven)
- View history
- Messaging
- Clinician → patient only
- SendGrid email
- Logged to database
- Auditing
- Immutable logs for:
- Metrics
- Check-ins
- Alerts
- Patient data access
- Target changes
- Messages
- CSV Export
- Metrics, check-ins, alerts (separate files)
- n8n Automation
- Missed reading checks
- Engagement checks
- Check-in reminders
- Scheduled cron workflows
Work Process & Expectations
- Weekly demos (required)
- Twice-weekly check-ins
- Daily GitHub commits (no local-only work)
- Clear communication; no skipped requirements
- Ability to propose technical improvements
- Pixel-perfect implementation