Skip to content
Original product buildJune — July 2025

Remote Work Marketplace

Built the original marketplace release through discovery and applications.

Nuxt · Vue · TypeScript · S3 · REST APIs · i18n

Context

I built the first version of a remote-work marketplace while its public identity was still taking shape. The product later moved through several names and ownership changes before evolving into the product that exists today.

I did not participate in those later rebrands. This case study covers the original product build, before ownership shifted to other developers as I moved to higher-priority work.

The exact public launch and domain-transition dates are no longer available, so I keep the timeline to what I can establish confidently: the initial implementation was built during June and July 2025, and the contributor pattern changed substantially beginning in August.

From shell to functional marketplace

The first release was more than a marketing page. I implemented the product path needed for candidates to discover an opportunity and submit their information:

  • responsive landing and navigation;
  • job-category and opportunity discovery;
  • opportunity list and detail pages;
  • Markdown-backed job content;
  • job-list and job-detail APIs;
  • contact and application forms;
  • candidate profile submission;
  • résumé upload;
  • S3 integration;
  • sitemap and SEO foundations;
  • internationalization structure;
  • legal content;
  • build, deployment, and production fixes.

I also established reusable buttons, links, cards, inputs, selects, and file inputs so the application could grow without every new screen inventing its own interaction patterns.

Working across the product path

This project required frontend implementation, server routes, file handling, content structure, storage, and release work in a short period.

The résumé-upload path is a useful example. A visible file input was only the first layer; the workflow also needed submission state, backend handling, object-storage behavior, and production fixes before it could support a real candidate journey.

That kind of end-to-end work became a pattern in the projects that followed.

Handoff

During June and July, I was the application's only contributor. Beginning in August, several other engineers became the dominant contributors while my activity dropped sharply.

That history reflects the handoff: I had delivered the original functional release, then shifted toward other higher-priority product and platform work.

What this project demonstrates

This project is evidence of early-stage product ownership:

  • turning an empty app into a usable workflow;
  • making reusable component decisions while moving quickly;
  • crossing interface, API, upload, storage, SEO, and deployment boundaries;
  • handing a working product to a wider team when priorities changed.

The later product evolution should not be read as entirely my work. My contribution was the foundation that preceded the later brand and ownership.