Freelance Node.js Developer Portfolio: Scalable Back-End & Web Solutions
Need a freelance Node.js or back-end developer? Below is back-end work I’ve delivered for companies worldwide — from scaling a Node.js SaaS platform from 50,000 to over a million users, to aggregating half a dozen third-party APIs into one reliable feed. As a freelance full-stack developer, I handle everything from database and API design to the user interface, working with Node.js, AWS, and MongoDB. Explore the projects below, or see my full portfolio for the full range of my work.
The problem: GoSchoolBox is the backend connecting school districts with tutoring companies. Growing from 50,000 to over a million users surfaced serious back-end bottlenecks such as slow page loads, gateway timeouts, and inconsistent responses under load.
The approach: I profiled the Node.js back-end to find the real bottlenecks, added APM (Datadog) for real-time visibility, refactored the critical workflows that buckled under heavy load, and rewrote slow MongoDB queries and indexes so lookups across millions of records ran in seconds.
The outcome: a stable back end that scaled past a million users with high throughput and consistent response times.
- AWS
- Datadog
- MongoDB
The problem: Stackbit’s website builder needed enterprise-grade features for large clients — managing projects across multiple roles and hierarchical structures, securely and at scale.
The approach: On the Stackbit team, I helped design and implement the backend for role- and hierarchy-based project management, focused on scalability, security, and collaboration.
The outcome: robust enterprise functionality that let large clients manage projects across teams and roles.
- Node.js
- MongoDB
- React
The problem: Burro’s customers needed to create, manage, and optimize navigation routes for fleets of autonomous farming robots, with that route data organized and reliably delivered to the robots.
The approach: I built a web app (React + Leaflet.js) backed by Node.js that lets customers draw and manage routes, integrating with Burro’s backend systems so route changes flow to the robots in the field.
The outcome: a streamlined route-management workflow that made a complex robotics task intuitive for customers.
- Node.js
- React
- Leaflet.js
The problem: Provenance needed backend systems built to align with business goals and hold up as the product scaled.
The approach: As the Node.js developer, I built and optimized the backend, worked with cross-functional teams to establish efficient workflows and clean, maintainable code, and made proactive technical improvements before they turned into debt.
The outcome: a maintainable, scalable backend foundation the team could keep building on.
- AWS EC2
- Node.js
- React.js
The problem: an investment platform needed investors to discover deals, connect with co-investors, and run virtual investment clubs, which meant secure documents, payments, and real-time comms all had to work together reliably.
The approach: I built the backend integrations with Docusign (secure signing), Stripe (payments), and Slack (real-time communication), and modeled the deal-tracking and investor-interaction flows for curated private groups.
The outcome: a scalable platform where the critical third-party services worked together seamlessly, supporting the platform’s growth.
- React
- Node.js
- MongoDB
The problem: Saycaster lets podcasters attach interactive “spots” (links, embeds, images, video) to specific moments in an audio track, which needs a backend that models time-anchored data and serves it reliably to listeners.
The approach: I built the platform on Node.js and PostgreSQL, designing the data model for spots tied to moments in a recording, and the APIs that deliver them into the listening experience.
The outcome: a backend that turns passive audio into structured, interactive content.
- Node.js
- PostgreSQL
- React
- D3.js
The problem: a Gatsby site needed continuously fresh, reliable content pulled from several unrelated sources such as crypto exchanges, GitHub, Twitter, Telegram. Each with its own API and rate limits.
The approach: I built a Node.js backend service to aggregate and process data from all of these APIs into one consistent feed, deployed on AWS for reliable, hands-off operation.
The outcome: a dependable data layer that keeps the site current automatically and insulates the front end from the messiness of each source.
- Node.js
- AWS
The problem: Filipi, a furniture e-commerce store on Next.js/Node.js/MySQL, needed its backend infrastructure hardened and kept running smoothly through a critical server migration.
The approach: I improved the backend infrastructure and managed platform operations throughout the migration to keep the store stable.
The outcome: a smooth migration with no disruption to store operations.
- Next.js
- Node.js
- MySQL