I am building an authentication library and a billing platform in Golang + Postgres. Auth-library is embedded only, while billing can be an embedded-library, and also a stand-alone application. The platform is intended to make it easy for Go-devs to write authentication (users register, OIDC, recover password, etc.), and manage billing their users (various billing providers in addition to Stripe, including crypto). These codebases are mostly written by AI (Claude Code and Codex) but the issue is that these tools suck. The write a lot of slop, and their systems don't work, and I don't trust them. With auth + billing, these are highly sensitive areas where we cannot afford to fuck up. Deliverables are: 1. a list of tasks the LLMs must do to refactor / fix these systems 2. a complete audit of all APIs (the surface areas / shapes that are used as system boundaries) 3. integration tests that will pass, if the LLM's code is correct 4. a complete security audit, to address any vulnerabilities / exploits possible I am only looking to hire someone in California / colorado. I want to work synchronously with them; for every hour you bill we'll be on a call together so that we can maximize communication bandwidth. I live in Denver, but I plan to move to SF soon. I'd be down to work together in person in the future, but for now we'll only be working synchronously-remotely. Human-written applications only. Template or LLM-written responses here will be rejected immediately. Please list your qualifications concisely. Don't say 'I am a Golang expert' say 'I worked at company X, and built system Y in Go which does Z.' Thanks for your time.

Looking for an experienced Bubble.io developer to build a crowdfunding platform MVP from the ground up. Core Features Needed: • User registration and profile creation with email domain restriction • Campaign creation and management • Donation flow with optional donor tip at checkout • Stripe Connect integration for automated payouts • Identity verification integration triggered at payout stage via third party API • Basic admin dashboard for campaign review and approval • Mobile responsive design How Verification Should Work: • Users create campaigns freely • Verification is triggered only once a campaign reaches a minimum funding threshold • Payout is held until verification is confirmed • Verified users receive funds automatically upon confirmation How Tipping Should Work: • Optional tip prompt presented to donor at checkout • Tip amount configurable by admin • Tips collected separately and routed to platform account Requirements: • Strong Bubble.io portfolio with similar platforms • Proven Stripe Connect experience specifically • Experience integrating third party APIs into Bubble • Clean, well documented workflows • Available for post-launch support Project Details: • Scope: MVP only, core functionality listed above • Timeline: 4-6 weeks

We are building a HIPAA-compliant SaaS platform for medication stewardship in skilled nursing facilities (SNFs). The platform allows clinical pharmacy consultants and providers to upload scanned medical documents, run AI-powered medication and disease state reviews, and generate clinical findings — all without storing any patient data. This is a focused, well-defined MVP. No scope creep. We need a developer who moves fast, communicates clearly, and has real experience with HIPAA-eligible AWS architecture. Core concept — stateless processing: This platform is intentionally stateless. Documents are uploaded, processed through OCR, analyzed by AI, and the findings are displayed to the user. Nothing is written to a database. No patient data or documents are retained after the session ends. The platform processes PHI transiently and discards it — significantly simplifying the HIPAA footprint while maintaining compliance. What you will build: 1. AWS infrastructure (HIPAA-eligible, stateless) — S3 used only as a temporary processing buffer (files deleted immediately after OCR completes) — AWS Textract for OCR processing of scanned PDFs and images — AWS Bedrock (Claude Sonnet) for AI-powered clinical analysis — AWS Cognito for user authentication only (no clinical data stored) — AWS Amplify or CloudFront for React frontend hosting — KMS encryption for data in transit — All services configured under AWS BAA coverage — No RDS or persistent database required for clinical data 2. React frontend — Clean single-page application — Document upload UI (drag/drop, supports PDF and image files) — OCR text display with basic edit capability before analysis — Free-text question input (user asks Claude questions about the document) — Claude response display panel — Copy to clipboard button on all output — User login and profile page (name, email, facility) — Membership and billing settings page — Stripe monthly subscription integration 3. HIPAA compliance — Stateless architecture — no PHI persisted after session — HTTPS enforced on all endpoints — AWS BAA signed and covering all services — User BAA acknowledgment on signup — Audit logging for access events — Privacy policy and terms of service integration What we are NOT building in this phase: — Mobile app — EHR or PointClickCare integration — Stored intervention history or dashboard — Cost savings calculator — Admin panel — Anything beyond the three core features above: upload, analyze, copy output Ideal candidate: — 3+ years React and AWS experience — Prior HIPAA-eligible AWS builds — please describe your specific experience in your proposal — Hands-on experience with AWS Textract or comparable OCR pipelines — Familiarity with AWS Bedrock or direct LLM API integrations — Experience with stateless or ephemeral data processing architectures — Stripe subscription integration experience — Strong communicator — weekly video check-ins required — Available to start within 2-4 weeks Engagement details: — Estimated scope: 40–60 hours — Timeline: 8–10 weeks — Budget: $2,500–$4,500 USD fixed price preferred — Payment milestones: 25% upfront, 25% at working OCR pipeline, 25% at working Claude integration, 25% at launch — Communication: Weekly video check-in + async messaging How to apply: In your proposal please answer these four questions specifically: 1. Describe a HIPAA-eligible AWS application you have built — what services did you use and how did you handle PHI? 2. Have you implemented stateless or ephemeral document processing before? How did you approach it? 3. What is your experience with AWS Textract or other OCR pipelines? 4. How would you integrate AWS Bedrock or a Claude API call into a React frontend securely? Proposals that do not answer these four questions will not be considered. About us: We are an early-stage clinical SaaS platform founded by a Clinical Pharmacy Specialist. We are building a tool that genuinely improves patient care and safety in long-term care settings. We want a developer who takes pride in clean, secure, well-documented code and wants to be part of building something meaningful in healthcare. If that is you, we would love to hear from you.

2. The core concept An online marketplace exclusively for verified trading card sellers (sports cards, Pokémon, Magic: The Gathering) to sell directly to buyers. Designed to recreate the feeling of browsing a real card show, online. The two features that make this different from a generic marketplace: Map-based discovery — buyers find shops via a US map with pins, not just a search bar Value box flip experience — buyers browse a seller's box of cards by flipping through them one at a time (card-back reveal, fan animation between cards), with a toggle to switch to a standard grid view Important clarification on value boxes: These are NOT mystery packs / blind boxes. Every card and its price is visible — buyers see exactly what they're getting before buying. The "flip" is purely a browsing interaction, not a gambling mechanic. 3. Business model Sellers pay a flat monthly subscription fee (target: ~$49/month, considering tiers — see below) Zero fees on individual sales — sellers keep 100% of every sale This directly undercuts eBay (13.25%/sale), Whatnot (8%/sale), and COMC (~12% all-in) Sellers are manually verified/approved before they can list — not an open marketplace. This is a core trust/quality signal for buyers. Possible future tiers: Starter ($29/mo), Pro ($49/mo), Elite ($99/mo with featured placement + priority support) — not finalized, flat single tier is fine for MVP 4. User roles Buyer Browse shops via map or category Browse a shop's inventory (flip view or grid view) Search by player, team, set Filter by price and category Save/watchlist cards Follow shops to get drop notifications Make an offer or buy now Message sellers directly Seller (verified/approved only) Apply for an account, gets manually approved Dashboard with stats: active listings, monthly sales total, open offers, follower count Upload cards via guided flow: photo → AI auto-detect details → review/edit → set price → publish Option to add a listing to a "value box" grouping or list it standalone Build and publish "drop announcements" (title, date/time, teaser text) that notify all followers Manage/respond to offers and messages Edit or delete listings Easy way for sellers to print off shipping labels. Option where sellers can put a description on each card, or just like in real life, no description needed and can put a price on the card with a photo and that’s it. Can be an option where you upload all the photos and every card in the “box” is $ per card. Easy and fast way to sell just like in real life at a card show. Jump to the top of the homepage. Different payment options for that. US map (accurate state borders, not abstract shapes) with shop pins If US map is too difficult to start with then just the seller's logo with a picture of a value box below it. Pins color-coded by category (sports / Pokémon / MTG / multi-category) Click or hover a pin shows a tooltip: shop name, city, specialty, listing count Drop announcement banners/strip at top (horizontally scrollable) Search bar (player/team/set/shop name) Category browse tiles at the bottom (Sports, Pokémon, MTG, Graded) Stats bar: total shops, total listings, live drops Shop profile / Value box browsing screen Shop header: avatar, name, city, specialty, verified badge Category tabs to filter that shop's inventory Search input + price filter dropdown + category filter dropdown Toggle between Flip view and Grid view Flip view: card stack visual (depth effect with cards behind), tap/click to flip the active card from back (VB-branded) to front (player name, set, price, condition badge, grade). Prev/next navigation with a "fan" animation. Action buttons: Buy Now, Make Offer, Save, Message Seller. Card metadata panel: condition, year, category, seller. Maybe kind of like flipping through photos on a dating app. Grid view: standard 3-4 column card grid, each card shows image/emoji, name, set, price, save heart icon Seller booth (dashboard) Header: shop avatar, name, city, verified badge, current plan/subscription status Stats row: active listings, monthly sales $, open offers, followers Drop announcement builder: title input, date picker, time picker, teaser text input, live preview of how it'll look to buyers, publish button Active listings list: thumbnail, name, meta info, price, status (Live / Offer Pending / Draft), edit/delete buttons "Add listing" button/flow: Step 1: Upload photo (camera, photo library, or bulk upload option) Step 2: AI-detected fields shown (player, year, set, grade) — powered by CollX API — with confidence score, all fields editable. Future possibility!!! Step 3: Set price, shown alongside a market price suggestion/range from CollX, toggle to add to a value box, category/team fields. Future possibility!!! Step 4: Publish (or save as draft) Step indicator showing progress through the 4-step upload flow Also needed but not yet prototyped (describe verbally / sketch if needed): Messaging/chat interface (buyer-seller threads) Offer management screen (accept/decline/counter) Watchlist screen Seller application/verification form (for new sellers applying) Buyer account settings Checkout flow (if handling payment processing for purchases, vs. just facilitating contact between buyer/seller) 6. Core functionality / logic needed User authentication with two roles (buyer / seller) Seller application + manual approval workflow (not self-serve signup) Database relationships: Users → Shops → Listings → Value Boxes; Listings ↔ Offers; Listings ↔ Messages; Shops ↔ Followers; Users ↔ Watchlist Stripe integration for recurring subscription billing (not one-time payments) Search/filter logic across multiple fields (text search + category + price range) Notification system: in-app + email when a followed shop posts a drop Map integration with custom pin placement (real lat/long coordinates, not abstract positions) Image upload and storage for card photos (Phase 2 / nice-to-have) CollX API integration for AI card detection from photos 7. Tech stack — open to recommendation, but my research points to: App builder: Bubble.io (no-code, but open to alternatives like Sharetribe or custom code if developer recommends and price works) Payments: Stripe (subscriptions) Maps: Google Maps API or Mapbox Email: Klaviyo or similar Card AI/pricing data: CollX API (Phase 2) Photo storage: Cloudinary or similar Eventual native app: Open to wrapping the web app via Median.co for App Store/Google Play once validated, rather than building native from day one 8. What I'm bringing to this meeting 3 fully interactive HTML/CSS/JS prototype files (every screen above, functional in any browser). Really don’t understand this part. Full written concept brief (features, screens, budget guidance, tech stack reasoning) Seller-facing pitch document (fee comparison math, used for recruiting sellers — shows the business model is thought through) Brand colors, fonts, and the "VB" mark already defined Domain + LLC already in place 9. Budget & timeline expectations Budget: $2,500–$4,500 for MVP (open to discussing fixed price vs. hourly) Timeline: No hard deadline, prioritizing finding the right developer over speed Phased approach preferred: Core features first (accounts, listings, map, Stripe subscriptions), flip animation and AI upload can follow as a second phase if needed to stay in budget 10. Questions I want to ask THEM in this meeting Have you built a marketplace with buyer/seller roles before? Can I see it? Have you integrated Stripe subscriptions (recurring) specifically, not just one-time checkout? How would you handle the map with custom pins — which tool/plugin, and have you done this before? How would you replicate the card flip + fan animation inside [chosen platform]? Is custom embedded code needed? What about the map idea? What's your recommended database structure for this, and does it match what I've outlined above? Will I be able to log in and manage/edit the app myself after you hand it off, or will I need you for every change? What's not included in your quote that I should expect to pay for separately (plugins, API costs, hosting)? What's your estimated timeline for an MVP with this scope? I need something that can be built and tested out for seller and buyers to use.

Looking for a Bubble developer to work on a legal-tech app that matches clients with lawyers. The role involves building a user-friendly interface and ensuring seamless functionality. The ideal candidate will have experience in legal-tech applications and be able to start immediately. This is a part-time position with a short-term engagement. Need immediate help with: User authentication and onboarding Client intake forms Lawyer profiles Matching logic Search/filter functionality Stripe payments (if applicable) Database architecture API integrations

React Native Developer Needed — Healthcare Dating App (StatDate) I'm a Registered Nurse with 13 years of ICU and PACU experience building StatDate — a dating app exclusively for verified healthcare professionals and EMS personnel. Think Tinder, but every user is checked against a national license database before they can interact with anyone. No impostors. No civilians. The concept is validated, the brand is built, the domain is live (statdate.com), and a full interactive prototype exists. I have a complete 40-page technical specification ready to hand off on day one. I need a developer to build the real thing. WHAT YOU ARE BUILDING - React Native app (Expo) — iOS and Android from a single codebase - Credential verification — integrates with Nursys, NPI Registry, and NREMT APIs - Swipe-based discovery feed with schedule-compatibility scoring algorithm - Real-time messaging with photo sharing - Subscription paywall — RevenueCat (mobile) + Stripe (web) - Report and block system — required for App Store approval - Node.js + PostgreSQL backend deployed on Railway - Admin dashboard for report queue and manual verification override SUBSCRIPTION TIERS - Free — swipe only, blurred likes count - On-Call ($9.99/mo) — messaging, schedule filter, full likes list, rewind - Rapid Response ($19.99/mo) — priority placement, boost, read receipts REQUIRED SKILLS — DO NOT APPLY WITHOUT THESE - React Native (Expo) — must have a live app currently in the App Store or Google Play - Node.js + Express — REST API design and implementation - PostgreSQL — schema design, migrations, query optimization - RevenueCat or Stripe — prior subscription integration required - AWS S3 or Supabase Storage — file upload experience - Real-time messaging — Socket.io or Supabase Realtime - Third-party API integration — external REST APIs with error handling NICE TO HAVE - Dating or marketplace app experience - Supabase Auth experience - App Store submission experience (Apple + Google) WHAT I PROVIDE - Complete 40-page technical specification with schema, API endpoints, screen inventory, and feature logic - Full interactive HTML prototype for UI/UX reference - Brand assets — logo, color palette, typography - Daily async availability for feedback and approvals TO APPLY — INCLUDE ALL OF THE FOLLOWING OR I WILL NOT RESPOND 1. Link to a live app you built currently in the App Store or Google Play 2. Your approach to the three license verification APIs (Nursys, NPI Registry, NREMT) 3. How you would architect real-time messaging for this app 4. Your estimated timeline 5. Your bid I will respond to qualified applicants within 48 hours.

This project is a continuation of the existing SMOX audit and production readiness review currently in progress. The objective is to continue working with the current auditor and transition from audit findings into implementation planning and execution. Current priorities include: • Review completed audit findings • Verify repository structure and production readiness • Implement 30-Day Smox Pro Trial functionality • Review Stripe Connect subscription management • Review Stripe webhook handling and payment events • Resolve subscription and payment-related issues • Correct booking timeline and client visibility issues • Resolve calendar history and scrolling issues • Improve notification reliability • Address production-impacting defects identified during the audit • Establish a milestone-based implementation roadmap Existing repositories, AWS access, Stripe access, audit documentation, and project assets will be provided as needed. This is not a new application build. The project already exists and is currently deployed. The goal is to continue the audit engagement and execute the highest-priority production readiness improvements identified during the review process.

I’m building the final UX surfaces for a July 1 SaaS launch and need a fast, reliable React + Supabase engineer who can execute clean, production‑ready screens and flows. The project is front‑end heavy, well‑defined, and focused on UI polish, dashboards, forms, and simple Supabase integrations. You’ll work directly with me (the founder) in a clear, async workflow with daily check‑ins. I move quickly, communicate clearly, and provide detailed requirements for each screen or flow. What I need built Dashboard_flows - user dashboards, scoring views, operator tools UX_surfaces - responsive screens using React, TypeScript, Tailwind Form_and_flow_logic - multi‑step flows, validation, state handling Supabase_integration - basic CRUD, auth, RLS‑safe queries Admin tools - simple internal views for data visibility UI polish - spacing, alignment, loading/error states Stripe_integration - light subscription or billing touchpoints This is not deep backend work. It’s clean, fast UI execution. How I work Clear requirements - I provide detailed specs for each screen Async- updates - daily check‑ins, async communication Fast iteration - I respond quickly and unblock immediately Direct founder access - no layers, no bureaucracy What I’m looking for React Typescript experience Tailwind UI polish Supabase familiarity Stripe comfort Clean communication US based Timeline & budget Start today 2 to 3 week contract 45 to 70 hr Potential ongoing work If you can start immediately and have examples of polished React/Tailwind work, I’d love to see your GitHub or recent projects.

# Full-Stack AI Engineer — Semantic Search + Next.js + Supabase (Long-Term, Contract-to-Hire) ## About We're building an AI-native platform that makes a large archive of recorded talks genuinely discoverable and useful: need-based semantic search over transcribed media, with a subscription product built around it. We have a clear product vision and architecture and are looking for a lead engineer to build the first version and grow with us long-term. Full product details are shared with shortlisted candidates under NDA — this post focuses on the engineering and the skills we need. ## The engineering challenge You'll build a two-part system that shares one database: 1. **A content pipeline (Python):** ingest recorded talks, transcribe them, chunk and enrich the transcripts with metadata using an LLM API, generate embeddings, and store everything in Postgres. 2. **A web app (Next.js):** fast, crawler-friendly, SEO-strong content pages with structured data; retrieval-based search that returns relevant source material with links/citations; user accounts; and Stripe-gated paid content. We care a lot about retrieval *quality* and clean, maintainable architecture — this is a real product, not a prototype. ## Required tech stack - **App:** Next.js (App Router), TypeScript, Vercel. Strong SSR/SSG, SEO, and JSON-LD structured-data experience. - **AI/backend:** Python; production RAG (embeddings, chunking, retrieval quality); LLM API integration. - **Data:** Postgres + **pgvector** (via Supabase); embeddings via a hosted model (Voyage/OpenAI). - **Auth & gating:** Supabase Auth with row-level security. - **Payments:** Stripe (subscriptions + one-time). ## Required skills - Shipped production Next.js (App Router) + TypeScript apps with strong SSR/SEO. - Built a real RAG / vector-search system in production — not a tutorial clone. - Comfortable in Python for data pipelines. - Postgres + pgvector and Supabase in production. - Stripe integration. - Plans before building; communicates clearly in writing. ## Nice to have - Audio/video transcription experience (Whisper / faster-whisper / Deepgram / AssemblyAI). - Agentic coding workflows (e.g., Claude Code). - Content-heavy SEO products or media libraries. ## Engagement - Hourly, contract-to-hire. ~20–40 hrs/week to start; long-term for the right person. - We start finalists on a **small paid test project** (a single self-contained slice of the pipeline) before the full engagement — that's how we evaluate fit. ## Confidentiality This is a proprietary product. Shortlisted candidates sign a mutual NDA before we share full scope and context. Please don't expect complete product details in the first exchange — strong technical applicants will have everything they need to be evaluated, and the rest follows the NDA. ## How to apply Applications that skip these are ignored: 1. **Start your proposal with the word `pgvector`** so we know you read this. 2. Link **two** projects: one live Next.js/SSR app, and one RAG/embeddings or LLM-integration project. Tell us what *you* personally built. 3. Answer briefly: *An offline embedding pipeline and a live search query must use the same embedding model — why does that matter, and how would you guarantee it?* 4. One line on your approach to chunking long-form audio/video transcripts for good retrieval.

Project Overview We are seeking a senior marketing analytics consultant for a one-time project to audit, fix, validate, and document the analytics infrastructure for our growing online education company. We sell state-approved online boating safety courses through a WordPress/LearnDash website and rely heavily on accurate marketing data to make business decisions. Our website and tracking infrastructure already exist. We are not looking for a web developer or general digital marketer. We are looking for a senior analytics specialist with deep expertise in GA4, GTM, marketing attribution, ecommerce tracking, and executive reporting. Our objective is simple: By the end of this project, we want complete confidence that our marketing data is accurate enough to confidently scale advertising spend and make business decisions. Current Tech Stack WordPress LearnDash WooCommerce Stripe Google Analytics 4 (GA4) Google Tag Manager (GTM) Google Ads Looker Studio GitHub What Success Looks Like At the conclusion of this project we should be able to confidently answer questions such as: How many purchases came from Google Ads? Is our ROAS accurate? What is our true CAC? Does Stripe revenue reconcile with GA4 and Looker Studio? Can we confidently increase advertising spend knowing our data is accurate? Can leadership rely on our dashboard for day-to-day decision making? We value clean, maintainable implementations over clever but fragile solutions. Phase 1 – Analytics Audit Review and audit: Google Analytics 4 implementation Google Tag Manager Google Ads conversion tracking Ecommerce tracking Funnel tracking Attribution across traffic sources Looker Studio calculations Identify: Duplicate events Missing events Incorrect calculations Attribution issues Tracking inconsistencies Data quality concerns Recommendations for improvement Phase 2 – Fix Tracking Issues Correct any issues discovered during the audit, including: GA4 event configuration GTM implementation Ecommerce tracking Funnel tracking Google Ads conversion tracking Attribution ROAS calculations CAC calculations Conversion rate calculations Our preference is to use GA4 as the primary analytics source whenever appropriate, with Stripe serving as the financial validation source. Phase 3 – Validate the Data Once fixes are complete, validate the implementation using real transactions. We want purchase data to reconcile consistently across: Stripe Google Analytics 4 Google Ads Looker Studio Our goal is that a completed purchase is accurately reflected across all reporting platforms. Phase 4 – Executive Dashboard Build a clean, professional executive dashboard that leadership can use every day. Include, at minimum: Users Sessions Traffic sources Course views Registrations Checkout starts Purchases Revenue Conversion rates ROAS CAC Revenue by traffic source Revenue by state If there are additional KPIs you believe would improve executive decision-making, we'd appreciate your recommendations. Phase 5 – Documentation & Handoff Provide: Documentation explaining the tracking implementation Documentation explaining dashboard calculations Documentation of any custom logic A recorded walkthrough or live handoff session Recommendations for maintaining the system going forward Required Experience Please apply only if you have significant experience with: Google Analytics 4 Google Tag Manager Looker Studio Ecommerce analytics Marketing attribution Conversion tracking Google Ads WordPress Preferred: BigQuery SQL Stripe integrations Server-side GTM / server-side tracking Project Details Project Type: Hourly Expected Rate: $75–125/hour (exceptional candidates outside this range will still be considered) Expected Engagement: Approximately 20–40 hours, depending on findings during the audit We understand the exact scope cannot be determined until the analytics system has been reviewed. Please include your estimated hours and any assumptions behind your estimate. No work beyond the agreed scope should be completed without approval. To Apply Please begin your proposal with the phrase: "Data integrity first." Then include: Examples of GA4 implementations you have audited or repaired. Examples of executive dashboards you have built. Experience with ecommerce businesses. Experience reconciling GA4 with Stripe (or another payment processor). A brief explanation of how you would diagnose inconsistent marketing data. What are the first five things you would audit in an existing GA4/GTM implementation, and why?