Any
Weekly salary (fair payment)
30
Jan 27, 2026
We are building a custom CRM platform and are looking for a Backend Developer focused on core services and the data layer. Your primary responsibility is to implement the backend foundations: Supabase/Postgres data modeling, authentication flows,
You will collaborate closely with an API Developer who will expose and evolve the public/internal API layer. Your work provides the stable, secure, and well-structured backend “engine” that the API layer builds upon.
Responsibilities
• Own the data layer (Supabase/Postgres)
• Design schemas for CRM entities (users, leads, contacts, pipelines, activities, permissions, etc.)
• Create migrations, indexes, constraints, and data integrity rules
• Optimize queries and storage patterns for scale and performance
• Implement core business logic
• Domain rules (workflow states, pipeline transitions, data validation, deduplication)
• Background jobs where needed (sync tasks, scheduled processing,
• Authentication & identity workflows
• Secure login, session/token handling, user lifecycle (sign-up, verification, password resets)
• RBAC/permission modeling and enforcement support
• Audit trails and security-relevant event logging
•
• Transactional
• SMTP/provider integration, template handling, retries, and error visibility
• Security by default
• Secure secret handling, rate limiting strategy inputs, brute-force prevention concepts
• GDPR-friendly data design considerations (retention, access logging, exports)
• Quality & reliability
• Automated tests for core logic and critical flows
• Monitoring/logging hooks, debugging production issues, performance tuning
Requirements
• Strong experience building backend systems with a focus on data modeling and business logic
• Solid knowledge of PostgreSQL (schema design, indexes, constraints, query optimization)
• Experience with Supabase (or willingness to learn quickly); familiarity with Postgres-based platforms
• Proven experience implementing auth and
• Strong engineering fundamentals: testing, clean code, maintainability, debugging
Nice to have
• Multi-tenant SaaS patterns, data partitioning, and permission models
• Experience with row-level access strategies (even if handled outside the API layer)
• Observability tooling (structured logs, tracing, metrics)
Collaboration / Interfaces
• Works closely with the API Developer, providing:
• Stable domain services and data access patterns
• Clear contracts for what the API layer can call and how errors are surfaced
• Documentation for domain behavior and data rules