Backend Developer Needed – Supabase Marketplace Backend (MVP)
Budget: ₹12,500 – ₹37,500 INR
We are building a mobile-first marketplace backend using Supabase and are looking for an experienced backend developer to help complete the MVP backend.
This project focuses purely on secure backend architecture and logic.
Frontend UI is already in progress and will consume backend APIs. Scope of Work (MVP Only)
1) User & Role Management
OTP-based authentication
Two immutable roles (Role A / Role B)
Role-based access enforced via RLS
No role switching after signup
2) Project Lifecycle Logic
Implement a strict lifecycle:
open → hired → completed
Backend must enforce:
Only Role A can create projects
Only one Role B can be selected per project
State transitions cannot be skipped or reversed
3) Proposal System
Role B users can submit proposals
Proposal visibility controlled by backend
Automatic rejection of other proposals once one is selected
4) Controlled Visibility (Matching)
Not all Role B users see all projects
Backend assigns visibility via a mapping table
Role B users can only read their assigned visibility records
No frontend-controlled matching logic
5) Messaging (Restricted)
Messaging enabled only after selection
Messages validated server-side
Message inserts blocked if permissions fail
6) Anti-Abuse / Compliance
Server-side detection of:
Phone numbers
External contact attempts
Violation logging with escalation:
Warning
Temporary restriction
Account suspension
7) Staged Payments
Three-stage payment flow:
Advance
Mid-stage
Final settlement
Backend enforces order and prevents duplication
Ledger entries required for auditability
Exact revenue formulas will be shared after onboarding.
This project focuses purely on secure backend architecture and logic.
Frontend UI is already in progress and will consume backend APIs. Scope of Work (MVP Only)
1) User & Role Management
OTP-based authentication
Two immutable roles (Role A / Role B)
Role-based access enforced via RLS
No role switching after signup
2) Project Lifecycle Logic
Implement a strict lifecycle:
open → hired → completed
Backend must enforce:
Only Role A can create projects
Only one Role B can be selected per project
State transitions cannot be skipped or reversed
3) Proposal System
Role B users can submit proposals
Proposal visibility controlled by backend
Automatic rejection of other proposals once one is selected
4) Controlled Visibility (Matching)
Not all Role B users see all projects
Backend assigns visibility via a mapping table
Role B users can only read their assigned visibility records
No frontend-controlled matching logic
5) Messaging (Restricted)
Messaging enabled only after selection
Messages validated server-side
Message inserts blocked if permissions fail
6) Anti-Abuse / Compliance
Server-side detection of:
Phone numbers
External contact attempts
Violation logging with escalation:
Warning
Temporary restriction
Account suspension
7) Staged Payments
Three-stage payment flow:
Advance
Mid-stage
Final settlement
Backend enforces order and prevents duplication
Ledger entries required for auditability
Exact revenue formulas will be shared after onboarding.