Frontend Developer / Site Cloner (custom + Railway)

About the role

We run a portfolio of ecommerce brands. No hosted store platforms, no WordPress, no page builders — we build our own custom sites, from code, and we deploy them ourselves on Railway. We launch new ones constantly.

Your job: take a reference site we give you and rebuild it as a custom, self-hosted site — same layout, same sections, same behavior, same mobile rendering — under the new brand, deployed live on Railway, then wired to our external checkout and tracking.

You are not designing anything. You reproduce a layout exactly, in clean code, fast, and ship it live. Copy, images, product data and brand kit all come from us.

If you can take a reference site in the morning and hand back a live, mobile-perfect, tracking-verified URL by the end of the day, you will never run out of work with us.

The deadline: this is the core of the job

Every site ships live within 24 to 48 hours of kickoff. Not "usually". Every time.

24h for a site built from our existing base template (most of the work)
48h for a site that needs new sections or something we haven't built before

Kickoff means the moment we hand you the complete package: reference site, brand kit, copy, images, product data, checkout parameters, tracking IDs. The clock starts there. If something is missing from that package, you tell us within the first hour — not at hour 20.

How this is possible: you are not designing, not writing copy, not sourcing images. You reproduce a layout from a reference, on a codebase we already built, with assets we already prepared. The whole system is built for speed, and your job is to keep it that way.

What we expect when a deadline is at risk: a message from you as soon as you see it coming, with what's blocking and what you need. A late site we knew about 12 hours in advance is a problem we can manage. A late site we discover at the deadline is not.

If you need a week to build a landing page, this role is not for you and you'll be miserable here. Please don't apply.

What you will do

Build

Reproduce a reference site's front-end in clean custom code: structure, sections, spacing, typography, animations, responsive behavior
Stack: HTML + Tailwind CSS + JavaScript, or Next.js / Astro / React depending on the project
No page builders, no WordPress, no drag-and-drop. You write the code.
Build it templated and reusable — we relaunch the same base under new brands, so brand name, colors, fonts, logo, domain, product data and checkout URLs live in one config file or env vars, never hardcoded across 40 files

Deploy

Railway: repo setup, Dockerfile or build config, environment variables, custom domain, SSL, redirects
Cloudflare DNS: records, SSL mode, caching, page rules
Fix your own deployment problems — build failures, SSL errors, env issues — without us holding your hand