DO NOT SEND AN AI GENERATED PROPOSAL. READ THROUGH THIS POST AND GIVE US YOUR HUMAN RESPONSE. Location: Remote Team size: Small (you’ll know everyone’s name) Stack: Java 21 / Guice / Gradle backend + React 19 / TanStack / MUI frontend **To apply** 1. Give us a few sentences for why you're a fit for the description below. 2. Include a Github/Gitlab/Gitea link to a recent PR you’re proud of (any language) 3. 5–10 minute Loom of you using Claude Code on a real task. **About the role** QAction is a large-scale Java enterprise document, records, and workflow platform — multi-project Gradle build, ~15 modules, customer-specific deployments (USDA, Ditco, Ascension, Mayo). The backend is being modernized behind an OpenAPI v2 surface (oasv2); the frontend is being rebuilt off GWT onto React 19 + TanStack Router/Query/Start with MUI v7. We need a developer who’s equally comfortable extending a v2 endpoint in a Guice-wired Java service as they are wiring up a TanStack Query call behind a Lexical editor or a virtualized data table — and who treats Claude Code as a peer on the keyboard, not a novelty. You’ll work directly with the product lead. No layers, no JIRA theater. Ship, review, iterate. **What you’ll do** Own vertical slices end-to-end: OpenAPI spec → Manager/ManagerImpl + EndpointImpl in QAction Java → React 19 / TanStack Query UI → JUnit + Playwright coverage. Extend the QAction Java backend: Guice (constructor injection only), Hazelcast-aware code paths, customer-deployment-aware module wiring, JUnit under oasv2. Build Modern UI features in the React 19 stack: TanStack Router/Query/Start, MUI v7 + Emotion, React Hook Form + Zod, Lexical, dnd-kit, OIDC auth (oidc-client-ts), TypeScript with the wrapper-component discipline already in place (Button, Icon, LabeledObject, ScrollShadows, etc. — never raw MUI in features). Move features off GWT onto the React 19 stack one slice at a time, without breaking the legacy app. Pair with Claude Code daily — write prompts that ship code, review agent diffs critically, and improve our skills/agents library when the workflow has friction. Keep integration tests honest: real DB + Solr + Keycloak at the seam, not mocks. Tech direction you’ll be living in **Backend** Java 21, Gradle multi-project (build single modules — ./gradlew QAction:build — never clean build) Guice DI, constructor injection, Manager/ManagerImpl naming (we don’t use “Service”) OpenAPI-first v2 endpoints in oasv2, canonical error model, paginated response classes as standalone beans in oasv2.beans Hazelcast clustering, Solr search, Postgres/MSSQL, Keycloak/OIDC FileNet integration, document import/migration tooling, RMT/remote services **Frontend** React 19 + TypeScript, Vite 7, TanStack Router + Query + Start + Table MUI v7 + Emotion, MUI X Date Pickers + Tree View Lexical (rich text), @dnd-kit + Atlaskit pragmatic-drag-and-drop, react-virtualized, react-pdf React Hook Form + Zod, oidc-client-ts + react-oidc-context, notistack, pino File naming kebab-case, @/ path imports, theme-first styling, wrapper components over raw MUI Adjacent surfaces in scopes over time **What we’re looking for** 8+ years shipping production app code across backend and frontend. You’ve owned services and UIs, not just one or the other. Java fluency — Guice or Spring DI, REST/OpenAPI design, JUnit. Bonus if you’ve worked in a 1M+ LOC enterprise Java codebase with customer-specific module deployments and didn’t flinch. Modern React fluency — React 18/19, TypeScript, TanStack Query (or React Query), a real opinion about effect dependency graphs, comfort with virtualized tables and rich-text editors. OpenAPI-first thinking. Specs are the source of truth, not documentation written after the fact. Claude Code power user. You write prompts that delegate well, you know when to use a subagent vs. inline, you’ve built or extended skills/hooks/MCP integrations. You can show us a recent session where Claude shipped something non-trivial under your direction. Small-team temperament. You’re allergic to ceremony. You read code before asking. You raise a small PR when it’s ready. **Nice to have** GWT (you won’t write new GWT, but you’ll need to read and migrate it). Workflow / BPMN, records management, e-signature, or ECM domain experience. Hazelcast, Solr, Keycloak operational familiarity. Lexical or another modern rich-text editor. Playwright (you’ll inherit a calibrated suite — we want you to improve it, not rewrite it). Docker compose stack bring-up across Postgres, MSSQL, Solr, Keycloak. Python services or Helm/Kubernetes deployment experience. **How we work** Small PRs. Every change ships through review. If it’s getting big, split it. Test-driven design. Tests come with the code, not after. JUnit on the Java side, Vitest + Playwright on the React side. Daily standups. 15 minutes, async-friendly, but we show up. Memory-backed Claude Code sessions — agents learn the codebase with you, not against you.

SEEKING HIGHLY MOTIVATED US DEVELOPERS / AMERICAN CITIZENS ONLY! Full-Stack and Mobile Developers needed for Back-end, Front-end, and Mobile development. We are seeking AMERICAN developers who have strong skills in PHP, Python, Java, Javascript, React, Vue.js, Typescript and Flutter. Both Web application and Mobile application development work available. Experience with data scraping / data analysis is a plus. Must have excellent command of Linux, SQL, and Git. No slackers, no agencies, no middlemen, no "teams". Please be the person you claim to be, and please be the individual who proposes to do the work. Serious candidates only. *NO VIBE-CODERS* *NO WINDOWS USERS* Please be a Mac or Linux user for your personal machine. You must be able to connect to our Linux servers and ready to hit the ground running with no issues. You must be motivated, enthusiastic, and ready to get to work. Must be willing to have brief 20-minute VIDEO interview. Be ready to bring your A-game! THIS JOB IS AVAILABLE FOR U.S. CITIZENS ONLY.

We’re looking for an experienced Full-Stack Developer to build and refine a modern, responsive web application. You should be comfortable owning both the front end and back end, working independently, and turning clear requirements into a polished, reliable product. What You’ll Do Build and maintain the web application from front end to back end Create a clean, fast, mobile-responsive UI Develop backend functionality, APIs, and database integrations Implement user authentication and account functionality Integrate third-party APIs/services as needed Test, debug, and optimize performance Deploy and maintain the production application What We’re Looking For Strong full-stack web development experience Excellent JavaScript/TypeScript skills Experience with modern frameworks such as React/Next.js Strong backend and database experience Experience with APIs, authentication, cloud deployment, and Git Ability to write clean, scalable, well-documented code Strong communication and ability to work independently Important: We want a developer who can think through problems and recommend solutions—not someone who simply waits for step-by-step instructions. When applying, please send 2–3 examples of web apps you personally built, briefly explain your role in each, and include your availability and hourly rate.

We are seeking a part-time frontend-leaning fullstack developer to migrate our marketing website from WordPress to a Next.js + Sanity stack. The ideal candidate will have experience in both frontend and backend technologies, with a strong focus on Next.js and Sanity. The role involves ensuring a seamless transition while maintaining the site's functionality and design. The commitment is around 20 hours per week.

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.

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!

We're looking for a API Technical Writer to create and maintain developer-facing documentation for our API products in a healthcare/SaaS environment. This role partners closely with Product and Engineering to produce API documentation, release notes, and customer-facing content for minor and major releases. The ideal candidate has real development experience, is comfortable working inside engineering workflows (not just editing docs after the fact), and can champion a document-first approach to API development. What You’ll Do • Create and maintain API documentation and customer-facing release notes for minor and major product releases in partnership with Product and Engineering teams. • Apply OpenAPI Specification (OAS 3.0) standards and champion a documentation-first approach, ensuring API contracts are clearly defined and aligned before development begins. • Write and maintain documentation in Markdown using Git-based workflows and participate in GitHub release and publishing processes. • Test and interact directly with REST APIs to validate functionality and create accurate examples and documentation (e.g., curl). • Explore opportunities to leverage AI and automation to improve documentation quality, maintenance, and API change tracking. • Independently gather information through hands-on experimentation and collaboration with subject matter experts to create technical documentation and process guides. • Maintain and organize technical reference materials, research, design specifications, and other documentation assets. • Continuously evaluate and improve documentation, partnering with Customer Success, Support, and customers to identify content gaps and enhance the developer experience. What You’ll Bring • Experience creating and maintaining developer-facing API documentation. • Working knowledge of the OpenAPI Specification (OAS 3.0) and API contract-based development practices. • Experience working in GitHub, including pull requests, branching strategies, and release/publishing workflows. • Strong Markdown writing skills and experience with Git-based documentation platforms. • Ability to call, test, and experiment with REST APIs and document JSON request/response payloads. • Experience creating API examples using curl; experience with JavaScript, Java, PHP, or similar languages is a plus. • Strong technical writing skills with the ability to translate complex product and engineering concepts into clear, accurate, and user-friendly documentation. • Demonstrated ability to independently learn technical systems and drive documentation efforts with minimal oversight. • Ability to thrive in a fast-paced, collaborative SaaS environment. Preferred Qualifications • Prior experience in healthcare and SaaS environments. • Familiarity with healthcare data and interoperability concepts, including PHI handling, patient identifiers, NPIs, and clinical workflow terminology. • Experience documenting integrations with EMR/EHR platforms such as Epic. • Ability to read and understand production code, API implementations, and system integrations. • Hands-on software development experience writing or maintaining production applications, APIs, or integration solutions. • Familiarity with TypeScript and/or JavaScript. • Experience serving in a hybrid Technical Writer, Documentation Engineer, or Developer Documentation role. • Interest in AI-assisted documentation workflows, content automation, or API change-tracking solutions.

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're looking for a senior full-stack engineer to take on hands-on work across our web platform, architecting features, building APIs, and delivering polished, performant UI. Looking for someone that can do full stack but is heavy UI developmenet leaning. You'll be doing: Building full-stack features end-to-end (dashboards, booking, payments, admin tools, etc.) Modernizing existing code and reducing technical debt Node.js services, REST APIs. Performance optimization across front-end and backend CI/CD, automated testing, container-based deploys You should have: 8+ years building production web apps Strong TypeScript across a modern framework (React) Solid Node.js / Express backend experience AWS or GCP, Docker, and CI/CD experience Comfort with PostgreSQL Automated testing (Jest, Vitest, or similar) Bonus: AdonisJS, Golang

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.