Senior Backend Engineer – Platform Infrastructure & Development

PLEASE READ COMPLETELY
PLEASE READ COMPLETELY
PLEASE READ COMPLETELY

Senior Backend Architect / Lead Backend Engineer (Long-Term Opportunity)

We are looking for an experienced backend engineer/architect to take over, stabilize, continue building, and help complete a large-scale multi-role media/content platform that already has a substantial frontend completed.

This is NOT a beginner project.
This is NOT a simple CRUD SaaS.
This is a complex long-term platform requiring real backend architecture thinking, infrastructure discipline, scalability planning, production stability, and ongoing feature development.

We are NOT looking for someone who only audits systems and disappears.
We are specifically looking for someone capable of BOTH:
- stabilizing/improving an existing backend foundation
AND
- continuing active backend development to help complete and scale the platform long-term.

⸻

Current Project Status

- Frontend/UI is already heavily built
- Large mobile-first UX already exists
- Multi-role platform architecture already exists
- Routing/navigation/frontend wiring already implemented
- Existing backend foundation already exists
- Security hardening + initial backend foundation phase already completed
- Existing backend now needs continued architecture cleanup, stabilization, expansion, and long-term development ownership
- Long-term roadmap already planned

This role is NOT only maintenance or infrastructure review.

The selected developer will also be expected to:
- continue building backend systems
- expand APIs/services cleanly
- complete remaining platform functionality
- improve backend architecture over time
- safely scale the platform long-term

⸻

Platform Complexity Includes

- multiple user roles/profiles
- entitlement systems
- subscriptions
- monetization
- creator/business workflows
- moderation systems
- analytics/event systems
- referral/affiliate systems
- messaging/inbox systems
- immersive media/content systems
- admin/staff tooling
- rewards/XP systems
- creator dashboards/tools
- advertiser systems
- queue/background processing systems

⸻

What We Need

We are looking for someone who can:

- audit and understand an existing backend/infrastructure
- identify architectural weaknesses
- stabilize backend systems where needed
- continue actively building and expanding backend features
- complete missing backend systems cleanly
- improve scalability/security/reliability
- design maintainable backend architecture
- enforce proper RBAC/permission systems
- improve deployment workflows
- improve monitoring/logging/observability
- organize/document systems for long-term maintainability
- think long-term about backend ownership and platform growth

This role is BOTH:
- backend stabilization
AND
- active backend development/ownership.

⸻

Tech Stack / Systems Involved

Experience with MOST of the following is strongly preferred:

- Node.js / NestJS
- PostgreSQL
- Supabase
- Railway
- Redis / BullMQ
- Stripe subscriptions + webhooks
- Cloudflare R2 / S3-style storage
- Twilio integrations
- SendGrid/email systems
- JWT auth systems
- RBAC / permissions architecture
- queue workers/background jobs
- infrastructure monitoring/logging
- API security
- webhook replay protection
- rate limiting/idempotency
- audit logs
- CI/CD pipelines
- staging/production environments

⸻

IMPORTANT

You will likely be reviewing another developer’s existing backend work, so experience inheriting/refactoring/stabilizing existing systems is VERY important.

However:
this is NOT just an “audit and review” position.

The goal is long-term backend ownership and continued platform completion/development.

We are looking for someone who can:
- safely inherit systems
- stabilize weak areas
- AND continue building the platform properly long-term.

⸻

What We Are NOT Looking For

We are NOT looking for:
- “feature patchers”
- copy/paste developers
- people who only know frontend
- people who disappear during infrastructure issues
- developers who cannot explain architecture decisions
- developers who blindly rely on AI without understanding systems
- developers who only want short-term contract work

Communication, reliability, backend ownership mentality, and long-term thinking matter heavily for this role.

⸻

Budget / Long-Term Opportunity

- Current backend phase budget is under $1600
- This is a large long-term project with ongoing work for the right person
- Looking for quality, architecture thinking, communication, and reliability over speed

The budget for this phase is specific, but this can lead to:
- long-term backend ownership
- ongoing maintenance work
- future projects
- retained backend support work

Every completed app/project will also require a mandatory 30-day maintenance/stabilization period after launch to handle:
- bugs
- deployment issues
- post-launch fixes
- infrastructure issues
- stability monitoring

After that period, long-term paid maintenance/support opportunities may continue based on:
- performance
- communication
- reliability
- backend quality
- ownership mentality

⸻

If you have read and understood the project:
- bid ONLY $100
- include your actual price in your proposal
- include the phrase:
“I’m ready now”

I will be asking detailed backend/system questions during evaluation.
If you are vague, avoid technical discussion, or cannot explain architecture decisions clearly, this is probably not the right fit.

This can turn into a long-term lead backend role for the right person.

IMPORTANT TECHNICAL CONTEXT

The frontend/platform foundation was heavily built using modern frontend tooling/workflows (React/Vite/Tailwind/shadcn style architecture), so we are specifically looking for someone capable of helping evolve the platform into a production-grade backend-powered web platform AND true native mobile app experience long-term.

This is NOT just a simple website backend.

The ideal developer should understand:
- scalable backend architecture for both web + mobile ecosystems
- API design for immersive mobile-first applications
- media/content delivery systems
- authentication/session handling across platforms
- queue/event-driven systems
- real production infrastructure workflows
- long-term platform scalability

Experience supporting or integrating with native/hybrid mobile app workflows (Capacitor, React Native, app deployment flows, push systems, background jobs, etc.) is a strong plus.