Technical Integration & Support Specialist (SQL, APIs, QA) — Supply Chain Software, Part-Time

FlexChain builds supply chain optimization software. Our clients are shippers, manufacturers and logistics providers who send us their operational data and use our platform to find savings and act on them. Clients run at high volume, and every client's data is isolated by design. We are hiring a part-time, ongoing technical resource to get each client's data into our platform, set up and test the integrations they need, check that outputs make sense, and handle the technical issues that come up along the way. This is a hands-on integration, QA and support role. It is not a senior engineering role, and we are not hiring for one. HOW YOU'LL WORK Most of the work happens in Claude Code against our codebase, conventions and runbooks. It will read the code, query the data and propose a fix. You are the one who confirms the answer makes sense, tests it, and explains it clearly. Someone who forwards whatever the tool said without checking is not a fit. WHAT YOU'LL DO Client data integration - Map client exports (order, shipment, product, location, supplier and rate files from ERPs, WMSs and logistics providers) to our schema and get them through validation without hand-editing rows - Resolve code and reference-data mismatches: map, request a new value, or push back to the client - Set up the client's account, users, locations, rates and run configuration, and confirm it with a first run - Work out what interface a client needs beyond a manual file (API-triggered runs, scheduled feeds, partner webhooks, SFTP), then set it up, test it end to end with real payloads, and QA it - Run a short weekly health check across live clients so a feed that has gone quiet is caught before the client notices - Verify optimization outputs before a client sees them and assemble the first-pass savings readout - Document each integration so the next one is faster Technical support - Take technical issues as they are escalated to you: a file rejected by validation, a run that failed or is stuck, status updates that stopped arriving, a number a client says doesn't match - Reproduce, trace the cause using logs and the database, and resolve it or hand it over with a clear write-up - Join calls with a client's IT team when the conversation is technical Small fixes and solutioning - Fix defects that surface during support and open a pull request; draft database changes as migration scripts for review - When a client asks for something the product doesn't do yet, analyze it, spec it, and present options with effort and tradeoffs WHAT YOU'LL WORK WITH Claude Code, GitHub pull requests, Postman or curl, read-only SQL access. Next.js, React, TypeScript. Azure SQL and T-SQL stored procedures. REST APIs and webhooks, n8n, Azure Functions. REQUIRED - You use Claude Code, Cursor or similar every day and can show how you check what it tells you - Solid SQL: enough to read a stored procedure, follow a number back through joins, and confirm or reject a diagnosis on your own - API and QA background: you have tested integrations for real (calling endpoints, reading webhook payloads, checking JSON against a spec, writing test cases, reproducing a bug step by step) - Working TypeScript: enough to review a diff and make a small change safely - Messy data is normal to you: column mapping, unit conversions, dirty codes, files that don't match the spec - Clear written English and the judgment to know when a fix is yours to make and when to escalate - Overlap with US Eastern hours. Latin America is a natural fit. From Eastern Europe you need to reliably cover until at least 2 pm ET. NICE TO HAVE - Supply chain or logistics exposure: shipping data, rate sheets, warehouse or 3PL systems - Spanish - Azure basics: App Service, Functions, SQL - Payment or shipping APIs in production ENGAGEMENT - Independent contractor, ongoing. Up to 20 hours a month to start, as needed. Hours grow as clients come on, with a path to a substantial part-time or full-time role. - Remote with US Eastern overlap. Blocking client issues are acknowledged within a couple of hours during Eastern business hours. This is not a 24/7 pager. - Contractor agreement and NDA before any system access. Please answer the screening questions in your proposal. Short and specific beats long.