Associate Mernstack Web Developer

Website Developer (Mern-Stack, Internal Properties)

Do you actually want to own something end to end, instead of owning "your part" of it? Can you go from a slow MySQL query to a janky Next.js render without waiting on someone else to unblock you? Do you like SEO enough to bake it in from the start, not bolt it on after launch?

Then, our Website Developer role here at CUBE84 may interest you.

In this gig,

1. You're the only one holding the keys
   You own the build, maintenance, and uptime of CUBE84's two internal websites — solo. No other developer is sharing this responsibility, which means when something breaks at 6pm, it's yours to fix, and when something ships well, it's yours too.

2. You build across the whole stack, not just your favorite layer
   You ship fixes, updates, and new pages using Next.js, Node.js, and MySQL. You write and maintain the REST APIs behind both sites and hook up third-party services where needed. Frontend problem or backend problem — you don't wait for someone else to diagnose it.

3. You turn other people's ideas into shipped pages
   You work directly with marketing and design, turning briefs and mockups into real, working pages in Tailwind CSS — and you don't get defensive about iteration rounds when their feedback changes what you built.

4. You think about SEO while you build, not after
   You apply on-page SEO as part of the actual build — semantic HTML, meta tags, structured data, sitemaps, page speed — because a site that ranks well isn't a separate project bolted on at the end.

5. You call the shots on your own two properties
   You prioritize and sequence work across both sites using your own judgment, and you know when a tradeoff is yours to make versus one your manager needs to weigh in on.

6. You keep things clean because there's no one else to catch what you miss
   You follow CUBE84's engineering standards — the repository pattern (routes, controllers, services, models) on the backend, reusable components with Redux Toolkit on the frontend, one common response format across every API — because clean structure is what makes solo ownership sustainable instead of a mess six months in.

It'll be awesome if you...

• Have 1–3 years building production websites with Next.js, Node.js, and MySQL

• Have working knowledge of Tailwind CSS for responsive, component-based UI

• Have practical SEO experience — technical on-page SEO, Core Web Vitals, mapping keywords to content

• Are genuinely comfortable owning a codebase solo — Git-based workflow, self-review, documentation that doesn't assume a second developer will read your mind (this one's non-negotiable)

• Can debug across the stack, not just the layer you personally wrote

More awesome, if you have

• Experience with Express.js or a similar Node.js framework

• Familiarity with AWS (EC2, S3, or similar)

• Hands-on use of Google Search Console, Lighthouse, or similar SEO/performance tooling

• Experience maintaining a live site solo, without a dedicated team around it