Job Description We are an early-stage SaaS platform prepping for an invite-only soft launch. Our application is built using a modern JavaScript stack (React frontend, Node.js backend). We are looking for an experienced, highly disciplined full-stack engineer to evaluate our current architecture for commercial readiness and finish our remaining launch features. This is a paid, contract-based project. We are looking for immediate execution, not co-founders or equity partners. How We Will Begin (Milestone 1: Paid 4-Hour Code Audit & Report) Before writing any feature code, your very first engagement will be a paid, 4-hour architecture diagnostic . We need an objective, expert assessment of whether our current codebase is robust enough for commercial deployment. • 3 Hours - Codebase Ingestion & Diagnostic: Deep-dive into our existing repository files to inspect data flows, state management, backend routing, and technical risk • 1 Hour - Deliverable Report: Provide a concise written summary answering: 1. Is the current architecture commercial-ready? (Yes/No, with specific reasons). 2. What exact refactoring or security measures are required to make it launch-ready? 3. Your fixed-price/hourly quote and exact timeline to complete the remaining tasks below. ________________________________________ Remaining Development Tasks (Post-Audit Scope) Phase 1: UX & Processing Flow • Scan Progress Animation: Redesign a multi-step loading/processing screen sequence (an 8-step pipeline tracking data ingestion, filtering, and quality standards) • Phase 2: Data Quality & Integrity Layer • Live Discovery Panel: Build/finalize a real-time sidebar panel that searches existing platform records as the user types to prevent duplicate database queries • Canonical Entity System & Search Normalization: Implement backend logic and frontend filters to normalize user search inputs (handling inconsistent capitalization, spacing, hyphens, abbreviations, and common aliases) to cleanly map multiple variations to a single canonical database record Technical Requirements • Strong proficiency in React (hooks, state management, clean architecture) • Strong proficiency in Node.js and relational/non-relational database normalization logic • Experience with smooth CSS/JS processing animations • Ability to write clear, actionable technical discovery/readiness reports To Apply Please submit your proposal detailing your experience auditing existing JavaScript codebases for commercial scale. Please explicitly confirm your availability to complete the 4-hour Code Audit & Report milestone.

We are seeking an elite, senior-level Full-Stack Developerto engineer a high-velocity, real-time horse racing web platform from the ground up. The core application loop revolves around a fast-paced snake draft for individual horse races, complete with an integrated, synchronized sub-second live video stream of the race. Following official track results, the platform automatically executes structured financial payouts to users using Venmo/PayPal Payout rails. The entire tech stack must be built utilizing a unified all-JavaScript environment (MERN stack) optimized to eliminate database race conditions and handle volatile real-time traffic spikes. Core Key Milestones & Project Deliverables: Milestone 1: Backend Infrastructure & User Security (15%) Set up a Node.js/Express.js application environment and establish a scalable MongoDB Atlas architecture. Implement user registration, secure JWT/bcrypt authentication, profile management, and verified phone-number registration and/or email registration. Milestone 2: Sports Data Ingestion & Automation (25%) Establish integration with a third-party commercial horse racing API (e.g., Equibase or Sportradar). Build persistent background workers (using BullMQ, Redis, or Node-Cron) to automatically ingest daily race cards, scratches, gate changes, and final official race metrics. Milestone 3: Real-Time Draft & WebRTC Video Integration (40%) Develop an interactive React.js draft dashboard utilizing Socket.io for live, synchronized state management. Implement our custom mathematical snake draft logic featuring a strict 20-second user-pick countdown timer. Build server-side automatic timeout handlers to auto-assign choices if a user disconnects or freezes. Embed an ultra-low latency HTML5 video canvas layer leveraging WebRTC (via WHIP/WHEP protocols) to ingest an RTMP stream from a media server (e.g., Ant Media or Wowza) ensuring sub-500ms video playback. Milestone 4: Venmo Payout Integration & Compliance Guardrails (20%) Seamlessly integrate the official PayPal/Venmo Payouts API to programmatically distribute money from our platform wallet directly to users' accounts and/or phone numbers. This can be worked around using a p2p format, if necessary due to compliance and regulation. Code a reliable system ledger that deducts a custom platform percentage rake prior to finalizing winner distributions. Implement an IP geo-fencing gateway (such as MaxMind GeoIP2) to block real-money contest entry from illegal jurisdictions. Technical Stack Requirements: Frontend: React.js (Next.js preferred), Tailwind CSS, Socket.io-client. Backend: Node.js, Express.js, Socket.io, Node-Cron or BullMQ.Database & Memory: MongoDB (Mongoose), Redis (for lightning-fast leaderboard and timer caching). Streaming Protocols: WebRTC, WHIP/WHEP, RTMP stream handling. Integrations: PayPal/Venmo Payouts SDK, REST/JSON Sports Data APIs, GeoIP lookup utilities. Strict Operational Code Quality Terms: 1. Repository Ownership: All codebase code and architectural modules must be pushed to our private company GitHub repository at least three times a week. Milestone releases will only be approved after clean local compilation and inspection. 2. IP Assignment: By applying for and accepting this position, you acknowledge that 100% of the developed application logic, system schemas, and code components represent a dedicated Work-for-Hire owned exclusively by the client. 3. ACID Database Transactions: You must guarantee and demonstrate via unit testing that the MongoDB schema handles marketplace swaps and concurrent drafting selections via absolute ACID Transaction Sessions to totally prevent double-spend or double-draft race conditions. To Apply, Please Answer the Following 3 Screening Questions: 1. How do you plan to structure the server environment and React architecture to keep a 30-second live countdown timer perfectly synced down to the millisecond for 4 or more different players concurrently browsing via WebSockets? 2. Please share a summary or a live link of a project you built from scratch that handled live WebRTC ultra-low-latency video delivery or complex stream handshakes. 3. What is your specific experience with financial ledger architectures? Explain how you intend to protect the MongoDB operations against multi-user transactional conflicts.

Full-stack developer (Node.js/TypeScript, React) with cloud/DevOps experience, and comfortable with PostgreSQL, S3-compatible storage, and Google Cloud service accounts. This is to support solid mobile app built for dual platforms, with a full ML comparison pipeline, and the supporting infrastructure. Initial Task will be an infrastructure migration (DevOps). Second task will be several front end and backend app updates.

We are seeking a skilled developer to complete a nonprofit camp search platform utilizing Next.js and PostgreSQL. The project aims for a targeted launch date of November 1, 2026. Your role will involve developing features, optimizing performance, and ensuring an intuitive user experience. If you are passionate about creating impactful solutions for nonprofits and have expertise in modern web development technologies, we want to hear from you!

JOB TITLE Build a React/Next.js Interactive Hockey Jersey Customizer Using an Existing SVG PROJECT OVERVIEW I’m looking for an experienced React/Next.js developer with strong SVG and interactive graphics experience to build a web-based hockey jersey customizer. I have a professionally designed SVG showing the front and back of a hockey jersey. The jersey artwork and silhouette must remain visually accurate. This is not a request to generate a jersey using CSS or approximate it with basic shapes. The supplied SVG must be used as the foundation. The goal is to let customers customize individual jersey sections, add graphics and numbers, create body and sleeve stripes, and save or download their completed design. The experience should feel similar to established sports uniform customizers while initially focusing on a polished 2D front-and-back SVG preview. MOST IMPORTANT REQUIREMENT The supplied hockey jersey artwork must be preserved. The jersey must continue to look like a real hockey jersey. The SVG geometry, seams, proportions, front view, and back view should not be replaced with a simplified illustration. The SVG will need to be organized into independently customizable regions without changing its overall appearance. PREFERRED TECHNOLOGY - React - Next.js - TypeScript - SVG-based rendering - CSS I am open to recommendations, but the finished project must work smoothly in modern desktop browsers, including Chrome. The customizer should use the provided SVG directly. Canvas libraries may be considered for overlays and interactions, but the underlying jersey should remain SVG-based and visually accurate. REQUIRED FEATURES 1. INDEPENDENT JERSEY COLOR REGIONS Users should be able to choose colors for individual jersey sections, including: - Main body - Sleeves - Shoulder caps/yoke - Collar trim - Collar diamond or insert - Laces - Bottom hem - Underarm gussets Changing one section must not accidentally affect another section. The developer may need to restructure, label, group, or mask paths inside the existing SVG to create these independent color zones. 2. FRONT AND BACK JERSEY PREVIEW The interface must display: - Front of the jersey - Back of the jersey - Both views updated in real time - Consistent colors and design elements across both views The jersey preview should stay fixed and visible while the customization menu scrolls independently. Opening or closing menu sections should not cause the jersey preview to jump around the page. 3. PLAYER NUMBERS Users should be able to enter a one- or two-digit player number. The customizer should display: - A large number on the back - One digit on each front shoulder/sleeve - One digit on each back shoulder/sleeve For example, if the number is 97: - Front-left shoulder displays 7 - Front-right shoulder displays 9 - Back-left shoulder displays 9 - Back-right shoulder displays 7 For a single-digit number, that digit can appear on all shoulder positions. Additional number requirements: - Selectable number fonts - Fill color - Outline color - Large back number movable vertically - Shoulder digits locked into approved positions - Shoulder digits rotated to follow the actual angle of the supplied jersey sleeves - Shoulder numbers must appear printed onto the jersey rather than floating over it The front and back shoulder placements must be consistent and visually balanced. 4. LOGO UPLOAD AND PLACEMENT Users should be able to upload a team logo in common formats such as PNG, JPEG, and SVG. Logo functionality should include: - Display on the front jersey - Drag-and-drop positioning - Resize handle - Preserve aspect ratio - Keep the logo inside an approved printable area - Visual selection or placement boundary - Save logo placement with the design The implementation should handle transparent PNG and SVG logos correctly. 5. TEAM OR DESIGN NAME Users should be able to enter a team name or design name. The name should: - Appear above the jersey preview - Be included when the design is saved - Be included in downloaded design data - Help identify the design later This is primarily a project/design label and does not necessarily need to be printed directly on the jersey. 6. REPEATING PATTERN UPLOAD Users should be able to upload one repeating pattern, such as camouflage, digital camouflage, or another seamless texture. Supported formats should include PNG, JPEG, and SVG. Pattern controls should include: - Pattern tile size or scale - Pattern opacity - Ability to select which jersey regions receive the pattern Users should be able to apply the pattern to any combination of: - Body - Sleeves - Shoulder caps - Collar trim - Collar insert - Hem - Gussets The pattern must stay clipped inside the selected jersey sections and must not spill outside the jersey. 7. MOVABLE BODY STRIPES The customizer should include an Add Body Stripe button rather than only a dropdown for selecting a predetermined number of stripes. Each body stripe should support: - Adding multiple stripes - Independent color - Independent vertical position - Direct vertical dragging on the jersey - Position slider as an alternative to dragging - Individual removal - Front and back synchronization - Clipping to the main body panels - No spill onto sleeves, the background, or unrelated sections A stripe moved on the front should move to the corresponding position on the back automatically. The stripe should remain horizontal across the body while respecting the jersey’s body shape. 8. MOVABLE SLEEVE STRIPES The customizer should also include an Add Sleeve Stripe feature. This is one of the more technically important parts of the project. Each sleeve stripe must: - Appear on all four visible sleeves - Use exactly the same color on every sleeve - Use exactly the same relative position on every sleeve - Use exactly the same thickness on every sleeve - Be perpendicular to the direction of each sleeve - Mirror correctly between left and right sleeves - Move along the sleeve direction - Be draggable directly on any sleeve - Include a position slider - Include an adjustable thickness control - Include a color picker - Include an individual remove button - Remain completely clipped to the sleeve paths Moving one stripe on any sleeve should update all four copies simultaneously. The developer must calculate the sleeve angles using the supplied jersey artwork rather than using arbitrary horizontal rectangles. No part of a sleeve stripe may appear on the main body, shoulder caps, underarm gussets, background, or any non-sleeve region. Multiple synchronized sleeve stripes should be supported. 9. SAVING AND DOWNLOADING DESIGNS Users should be able to preserve a design so it can be opened later. At minimum, the application should support: - Save in browser storage - Load from browser storage - Download design as a JSON file - Open/import a previously downloaded JSON design Saved design data should include: - Team/design name - All jersey colors - Player number - Number font - Number colors - Number placement - Uploaded logo - Logo position and size - Uploaded repeating pattern - Pattern settings and selected regions - Body stripes - Sleeve stripes - Stripe colors, positions, and thicknesses The save format should be versioned so future changes do not immediately break older saved designs. Please describe any limitations associated with storing uploaded images as data URLs in browser storage. 10. EXPORT OPTIONS Required: - Download the editable design configuration as JSON Please provide separate optional estimates for: - Export the front and back preview as PNG - Export a high-resolution production image - Export an SVG or print-ready file - Generate a PDF design proof - Generate a production summary listing selected colors and uploaded assets Please explain which export formats are practical when working with uploaded SVG, PNG, JPEG, fonts, patterns, and browser-rendered SVG content. USER INTERFACE REQUIREMENTS The layout should have: - Scrollable customization sidebar - Fixed/stable jersey preview area - Collapsible customization sections - Color pickers - Range sliders - Upload controls - Add/remove buttons - Clear status and error messages - Responsive behavior for smaller screens The interface does not need to replicate another company’s branding, but it should feel polished and easy to understand. Suggested menu sections: 1. Team name 2. Jersey colors 3. Body stripes 4. Sleeve stripes 5. Pattern 6. Player numbers 7. Logo 8. Save, load, and export SVG AND GRAPHICS REQUIREMENTS The selected developer should be comfortable with: - Editing and restructuring complex SVG files - SVG groups and path IDs - SVG transforms - Clip paths - Masks - Patterns - Dynamically changing SVG fills - Mirroring elements between front and back - Pointer events inside SVG - Translating browser pointer coordinates into SVG coordinates - Dragging and resizing SVG elements - Preserving the original SVG geometry - Handling transforms inherited from nested SVG groups - Preventing overlays from leaking into unrelated paths The developer must inspect the actual supplied SVG before finalizing the estimate. PERFORMANCE REQUIREMENTS The customizer should: - Update in real time - Drag smoothly - Avoid excessive React re-rendering - Work reliably in current Chrome, Safari, Firefox, and Edge - Avoid duplicating large uploaded images unnecessarily - Handle pointer and touch interactions where practical ACCESSIBILITY EXPECTATIONS Reasonable accessibility support should include: - Labels for form controls - Keyboard-accessible buttons - Clear focus states - Meaningful status messages - Accessible names for interactive SVG elements - Controls that do not rely entirely on color or pointer interaction DELIVERABLES - Complete React/Next.js source code - Updated production-ready jersey SVG - TypeScript implementation - Responsive interface - Working color controls - Number customization - Logo upload and placement - Pattern upload and placement - Body stripe builder - Synchronized sleeve stripe builder - Browser save/load - JSON download/import - Deployment instructions - Basic technical documentation - Explanation of the design JSON format - Clean Git history or delivery through a GitHub repository TESTING AND ACCEPTANCE CRITERIA The project will be accepted when: - The supplied jersey still looks identical to the approved SVG - Every color region can be changed independently - Front and back update correctly - Shoulder digits follow the sleeve angles - Logo placement and resizing work - Patterns remain inside selected regions - Body stripes remain inside the main body - Sleeve stripes remain exclusively inside the sleeves - All four sleeve stripes remain synchronized - Saved designs reopen accurately - The project builds without TypeScript errors - No major browser console errors occur INFORMATION TO INCLUDE IN YOUR PROPOSAL Please include: 1. Examples of SVG customizers, product configurators, design tools, or interactive graphics you have built. 2. Your experience with React, Next.js, and TypeScript. 3. Your experience with SVG clipping, transforms, masks, and pointer interactions. 4. Whether you recommend pure SVG, Canvas, Fabric.js, Konva, or a hybrid, and why. 5. Your estimated timeline. 6. Your estimated total cost. 7. Your hourly rate, if applicable. 9. Any risks or limitations you see. 10. Separate estimates for the core customizer, save/load functionality, PNG export, and print-ready export. 11. Whether you will personally complete the work or use subcontractors. 12. What files or information you need before providing a final fixed-price estimate. SUGGESTED MILESTONES MILESTONE 1: SVG PREPARATION AND TECHNICAL PROTOTYPE - Inspect and organize the supplied SVG - Preserve the approved jersey appearance - Create independent color regions - Confirm front and back rendering - Demonstrate one draggable overlay MILESTONE 2: CORE CUSTOMIZATION - Jersey colors - Collar components - Team/design name - Player numbers and fonts - Shoulder-number positioning MILESTONE 3: LOGO AND PATTERN TOOLS - Logo upload - Dragging and resizing - Print-area limits - Pattern upload - Region selection - Pattern scaling and opacity MILESTONE 4: STRIPE BUILDERS - Add/remove body stripes - Body stripe positioning - Add/remove sleeve stripes - Correct sleeve angles - Four-sleeve synchronization - Sleeve-only clipping - Thickness and color controls MILESTONE 5: SAVING, EXPORT, AND DEPLOYMENT - Browser storage - JSON download/import - Compatibility testing - Optional image export - Documentation and handoff BUDGET I’m currently gathering quotes to understand the realistic cost of building this correctly. Please provide either: - A fixed-price estimate with milestone pricing, or - An estimated range of hours and your hourly rate I’m more interested in an accurate, well-explained estimate than the lowest bid. Proposals that do not address the SVG interaction and clipping requirements will not be considered.

Immediate project: • Integrate a standalone HTML demo (a risk-indicators dashboard) into the main Next.js app • Restyle the integrated demo to visually match the existing landing page (typography, color, spacing, components) • Use static or mocked data for the dashboard views — this does not need to be wired to live Supabase data for this phase • UI consistency pass limited to the demo-facing pages a prospect would see in a live walkthrough (not the full app) • Deliver a clean, working build deployed on Vercel, ready for live demo use Timeline: Targeting completion within 2–3 weeks — this supports an active sales conversation, so reliability and responsiveness matter. Possible follow-on work (separate scope, hourly): • Wiring the dashboard demo to live Supabase data • Bug fixes and feature requests • Periodic maintenance, including an upcoming Supabase policy/security deadline • Ongoing point of contact for a non-technical founder

I need someone who can migrate and complete an AI-powered Travel Marketplace based on Lovable, Next.js, and Supabase. You will work through GitHub, ensuring seamless collaboration and version control. The project involves integrating AI features into a travel platform, requiring skills in web development and AI integration.

Overview I have a Next.js website with a newsletter signup form that currently submits directly from the browser to HubSpot's Forms v3 endpoint. I want to add a lightweight LLM-based spam filter that inspects each submission *before* it reaches HubSpot, and silently rejects (or flags) anything that looks like spam/bot/junk input. Current setup - Framework: Next.js (App Router, TypeScript, React client component) - The form component (`NewsletterForm.tsx`) POSTs directly to `https://api.hsforms.com/submissions/v3/integration/submit/[portalId]/[formGuid]` - Fields collected: `firstname`, `lastname` (optional), `jobtitle`, `email` - Portal ID and Form GUID are public form identifiers (no secrets today) What I want you to build 1. Create a server-side API route in the Next.js app (e.g. `app/api/subscribe/route.ts`) that: - Receives the form fields from the client - Runs an LLM spam/quality check (e.g. OpenAI or similar) to classify the submission as legit vs. spam — checking for gibberish names, fake/disposable emails, nonsense job titles, injection attempts, etc. - If legit → forwards the submission to HubSpot (server-side) - If spam → rejects gracefully with a generic message (no HubSpot write) 2. Update the existing `NewsletterForm.tsx` to POST to the new internal API route instead of calling HubSpot directly. 3. Keep the LLM API key server-side only (use an environment variable — never expose it to the client). 4. Preserve the existing UX: loading / success / error states should still work. Deliverables - Working API route with the LLM spam check + HubSpot forwarding - Updated form component - Brief note on which env vars to set (`OPENAI_API_KEY`, etc.) and how to configure them - Clean, typed TypeScript that matches the existing code style Nice to have (optional) - Basic rate limiting / honeypot field as a cheap first line of defense before the LLM call - Configurable spam threshold or a logged "reason" when something is rejected Requirements to apply - Strong Next.js App Router + TypeScript experience - Experience calling an LLM API (OpenAI or equivalent) from a server route - Familiarity with HubSpot Forms API is a plus To apply, please briefly answer: 1. Which LLM/provider would you use and roughly what would it cost per submission? 2. How would you handle the case where the LLM API is slow or down — do you fail open (let it through) or fail closed (block it)? 3. Have you integrated with HubSpot Forms before? (yes/no is fine)

I need a full-stack developer to build a simple AI-powered chat assistant. The app should allow users to type a question and receive a response from the ChatGPT API. The UI should be clean, responsive, and built with React and TypeScript. Main Requirements: - Build a simple React + TypeScript frontend - Add a chat input and response area - Connect the app to the ChatGPT/OpenAI API - Show loading state while the AI is responding - Handle basic API errors - Keep the code clean and easy to understand - Provide short setup instructions in a README file

We run a small B2B SaaS platform used by logistics teams to manage customer orders, delivery notes, invoices, and internal approvals. The app is already live, but we have several issues affecting daily use: The dashboard loads slowly when users filter large order lists. Some invoice statuses are not updating correctly after payment. Admin users also need a better way to edit customer records without touching the database directly. We are looking for a full-stack developer who can review the existing codebase, identify the main issues, fix the highest-priority bugs, and help us improve the product over time. Current stack: React Node.js / Express PostgreSQL Prisma AWS S3 Stripe Vercel / Render First scope: Review the order dashboard performance Fix invoice status sync issue Add simple customer edit flow for admins Document what was changed Recommend next improvements Please apply only if you have worked on production full-stack apps before.