I have an existing website built with React and Sanity CMS that needs updates. The ideal candidate will have experience in both React and Sanity CMS, and be able to make necessary updates to the website. This project involves maintenance and possibly feature enhancements to ensure the website remains functional and user-friendly.

Frontend: React Native (Expo SDK 54), TypeScript Backend: Firebase — Firestore, Cloud Functions (Node, v1), Firebase Auth, Firebase Storage Architecture: Multi-tenant data model (multiple client organizations sharing one Firestore database, isolated by security rules) Auth: Email/password via Firebase Auth, role-based access (general contractor / subcontractor roles) Firebase / React Native SaaS (Contract, with potential for ongoing work)

I have an HTML project that requires backend coding to be completed. The tasks involve data storage and geolocation, among other coding needs. The ideal candidate should have experience in backend development and be able to integrate these features effectively.

Deploy an existing Node.js/Express app and configure SMS. I have a complete, working dispatching app (Node + Express + SQLite, plain-JS frontend). I need someone to: (1) deploy it to Render or Railway with a persistent disk and HTTPS, (2) set up a Twilio account/number and wire in the credentials so it sends automated daily texts, (3) confirm the 6 AM scheduled texts fire reliably, and (4) be available for small tweaks afterward. Code, README, and deploy steps are all included. Should be a few hours for someone experienced. Please share similar Node deployment work you've done.

Systemize and build out Framer components, templates, and styles to efficiently create landing pages. The goal is to establish a reusable framework that streamlines the design process. Ideal candidates will have experience in Framer and landing page design, with a focus on creating consistent and adaptable elements.

What this is: I'm the founder of a working AI SaaS platform (FastAPI/uvicorn backend, React/Vite frontend, deployed on AWS). The product pipeline is built and live! I need an experienced engineer to build the authentication, payments, and usage-entitlement layer that gates the product behind login and paid usage. You'll work against a runnable stub repository (real routes + data shapes, proprietary internals removed) - so you can build and test the full layer without ever touching the core IP, and afterwards - I will merge your work into the production app! Scope: • Auth (Clerk): signup/login, session lifecycle, backend session/JWT verification, inject a validated `user_id` into protected endpoints. • Payments (Stripe): Checkout for purchasing usage credits, plus a webhook that credits the user's ledger on successful payment. The webhook MUST be signature-verified, idempotent (Stripe retries-credit exactly once), and reconcilable (handle webhook-failed-but-payment-succeeded). • Entitlement ledger (the core): a credit balance per user with atomic check-and-decrement (two concurrent requests must never double-spend) on PostgreSQL. A `check_entitlement(user_id, ...)`gate that expensive endpoints call before doing paid work. • Server-side route gating: enforce entitlement on every paid endpoint (not just hidden in the UI); clean 401/402/403 responses. • Frontend integration (React): login/signup UI, buy-credits/checkout flow, balance display,graceful "out of credits" states, wired to the above. • Tests for the money-critical paths (webhook idempotency, atomic decrement, gating-bypass attempts). Stack you'll work with: Python 3.11, FastAPI, Pydantic, uvicorn (Linux). React + Vite, Tailwind. PostgreSQL. Clerk. Stripe. Who I'm looking for: Someone who has shipped this exact kind of system to production before. In your proposal, briefly tell me: 1. How you ensure Stripe webhook idempotency and handle reconciliation when a webhook fails but payment succeeded. 2. How you'd implement the atomic credit check-and-decrement so concurrent requests couldn't double-spend. 3. A relevant production system you've built (Stripe + auth + usage metering ideally). *I'd much rather a short, specific proposal - than a long generic one!* Working with me: I'm an engaged founder who genuinely enjoys building, and I want this to be a good experience for both of us! I'm responsive, communicate clearly, and I respect your expertise - because you're the specialist here,and I'm hiring you because you know this much better than I do! I'm not a micromanager and I'm not nitpicky - I just want the end results to be solid! I review in milestones, asking questions because I like understanding the work (not because I'm second-guessing you), and I make decisions quickly so you're never stuck waiting on me! The scope is already well-defined (detailed spec + a runnable stub repo on engagement), so you're not pricing around a vague, shifting target - it's a clean, bounded build. I care about getting the money-handling pieces right, and I'm betting you do too - if that resonates, I think we'll work well together! IP / engagement: A mutual NDA + IP-assignment (work-for-hire) before repo access. You build against stubs; you won't receive the proprietary pipeline. Work is milestone-based, fixed-bid preferred. To apply: Answer the three questions above + share 1-2 relevant examples, and ballpark your timeline and milestone structure (suggested: auth → payments+webhook → ledger+gating → frontend → tests/docs)!

I have a Webflow website that is 95% complete. The design and build are largely done — I just need an experienced developer to come in and execute a specific punch list of fixes. No guesswork, no interpretation — you will receive a detailed checklist with every change clearly outlined. This is not a build-from-scratch project. You will be inheriting an existing Webflow project and working from a clear, itemized list. If you're comfortable jumping into someone else's Webflow setup and executing precisely, this is a straightforward engagement. Fix categories include: Resolution & scaling — site was designed on a 1728×1117 base (MacBook Pro 16"). Must scale correctly and be explicitly tested and approved across all of the following breakpoints: Desktop: 1920px, 1728px, 1440px, 1366px, 1280px Tablet: 1024px, 768px Mobile: 475px, 425px, 390px, 375px, 320px Mobile fixes Browser continuity — Chrome and Safari must render identically Graphic resolution Spacing & layout inconsistencies All fixes will be clearly outlined in an Excel checklist provided at the start of the engagement. Every breakpoint listed above is in scope. No exceptions. What I'm looking for: Strong Webflow experience, especially with interactions, animations, and responsive behavior Comfortable working within an existing project structure Detail-oriented — pixel-perfect execution matters Please include your hourly rate or a fixed-price quote Figma file and full checklist provided upon engagement.

Hello- I need a new website for a new project. Wordpress should be fine. I gravitate towards html-looking websites instead of more template heavy super modern designs. I usually send hand drawn copies of what I want it to look like, along with the text on word docs, and then rely on professionals like you to sharpen the vision and bring it to life!

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)

We are a fast-growing telecom / AI-First CPaaS serving sms and voice API's. We are building the first AI-first communications platform (SMS, Voice, RCS, AI agents) designed for speed, simplicity, and real-world business outcomes. We are not looking for a “task completer.” We are looking for a true senior engineer who: thinks in systems moves fast makes decisions independently writes clean, scalable code uses AI tools (Claude, etc.) as a force multiplier ⚠️ Read This First *DO NOT APPLY IF YOU ARE PRETENDING TO BE IN A DIFFERENT COUNTRY. PROOF OF RESIDENCY IS REQUIRED. Most applicants will not be a fit. If you need: detailed tickets hand-holding constant direction This is NOT the role for you. If you are the type of engineer who: sees a problem and solves it end-to-end improves architecture without being asked ships quickly without sacrificing quality You will thrive here. What You’ll Do Build and ship full-stack features across our platform (messaging, voice, AI workflows) Make architectural decisions (not just implement) Improve system performance, reliability, and scalability Work directly with founders (no PM layers) Move from idea → production very quickly What We Expect (Non-Negotiable) 5+ years real full-stack experience (not just titles) Strong backend experience (Node.js / APIs / infra) Strong frontend experience (React or similar) Experience building production systems at scale Ability to work autonomously with minimal direction High ownership mentality Bonus (but highly valuable) Experience with telecom / CPaaS / messaging Experience with AI integrations (LLMs, agents, workflows) Experience optimizing performance at scale Startup experience (especially early-stage or fast growth) How We Work Small, high-output team Very fast iteration cycles No unnecessary meetings High trust, high expectations We use AI tools heavily (Claude, etc.) — you should too What We Care About Most Not your resume. We care about: How you think How you build How fast you execute The quality of your code To Apply Please include: Links to projects you’ve built (real production work) A short explanation of: a system you designed end-to-end a difficult technical decision you made independently Your GitHub Optional (but strong signal): Share how you use AI (Claude, etc.) in your workflow Compensation Competitive (based on experience) Long-term opportunity with a fast-growing, profitable company If you are truly senior, this will feel obvious. If not, this role will be very uncomfortable. **THIS IS A FT, HOURLY ROLE. PROVIDE YOUR REQUESTED HOURLY RATE IN PROPOSAL**