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 are building a production SaaS platform called MarketLens, designed for investment teams and analysts who need real-time market intelligence combined with AI-generated insights and portfolio tracking tools. What You’ll Do - Build and maintain the core backend services in Python (FastAPI / Django) - Develop frontend dashboards using React (TypeScript preferred) - Integrate real-time data pipelines (WebSockets, streaming APIs, or message queues) 1. Implement AI features such as: 2. Market summarization using LLMs 3. Portfolio risk explanations 4. Automated insight generation from time-series data - Design and maintain scalable APIs for analytics and user data - Work on subscription and billing logic (Stripe integration) - Improve system performance, especially around data freshness and dashboard latency - Participate in architecture decisions for scaling AI + data workloads Our clients are small to mid-sized hedge funds and financial advisory teams who currently rely on fragmented tools like Bloomberg exports, spreadsheets, and separate analytics dashboards. MarketLens aims to unify all of this into a single workflow.

CONFIDENTIAL PROJECT — NDA REQUIRED BEFORE DETAILS ARE SHARED We are a US-based LLC seeking an expert React Native developer with deep Twilio Programmable Voice experience and daily Cursor AI proficiency for a mobile app project on iOS and Android. REQUIREMENTS — Please read carefully before applying: Twilio Programmable Voice expert level only. You must have built real production applications using Twilio Programmable Voice for live call routing, interception, or telephony workflows. SMS or video experience does not qualify. Cursor AI required. You must use Cursor as your primary coding environment daily. This is how we move fast. React Native apps currently live in the App Store and Google Play. Links to published apps required in your proposal. Firebase Cloud Functions deployment experience required. Full time availability — 35 to 40 hours per week preferred. Must sign NDA and IP Assignment Agreement before any project details, files, or designs are shared. All code committed daily to client owned private GitHub repository. Weekly written progress update every Friday without exception. INTERVIEW PROCESS: Shortlisted candidates will answer technical Twilio Programmable Voice questions and complete a paid test task before hiring. TO APPLY — Answer all four questions or your proposal will not be reviewed: Describe 2 projects where you used Twilio Programmable Voice for live call routing or telephony. What did you build? How long have you used Cursor AI and how do you use it daily? Provide links to 2 live React Native apps you built in the App Store or Google Play. What is your availability in hours per week starting immediately?

Overview: I have a marketing site for my construction/remodeling business built in Lovable (Vite + React single-page app). The problem: it's client-side rendered, so search engines and AI crawlers (GPTBot, Perplexity, ClaudeBot) and social link previews receive an empty HTML shell with no content. Google has only indexed 6 of my 89 pages because of this. I need the site served as fully prerendered static HTML so every route returns real content in the raw HTML — no JavaScript required to see it. Scope of work: Export my existing Lovable project to GitHub (I'll authorize access). Add a build-time prerendering step (react-snap or equivalent) that generates a static HTML file per route — including all service pages and the ~58 service-area pages. Deploy to Netlify or Cloudflare Pages (your recommendation) with the prerender step running automatically on each build. Point my existing domain (www.mastersconstructiongroup.com) to the new host via DNS. I'll provide registrar access or make the changes you specify. Critical requirement: I must be able to keep editing the site in Lovable after the move. Set up the GitHub → host pipeline so that when I publish edits from Lovable, they automatically flow through and redeploy the prerendered site. I do NOT want to edit code for routine content changes. Please confirm you can preserve this workflow. Acceptance criteria (how I'll confirm it's done): Running curl (no JavaScript) on the homepage and at least 3 interior pages returns the page's real title, H1, and body content in the raw HTML. The LocalBusiness / GeneralContractor JSON-LD schema is present in the raw HTML. I can make a content edit in Lovable, publish, and see it live on the domain without developer involvement. Helpful notes: The Lovable export is already partly prepared for this: main.tsx uses hydrateRoot(), internal links render as real anchor tags, and react-helmet is wired up for per-page head tags. There's also a react-snap config recipe I can share with you. This should be a small, well-defined job. Please include in your proposal: a fixed-price quote, estimated turnaround, and a one-line confirmation that you can keep my Lovable editing workflow intact after the move.

Professional Auto Appraisals is seeking an experienced full-stack developer to add a customer onboarding portal to our existing appraisal management application. Important: We already have a working claim management/tracking system. We are not looking for a new CRM, dashboard, or claim management platform. This project is to extend our existing application and automate the client onboarding process. Developer must be comfortable reviewing and modifying an existing codebase. This is not a greenfield project. The selected developer will be extending an existing appraisal management application and integrating new functionality into the current architecture. Project Goal Create a customer-facing portal that allows a client to: * Submit claim information * Upload documents * Complete required agreements * Sign documents through DocuSign * Pay online * Automatically create a claim in our existing application after onboarding is complete Required Workflow Step 1 - Customer Intake Customer completes an online intake form from our website. The form should collect: * Name * Email * Phone number * Address * Insurance carrier * Claim number * Adjuster information * Vehicle year, make, and model * VIN * Mileage * Settlement offer amount * Lienholder information * GAP coverage information * Vehicle photos * Insurance valuation report * Supporting claim documents Step 2 - Document Generation The intake information should automatically populate our existing document templates: * Appraisal Agreement * Letter of Authorization * Right to Appraisal Request (if applicable) Step 3 - Embedded DocuSign Signing We already have a DocuSign account. Requirements: * Use the DocuSign API * Use embedded signing directly within the website/application * Auto-populate templates with intake information * Obtain signatures on the Appraisal Agreement and Letter of Authorization * Return completed documents to the application Step 4 - Online Payment After signing is complete, the customer should pay online. Requirements: * Stripe integration preferred * Payment confirmation stored in the application * Failed payment handling * Receipt generation Step 5 - Claim Creation A claim should only be created in the production claim tracker after: * Required documents have been signed * Payment has been successfully received Once those conditions are met, the system should: * Create a new claim record in the existing application * Attach all intake information * Attach uploaded files * Attach signed PDFs * Set initial status to: "New Intake - Paid" Optional Lead Tracking Prior to payment, the system may maintain a temporary lead record for incomplete or abandoned submissions. These records should not appear as active claims in the production claim tracker. File Storage The system should: * Store uploaded files securely * Store signed PDFs * Associate all files with the claim record * Google Drive integration is preferred if practical with the existing application architecture Technical Requirements Experience with: * Existing application integrations * React * Node.js * Replit deployments * PostgreSQL or similar databases * DocuSign API * Embedded DocuSign signing * Stripe integration * Webhooks * Secure file uploads * Google Drive API * Mobile-responsive interfaces Deliverables * Customer intake portal * Document automation * DocuSign integration * Payment integration * Automatic claim creation * File upload and storage * Status automation * Documentation for future maintenance When applying, please provide examples of: * DocuSign API projects * Embedded signing implementations * Stripe integrations * Workflow automation projects * Applications integrated into existing systems rather than built from scratch The ideal developer understands API integrations, workflow automation, and extending an existing application without replacing current functionality. The ideal candidate is someone who's built: SaaS applications Customer portals Payment workflows E-signature integrations Not someone whose experience is primarily brochure websites or WordPress sites.

Rebuild a travel agency SaaS platform from a working no-code prototype to Next.js + Supabase. Features include Notion-style CRM, AI proposal builder (Claude API), client portal, commission tracking, Stripe billing, and Duffel flights API. Row-level security required. Fixed price project. Full working prototype provided as reference.

About the Role We are a funded fintech startup building a first-of-its-kind platform at the intersection of digital banking and social media intelligence. Think credit scoring — but for creators and entrepreneurs. Our platform combines financial tools, OAuth-connected social data, and a proprietary scoring engine into a seamless product used by creators, small business owners, and entrepreneurs. We are looking for a Senior Full-Stack Developer to own our entire technical stack — from server infrastructure to front-end experience — and help us scale from beta into a full product launch. This is not a freelance gig. This is a full-time salaried role with real equity potential at an early-stage company that is actively raising its seed round. You will be the technical backbone of the company. You will work directly with the founding team. What You Will Be Working On A PHP/Laravel API backend serving a multi-app ecosystem across production, staging, and demo environments A vanilla JS + HTML/CSS front-end for a consumer-facing creator dashboard, public profile pages, and a verification system A proprietary scoring engine that processes consented, first-party OAuth data from platforms including X/Twitter, Instagram, TikTok, LinkedIn, and YouTube A digital banking portal for investor and user financial management (Mercury, Dwolla, Stripe integrations) A server infrastructure running on a dedicated Hetzner bare-metal server (Ubuntu 24, Plesk, Apache, MySQL, Redis) that you will own end to end An admin dashboard for internal team operations — user management, lending, capital, communications Upcoming work: CI/CD pipeline implementation, Redis migration to internal infrastructure, TikTok and Meta OAuth API wiring, mobile-responsive passes, and banking partner integration The Stack Backend: PHP 8.x / Laravel, MySQL, Redis Front-End: Vanilla JavaScript, HTML5, CSS3 (no framework — clean component-based architecture) Infrastructure: Ubuntu 24.04, Plesk Obsidian, Apache, Hetzner dedicated server Integrations: OAuth 2.0 (X, Instagram, TikTok, LinkedIn, YouTube), Dwolla, Mercury, Twilio, Firebase, Stripe, Shopify Version Control: GitHub (org-based, branch workflow) Other: QR code generation, real-time verification systems, social data normalization What We Are Looking For Must-haves: 5+ years of full-stack development experience Strong PHP/Laravel — you can read, debug, and architect Laravel apps without hand-holding Solid vanilla JavaScript — you do not need React or Vue to build clean, fast, interactive UIs Comfortable owning server infrastructure — SSH, Linux, Plesk or cPanel, Apache config, MySQL administration Experience with OAuth 2.0 integrations — connecting to social media platform APIs is second nature Familiarity with fintech concepts — payments, banking APIs, KYC/AML flows, or financial data handling Git workflow discipline — clean commits, branch management, no cowboy pushes to main Strong written communication — you document your work, you write clear commit messages, you can explain architecture decisions to non-technical stakeholders Strong pluses: Experience at a fintech startup or financial technology company Familiarity with social media platform developer programs (X API, Meta Graph API, TikTok for Developers) Experience setting up CI/CD pipelines (GitHub Actions, Forge, Envoyer, or similar) Experience with Redis configuration and migration Any background in credit scoring, data normalization, or analytics engine architecture Prior W-2 employment experience (this is not a 1099 contractor role) What You Get Full-time salaried position — compensation discussed during interview based on experience Direct access to and collaboration with the founding team The opportunity to be the lead technical voice at a company that is actively fundraising and preparing for a full public launch A codebase that is real, live, and in use — not a greenfield project, not a prototype Remote-first culture — flexible hours, async-friendly, results-driven What This Is Not This is not a short-term project or hourly contract This is not a role where you will be handed a spec and left alone This is not a company where the tech is an afterthought — the product IS the technology

Description We are building Cardinal Hearts, a Stanford-centered digital wellness and anonymous peer support platform designed to help students navigate romantic relationships--share experiences, seek support, access personalized resources, and foster meaningful reflection in a psychologically safe environment. The platform will be fully accessible across both mobile and desktop devices, with a seamless, intuitive experience on each. We are looking for a talented full-stack developer to build a high-resolution functional MVP/prototype with scalable frontend and backend architecture. This is not a traditional social media platform — the interaction model should feel intentional, supportive, privacy-conscious, and community-centered. --- Core Features Frontend Development We need a modern, clean, responsive application that works seamlessly across: * Mobile devices * Tablets * Desktop/laptop browsers Key features include: * Anonymous posting feed * Post creation flow * Stanford-inspired branding/aesthetic * Tagging/filter system: * “Seeking Advice” * “Just Wanted to Share” * User onboarding/login flow * Saved/bookmarked posts * Ability to “follow/save” posts for later viewing * Personal Diary feature (see below) * Responsive UI optimized for both mobile and desktop --- Community Interaction Features We want engagement to feel emotionally supportive rather than performative social media. Features include: * “I Resonated” reaction button on posts * Anonymous resonance counts visible publicly * Optional sorting/filtering by most resonated posts * Private “This Didn’t Resonate” feedback option (not visible to other users; used only for internal analytics and personalization) * Aggregate engagement signals used to improve content surfacing and recommendations --- Diary Feature (Personal Reflection System) Each user will have a **Diary**, which serves as their personal timeline of activity and reflection. Core functionality: * All public posts automatically appear in the user’s Diary, organized by date * Users can also write **private diary entries** that are never shared publicly * Clear distinction between: * Public posts (community-visible + stored in diary) * Private reflections (personal only) Diary capabilities: * Chronological timeline view of all entries * Ability to filter between public and private entries * Optional tagging of entries (e.g., reflection, advice-seeking, personal note) * Centralized place to revisit personal experiences over time --- Mood & Reflection Calendar Feature We also want a reflective mood tracking system inspired by apps like *Natural Cycles*. When users reflect or write in their diary, they can optionally select a **mood using an emoji-based system** (e.g., “Anxious 😟”, “Sad 😔”, “Calm 🙂”, etc.). Core functionality: * Users can attach a mood to each entry (optional) * Mood input should be fast and lightweight (emoji + label selection) Visualization: Users can view their data in: * Daily view (mood + associated entries) * Weekly trends * Monthly calendar or heatmap visualization of mood patterns Purpose: This feature helps users identify emotional patterns over time by connecting: * Mood states * Life events/reflections * Written posts Example: A user may notice repeated “anxious” moods on days involving a specific relationship dynamic, enabling deeper self-awareness and reflection over time. The goal is to support insight, not diagnosis — helping users better understand emotional patterns and triggers. --- Resource Library + Personalized Recommendations We are also building a curated **digital resource library** populated with materials from Stanford’s SHARE (Sexual Harassment/Assault Response & Education) office. Library may include: * Books * Articles * PDFs * Support resources * Educational materials Features: * Admin upload and management system * Categorization/tagging of resources * Personalized recommendations based on: * User posts * Diary entries * Mood data * Tag usage Recommendation system: Can initially be rules-based (no need for full AI at MVP stage) Examples: * Users expressing loneliness may be shown community/support resources * Users seeking relationship advice may receive relevant reading materials Privacy and sensitivity are critical to design. --- Analytics Dashboard (Admin/Internal) We need a basic analytics dashboard including: * Total users * Daily/weekly active users * Posts over time * Most-used tags * Most resonated-with posts * Resource engagement metrics * Repeat visitor tracking Advanced visualization requests: * Calendar view of engagement activity * Heatmap-style visualization for user engagement over time * Trend tracking for usage patterns (daily/weekly/monthly) We are open to recommendations for the best charting libraries/tools. --- Backend Development Requirements * Secure Stanford-only login/authentication * Stanford SSO preferred if feasible * Otherwise .edu-based restriction system * Database architecture and setup * Anonymous posting logic (ensuring privacy separation from identity) * User accounts and diary storage system * Saved posts/bookmarking system * Tag and category management * Moderation/reporting tools (basic MVP) * Scalable backend structure for future expansion --- Preferred Tech Stack Open to recommendations, but currently considering: * React / Next.js * Node.js * Firebase or Supabase * PostgreSQL --- Ideal Candidate * Strong full-stack web development experience * Experience building social or community platforms * Strong UI/UX instincts * Experience with authentication and secure systems * Comfortable building privacy-first products * Strong communication and fast execution mindset * Product/design thinking is a plus Bonus if you have experience with: * Anonymous social platforms * Mental wellness or student-facing products * Recommendation systems * Data visualization dashboards --- Deliverables * Functional high-fidelity MVP/prototype * Clean, documented codebase * GitHub repository handoff * Deployed staging/testing environment --- To Apply Please include: 1. Relevant portfolio/projects 2. Recommended tech stack for this build 3. Estimated timeline 4. Estimated budget range 5. Your approach to: * Anonymous posting architecture * Diary + mood tracking system * Personalized recommendation system 6. Any suggestions or improvements based on your experience We are aiming to move quickly and begin development ASAP.

We are looking for a highly skilled Full Stack Engineer who can go beyond development and act as a technical consultant for our clients. The ideal candidate should be comfortable communicating directly with clients, leading technical discussions, and eventually taking on a Project Manager role within our team. - Requirements Strong Full Stack Software Development experience Excellent verbal communication skills and confidence in client-facing calls Ability to provide technical guidance, project planning, and consulting Strong problem-solving skills and ownership mindset Comfortable working independently in a remote environment - Mandatory Conditions Must be available and responsive during U.S. business hours (EST/PST). This is not a full-time position initially, but timely communication is required. Must have a quiet home office, reliable high-speed internet connection, and a professional-quality headset. Must be comfortable participating in client meetings and technical discussions. - Growth Opportunity If you demonstrate strong performance and reliability during the first three months, we intend to transition you into a long-term paid position within our organization.

Expectations include setting up development, staging and production environments in AWS, creating and managing the CI/CD pipeline and support for front end development and integration with the API.