Two-Way Messaging Project

We’re hiring one contract full-stack engineer to build an in-app two-way messaging module for our education SaaS product. We’re moving fast, staying lean, and optimizing for strong execution with minimal rework. Completion of the paid sample project is required to be considered.

Tech stack (required)
React (frontend)
Node.js + NestJS (backend)
GraphQL
MySQL
GitHub
Must overlap at least 4 hours/day with US Eastern

What you’ll build (high-level)

Two-way messaging between:
School Admins + Teachers ↔ Parents + Students
The MVP should cover:
Conversations + message thread UI
Sending/receiving messages
Role-based access rules
Unread/read behavior
A minimal foundation for reporting/insights (event tracking / metrics-ready structure)
Engagement model
Fixed-bid preferred (milestones)
Potential for ongoing work after the initial project

What to include in your application
1–2 relevant examples (messaging, workflow SaaS, real-time features, permissions, etc.)
Your availability + confirmation of 4+ hours EST overlap
Any initial assumptions or questions you’d want answered before starting

Required paid sample project
Purpose: Evaluate code quality, product thinking, scoping, and communication.
Timebox: 4–6 hours
Payment: $250 via Guru SafePay upon submission (regardless of selection)
Submission: GitHub repo + docs + short demo video (no deployment required)
Sample project: Messaging POC (minimal)
Build a small messaging proof-of-concept that demonstrates:
A simple UI to switch between mock users (Admin / Teacher / Parent / Student)
Ability to send messages and view a thread
Basic permission enforcement consistent with “Admins/Teachers ↔ Parents/Students”
Keep it simple—this is not production code.
Required deliverables
GitHub repo that runs locally with clear instructions
Demo video (max 5 minutes) showing the POC working
TECHNICAL_APPROACH.md (1–2 pages) including:
High-level approach (frontend, backend, data model, API shape)
Key risks/edge cases you’d plan for in the real build
What technical prep work you’d do first (e.g., clarifying rules, schema review, instrumentation plan)
PROJECT_ESTIMATE.md (required)
Provide a full estimate for delivering the real messaging project:
milestone plan (MVP → hardening → insights/reporting foundation)
timeline
fixed-bid cost (or milestone costs)
assumptions + what would change the estimate
what you need from us (access, sample data, permission rules, etc.)



 ... Show more