Lead Full-Stack Engineer to own a working B2B ordering portal.

Nexis3 is a cabinet and door manufacturer in Rochester, NY. Over the past month we've built a customer ordering portal on top of our ERP's product and pricing data. The hard parts are proven and working locally. We're now hiring one engineer to own the product: implement the finished design, build the production backend, take it live, and keep it running. This is an ownership role, not a ticket queue. The owner (me) sets direction, owns the ERP data and rules, and tests. You own the software. WHAT ALREADY EXISTS - A working React/TypeScript portal (order builder, catalog, order history, account) and an internal order-desk app, running against real data on our network. Functionally complete for our first product line; visually a proof of concept. - A finished design for the production UI, delivered as an exportable design bundle: navigation, dashboard, order builder, order desk, light and dark themes. - A pricing/configuration engine that replays our ERP's own rules from a read-only projection — validated against 800 historic order lines at 100% configuration and 99%+ pricing agreement. Versioned library, tested, no runtime dependencies. - Read-only extractors from on-premise SQL Server: public catalog data, and private per-customer orders and organizations, with validators and documented schemas. - A documented API contract with a local dev implementation the portal already runs on; the order export in the XML our ERP imports, proven end to end. - Two GitHub repos with architecture docs, decision logs, a schema reference, and a screen inventory of what's v1. WHAT YOU'LL DO Front end - Implement the finished design on the existing data layer (provider seam, evaluator, API client). Restructure and restyle; keep the behavior the current screens define. Token-based theming for light/dark. - Bring in a front-end or design specialist under you if the reskin warrants it. Backend and operations - Production backend implementing the API contract: dealer and staff accounts, authentication, server-side per-tenant authorization, staff act-on-behalf. - Hosting on Azure: app service or containers, Azure SQL, secrets, HTTPS, backups, GitHub deploys. - Production sync: schedule the existing extractors against on-premise SQL Server and publish to Azure, validators as a gate. - Reliable order delivery from cloud to our on-premise ERP import folder: retries, idempotency, a record of every send, confirmation back. - Order status to customers with email notifications; conversation and file store per order; two-way email; Stripe for customers without terms. - Logging, monitoring, alerting, on-call. Out of scope: the pricing engine's rules and ERP-side catalog work — those have an owner. OUR STACK TypeScript throughout: React + Vite, Node extractors, Fastify dev API, mssql. SQL Server on premises. Azure. GitHub. A .NET backend is acceptable if you make the case; the API contract is language-neutral. WHO WE'RE LOOKING FOR - You've owned a product end to end: shipped a UI to a finished design, built and run the backend, and lived with it in production — auth, deploys, backups, monitoring, incidents. - Strong React/TypeScript and strong SQL Server and Azure. Comfortable with hybrid: the source of truth stays on premises. - You've built cloud-to-on-premise integrations and know where handoffs break. - Security-minded by default: per-tenant isolation, secrets, fail-closed authorization. - You work well with a hands-on, technical owner who knows the ERP deeply and uses AI coding tools: you read the repos before proposing, write things down, demo weekly, and say so when you disagree. Nice to have: Stripe, transactional email, manufacturing or configurable-product experience. HOW WE'LL WORK Phase 1 — paid discovery, about one week: read the repos, the contract, and the design; review the Azure environment; propose an architecture and a phased plan with an estimate. We expect you to push back on something. Phase 2 — production foundation and the UI: hosting, auth, sync, delivery pipeline, and the finished design on the existing data layer. Goal: the first real dealer places an order through the portal and it lands in the ERP. Roughly 8–12 weeks, subject to discovery. Phase 3 — notifications, messaging and files, email, Stripe. Ongoing — retainer for operations, on-call, and enhancements (a second product line is already in preparation). Remote is fine with 3–4 hours daily overlap with US Eastern. Shortlisted candidates get read access to the repositories and the design.