We're a fast-moving company with a strong in-house backend team looking to add a dedicated frontend developer on a retainer basis. This is not a one-off gig, we need someone available, responsive, and able to execute quickly when projects move. We're expanding our dev capacity and want to bring on someone who is hands-on, communicative, and fully present on every project they take on. Direct collaboration with our internal team is essential, we move fast and need someone who moves with us. WHAT YOU'LL BE DOING: Working directly alongside our in-house backend developers, design team, and marketing team to build and maintain web interfaces, implement designs, and ship features quickly. You'll own the frontend layer completely. WHAT WE NEED YOU TO KNOW COLD: - Tailwind CSS — this is non-negotiable, it's our primary styling approach - React and TypeScript — you should be writing this daily - Laravel — familiarity required, it's a core part of our backend stack - Astro — familiarity expected, you'll encounter it in our stack - Clean, responsive UI implementation with an eye for detail WHAT WE'RE LOOKING FOR: - Someone who writes their own code and takes full ownership of their work - Strong availability during US business hours - Fast turnaround without cutting corners - Clear, proactive communication throughout every project TO APPLY, PLEASE INCLUDE: - Your portfolio or GitHub link - 2–3 examples of projects built with Tailwind + React - A short note on your availability and how you handle tight deadlines

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**

I have a production-ready React/TypeScript health record web application built with Lovable (AI app builder) that needs to be migrated to professional infrastructure I own before public launch. I also need Claude Code (Anthropic's AI coding CLI) set up so I can continue building features independently after migration without relying on Lovable. This is a one-time migration project with a clear scope and a complete data export already prepared. I need someone experienced, detail-oriented, and trustworthy — this is a health application handling sensitive patient data. What I already have: Vercel Pro account — ready to connect Supabase account — ready to create new project GitHub repository — connected and available Domain: fullycharted.app — DNS access available Complete bulk export ZIP from Lovable Cloud — all tables as CSV/JSON, all storage files, complete supabase/migrations/ folder 2 beta users currently — minimal data to migrate Mac computer for local development setup The application: React/TypeScript frontend with Vite and TailwindCSS Supabase backend — PostgreSQL, Row Level Security, Edge Functions, Storage buckets Supabase Auth for authentication 1,326 automated tests passing Currently hosted on Lovable Cloud fullycharted.app currently points to a separate landing page — needs to point to the full app after migration What I need done: Connect GitHub to my Vercel account and configure build settings for Vite/React and all environment variables Create new Supabase project in my account — run supabase db push using migrations folder, import all table data from CSV/JSON export, re-upload all storage files (lab documents, imaging, diagnostic studies), verify all Row Level Security policies working correctly Configure all environment variables — VITE_SUPABASE_URL, VITE_SUPABASE_PUBLISHABLE_KEY, VITE_ADMIN_EMAIL, and any others currently in Lovable DNS configuration — point fullycharted.app to Vercel, configure www redirect, verify SSL certificate Handle 2 beta user accounts — coordinate password reset timing before DNS cutover Full verification — app loads at fullycharted.app, login works, patient data intact, emergency view works without auth, file uploads work, admin route gated correctly, all 1,326 automated tests pass, RLS verified (no cross-account data access) Claude Code setup on my Mac — install Node.js, install Claude Code CLI, clone repository locally, configure local environment variables, verify app runs locally (npm run dev) and tests pass (npm test), walk me through one simple change so I understand the workflow Documentation and handoff — all environment variables documented, Vercel and Supabase configuration documented, local development workflow documented, GitHub push triggers Vercel deployment confirmed Security requirements: This is a health application. RLS policies must be verified after migration. Patients must only access their own data. Admin route gated to one specific email. Public emergency routes work without exposing other patient data. What I will provide: Access to my Vercel account Access to my Supabase account Complete bulk export ZIP GitHub repository access Domain registrar access for DNS Anthropic API key for Claude Code Quick responses throughout the project Success looks like: fullycharted.app loads the full application Beta users can reset password and log in with all data intact All 1,326 tests passing I own all infrastructure completely Claude Code installed, configured, working Complete documentation in my hands Follow-on work: I have a second application (MySynapse — homeschool platform) on the same stack needing the same migration in 1-2 months. Strong performance here leads to that second project directly. To apply please include: Examples of similar Lovable/managed platform to Vercel migrations Supabase RLS and migration experience Your approach to data integrity verification Confirmation you are comfortable with health app security requirements

Note: We are a well-funded startup with a very high engineering bar, working alongside senior engineers with experience from leading AI labs. This is a smaller initial paid task, but we pay well for excellent work and there is potential for a much larger collaboration if the fit is strong. Your PRs will be reviewed by strong engineers, so we are looking for someone who takes ownership, thinks clearly, and cares about shipping clean, production-ready code. Please only apply if you can hold yourself to that standard. We are not looking for generic AI-generated output or low-effort execution. # Implement Probabilistic Attribution Between Marketing Website and Electron Desktop App We have a marketing website where users can click to download our Mac desktop app. The app is distributed as a standard Mac DMG and built with Electron. We use PostHog for product analytics, and we also run Google Ads. Users may eventually sign in inside the desktop app through ChatGPT/auth, but many users will first be anonymous. We want to implement a simple first version of attribution that helps us understand which website visitors / ad campaigns / download clicks later become desktop app users. ## Goal Build a lightweight probabilistic matching system that connects: 1. A user visiting the marketing website 2. The same user clicking “Download” for the Mac DMG 3. The desktop app being opened for the first time 4. The user later signing in, when applicable The goal is not perfect identity matching. The goal is good-enough attribution for our current low-volume flow, roughly around 100 download clicks per week. ## What needs to be figured out The developer should determine the best simple implementation for: - Capturing enough information on the marketing website when someone clicks the Mac download button - Capturing enough information from the Electron app on first open - Matching those two events probabilistically on the backend - Passing useful attribution information into PostHog events - Associating the attribution with the authenticated user once the user signs in - Testing that the full flow works end-to-end The likely matching signals are things like timestamp proximity, hashed IP, platform, timezone, language/locale, and other non-invasive browser/app context. The implementation should avoid overcomplicated or privacy-invasive fingerprinting. ## What we should do Implement a simple backend-backed attribution flow: - When someone clicks “Download for Mac” on the website, create a download-attribution record. - Capture campaign data such as UTMs, Google Ads click ID if present, landing page, referrer, and PostHog anonymous/browser ID where available. - When the Electron app first opens, create or retrieve a persistent app install ID. - Send a first-open event from the app to the backend. - Backend attempts to match that first app open to a recent download click. - Store the match with a confidence level such as high/medium/low/unmatched. - Send attribution metadata as properties on relevant PostHog events. - Once the user signs in, connect the app install and attribution record to the authenticated user ID. ## What we should not do in this version We do not want to overbuild this. Do not: - Generate a unique DMG per user - Modify the signed Mac app bundle - Inject tokens into the installer - Implement custom deep links yet - Build a full deterministic attribution system - Use probabilistic matching to permanently merge PostHog user identities - Send raw IP addresses to PostHog - Add invasive browser fingerprinting Probabilistic attribution should be treated as estimated attribution, not as guaranteed user identity. ## Expected deliverables The task is complete when: - The website download flow records download intent and campaign metadata. - The Electron app records first-open/install metadata. - The backend can probabilistically match app first opens to recent website download clicks. - PostHog receives app events with attribution properties when a match exists. - The system links the app install to the authenticated user after sign-in. - There is a way to inspect/debug attribution matches. - The implementation is tested locally or in staging with realistic flows: - normal download → immediate app open - delayed app open - no matching download - multiple download clicks from the same network - user signs in after opening the app ## Important constraint This is a first version. We prefer a simple and maintainable solution that gives us useful attribution data over a complex solution that tries to be perfectly accurate.

Full-Stack Developer Needed to Migrate Replit Calibration Lab App to Local Server Environment Project Overview We have a custom Calibration Laboratory Management application that was developed on Replit and is currently functional. We are seeking an experienced software developer to migrate the application from the Replit environment to a locally hosted solution that can run on our company computers and servers. The goal is to create a stable, secure, and maintainable deployment that operates within our organization's network while preserving all existing functionality. Responsibilities Review and assess the existing Replit codebase Migrate the application to a local/on-premises environment Configure and deploy the application on Windows or Linux servers Migrate and configure the database (if applicable) Set up user authentication and security best practices Create installation and deployment documentation Provide recommendations for long-term maintenance and scalability Assist with testing and troubleshooting during deployment Required Skills Full-stack software development Experience with Replit migrations Node.js, React, Python, or similar web application frameworks Database administration and migration Windows Server and/or Linux server deployment Networking and local server configuration Docker experience (preferred) Git/GitHub version control Deliverables Fully functioning local version of the application Configured database and server environment Deployment documentation Backup and recovery recommendations Source code repository with all changes

We're building a data-driven platform in the beauty/cosmetics space. We've already collected a very large volume of scraped product and brand data, and it's messy - inconsistent formats, duplicates, missing fields, mixed languages, and unreliable values. Your job is to turn that raw data into something clean and reliable, and to build the web application on top of it. This is not a quick gig. We're looking for someone to stay with us for roughly a year and grow with the product. What you'll be doing Building and maintaining a Next.js (App Router) front end and back end Designing and managing our Supabase setup (Postgres schema, RLS policies, auth, storage, edge functions) Cleaning, normalizing, and deduplicating large beauty datasets (this is a major part of the role) Building data pipelines to process and validate incoming scraped data Writing transformation/normalization logic (units, brand names, categories, ingredients, pricing, etc.) Setting up data-quality checks and monitoring Iterating on features with us as the product evolves You should have Strong production experience with Next.js and Supabase (please point to specific projects) Solid SQL/Postgres skills - not just ORMs Real experience cleaning and normalizing large, messy datasets (Python/pandas or similar is a plus) Comfort working with scraped data and all the inconsistencies it brings Good written English and reliable communication Ability to work independently and own your part of the product Nice to have Experience in e-commerce, catalog, or product-data projects Familiarity with data pipelines / ETL tooling Some ML/NLP experience for entity matching or text cleanup Budget We expect this to run around $4,000–$5,000 USD per month depending on experience and hours. This is a long-term commitment, so stability and quality matter more to us than the lowest rate. To apply, please include: Similar past work - links or short descriptions of Next.js + Supabase projects, and at least one data-cleaning/normalization project you've done. Your time zone and your typical available hours - we need to know there's reasonable overlap. Your expected monthly budget within the range above (or your rate if hourly). Applications that don't address all three points will not be considered. A short note on how you'd approach cleaning messy beauty product data is a big plus. We read every proposal carefully and respond quickly to strong candidates. Looking forward to working with you.

We are interested in developing a web app that will allow us to automate a lot of the administrative tasks we need to do to carry out our work. The app will serve three main functions: 1) Provide a simple and easily accessible interface that will allow users to submit expense information that will be automatically stored in our organization's Google Drive. 2) Allow for admin to review this information and engage in a dialogue with the user if necessary. 3) Track all expense data in an organized way to a) allow users to view project expense summaries and b) allow admin to create and generate expense reports. Attached is an overview of how each interface should articulate with the others as well as a detailed summary of what each interface could look like. Note that the details here are not comprehensive and questions are expected, but the general shape is there. Note that these interfaces will need to effectively and seamlessly articulate with one another as well as external systems like Quickbooks.

Core Architectural Workflow 1. Client Intake & Data Collection The customer visits the Porkbun-hosted website and completes a secure, multi-step intake form. The form dynamically captures customer details, the specified number of signers, and handles secure multi-file document uploads. 2. Asynchronous API Triggering Blue Notary API: The website backend instantly delivers an API payload to Blue Notary to establish the live signing session container, pushing the customer data and uploaded document streams directly into the digital meeting room. QuickBooks Online API: Simultaneously, the backend contacts QuickBooks to check for an existing client record or generate a new Customer Profile. 3. Credit Card Tokenization (Vaulting) To maintain absolute data security and avoid PCI-compliance liabilities, the developer will embed the QuickBooks Web Payments SDK directly into the booking page. When the client clicks "Book," the secure iframe captures and tokenizes the credit card information with QuickBooks Payments, returning a secure payment token (paymentMethodToken). The website backend securely maps this token to the customer profile for later use; no actual credit card numbers are ever stored on our servers. 4. Post-Session Admin Portal & Dynamic Billing Because RON platforms track identity verification but do not consistently pass live, rolling digital stamp/seal counts to external billing systems in real time, the developer will construct a secure, password-protected administrative interface on our domain (e.g., /admin/billing). Upon logging out of a completed Blue Notary session, the admin opens this dashboard, selects the client, and types in the Actual Signers and Actual Seals Placed. Automated Billing Logic Formula Upon submitting the administrative form, the server executes the programmatic pricing formula: Total Invoice = Base Session Fee + (Additional Signers × Signer Rate) + (Additional Seals × Seal Rate) The backend automatically executes these final steps via the QuickBooks API: Generates a professional line-item invoice reflecting the base fee and exact volume variables. Commands QuickBooks Payments to immediately process the charge using the vaulted credit card token. Locks in the clean processing rate (e.g., flat 2.99% invoiced rate) with zero added per-transaction service fees or third-party overhead. Triggers the automated delivery of the official QuickBooks paid receipt directly to the client's inbox. Developer Job Posting Copy Project Overview: Looking for a talented full-stack developer to redesign/update a website hosted on Porkbun, build a custom multi-signer intake form with secure document upload, and integrate direct, custom backend automations with Blue Notary and QuickBooks Online. No third-party automation tools (Zapier/Make) are permitted. Key Deliverables: Frontend Intake Form: Clean, mobile-responsive design allowing secure file uploads and dynamic forms based on input signer counts. Direct Blue Notary Integration: Connect to Blue Notary’s REST API to instantly initiate a session and pass files upon customer submission. QuickBooks Payments SDK Integration: Implement secure credit card vaulting/tokenization at intake using the official QuickBooks Web Payments SDK. Admin Post-Session Billing Tool: Create a lightweight, secure internal portal where the admin inputs final signer and seal counts. Automated Invoicing Engine: Calculate the final pricing via code on admin submission, generate a line-item invoice in QuickBooks, charge the vaulted card token automatically, and trigger the receipt. Technical Requirements: Proven experience with backend languages (Node.js, Python, PHP, or Go). Deep familiarity with QuickBooks Online Accounting & Payments APIs (specifically tokenized card charges and invoice generation). Strong understanding of REST APIs, webhooks, JSON payloads, and secure file handling over HTTPS. Ability to deliver clean, documented, standalone code without external platform dependencies.

We are seeking a skilled TypeScript developer to integrate Square transactions and menu/inventory data into our MVP. The ideal candidate will have experience with Square APIs and be able to implement secure payment processing. This is a part-time, short-term project with a focus on delivering a seamless user experience.

Before you apply read this first.: This is not a standard contract. We are not looking for someone to build something and disappear. We are looking for a developer who genuinely cares about people experiencing homelessness and wants to be part of something that actually changes lives. If that is not you, this post is not for you. If it is keep reading. What Is Operation Iron Gate: Operation Iron Gate is a physical intake hub in Vallejo, California built specifically for the unsheltered. Any homeless person can walk through our door and receive help no matter what barriers they are carrying, no matter what their documentation looks like, no matter how many times they have been turned away before. The rule is simple: nobody gets denied. We call it Yes by Default. Instead of looking for reasons to say no, we look for the next valid move. Every single time.When someone walks in, a case gets opened immediately. Every barrier they are facing gets documented. A next step gets started before they leave the building. And the system tracks every single movement of that case every action, every referral, every handoff until they actually receive the resource they need. Not a phone number on a piece of paper. The actual resource. It sounds too good to be true. That is exactly why we built the technology to make it real. What You Are Building — Phase 1 Only: We are currently hiring for Phase 1 only. This is the core platform build. We are keeping it focused. Once the pilot launches in Vallejo and the system is proven in the real world, we will move into the AI layer and long-term development. But right now we need Phase 1 built right. The platform is called DSAS the Digital Steward Authorization System. It is the brain of Operation Iron Gate. Here is what Phase 1 covers: * Case creation engine when someone walks through the door, a case opens immediately. One screen, one submit. * Barrier capture system every barrier the person is facing gets documented and connected to a next action. * Yes by Default enforcement a denial without a legal reason code is blocked by the system itself at the database level. * Three-tier triage system urgent cases get a 2-hour movement deadline with auto-calculated countdown. * Steward escalation queue hard cases route instantly to senior reviewers who make binding decisions. * MDO Live View: real-time monitoring screen showing every active case, who owns it, where it is stuck, how long it has been sitting. * Automated alert engine fires when a case stalls, when a deadline is missed, when a partner does not respond. * Glass Dashboard public-facing transparency layer showing the community how the system is performing in real time. * All data feeds automatically from the system. No manual entry ever. * IGAC credential system when someone arrives without ID, a credential is issued immediately on Day 1 so the case can keep moving. * 7-role permission matrix enforced at the API level on every endpoint. * Append-only audit trail tamper-evidence logging. Nothing gets deleted or edited after it is written.. The full technical specification is already built: * Every database field is named. * Every logic rule is written. * Every automated alert is defined. * Every role permission is mapped. You are not figuring out what to build. You are building something that is completely designed and ready to be coded. Technical Requirements Required: * Strong backend / full-stack development 3+ years building complex platforms * Relational database expertise PostgreSQL or MySQL complex logic enforced at the database level * Role-based access control enforced at the API level * Automated alert engines time-based and condition-based triggers * Append-only audit logging with tamper evidence * Real-time data feeds * REST API development Strongly preferred: React or similar framework for front-end interfaces. Mobile-responsive design Access Points may operate from tablets and phones. Civic tech, social services, healthcare, or government platform experience. We are open to your stack recommendation. Tell us what you would use and why. Who We Are Looking For: We need someone who is technically strong. But more than that we need someone who reads about Operation Iron Gate and feels something. Someone who understands that every field in this database is a real person's life. Someone who will flag a problem in the spec before building it wrong. Someone who stays when things get hard. Someone who wants to be part of this mission not just compensated for it. If you are only here for the money, this is not the right fit. If you want to build something that matters we want to talk to you. Compensation: Read This Carefully: This is a fixed-price contract via Upwork with milestone-based payments. Here is exactly how it works and why we structured it this way. We are paying in four milestones. Every single payment is tied to something real being delivered and confirmed not just promised. * 25% on project start you have skin in the game from day one and so do we. * 25% when the database and core logic is confirmed complete confirmed by the developer handoff checklist, not by your word alone. * 25% when the full intake flow and MDO Live View is confirmed complete again, confirmed by the checklist. * 25% at final sign-off when every single item on every Tier 1 handoff checklist is confirmed complete Nobody gets paid until something real is delivered and confirmed. The checklist is the protection for both of us. You cannot say something is done and collect payment if the checklist says otherwise. That is not a lack of trust that is how professional projects get built correctly. There is one more thing we need in this contract and we want to be upfront about it. The contract will include a scope change clause. That means if we ask you to build something that was not in the original specification something we did not think of, something new that becomes a change order and gets priced separately. It does not get quietly absorbed into the fixed price and it does not become a source of resentment on either side. You build what is specified. Anything beyond that gets negotiated openly and fairly. Fixed rate. Milestone payments. Handoff checklist as the payment trigger. Scope change clause in the contract. That is how we protect Pathfinders for Hope's mission funding and make sure you get treated fairly too. Additional terms: * NDA required before any specifications are shared * Work-for-Hire Agreement required before development begins all code belongs to Pathfinders for Hope * Rate is negotiable based on experience To Apply: Submit your proposal with your answers to all eight questions, a description of your most relevant project, your recommended stack, your honest Phase 1 timeline estimate, and your rate. We are building the operating system that proves homelessness can be solved one city at a time. If that is the kind of work you have been waiting for, we want to hear from you.