Are you a backend engineer who enjoys debugging, improving existing systems, and completing real product features in a fast-moving startup environment? We are building a platform for the foodservice industry focused on bid management, rebates, contracts, invoices, and document automation. We are looking for a backend developer to help us fix, complete, and stabilize several important modules in our application. This will begin as a paid trial project. If the work is completed successfully, there is an opportunity for ongoing development work as we continue to grow. Main Tasks We currently have several backend modules already built, but they are incomplete, buggy, or not working as expected. Your main responsibility will be to review the existing code, identify issues, fix bugs, complete missing functionality, and make sure the modules work properly from end to end. 1. Invoice Management Module We currently have an invoice module, but it is not working as expected and has multiple bugs. This module also connects with Stripe, so we need someone who can troubleshoot and complete the Stripe-related backend workflows. Responsibilities may include: Debugging the existing invoice management module Fixing invoice creation, updating, viewing, and status logic Reviewing and fixing Stripe integration issues Ensuring invoice/payment data is handled correctly Improving API reliability, validation, and error handling Testing the full invoice workflow from admin and user perspectives 2. Contracts Module We currently have a contracts module, but it is not fully functional. At the moment, admins are not able to properly create contracts, and users are not able to view or sign open contracts. This module uses DocuSign, so experience with DocuSign or similar e-signature integrations is strongly preferred. Responsibilities may include: Debugging the existing contracts module Fixing admin contract creation workflows Fixing user contract viewing and signing workflows Reviewing and fixing DocuSign integration issues Ensuring contract statuses update correctly Handling permissions and access control for admins and users Testing the complete contract lifecycle from creation to signature 3. Document Classifier Module We have a document classifier module that works in some cases, but it fails when multiple files are loaded through S3 and has additional bugs. We need help stabilizing the file processing and information extraction workflow. Responsibilities may include: Debugging the existing document classifier module Fixing issues with multiple file uploads through S3 Improving information extraction reliability Handling batch file processing correctly Fixing bugs related to file parsing, storage, and classification Improving error handling and logging for failed document processing Testing single-file and multi-file workflows What You’ll Do You will be working primarily on backend development and debugging for an existing application. This is not just new feature development — we need someone comfortable jumping into existing code, understanding how the system works, finding bugs, and completing unfinished backend workflows. Your work may include: Reviewing and debugging existing Nest.js/TypeScript backend code Building and fixing RESTful API endpoints Working with Stripe, DocuSign, S3, and document-processing workflows Improving validation, permissions, error handling, and logging Testing APIs using Postman or similar tools Coordinating with frontend developers to ensure features work end to end Creating or updating backend/API documentation as needed Using Git and our CI/CD workflow for deployment Tech Stack Our current backend stack includes: Nest.js TypeScript REST APIs Stripe integration DocuSign integration S3 file storage Document classification / extraction workflows CI/CD pipelines Postman or similar API testing tools Slack and ClickUp for communication and task tracking Skills We’re Looking For The ideal candidate should have: Strong experience with Nest.js and TypeScript Experience debugging and completing existing backend modules Strong understanding of RESTful API design Experience with third-party API integrations Experience with Stripe is strongly preferred Experience with DocuSign is strongly preferred Experience with S3 or cloud file storage is preferred Ability to troubleshoot complex backend bugs Strong API testing skills using Postman or similar tools Good understanding of authentication, authorization, and permissions Ability to write clean, maintainable code Clear communication and reliable follow-through Comfort working in an agile startup environment Compensation and Trial Period This role will start with a paid trial sprint. Compensation is $100 per completed 2-week sprint, paid after successful completion, testing, and verification of the assigned sprint work. We understand this is modest starting compensation, but we are looking for someone who wants to grow with the company. If the initial work is completed successfully, we would like to continue working together on additional backend features, improvements, and platform modules. There may also be an opportunity for full time employment consideration after a successful trial period, based on performance, reliability, and long-term fit. Why Join Us? Meaningful Product Work Your work will directly improve core parts of our platform, including invoices, contracts, payments, and document automation. Startup Growth Opportunity We are an early-stage company building in the foodservice bid and rebate space. The right person can grow with us as the platform expands. Real Ownership You will not just be assigned small isolated tasks. You will help complete important backend modules that are central to the product. Flexible Collaboration We use Slack and ClickUp to manage tasks and communication. Standups may be scheduled as needed, and we work in an agile sprint-based structure. How to Apply Please apply with: A brief summary of your backend experience Your experience with Nest.js and TypeScript Any experience with Stripe, DocuSign, S3, or document processing Examples of backend modules or integrations you have built or fixed Your availability for a 2-week sprint Confirmation that you are comfortable working on a paid trial sprint with the possibility of ongoing work We are looking for someone who can start by helping us fix and complete the invoice, contracts, and document classifier modules. If the work goes well, we would like to hire you for additional backend development work as we continue building the platform.

I need a backend developer to deploy an already-written Node.js/Express server to Railway, connect it to an existing Supabase project, and complete a third-party OAuth/webhook integration with the Garmin Connect API. This is a deployment and configuration task, not a build task. Expected time: 3–6 hours for someone experienced with this exact stack. What’s already done • Server code is fully written (Express routes for OAuth callback, webhook receiver, token refresh, deregistration) • Supabase database schema is created with tables and RLS policies • Supabase private storage bucket is created • Code runs successfully on localhost What you’ll do 1. Deploy the provided GitHub repo to a Railway project I’ve already created 2. Configure environment variables in Railway 3. Verify the deployed health check endpoint responds correctly 4. Set up a Railway Cron job for hourly token refresh 5. Provide me with three endpoint URLs to register with Garmin (I’ll handle the Garmin portal myself — you won’t need access to it) 6. Run an end-to-end smoke test using Garmin’s API testing tools to confirm the full flow works (webhook received → FIT file downloaded → stored correctly) 7. Document any bugs you find and fix What you’ll be given access to • A standalone GitHub repo (just this server — not my main app codebase) • My Railway project (Member role) • My Supabase project (Developer role) • Environment variable values, shared securely once you’re onboarded What you will NOT need or have access to • iOS app codebase • Garmin Developer Portal login • Any production user data (this is a 5-person alpha test — no real user data exists yet) • Any other part of my systems Requirements • Demonstrated experience deploying Node.js/Express apps to Railway (please share an example or describe a past project) • Experience with OAuth 2.0, ideally including PKCE flow • Experience with Postgres (Supabase or similar) including basic schema/RLS understanding • Comfortable working from a written technical brief with minimal back-and-forth • Available for a short, focused engagement — not looking for ongoing work right now (though that may be possible later if this goes well) Budget & terms • Fixed price for defined scope, paid via Upwork • Budget: $300–500 depending on experience, payable on completion of the smoke test • All access (GitHub, Railway, Supabase) will be revoked/rotated at the end of the engagement — this is standard practice on my end, not a reflection of trust To apply, please answer 1. Have you deployed a Node/Express app to Railway before? Please describe briefly. 2. Have you worked with OAuth 2.0 PKCE flows? In what context? 3. In one or two sentences: how would you handle a webhook that must respond within 30 seconds, but also needs to do slower async work (like downloading a file) afterward? 4. Your availability to start and rough timeline to complete Looking forward to hearing from 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.

Stripe Connect marketplace integration including: Client pays for a booking through the platform Payment is held by Stripe until the shoot is marked complete Platform automatically takes 15% commission Videographer receives 85% paid out to their connected bank account Videographer onboarding flow to connect their Stripe account and enter payout details Refund handling if a booking is cancelled before the shoot Booking status updates automatically when payment is made, held, and released Both client and videographer dashboards show accurate earnings and payment history NEXT: Email notifications via Resend when a booking is confirmed, payment is received, and payout is sent An admin dashboard where I can see all bookings, payments, and platform activity in one place What I'm looking for in a developer: Someone who has specifically built Stripe Connect marketplace integrations before, not just general Stripe experience but the full marketplace split payment setup. Please include examples of marketplace projects you've built in your proposal. Please answer these three questions in your proposal: Have you built a Stripe Connect marketplace integration before? If yes describe the project briefly. What is your estimated timeline for this specific scope of work? What is one potential challenge you'd anticipate with this project and how would you handle it? If you're interested and looking to take the site to next level. I would love to chat more, tell you about the business and see if we would be a good fit!

WHO WE ARE LOOKING FOR We are a digital strategy firm managing website builds for B2B clients. We are not looking for a one-off hire — we are looking for a reliable WordPress developer or small team to become our go-to partner for an ongoing pipeline of work. This posting is for our first project. We have three additional similar projects coming in the next few weeks, all with the same profile: React prototype to WordPress conversion, custom interactive components, deployment to client hosting. If this first project goes well, we will bring you all of them. After each launch, we expect ongoing maintenance and update work on a per-project basis. If you are looking for a single project, this is not the right fit. If you want a consistent source of well-specified work with a team that communicates clearly and pays on time, read on. THE PROJECT We have a fully designed and approved React/Vite website prototype for a B2B commercial services company. The design is finished and client-approved. We need it converted into a production-ready custom WordPress theme and deployed to the client's hosting account (GoDaddy or SiteGround). This is a conversion project, not a design project. Your job is to build what already exists in the prototype — exactly as it looks, exactly as it behaves. No design decisions required from you. Full technical documentation including the prototype URL, page specifications, and a detailed component spec will be shared with qualified applicants after an initial screening conversation. SCOPE The site is 15 pages. The most complex component is an interactive Google Maps portfolio map showing 400+ real project locations with marker clustering, state-level shading, a filter panel, and a click-to-expand project detail view. There is also a multi-step JavaScript ROI calculator on the homepage that must be rebuilt with full functional parity. The theme must be a fully custom WordPress theme — no Elementor, no Divi, no WPBakery, no page builders of any kind. The client needs to make basic text edits through Gutenberg without breaking the design. Advanced Custom Fields or equivalent is required for structured content. You will also handle deployment: WordPress install, theme setup, DNS coordination, and go-live confirmation on the client's hosting account. TECHNICAL REQUIREMENTS The site must hit a PageSpeed mobile score of 75 or higher. Google Fonts must be self-hosted — not loaded from the CDN. Images must be served in WebP with proper srcset. The Google Maps script must load asynchronously and only on the portfolio page. The design uses sharp corners throughout (border-radius zero) and a specific color system that must be preserved exactly. Every page needs individually configurable meta titles, meta descriptions, and Open Graph tags. The theme must be compatible with Yoast SEO or Rank Math. ONGOING RELATIONSHIP After each project launches, we will bring you maintenance and update work on a per-request basis — content updates, new pages, plugin updates, client revisions. We scope and pay per request, no retainer required. We are looking for someone who wants to be our first call, not a one-time vendor.

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

Project Overview We are seeking an experienced React developer to complete and enhance an existing web-based title and real estate document management application. The software is approximately 80% complete and is currently deployed and operational. The application is used to manage title search orders, enter title data, track chain of title information, and generate real estate-related documents. We are looking for a developer who can review the existing codebase, understand the current architecture, and complete the remaining development tasks. Current Technology - Existing React-based web application - Source code maintained in GitHub - AWS-hosted deployment - Existing database and user interface already functioning Scope of Work 1. User Interface Enhancements - Add new data entry fields throughout the application - Modify existing forms and layouts - Improve usability and workflow efficiency - Ensure data validation and proper field formatting 2. Title Data Management - Enhance title search and chain-of-title data entry screens - Support additional title-related information fields - Maintain automatic organization and sorting of title records 3. Dynamic Document Assembly - Complete the document generation system - Generate Microsoft Word documents from entered data - Populate templates with user-entered information - Conditionally include or exclude sections based on available data - Support dynamic chain-of-title sections (for example, if there are 9 title transfers, generate 9 sections instead of a fixed number) 4. Mapping Features - Complete mapping functionality - Display property-related mapping information - Integrate mapping data into the workflow where appropriate Ideal Candidate - Strong React experience - Experience working with existing codebases - Experience with AWS deployments - Experience with document generation and template systems - Ability to understand business workflows and recommend improvements - Strong communication skills Deliverables - Review existing application and provide assessment - Complete outstanding features - Test all functionality - Deploy updates to production environment - Provide documentation for future maintenance To Apply Please provide: 1. Relevant React projects you have completed 2. Experience working with AWS 3. Experience with dynamic document generation or template systems 4. Estimated availability 5. Your approach to taking over and completing an existing application We are looking for a long-term relationship with a developer who can continue improving the platform after the initial project is completed.

ePanicButton is an 18-year-old B2B SaaS real-time alert platform (Windows desktop client, React Native mobile app, admin portal, REST API), mid-way through a major modernization: portal rebuild, production server migration, and a shift toward AI-assisted development. We're a small, bootstrapped business — no VC funding, no big budget, and no room for enterprise-scale overhead. We need a senior engineer with real entrepreneurial experience — someone who's built or run their own thing and knows how to bring enterprise-grade discipline to a lean operation without over-engineering it. This is primarily a hands-off oversight role: the founder handles day-to-day setup and coding using AI tools (Claude, Claude Code), and you review the work, verify the high-risk items yourself, and weigh in on major architecture decisions. When something gets stuck — a deployment issue, a security question, an architecture call that matters — you're able to step in directly and get hands-on to unblock it. You'd effectively be the technical boss: the founder builds day-to-day, and you set standards, review and verify the work, and own final say on the platform's operational integrity — all in a way that fits a small company's budget and pace. ## Priorities, In Order **1. Secure and stabilize the program.** Get infrastructure, credentials, certificates, source control, and deployment process under real, enterprise-grade management so the platform runs effectively and reliably — no more surprises. **2. Establish AI-driven development and program management.** Build the process, guardrails, and review discipline for a workflow where the founder handles the actual AI-assisted coding, and you own the architecture decisions, code review, and release management around it. **3. Bittensor integration.** Help guide and oversee the buildout of our REST API messaging layer to serve the Bittensor decentralized AI mining/subnet community as a new channel-partner market. ## Core Responsibilities - Review infrastructure architecture, server management, backup, and disaster recovery decisions; personally verify high-risk items (credentials, DNS, prod access) rather than just reviewing notes about them - Oversee consolidation and hardening of credentials/secrets management; confirm it's actually done right, not just described as done - Confirm certificate lifecycle management is properly set up and tracked (SSL/TLS, renewals) - Set standards for GitHub structure, access control, branch strategy, and release process; step in directly if something gets stuck - Review and approve AI-generated code and architecture before it hits production; weigh in directly on major architecture decisions - Be available to get hands-on and unblock things — a stuck deployment, a security question, an architecture call that matters — even though day-to-day execution isn't the default expectation - Mentor the founder as a working AI-assisted developer; coordinate outside contractors toward one architecture - Weigh in on strategy for the Bittensor/API-partner buildout once the foundation is secure ## What We're Looking For - Senior engineer (CTO, VP Eng, Head of Infrastructure, or equivalent) with real production ownership at scale - Entrepreneurial background — has run or built something of their own, not just managed inside someone else's org - Comfortable working with a small, bootstrapped company's budget and pace — pragmatic about scope, not looking to build enterprise overhead we can't afford - Primarily comfortable in a review/oversight capacity, but able and willing to get hands-on directly when something is stuck or a decision is high-stakes enough to warrant it - Comfortable with server/cloud infrastructure, DNS, certificates, and secrets management discipline - .NET/SQL Server background (our stack); ASP.NET Core, SignalR, Azure/Windows Server a plus - Real current experience working alongside AI coding tools — comfortable reviewing and directing AI-assisted dev, not just aware of it - Strong communicator who can explain technical risk clearly to a non-developer founder **Nice to have:** B2B SaaS / white-label / multi-tenant experience, real-time notification systems, familiarity with Bittensor or decentralized AI/Web3 ecosystems, prior fractional CTO experience with founder-led companies. ## How We Work This is a genuine partnership for our next stage of growth, not a one-off audit — we're securing the platform's foundation, then building out the AI-driven development process, then expanding into the Bittensor/API-partner market. Expect close communication, real decision-making authority, and someone who wants to grow into this alongside us.

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.

We're looking for a heavy-hitting lead developer to build our new ERP project from scratch using a .NET back-end, an Angular front-end, and a SQL database. This is a massive, end-to-end initiative, meaning you will completely own the roadmap, system architecture, team leadership, and final rollout. We need an expert who can sit down with our department heads, figure out our operational needs, and actually design a clean SQL database schema and scalable cloud infrastructure to make it happen. You'll be managing our .NET and Angular developers directly, so you need to be highly comfortable keeping complex software builds on track and speaking their language. Realistically, we need someone with at least seven years of experience under their belt, specifically leading large-scale enterprise ERPs built on Microsoft and modern web stacks. This is a full-time role with solid competitive pay and benefits depending on your setup.