Streamline PostgreSQL Projects with Vollna

We have a fully built invoice management web application for small businesses in Saudi Arabia. The app is complete and running — including invoices, credit notes, dashboard, PDF generation, and Arabic/English support. We need a developer to connect it to ZATCA Phase 2 (Fatoora) e-invoicing system using ApiZatca.com as the API wrapper.
Important: You are NOT building ZATCA integration from scratch. The API wrapper (ApiZatca) handles all XML generation, cryptographic signing, QR codes, and ZATCA submission. Your job is to connect our existing app to this API and handle the required backend and UI wiring.
About the App:
∙ Framework: Next.js 14 (App Router)
∙ Language: TypeScript
∙ ORM: Prisma with PostgreSQL (Neon)
∙ Auth: NextAuth.js
∙ Styling: Tailwind CSS v3
∙ Arabic/English bilingual (RTL/LTR)
∙ Hosted on Vercel
What is already built:
∙ User authentication (signup/login)
∙ Business profile management
∙ Customer management (CRUD)
∙ Invoice creation with multiple items
∙ Invoice status flow (Draft → Issued → Paid → Cancelled)
∙ Credit notes / refunds (full refund linked to original invoice)
∙ Dashboard with sales analytics
∙ Compliance status panel (green/yellow/red)
∙ PDF generation for invoices and credit notes
∙ WhatsApp sharing
∙ Mock ZATCA service layer ready to replace
∙ All ZATCA database fields exist in Prisma schema (uuid, zatcaStatus, qrCode, invoiceHash, zatcaResponse, zatcaSubmittedAt)
∙ HANDOFF.md documentation included in repo
∙ Protected GitHub branch (zatca-integration) ready for you
==================================================
SCOPE OF WORK
1. ZATCA Integration via ApiZatca
∙ Replace mock service in /lib/zatca/service.ts with real ApiZatca API calls
∙ Send invoice data as JSON to ApiZatca
∙ Receive and process responses (cleared/rejected/reported)
∙ Store returned QR code, invoice hash, and ZATCA response in database
∙ Handle B2B invoices (real-time clearance)
∙ Handle B2C invoices (reporting within 24h)
∙ Submit credit notes to ZATCA referencing original invoice UUID
∙ Implement proper error handling with Arabic error messages
2. ZATCA Onboarding Flow
∙ Build UI wizard to help users complete ZATCA registration
∙ CSR generation → OTP verification → CSID obtainment
∙ Guide user through Fatoora portal connection
∙ Store certificates securely
3. Scheduled Submission (Cron Job)
∙ Add scheduled job that runs every 1-4 hours
∙ Finds all invoices and credit notes with zatcaStatus = PENDING
∙ Submits them to ZATCA via ApiZatca
∙ Updates status based on response
∙ Retries failed submissions on next run
∙ Dashboard shows count of pending items awaiting submission
4. UI Updates
∙ Replace QR code placeholder with real QR from ZATCA response
∙ Show ZATCA status on each invoice and credit note (معتمدة / مرفوضة / قيد الإرسال)
∙ Translate ZATCA error codes to simple Arabic messages
∙ Show pending submission counter on dashboard
∙ Show alert if any submission fails
5. Testing
∙ Full testing on ZATCA Sandbox environment
∙ Test B2C simplified invoices (reporting)
∙ Test B2B standard invoices (clearance)
∙ Test credit notes submission
∙ Test error scenarios (rejected invoices, network failures)
∙ Test scheduled job runs correctly
∙ Fix all issues found during sandbox testing
6. Production Go-Live
∙ Switch from sandbox to production after validation
∙ Verify production submissions work correctly
∙ Clean environment variable switch (ZATCA_MODE=sandbox → production)
∙ Monitor first batch of production submissions
7. Documentation
∙ Clear comments on all new/modified code
∙ Update HANDOFF.md with changes made
∙ List of environment variables added
∙ Instructions for future maintenance
==================================================
WORKING RULES
∙ Work ONLY on GitHub branch: zatca-integration
∙ Do NOT push directly to main branch
∙ Submit Pull Request when complete for review
∙ Separate development database provided
∙ Do not modify existing working features
∙ Keep code clean, typed, and consistent with codebase
∙ All UI text must use i18n keys (Arabic + English)
∙ All API routes must return clean JSON
∙ Commit frequently with descriptive messages
==================================================
DELIVERABLES
1. Working ZATCA integration for invoices and credit notes
2. ZATCA onboarding wizard for users
3. Scheduled job for automatic pending submissions
4. Updated UI with real QR codes, statuses, and error messages
5. Sandbox-tested and validated
6. Production-ready and verified
7. Updated documentation
8. Pull Request ready for review

TO APPLY — ANSWER THESE QUESTIONS
1. How many ZATCA Phase 2 integrations have you completed?
2. Have you used ApiZatca.com or similar wrapper? If not, which method did you use?
3. Share 1-2 Next.js/TypeScript projects you worked on.
4. Your estimated timeline for this scope.
5. Your fixed price for this project.
Do NOT apply if you have zero ZATCA experience.

Car How — Automotive How-To Video Library
A subscription-based platform for automotive technicians and collision repair shops to access short-form instructional videos organized by vehicle year, make, model, and generation.
Core Features:
• User authentication with Stripe subscriptions ($19.99/month)
• Video library searchable by make, model, generation year range, and part
• Admin panel to upload and manage videos
• Video player with metadata display
• Mobile-responsive design
• Generation-aware filtering (e.g., “2015–2020 F-150”)
Tech Stack:
• Frontend: React with responsive design
• Backend: Node.js with Supabase
• Payments: Stripe integration
• Video Hosting: Cloudflare Stream or Vimeo API
• Database: PostgreSQL (via Supabase)
Timeline: 4 weeks
Budget: $3,000

UPDATE: The app already has generation-based year ranges built in. Video uploads should tag by generation (e.g., ‘13th Gen F-150 2015-2020’) which automatically applies to all years in that range. See the collision-repair-library.jsx file for the full generation data structure.

Phase 1: Backend Migration (Weeks 1-2)
Node.js/Express or Fastify backend deployed on Railway
Port the AI pipeline from PHP to Node.js — all 6 phases (Image Sort, Lens, Gemini Eyes, Claude Brain, Gemini Search, Claude Write)
Async/concurrent processing — run Lens, Gemini, and Claude calls in parallel where possible. Target: 30-40 second pipeline (currently 90 seconds in PHP)
PostgreSQL database for users, products, orders, subscriptions
Stripe integration for payments, subscriptions, and seller payouts (replacing WooCommerce)
REST API for the frontend to consume
WebSocket support for real-time draft updates (replacing polling)
Job queue (Bull/BullMQ with Redis) for pipeline processing — handle 50+ concurrent jobs
Phase 2: Frontend (Weeks 2-3)
React/Next.js frontend replacing the WordPress PWA
Mobile-first responsive design — the primary interface is a phone
Seller flow: photograph items, submit, see real-time pipeline progress, review drafts, approve/publish
Buyer flow: browse, search, filter by category/market, purchase with Stripe
Admin dashboard: user management, commission tracking, pipeline monitoring
SEO-optimized pages for Silicon Valley cities (Atherton, Palo Alto, Menlo Park, etc.)
Phase 3: Advanced Features (Week 3-4)
Docker container setup for future C++ image processing module (native background removal via OpenCV)
N-API bindings scaffold for C++ integration
Image CDN integration (Cloudflare Images or similar)
Email notification system (Resend or SendGrid)
Rate limiting and abuse prevention
Required Skills
Strong Node.js/TypeScript — this is the core of the backend
React/Next.js — mobile-first, responsive design
PostgreSQL — schema design, migrations, efficient queries
Railway or similar PaaS (Render, Fly.io) — deployment, environment management
Stripe API — payments, subscriptions, Connect for seller payouts
REST API design — clean, documented endpoints
WebSocket implementation — real-time updates
Redis / job queues — BullMQ or similar for async processing
Docker — containerization for deployment and future C++ integration
AI API integration experience — comfortable with Anthropic, Google AI, and third-party APIs
Nice to Have
C++ / N-API experience for future native module integration
OpenCV / computer vision experience
E-commerce platform experience (WooCommerce, Shopify, or custom)
SEO implementation experience

We're building a coordination platform for the travel and hospitality sector - specifically for tour, trip, and event operations. We're moving off Airtable onto Supabase as our permanent data foundation, and we need a senior database architect to design the schema and lead the migration.

This is foundational work. The schema you build will power the product for years. We already have a Retool developer for the application layer, so this role is focused on getting the data layer *right* - not on building dashboards.

Our Airtable base is well-maintained - we've been disciplined about data hygiene from the start. This isn't a cleanup job. It's about taking a clean operational base and giving it the relational rigor, constraints, and scalability that Airtable can't provide.

**About the project**

Our platform is built on one core principle: unified data. One set of canonical records, with multiple views into the same source of truth. No duplication, no view-specific data stores, no denormalization shortcuts. We have a written engineering charter that codifies this approach - we'll share it with shortlisted candidates.

**Scope**

- Audit our current Airtable base (~20 tables, a few thousand records) and propose a clean Supabase schema
- Design entity relationships, foreign keys, and constraints with full referential integrity
- Implement row-level security from day one (multiple user roles across our platform)
- Plan and execute the migration from Airtable to Supabase, with attention to any edge cases or normalization opportunities that emerge during the audit
- Set up proper environments (staging + production), migration tooling, and backup procedures
- Document the schema and decisions for our team and our Retool developer
- Ongoing consultation as we build on the foundation (likely part-time after initial migration)

**Timeline**

We're looking to complete the initial schema design and migration within 2-3 weeks of kickoff, with ongoing collaboration after that as needed.

**Budget**

$75–$100/hr depending on experience. We'd rather pay for someone who gets it right the first time than retrofit later.

**Who we're looking for**

- Demonstrable experience designing production PostgreSQL/Supabase schemas from scratch - not just using them
- Prior experience migrating data from Airtable (or similar no-code tools) to a real relational database
- Comfortable with row-level security, UUIDs as primary keys, foreign key constraints, and database migrations as code
- Able to push back thoughtfully on bad ideas (including ours) and explain database concepts to non-technical stakeholders
- Bonus: experience with travel, hospitality, or operations/coordination platforms

**Not a fit if**

- You're a Supabase generalist who's mostly built CRUD apps on top of it
- You'd rather "migrate as-is and clean up later"
- You don't have opinions about schema design

**To apply**

Please include:

1. A short Loom (3-5 min) walking us through a relational schema you've designed - what the entities were, how you handled relationships, and one decision you'd make differently in hindsight. Applications without a Loom won't be reviewed.
2. One or two examples of past Airtable → Supabase (or similar) migrations, with rough scale
3. Your hourly rate and availability over the next 2-3 weeks
4. One question you'd ask us before quoting

Looking forward to hearing from you.

Project: SaaS Backend – Authentication, User Accounts, and Subscription Billing (Initial Test Task)

Overview:
I have already built a working frontend application. I am now looking for a developer to build the backend foundation.

This is NOT a full project yet.
This is a paid test task to evaluate quality before continuing.

Test Task Scope:
Build a basic backend system that includes:

- User registration
- User login
- Password reset
- Secure authentication (JWT or session-based)
- Basic database structure for users

Requirements:

- Experience building SaaS applications
- Experience with authentication systems
- Clean and simple architecture
- Clear communication

Important:

- No UI required (API only)
- Keep solution simple and clean
- Do not overengineer

Tech preference:
Node.js / REST API / PostgreSQL (or similar)

Next Phase (if test is successful):

- Multi-tenant company accounts
- Roles and permissions
- Stripe subscription billing
- Customer data storage
- Admin panel

To apply, please include:

1. Example of a SaaS or backend system you built
2. Short explanation of how you would structure this test task
3. Confirmation that you understand this is a test task first

I will select 1–2 developers for this test task before proceeding further.

Set up an integration with all marketing tools into Windsor.ai. Bridge it over an integration to a database, preferably Supabase and Replit. The task involves working with specific tools like Windsor.ai, Supabase, and Replit, requiring experience in API integration and database management.

• Given this stack: Windsor.ai → Supabase (Postgres) → Replit dashboard, how would you structure the database tables for Shopify (orders/revenue) and ad platforms (spend/campaigns)? Keep it brief.
• Have you worked with marketing or e-commerce data before (Shopify, Google Ads, Meta Ads, etc.)? If yes, what did you build?
• Shopify has revenue data and Google Ads has spend data. How would you combine them to calculate ROAS?
• How would you keep this setup simple and not overengineered
• What’s the best way for a frontend (Replit app) to query Supabase efficiently?

We are looking for an experienced Odoo 16 developer to build a custom bank reconciliation automation module for a multi-company retail/restaurant operation.

The module should allow accounting users to upload bank statement files from different banks in formats such as Excel or CSV or OFX, normalize the data, classify transactions, and reconcile them against Odoo records.

Main scope:
• Build a custom module for Odoo 16 Enterprise.
• Import and normalize bank statements from multiple banks.
• Create configurable mapping rules for different bank formats.
• Identify transaction date, amount, reference, description, bank account, company and store when available.
• Match bank deposits against POS sales by date, store, session and payment method.
• Match outgoing payments against supplier payments or clearing accounts.
• Detect full matches, partial matches, duplicates, discrepancies and unmatched transactions.
• Generate reconciliation summaries and exception reports.
• Create or suggest accounting entries in Odoo.
• Keep full traceability, logs and audit evidence for every reconciliation.
• Provide dashboards or list views for accounting review and approval.

The full Terms of Reference, sample files, screenshots and process diagrams will be shared with shortlisted candidates.

Please apply only if you have experience with:

• Odoo 16 accounting customization.
• Bank statement imports and reconciliation workflows.
• POS, sales, payments and journal entries in Odoo.
• Python, Odoo ORM and PostgreSQL.
• Accounting logic, journals, payments, reconciliation models and multi-company setups.

We will not provide access to our database; you must develop it on your own server and share the repository for testing.

In your proposal, please include:

• Similar Odoo accounting or reconciliation projects.
• Your proposed technical approach.
• Estimated timeline.
• Fixed-price or phased estimate.
• Key assumptions before quoting.

We're building a CRM for our trading desk and need an experienced full-stack developer to add a new module: a real-time trading activity feed with filtering, role-based visibility, and a summary stats panel.

The backend is already running on Node.js + PostgreSQL with Prisma. The frontend is Next.js + React + TypeScript. We need someone who can plug in cleanly - no time to explain basics.

Scope of work (about 4 days):

- Day 1-2: Build the activity log API endpoint (Node.js/Prisma) with filters (by date, instrument, user role) and connect it to the existing PostgreSQL schema
- Day 2-3: Build the dashboard page in Next.js - activity feed table, filters UI, summary stats (total volume, P&L, trade count)
- Day 3-4: Add role-based visibility (admin sees all users, trader sees only their own), write basic tests, deploy to staging

You must have:
- Production experience with Next.js, React, Node.js, Prisma, PostgreSQL
- Understanding of RBAC / permission-based data filtering on the API layer
- Experience with financial or trading data (not required but a huge plus)
- Clean TypeScript - no any types, no spaghetti

Not a good fit if:
- You've only built todo apps or personal projects
- You need 2 days of setup time before writing real code
- You treat TypeScript as optional

Budget: Fixed price, $400-800 depending on experience
Timeline: 4 working days from start
Communication: Daily async update + final walkthrough call

We are looking for a contract to hire full stack developer. The position is remote but the candidate has to be located in the continental US and not in California, New York or Illinois. Visa sponsorship is NOT possible for this position since it will be rolled to full time for the right candidate.

Role Overview:
The Full Stack Developer is a key technical contributor responsible for architecting, building, and maintaining robust, scalable web applications across the full technology stack. This role works at the intersection of product innovation and engineering excellence — collaborating closely with cross-functional teams to deliver high-quality software solutions that drive business value. The ideal candidate brings deep technical expertise alongside a passion for research and development, continuously exploring emerging technologies and contributing to the evolution of our platform.

Key Responsibilities:
Design, develop, test, and deploy scalable web applications and APIs across the full stack — from database schema to UI components
Create AI applications where appropriate to enhance the business
Lead architectural decisions and code reviews, ensuring high standards for maintainability, security, and performance
Participate actively in R&D efforts: evaluate new technologies, build proof-of-concept prototypes, and contribute findings to engineering roadmap discussions
Collaborate with product and design teams during sprint planning and discovery sessions to shape technical solutions
Optimize application performance, identify bottlenecks, and implement improvements across front-end and back-end systems
Write comprehensive unit, integration, and end-to-end tests to ensure software reliability
Contribute to internal technical documentation, architecture diagrams, and R&D reports
Mentor junior developers through pair programming, code reviews, and knowledge-sharing sessions
Stay current with industry trends and proactively recommend tooling or process improvements
Participate in on-call rotation and support incident response as needed

Required Qualifications:
Bachelor’s degree in Computer Science, Software Engineering or a closely related field.
5+ years of professional full stack development experience in a tech/software environment
2+ years of experience participating in or leading R&D projects, including prototyping and technical evaluation
Demonstrated experience with agile/scrum methodologies and CI/CD pipelines
Front-end: Proficiency in JavaScript/TypeScript and modern frameworks (React, Vue, or Angular)
Back-end: Strong experience with server-side languages such as Node.js, Python, Java, or Go
Databases: Solid understanding of both relational (PostgreSQL, MySQL) and NoSQL (MongoDB, Redis) databases
Cloud & DevOps: Hands-on experience with cloud platforms (AWS, GCP, or Azure), Docker, and Kubernetes
APIs: Deep knowledge of RESTful API design; familiarity with GraphQL
Version Control: Expert-level proficiency with Git and collaborative branching workflows
Security: Understanding of application security best practices (OWASP, authentication, data encryption)

Preferred Qualifications:
Master’s degree in Computer Science, Software Engineering or like discipline
Relevant certifications (e.g., AWS Certified Developer, Google Professional Cloud Developer)
Experience publishing or presenting R&D findings (internal whitepapers, conference talks, or technical blog posts)
Background working with machine learning integrations, data pipelines, or AI-assisted tooling
Prior experience in a tech startup or fast-paced product engineering environment
Contributions to open-source projects or public technical communities
Experience with WebSockets, real-time systems, or event-driven architecture
Familiarity with serverless architectures and microservices patterns
Knowledge of performance profiling tools and advanced debugging techniques
Exposure to infrastructure-as-code tools such as Terraform or Pulumi

Other Qualifications:
Successfully pass background check for cybersecurity access requirements.
Proven ability to design and implement complex, distributed full stack applications in a production environment
Ability to use AI development tools at an expert level
Strong command of both front-end and back-end development paradigms, with an eye for performance and scalability
Experience contributing to or leading R&D initiatives, including prototyping novel solutions, evaluating new frameworks, and translating research findings into production-ready features
Excellent collaboration and communication skills, with the ability to engage effectively with product managers, designers, and engineering peers
Self-motivated with a growth mindset, comfortable with ambiguity and eager to take ownership of technical challenges
Demonstrated ability to mentor junior and mid-level developers and contribute to a culture of engineering excellence

• Include a link to your GitHub profile and/or website
• Describe your recent experience with similar projects
• Please list any certifications related to this project

We're building an AI writing assistant for students, think Jenni AI + Paperpal. The core pipeline works, but we need a backend/AI specialist to improve accuracy, optimize performance, and prepare it for scale before public launch.


------------------------------------------------------------------------------------------------------------------------------------

Tech Stack:

Backend: FastAPI + async SQLAlchemy 2.0, Python codebase
Data Layer: PostgreSQL, Redis, MinIO/S3
AI Infrastructure: LiteLLM gateway (multi-LLM routing), RAG pipelines

------------------------------------------------------------------------------------------------------------------------------------
What You'll Do:
1-Audit and integrate new evidence sources: Map the gaps in OpenAlex coverage, evaluate 2-3 alternative academic databases, and integrate at least one new source into the retrieval pipeline
2-Build hallucination detection: Implement citation requirement logic so every claim must be traceable to a retrieved document. Add a rejection gate that flags unsupported statements before generation completes. Test and measure citation coverage improvement
3-Fix tone/style drift: Build a coherence checker that scans new paragraphs against the document's existing sections for voice, argument structure, and terminology consistency. Flag mismatches for revision
4-Speed up streaming: Profile the current pipeline for bottlenecks, reduce LLM latency (optimize batching, caching, routing), and improve streaming UI responsiveness. Target: faster first-token output
5-Improve evidence ranking: Refine RAG retrieval scoring so the top results are actually the most relevant. Test reranking models or implement custom scoring logic
Strengthen quality gates: Add checks in the evaluation framework to catch: missing citations, tone inconsistency, unsupported claims. Adjust thresholds and trigger auto-revision appropriately

And more will be discussed in DM
------------------------------------------------------------------------------------------------------------------------------------
You Need:

Production LLM pipeline experience (shipped, not experimental)
1- RAG architecture expertise
2-Python, FastAPI, PostgreSQL, Redis
3-Work with LLMs as infrastructure (APIs)
4-Concrete metrics from previous work (latency, relevance, cost improvements)
5-Know what's possible with existing LLM APIs vs. custom engineering
6-Portfolio: Share GitHub profile\ repo, previous project links, or case study showing your work. We need to see real code

------------------------------------------------------------------------------------------------------------------------------------
Nice to Have:
LiteLLM or multi-provider LLM routing
Vector database tuning
Academic/research writing tools experience (Jenni, Paperpal, similar)
EdTech background
FastAPI at scale

Skills: Python, PostgreSQL, Redis, Backend Development, FastAPI, AI Development, LLM Integration

We're a personal injury law firm in Fort Worth, TX that has built a custom case management platform called Pulse to replace our current software. The app is approximately 90% complete and we need a skilled developer to get it across the finish line and live.

The Stack
Next.js 14 (App Router), TypeScript, Prisma, Supabase (PostgreSQL), Tailwind CSS, deployed on Vercel.

What's Already Built
The core is done — database schema, 26+ API routes, authentication (NextAuth), role-based access, a full case management UI with 20+ pages, and integrations with SharePoint (Microsoft Graph), QuickBooks, Dialpad, Resend, and an AI document generation system. A data migration script from our existing software (FileVine) has been built and tested on a trial run.

What Needs to Finish

Wire up remaining pages and fix a handful of display/data issues
Complete Clerk auth migration and set up row-level security (RLS) in Supabase
Bland.ai voice agent integration (account setup + webhook)
Cleanup of demo/hardcoded data on a few pages
Own the final production data migration from FileVine at go-live
Final QA, UAT with ~26 staff members, and go-live support

Ideal Candidate

Strong Next.js + TypeScript (App Router, server actions, route handlers)
Comfortable with Prisma and PostgreSQL
Has shipped real production apps, not just side projects
Can read existing code and work within it — this is NOT a greenfield build
Bonus: experience with legal tech, Microsoft Graph API, or Supabase RLS

Scope & Timeline
This is a contract engagement. Estimated 40–80 hours depending on your pace. We'd like to be live within 6 weeks. Possibility of an ongoing retainer for maintenance after launch.
To Apply
Share 2–3 examples of production apps you've built or contributed to, ideally with Next.js. In your proposal, briefly describe how you'd approach inheriting a 90%-complete codebase — specifically, what you'd do in the first few hours before writing a single line of code. Proposals that don't answer this will not be considered.
Technical Assessment
Shortlisted candidates will be sent a short code challenge (30–60 min) involving a buggy Next.js API route similar to what you'll be working in. No setup required — just read, fix, and add a small feature. We'll review your submission before any interview.

We're building a web-based Laboratory Information System (LIS) with 6 core modules: Sample Traceability, Chain of Custody, Audit Trails, QC Management (Westgard rules + Levey-Jennings charts), Result Verification & Sign-out, and HIPAA Data Security.

What you'll build:
A fully functional clinical lab portal — real-time dashboards, barcode/QR scanner integration, multi-level result sign-out workflows, immutable audit logs with hash chaining, AES-256 encryption, and role-based access control.

Tech we expect:
React or Vue.js · Node.js or Python (FastAPI/Django) · PostgreSQL · Docker/Kubernetes · HL7/FHIR integration · HIPAA-compliant cloud (AWS or Azure)

You must have:

Prior HIPAA-compliant healthcare or clinical software experience
5+ years full-stack development
Ability to sign a BAA (Business Associate Agreement)
Strong English communication

ZEIL is on a mission to become New Zealand’s most loved job marketplace, and to do that we need incredible talent. Talent that’s driven by a shared desire of becoming the best and
working with the best. We embrace the rich diversity of Aotearoa, building teams that reflect varied cultures and backgrounds. As helpful disruptors, we celebrate progress and advocate for the success of our members. At ZEIL, we value new perspectives and believe in making a meaningful impact. If you’re passionate about growth and inclusivity, we encourage you to join our journey.

Mō Te Tūranga – About The Role
We’re looking for a Senior Software Engineer with a platform engineering focus to lead the architecture, reliability, and evolution of ZEIL’s cloud infrastructure and developer experience. This role sits at the intersection of infrastructure, software design, and engineering enablement — you’ll own the technical direction of our AWS platform, champion infrastructure-as-code, and drive innovation in how our engineers build and ship software. You’ll also be a pioneer in integrating AI and agentic workflows into our engineering processes, helping the team work smarter and move faster. If you care deeply about automation, reuse, cost efficiency, observability, and giving engineers the best tools and platforms to do their work, this role is for you.

What You’ll Do

Own and evolve ZEIL’s AWS infrastructure, with a focus on cost optimisation, reliability, observability, and scalability.
Design and maintain reusable, templated Terraform modules so new services and processes can be spun up quickly using proven, familiar architecture. We aim for 100% of our infrastructure in Terraform.
Architect robust backend and platform systems leveraging deep knowledge of SQS, Lambda, EventBridge, ECS, and broader AWS services.
Build and maintain GitHub Actions pipelines, including reusable workflow templates that streamline build and deployment across multiple repositories.
Champion observability across all services — ensuring comprehensive logging, metrics, tracing, and alerting are built in from day one, not bolted on after.
Drive adoption of AI-powered agentic workflows to help engineers streamline their day-to-day development, testing, and operational tasks.
Build and maintain data ingestion pipelines using TypeScript, Python, and Bash scripting.
Manage and optimise our Docker-based containerised workloads, ensuring consistent and reproducible environments across development, CI, and production.
Collaborate with developers and business stakeholders to understand complex requirements, translating them into scalable platform solutions.
Troubleshoot and resolve advanced technical challenges across infrastructure, CI/CD, and backend systems.
Stay at the forefront of platform engineering, DevOps, and AI tooling best practices, continuously elevating the team’s capabilities.

Key Responsibilities

Infrastructure Ownership: Architect, maintain, and optimise our entire AWS estate. You are the go-to person for infrastructure decisions, cost management, and platform reliability.
Terraform & IaC: Champion 100% infrastructure-as-code. Build and curate a library of reusable Terraform modules that accelerate service creation and enforce consistency.
CI/CD & Developer Experience: Own our GitHub Actions pipelines and reusable workflow templates. Continuously improve build, test, and deployment automation across all repositories.
AI & Agentic Workflows: Lead innovation in AI-assisted engineering. Identify opportunities to integrate agentic AI tools into development workflows, code review, testing, and operations.
Backend & Data Pipelines: Design, development, and implementation of backend integrations using APIs (e.g., REST APIs) with a strong focus on the .NET framework (C#, ASP.NET). Design and build data ingestion and processing pipelines. Ensure backend systems are performant, observable, and well-integrated.
Architecture & Technical Leadership: Set technical direction at both the infrastructure and software design level. Mentor engineers and drive architectural standards across the organisation.
Observability & Reliability: Establish and maintain observability standards across all services. Ensure teams have the logging, metrics, tracing, and alerting they need to confidently operate and debug production systems.

Key Requirements
Eligible to work in New Zealand.
Bachelor’s Degree in Computer Science, Engineering, or a related field — or equivalent combination of education and relevant experience.
Deep, hands-on experience with AWS services, particularly SQS, Lambda, EventBridge, ECS, S3, API Gateway, and OpenSearch.
Strong expertise in Terraform, including designing and maintaining reusable module libraries and managing state at scale.
Proven experience building and maintaining CI/CD pipelines in GitHub Actions, including reusable workflow templates.
Proficiency in TypeScript, Python, and Bash scripting.
Strong experience with databases: DynamoDB, PostgreSQL, and OpenSearch.
Demonstrated ability to drive cost optimisation across cloud infrastructure.
Strong experience with Docker for containerised workloads across development, CI/CD, and production environments.
A passion for observability — experience implementing logging, metrics, tracing, and alerting to ensure production systems are transparent and debuggable.
Experience with or strong interest in AI/ML tooling and agentic workflows for developer productivity.
Exceptional problem-solving and analytical skills, capable of leading solutions for complex technical challenges.
Strong written and verbal communication skills, with the ability to convey complex technical concepts clearly.

Beneficial Skills & Experience
Experience with Kubernetes and orchestration tools such as Amazon EKS.
Familiarity with message queuing systems beyond SQS (e.g., Kafka, RabbitMQ).
Experience with Google Cloud Platform (GCP) services alongside AWS.
Knowledge of data engineering tools and practices (e.g., BigQuery, ETL/ELT pipelines).
Experience with eCommerce or payment technologies (e.g., Stripe) and email platforms (e.g., SendGrid, HubSpot).
Hands-on experience migrating infrastructure to code from manual/ClickOps setups.
Experience with observability platforms such as CloudWatch, Datadog, Grafana, or similar

Please start your proposal with the word CHALK so I know you read this carefully. Proposals that do not start with CHALK will not be reviewed.

I have a fully working frontend prototype that needs to be wired to a real backend. Looking for a senior full-stack developer for a 6–8 week fixed-price engagement, starting with a 1–2 day paid trial task.

The product: A digital platform for private golf clubs to run wagering events (Calcutta auctions, Nassau game tracking, member games, parimutuel pools). Twelve game types are already built and working in the demo.

Current state:

- Frontend is built — HTML, CSS, JavaScript, no framework
- Data currently lives in browser localStorage
- All UI/UX, design system, and game logic are complete
- Live demo at chalkandsettle.com

What I need built:

1. Supabase backend — Postgres schema for games, players, scores, clubs, subscriptions. Row-level security for multi-tenant club isolation. Real-time subscriptions for live auction bid updates and live scoring.

2. Authentication (Clerk) — Three roles: club admin, tournament director, club member. Member access via QR code without account creation.

3. Stripe subscription billing — Annual club subscription ($1,999–$2,399/year). Per-event trial option ($399/event). Webhook handling for subscription state.

4. Wire the existing frontend to the backend — Replace all localStorage calls with Supabase. Hook up real-time updates across admin, display board, and member views. Maintain existing UI/UX exactly as-is.

5. Deploy + monitor — Vercel deployment with proper environment management. Sentry error tracking. Basic logging.

What I'll provide: Full demo codebase (clean, well-organized HTML/CSS/JS), complete config schema reference document defining all data structures, design system tokens, detailed walkthrough, responsive feedback during the build.

Engagement structure:

Step 1 — Paid trial task ($200–$400, 1–2 days). Before committing to the full project, the finalist will complete one small, scoped task (e.g., set up a fresh Supabase project and demonstrate row-level security between two test clubs). This is paid work, not spec work. Win or lose the project, you get paid for the trial.

Step 2 — Full engagement. Milestone-based payments through Upwork escrow. 25% to start, then 25% chunks tied to deliverables, final 25% on completion and acceptance.

Hard requirements (proposals missing any of these will not be considered):

- Portfolio link or GitHub showing similar work
- At least one Supabase + Stripe project shipped to production
- 90%+ Job Success Score on Upwork
- Fluent English, written and spoken
- Minimum 4 hours of overlap with US Eastern Time, Monday–Friday
- Willingness to do a video call before any work begins

About me: I built the entire prototype solo without prior engineering experience, using AI-assisted development. I understand the product deeply but am hiring for the production backend work specifically. I'll be a responsive, technical-enough partner — not someone who'll disappear and expect you to figure everything out.

Timeline: Looking to start the paid trial within 4–6 weeks. Want to evaluate candidates now and lock in the right person.

Red flags that will get you rejected immediately: Asking for full payment upfront. Bidding wildly low ($2K total or less — I know what this work costs and a low bid means you're either lying about scope or planning to disappear). Boilerplate proposals that don't reference specifics from this post.

Detailed materials (codebase walkthrough, schema reference, design tokens) will be shared with shortlisted candidates after the initial video call.

We are moving beyond simple "if-this-then-that" automations. We are building a sophisticated, Agentic AI System for our restaurant ordering platform. We need an architect who can build an autonomous agent in n8n that doesn't just follow a path, but "reasons" through tasks, manages its own state, and interacts directly with our production database and CRM (GoHighLevel).

The Project (Phase 1: Agentic Foundation)
Your goal is to build an n8n pipeline where an AI Agent acts as the bridge between our PostgreSQL database, our GoHighLevel CRM, and our Next.js frontend.

Key Deliverables:

Autonomous Tool-Use: Implement an n8n AI Agent node that uses specific tools to query PostgreSQL to verify restaurant data and check onboarding status in GoHighLevel.

Structured Output & Validation: The agent must use JSON Schema enforcement. It must output strictly structured JSON to update database records and trigger frontend state changes in Next.js.

Self-Correction Logic: If a tool returns an error (e.g., a query fails or a GHL contact isn't found), the agent must "reason" through the error and retry with corrected parameters (Max 3 iterations) before failing gracefully.

CRM Synchronization: Ensure that data flows bidirectionally between the Postgres DB and GoHighLevel tags/custom fields based on the agent's logic.

Security-First Architecture: No raw SQL injection. You will build defined tools/API endpoints for the agent to interact with the database securely.

Our Tech Stack
Automation: n8n (Advanced AI Agent nodes, Tool nodes, Sub-workflows).

AI Models: Claude 3.5 Sonnet (Primary reasoning) & GPT-4o.

Database: PostgreSQL (AWS RDS).

CRM: GoHighLevel (API-based automation).

Full Stack: Node.js & Next.js.

What We Are Looking For
Agentic Experts: You have built workflows where the AI "decides" which tool to use next.

n8n Power Users: Deep expertise in n8n error handling, "Wait" nodes, loops, and custom JS function nodes.

JSON Schema Ninjas: You know how to prevent AI hallucinations by forcing strict output formats.

CRM Integrators: Specific experience with the GoHighLevel API and syncing CRM data with external SQL databases.

How to Apply
To filter out generic/AI-generated applications, please answer the following technical questions:

Handling Hallucinations: How do you typically handle looping and hallucinations when an AI Agent is querying a PostgreSQL database? How do you ensure it doesn't "invent" a database schema?

The "Agentic" Proof: Briefly describe a multi-step agentic system you have built in n8n where the AI had to use at least two different tools to complete a task. (Bonus: Attach a Loom walkthrough or screenshot).

CRM Flow: How do you handle rate-limiting or synchronization conflicts when n8n is updating both a SQL database and GoHighLevel simultaneously?

Availability: Confirm you can start immediately on Phase 1.

I want to build a production-ready web dashboard and I am looking for a full-stack partner who can take the idea from wireframe to deployment using React on the frontend, Django on the backend and clean, well-documented REST APIs in between.

Scope of work
• Design the data model and PostgreSQL schema that will feed the dashboard’s widgets and charts.
• Implement the Django backend with token-based user authentication, role management and a reusable REST layer.
• Create a React SPA that consumes those endpoints, renders dynamic charts/tables and adapts gracefully to desktop and mobile.
• Package the solution for easy deployment (Docker or similar) and hand over a Git repository with clear setup instructions.

I am comfortable discussing architecture decisions and will contribute code where I can, but I need your expertise to make sure the project is structured correctly and delivered on schedule. Clean code, concise commits and unit tests for critical logic will be part of the acceptance criteria.

If you have solid experience delivering dashboards with React, Django and APIs, let’s talk about milestones and start building.

Skills: Python, Django, Node.js, PostgreSQL, React.js, Docker, Full Stack Development, REST API

We are seeking an experienced Python developer to work on a project involving data processing and analysis. The ideal candidate will have a strong understanding of Python programming and experience with data structures and algorithms. Responsibilities include developing efficient code, troubleshooting issues, and collaborating with the team to ensure project goals are met. Familiarity with Django and PostgreSQL is a plus.

HotelOS is an AI-powered hotel operations platform built by a working hotelier — someone who lives the broken processes every day. The mission is simple: replace the disconnected Excel sheets, email chains, and manual workflows that hotels rely on with a single platform that actually works.

The platform is already partially running in production at a live hotel. Every morning at 8:30 AM an automated Python script reads the night audit, processes it through Claude AI, and delivers a formatted executive briefing to the GM's inbox. This is a real product with real data — not a concept.

We are now hiring a senior developer to build Stage 1 of the full platform — three connected modules that work together to create a product we can sell to hotels immediately.

• PDF invoice arrives by email. Using Claude API, how do you extract the data, match it to a PO, and what happens when it doesn't match?"

We are a Colorado-based telecommunications contractor looking to add a part-time contractor to our team for approximately 32 hours per week. We are looking for someone who is available online during our normal business hours, Monday through Thursday, and who can become an ongoing technical resource for our business.

This role is primarily a development, data automation, and internal tooling role. We have a heavy ongoing need to push, pull, transform, store, recall, and report on data across multiple platforms and systems. A large part of the work will involve using APIs to move data from one system to a central location, transform it, store it, and then send it to another system or make it available through dashboards, reports, automations, or internal web apps.

We are looking for someone who is comfortable working across APIs, Python, databases, automation platforms, and lightweight web applications. The ideal person has a strong developer mindset and can help us build practical tools that improve workflows, reduce manual work, and make data easier to access and use.

What You’ll Work On

You may help us with projects such as:

Building and maintaining API integrations between different platforms
Pulling data from third-party systems, transforming it, and storing it reliably
Pushing cleaned or structured data into other systems through APIs
Creating backend workflows and automation scripts
Building lightweight internal web apps, dashboards, portals, or admin tools
Working with databases to store, query, update, and recall data
Improving existing automations and workflows
Helping design better ways for users to interact with business data
Creating reports or data views that make information easier to understand
Using AI tools where helpful to parse emails, PDFs, documents, or unstructured data
Supporting and improving existing systems built with Make.com, Python, MongoDB, AWS S3, and similar tools
Core Skills We’re Looking For

We are looking for someone with experience in several of the following areas:

Strong API experience, including REST APIs, authentication, pagination, rate limits, webhooks, retries, logging, and error handling
Python development experience for manipulating, transforming, storing, and recalling data
Experience working with modern databases such as MongoDB, PostgreSQL, MySQL, DynamoDB, or similar
Ability to build backend services, scripts, and data workflows
Ability to build simple but useful frontend interfaces or internal web apps
Experience moving data between SaaS platforms, databases, cloud storage, and internal tools
Experience with automation platforms like Make.com, Zapier, n8n, Pipedream, or similar
Familiarity with AWS S3, data lakes, or cloud-based storage
Familiarity with GitHub, Terraform, Ubuntu/Linux servers, or basic cloud infrastructure is a plus
Experience with AI tools such as GPT, Claude, Cursor, or similar
Experience with app-building tools such as Base44, Lovable, Bolt, Replit, or similar is a plus
Ability to write clear documentation and build systems that are maintainable
Current Tools and Platforms

Some of the tools and platforms we currently use include:

Make.com
MongoDB
AWS S3 data lake
GitHub
Terraform
Microsoft 365
Monday.com
QuickBooks Online
Various SaaS platforms with APIs
GPT/Claude-style AI tools for parsing and automation

You do not need to be an expert in every platform we use. The most important thing is that you are strong with APIs, data manipulation, automation, databases, and practical software development.

Ideal Candidate

The ideal candidate is someone who:

Thinks like a developer, not just a no-code automation builder
Can understand messy business processes and turn them into reliable technical workflows
Is comfortable reading API documentation and figuring out how to connect systems
Can use Python to clean, transform, and move data
Can build practical internal tools and web apps when a simple interface would solve a problem
Understands how to store data in a way that can be queried, reported on, and reused later
Communicates clearly and documents their work
Can work independently but is also comfortable collaborating with a small business team
Is comfortable using AI tools to speed up development, research, parsing, and workflow design
Cares about building reliable, maintainable solutions rather than quick hacks
Schedule and Availability

This is an ongoing contractor role for approximately 32 hours per week.

We are looking for someone who can be available online during our business hours (MT), Monday through Thursday, in a way that allows for regular communication, project planning, and collaboration.

To Apply

Please briefly share your relevant experience with APIs, Python, databases, automation workflows, and internal web apps. Include a few examples of similar projects you have built and your availability during Monday–Thursday business hours.

We are looking for someone who can become a reliable long-term technical partner for our business as we continue improving how we move, store, automate, and use data.

I need an experienced server/security specialist to fix database security vulnerabilities on my WordPress website hosted on SiteGround.

A vulnerability scanner detected the following:

* Publicly exposed MySQL port (3306)
* Publicly exposed PostgreSQL port (5432)
* Multiple Oracle MySQL critical patch update vulnerabilities (outdated version detected)
* Database instance/version disclosure

Website details:

* WordPress site
* Hosted on SiteGround

What I need done:

* Audit current database exposure and confirm what is actually public
* Restrict or close public access to MySQL (3306) and PostgreSQL (5432) if not required
* Patch/update MySQL if necessary
* Verify WordPress functionality after changes
* Re-scan or validate vulnerabilities are resolved
* Ensure no downtime or data loss

Requirements:

* Strong experience with SiteGround hosting
* WordPress infrastructure/security experience
* MySQL/PostgreSQL hardening experience
* Firewall/network security knowledge

Please include:

1. Your experience with SiteGround security hardening
2. Your approach to fixing this
3. Estimated turnaround time

Looking for someone who can start ASAP.

We’re looking for a skilled Back-End Developer with at least 3 years of professional experience building scalable web applications and APIs. You’ll play a key role in developing the server-side systems that power a fast-moving platform in the transportation/logistics space.

This is an opportunity to join a growing team where your work will have direct impact. We value developers who take ownership, solve problems efficiently, and care about writing maintainable code.

Responsibilities
• Build and maintain backend services using Node.js and Express.js
• Design, develop, and maintain secure, scalable REST API endpoints
• Work with real-time systems using WebSocket technology
• Design efficient database schemas and relational data models
• Write optimized SQL queries and maintain PostgreSQL databases
• Integrate third-party APIs and external services
• Troubleshoot production issues and improve backend performance
• Collaborate with front-end developers, designers, and stakeholders
• Participate in architecture discussions and improve development processes
Requirements
• 3+ years of professional backend development experience
• Strong hands-on experience with Node.js and Express.js
• Proven experience building and maintaining REST APIs
• Understanding of WebSocket connections and event-driven systems
• Experience with database design and data modeling
• Strong experience using PostgreSQL
• Familiarity with authentication, authorization, and security best practices
• Comfortable working in startup or fast-paced environments
• Strong communication skills and ownership mindset
Bonus Skills
• Experience with cloud platforms such as AWS
• Experience with queues/background jobs
• Familiarity with Docker and CI/CD pipelines
• Exposure to logistics, transportation, or marketplace platforms
• Familiarity with Laravel
• Ability to leverage AI tools while maintaining accountability for code quality

PERN Stack Developer – Dental Practice Management Platform

We're building a comprehensive dental practice management application and looking for an experienced developer to join us.


What you'll do:
- Work on a dockerized PERN stack application (PostgreSQL, Express, React, Node.js) deployed on AWS.
- You'll be writing and shipping code regularly, maintaining infrastructure, and helping us scale a product that's already serving paying customers.


What we're looking for:

- Strong hands-on experience with the PERN stack
- Comfortable with Docker and AWS deployments
- Active Cursor license and genuine proficiency using it as your daily driver
- Healthcare software experience is a plus
- Available during US Eastern hours, including weekends

• Describe your recent experience with similar projects
• Include a link to your GitHub profile and/or website
• What frameworks have you worked with?
• Describe your approach to testing and improving QA

Project Title:
Build a SnapSell-style Paywall Platform for Web, iOS and Android

Project Description:

I want to build a SnapSell-style digital content paywall platform where creators can upload files, set a price, generate paid access links, and buyers can unlock the content after a one-time payment.

The platform should work on:

- Web
- iOS
- Android

The goal is similar core functionality to SnapSell, but with my own custom branding, custom UI, and a more premium/luxury design. Do not copy SnapSell’s logo, branding, copyrighted UI, or assets. SnapSell should only be used as a functional reference.

Preferred design direction:
- black + gold luxury style
- or black + white + red + gold premium style
- modern, clean, attractive, high-converting UI

The final brand name and logo are not ready yet. A temporary text-based placeholder can be used during development.

Core Flow:

Creator uploads content → Creator sets price → System generates paid link → Buyer opens paywall page → Buyer pays → Content unlocks securely → Buyer can access purchased content again later after login.

Core Features:

1. User Accounts
- Creator registration/login
- Buyer registration/login
- Password reset
- Basic profile settings
- Purchased content linked to buyer account
- Uploaded content linked to creator account

2. Creator Dashboard
Creators should be able to:
- upload files
- manage uploaded files
- set prices
- generate paid access links
- view paid links
- view sales
- view earnings
- view basic statistics

3. Content Upload
Creators should be able to upload:
- videos
- images
- PDFs
- ZIP files or similar digital downloads

For the MVP, the file size limit can be around 500MB per file, unless you recommend another limit.

Files must be stored securely using private storage, preferably AWS S3 or a similar secure storage solution.

4. Teaser / Preview Mode
Before payment, buyers should see a teaser or preview page.

After successful payment, the buyer should unlock the full content.

5. Paid Link / Paywall System
The system should allow creators to:
- upload content
- set a price
- generate a unique paid link
- share the link with buyers

The buyer page should include:
- teaser / preview
- price
- payment button
- secure unlock after payment

6. Payment Integration
Payments should support one-time payments only for the first version.

Preferred payment system:
- Stripe Checkout or Stripe Payment Element for web
- Stripe webhooks for secure payment confirmation

Important:
- Payment confirmation must happen through secure webhook verification
- Content should only unlock after successful payment confirmation
- Stripe test mode and live mode should be configured
- Payment records should be saved in the database
- Duplicate webhook events should be handled safely

For iOS and Android, please explain your recommended payment approach and how you will handle Apple App Store and Google Play rules.

7. Protected Content Access
Paid files must not be publicly accessible.

The system should use:
- private file storage
- signed URLs or token-based access
- purchase validation before access
- short-lived access URLs
- logged-in buyer access for purchased content

Buyers should be able to log in later and access purchased content again on all their devices.

8. Admin Dashboard
The admin dashboard should include:
- manage users
- manage creators
- manage buyers
- manage uploaded content
- view payments
- view transactions
- view platform revenue
- disable/delete content if needed
- disable users if needed
- basic analytics
- basic payout overview

9. Creator Payouts
For the MVP, manual creator payouts are acceptable.

The admin should be able to see:
- sales per creator
- earnings per creator
- payout status

Automatic Stripe Connect creator subaccounts and automatic commission splitting can be added later as a separate future phase.

10. Web App
The web version should be responsive and work on:
- desktop
- tablet
- mobile browser

The web version should include:
- public landing page
- creator signup/login
- buyer signup/login
- creator dashboard
- buyer paywall page
- buyer library / purchased content page
- admin dashboard

The landing page should be simple, clean, and conversion-focused. It is useful, but not the main priority. The main priority is the working paywall system.

11. iOS and Android Apps
The project should include mobile apps for:
- iOS
- Android

Preferred mobile framework:
- Flutter preferred
- React Native is also acceptable if you explain why

The mobile apps should use the same backend API as the web app.

The mobile apps should include:
- login/register
- buyer access to purchased content
- paid content viewing
- mobile-friendly content access
- creator dashboard or basic creator functionality if possible

Please clearly explain what is included in the mobile apps and what is not included.

12. Affiliate / Partner Program — Optional Separate Quote
Affiliate should not block the core MVP.

Please quote this separately.

Possible affiliate features:
- referral links
- track referred users
- commission after successful payment
- admin can set commission percentage
- affiliate can view earned commission
- admin can view affiliate earnings

13. MLM — Future Phase Only
Full MLM is not required for the first version.

Please structure the backend so that MLM or multi-level commission logic can be added later.

If you offer a basic MLM version, quote it separately and clearly describe:
- number of levels
- commission logic
- admin controls
- payout logic
- refund handling

The main priority is the core paywall platform first. Affiliate and MLM should be separate modules or future milestones.

Recommended Tech Stack:

You may recommend your own stack, but please explain your choice.

Possible stack:
- Web: React.js / Next.js
- Mobile: Flutter or React Native
- Backend: Node.js / NestJS, Django, or Laravel
- Database: PostgreSQL preferred, MySQL acceptable
- Storage: AWS S3 private bucket or similar
- Payments: Stripe Checkout / Stripe Payment Element + webhooks

Technical Requirements:
- Clean backend API
- REST or GraphQL
- Secure authentication
- Secure file access
- Stripe webhook handling
- Database structure
- Responsive web frontend
- Mobile apps using same backend
- Admin dashboard
- Creator dashboard
- Deployment documentation
- GitHub source code delivery

Deliverables:
- Web application
- iOS app source code
- Android app source code
- Backend source code
- Admin dashboard
- Creator dashboard
- Buyer paywall page
- Buyer purchased content page
- Database setup
- Secure file storage setup
- Stripe integration
- Webhook setup
- Deployment instructions
- Environment variable documentation
- GitHub repository access
- Full source code
- 14–30 days bug fixing after delivery

Suggested Milestones:

Milestone 1:
UI/UX design, architecture, database planning, key screens

Milestone 2:
Backend setup, database, authentication, user roles

Milestone 3:
Content upload, private storage, file validation, teaser/preview mode

Milestone 4:
Paid link generation, buyer paywall page, pricing logic

Milestone 5:
Stripe payment integration, webhook verification, payment records

Milestone 6:
Protected content unlock, signed URLs/token access, buyer re-access after login

Milestone 7:
Creator dashboard and admin dashboard

Milestone 8:
iOS app core functionality

Milestone 9:
Android app core functionality

Milestone 10:
Testing, deployment, documentation, GitHub handover

Optional Milestone 11:
Affiliate / partner program

Optional Milestone 12:
MLM / multi-level commission system

Payment Rules:
- All communication must stay inside Freelancer.com
- All payments must stay inside Freelancer.com
- No external payments
- No full upfront payment
- Milestones are only released after testing
- Final payment only after full source code, GitHub access, deployment instructions, and working demo are delivered

Please Answer These Questions in Your Proposal:

1. Have you built a paywall, paid content, creator monetization, marketplace, affiliate, or micropayment platform before?
2. Which tech stack would you use and why?
3. Would you use Flutter or React Native for iOS and Android?
4. Will web, iOS, and Android use the same backend API?
5. How will you securely store uploaded files?
6. How will you protect paid files from unauthorized access?
7. How will you handle Stripe payments and webhooks?
8. How will you handle payments on iOS and Android with Apple/Google rules?
9. Will buyers be able to access purchased content again later after login?
10. What is included in your price?
11. What is not included in your price?
12. How much extra would affiliate features cost?
13. How much extra would MLM features cost?
14. How long will the full Web + iOS + Android MVP take?
15. Will you help with App Store and Google Play submission?
16. Will all source code be pushed to my GitHub during development?
17. How many days of bug fixing are included after delivery?
18. Can you provide a clear fixed-price milestone breakdown?

Budget:

Please quote separately:

A) Web MVP only

Includes:
Upload → Paid Link → Payment → Protected Access → Creator Dashboard → Admin Panel

B) Web MVP + iOS app + Android app

Includes:
All Web MVP features plus mobile apps using the same backend API

C) Web MVP + iOS/Android app + basic affiliate system

D) Future MLM extension

Important:

Please do not send a generic proposal.

I need a clear technical plan, fixed price, timeline, and milestone breakdown.

The core product must work first:

Upload → Paid Link → Payment → Protected Access → Creator Dashboard → Admin Panel → iOS/Android App

Affiliate and MLM can be discussed as separate future phases.

Skills: Mobile App Development, PostgreSQL, Laravel, Stripe, Web Development, Payment Gateway Integration, React Native, Flutter, Next.js

1. Project Overview
We are building a content-driven commerce platform where users discover and purchase products through short-form video content.

The platform combines elements of:

short video platforms (Reels / TikTok)
influencer storefronts
multi-category marketplace

2. Core Concept
Creators (bloggers) publish short-form videos.

Each video can include linked products.

Users:

watch videos
interact with products
click and proceed to purchase
The platform tracks all interactions and performance metrics.

3. System Architecture (Fixed)
The project must be built using the following infrastructure:

Frontend hosting: Vercel
Code repository: GitHub
Backend / Database / Auth / Storage: Supabase
Tech Stack Requirements
Frontend: Next.js (React)
Hosting: Vercel
Backend: Supabase (serverless logic where required)
Database: PostgreSQL (via Supabase)
Authentication: Supabase Auth
File & video storage: Supabase Storage

4. Core Modules

4.1 Video-to-Shop Module (Highest Priority)
Each video must support:

video upload (creator dashboard)
video playback (frontend)
attaching multiple products (1–5 per video)
product overlay UI during playback
“Buy from video” button
User Flow:
User opens video
Product overlay appears
User clicks product
User navigates to product page (internal or external)
Purchase is completed
Tracking Requirements:
System must track:

video views
product clicks
click-through rate (CTR)
conversions (if available)
revenue (if integrated)


4.2 Marketplace Module
The platform must include a multi-category marketplace.

Main Categories:
Beauty & Personal Care
Fashion
Health & Supplements
Fitness & Sports
Home & Living
Electronics & Gadgets
Food & Beverages
Kids & Baby
Pets
Marketplace Sections:
Trending
Recommended (“For You”)
Bestsellers
New Arrivals
Shop from Videos (critical feature)
Filters:
Category
Price
Rating
Brand
Creator

4.3 “Shop from Videos” Section
This is a core feature.

Requirements:

grid of videos
each video displays linked products
ability to purchase directly from video
video-first browsing experience

4.4 Creator Profile Page (Public)
Each creator must have a public page including:

profile (photo, bio)
video feed (Reels-style layout)
products linked to videos
reviews section
Important UX Requirement:
Video content must appear before product listings.

4.5 Creator Dashboard
Creators must be able to:

upload videos
attach products to videos
manage linked products
view analytics:
views
clicks
conversions
revenue

4.6 Admin Panel
Admin must manage:

creators
products
categories
orders
payouts (optional for MVP)
video moderation

5. Data Structure (High-Level)
The system must include entities:

Users
Creators
Videos
Products
Categories
Click events
Orders (if integrated)

6. Analytics System
Video-level:
views
clicks
CTR
conversions
revenue
Creator-level:
total revenue
conversion rate
Platform-level:
total GMV (sales volume)
top creators
top products

7. Integrations (Optional / Phase 2)
External marketplaces (Shopify or others)
Payment systems (Stripe or similar)
UTM / tracking system

8. MVP Scope (Phase 1)
The first version must include:

video upload and playback
attaching products to videos
“Buy from video” functionality
basic marketplace (categories + product grid)
creator dashboard (basic analytics)

9. Non-Functional Requirements
clean, modern UI (mobile-first)
fast video loading
scalable architecture
ability to extend features

10. Important Product Note
This is NOT a standard e-commerce website.

This is a content-first commerce platform, where:

video is the primary entry point
products are secondary
UX must prioritize discovery through content

11. Future Scalability (Important)
The system must be designed to allow:

migration to external storage/CDN (if needed)
scaling of video delivery
extension of analytics

12. Deliverables
fully functional MVP
deployed on Vercel
connected to Supabase
clean codebase in GitHub
basic documentation

13. Candidate Requirements
experience with marketplaces or social platforms
strong understanding of UX
experience with video-based features (preferred)

14. Application Requirements
Please include:

relevant projects
proposed approach
timeline for MVP
estimated budget

We are looking for a skilled Backend Developer to join our team and help build a robust, scalable, and high-performance web application. The ideal candidate has strong experience in backend technologies, API development, and database management.

You will be responsible for designing, developing, and maintaining server-side logic, ensuring high performance and responsiveness to requests from the frontend.

Responsibilities:

Develop and maintain backend services and APIs.
Design and optimize database structures.
Ensure application performance, scalability, and security.
Integrate third-party APIs and services.
Collaborate with frontend developers and other team members.
Debug and resolve technical issues efficiently.

Requirements:

Proven experience as a Backend Developer.
Strong knowledge of one or more languages: Node.js, Python, PHP, or Java.
Experience with frameworks like Express, Django, Laravel, or Spring Boot.
Solid understanding of RESTful APIs and microservices architecture.
Experience with databases: MySQL, PostgreSQL, MongoDB.

Familiarity with version control systems (Git)
Understanding of cloud services (AWS, GCP, or Azure) is a plus

Nice to Have:

Experience with Docker & CI/CD pipelines
Knowledge of authentication systems (JWT, OAuth)
Experience in high-traffic or scalable applications
Experience Level: Intermediate to Expert

How to Apply:

Please include:
Relevant portfolio or past projects.
Brief explanation of your experience with backend systems.
Your preferred tech stack.
Availability and estimated timeline.

The project
We run a cultural events aggregator for Barcelona that scrapes ~250 venues, theaters, cinemas, festivals, and cultural centers, and syncs the data to a CMS. The scraper is built in Python and is partially working — core architecture is solid, but a significant portion of sources are either not scraping at all or producing incomplete data.
We need a developer to complete the original scope: get all sources working reliably and fix data quality on the ones already connected.

What needs fixing
~40 sources currently returning zero events.
These fall into a few clear technical categories: sites behind Cloudflare or anti-bot protection, JavaScript-rendered agendas, institutional portals sharing a common CMS, and two specialty ticketing platforms. The fix approach is different for each group — a good applicant will know what questions to ask.

Data quality issues on already-connected sources.
Several venues are scraping but returning incomplete records: missing or placeholder descriptions, prices not extracted (the price exists but requires following a link), missing images, and missing dates. The issues are concentrated in specific venues with identifiable patterns.

A handful of sources missing from the config entirely.
A few venues that were in the original brief never made it into the scraper config. Most share a CMS with sources that are already partially handled.

Edge cases to handle correctly.
A few sources have quirks: events with no year in the date, recurring shows that should not be deduplicated, and one source that includes events from another city that need to be filtered out.

Fix AI classification for web-scraped sources.
The scraper classifies events into a custom taxonomy (type, subtype, genre, subgenre) using GPT-4o-mini. This works on ticketing platforms but is unreliable on direct web sources. The core issue: the classification prompt is written in the developer's language (Portuguese), not Spanish, which degrades accuracy. The fix involves rewriting the prompt and improving the context passed for low-metadata events.

Add description standardization.
Descriptions are currently copied verbatim from source pages — different lengths, tones, and formats per venue. We need a post-processing step that rewrites each description following platform guidelines: consistent voice, 2-4 sentences, informative (not promotional), preserving factual content. This should only run on real descriptions, never on placeholders.

Tech stack
Core: Python 3.12,
BeautifulSoup4, requests — static HTML extraction
Selenium + undetected-chromedriver — JS-rendered pages
LangChain + GPT-4o-mini (OpenRouter) — AI extraction for complex pages
ScraperAPI — proxy/rendering, already integrated
Supabase (PostgreSQL) — storage
Webflow API v2 — CMS sync
The codebase follows Clean Architecture and is documented for AI-assisted development (Claude Code). Existing venue-specific extractors are well-structured and serve as clear templates for new ones.

Project Overview:
We are building a multi-tenant SaaS CRM platform (marketing agencies + their clients).
The system is currently built on Base44 (React SPA + serverless functions), and we are planning a full migration to a custom infrastructure.

This is NOT a simple project.
We are looking for a senior-level developer who understands SaaS architecture, multi-tenancy, permissions, and integrations.

Current System Includes:

React SPA (Vite-based)
Base44 backend functions (serverless)
Multi-tenant structure (Platform → Agency → Client Workspaces)
Role & permission system
CRM modules:
Leads, Clients, Projects, Payments, Expenses
WhatsApp integration (Green API)
Facebook Lead Ads integration
TikTok Lead Ads integration
Google Ads + Google Calendar integrations
Reporting system (cross-platform metrics)
Automation engine (triggers + workflows)

Goal:
Migrate the entire system from Base44 to a fully independent architecture, including:

Custom backend (Node.js / NestJS / Fastify)
PostgreSQL database (with proper schema design)
JWT-based authentication system
Full replacement of Base44 SDK
API-first architecture
Secure multi-tenant isolation

Scope of Work (Phased):

Phase 1 — Architecture & Foundation

Design full database schema (PostgreSQL)
Implement authentication (JWT, roles, permissions)
Define API structure
Setup server & infrastructure (Docker optional)

Phase 2 — Core Modules Migration

Leads / Clients / Workspaces
Permissions system
Basic CRM functionality

Phase 3 — Integrations

WhatsApp (Green API)
Facebook / TikTok Leads
Google Ads / Calendar

Phase 4 — Reporting & Automation

Metrics ingestion
Reporting engine
Automation workflows

Phase 5 — Final Migration & Deployment

Data migration from Base44
Replace frontend API calls
Production deployment

Technical Requirements:

Strong experience with Node.js (NestJS preferred)
Deep understanding of PostgreSQL (schema design, indexing, performance)
Experience building SaaS platforms (multi-tenant חובה)
Authentication systems (JWT, RBAC)
API design (REST / GraphQL)
Experience with webhooks & third-party integrations
Frontend understanding (React) – not primary but required

Bonus (Big Advantage):

Experience migrating from no-code / low-code platforms
Experience with marketing APIs (Meta, TikTok, Google Ads)
Experience with WhatsApp APIs
DevOps knowledge (Docker, CI/CD)

Important Notes:

This is a long-term project, not a quick fix
Clean, scalable architecture is critical
Security and data integrity are top priority
We will work in phases with clear milestones

To Apply, Please Include:

Links to SaaS systems you built (must include multi-tenant logic)
Short explanation of how you would approach this migration
Your experience with authentication & permissions systems
Your preferred backend stack

Budget:
Flexible – depends on experience and scope (long-term engagement)

Working Style:

We work with AI tools (Claude / Cursor / automation)
Fast iterations, clear communication
Looking for someone who can think, not just execute