We are a high-end design studio and a team of young creative professionals trying to conquer the world through design, art, and style. :)

The short version

We are looking for one developer to own all of it. Not someone who does the front end while someone else handles the CMS and someone else handles deployments. One person who builds the whole thing properly, then builds the system so the next project is faster.

What you'll build

Immersive experience sites. Three.js and WebGL, GSAP and ScrollTrigger, smooth scrolling, shaders where they earn their place. On our sites, scroll is how the story gets told — motion is a core part of the work, not decoration.

Headless WordPress into Next.js. Custom post types, ACF, GraphQL or REST, previews, revalidation, media handling. Clients should be able to edit their own site without calling us and without breaking anything.

Dashboards and web apps. Data-heavy interfaces, authentication, real state management, third-party integrations. Less glamorous, equally ours.

The base underneath all of it. Starter repositories, a component library, deployment pipelines, conventions, and documentation. Every project should begin further along than the last one did. This is a real part of the job, not something you get to when there's time.

What we're looking for

Real coding ability. JavaScript and TypeScript, properly. You can read code you did not write and fix what is wrong with it. This is the skill we will test hardest.

Three.js and WebGL, hands-on. Not "I followed a tutorial once." You understand the render loop, draw calls, what geometry and materials actually cost, and how to debug a scene that runs at 12 FPS on a mid-range laptop. GLSL and React Three Fiber are a strong plus.

Next.js at a senior level. App Router, Server Components,



rendering and caching strategies, route handlers. Node.js and TypeScript are your everyday tools, not things you reach for occasionally.

Headless WordPress, end to end. You have shipped it, maintained it, and know where it bites — previews, draft states, editor experience, media, and keeping a decoupled setup from turning into two codebases that disagree with each other.

CSS craft and pixel accuracy. This matters more to us than framework knowledge. Our sites are design-led, and you will build from proper art direction, so your job is to match the design exactly — spacing, typography, breakpoints, every state, every transition. A site that is nearly the design is not the design.

Performance. 3D and design-heavy sites are heavy by default. Asset budgets, model and texture optimization, image formats, lazy loading, font loading, bundle size, Core Web Vitals. Making a rich site load fast is a real skill, and we need it.

Security, actually done. Headless WordPress is a live attack surface, and most people ignore it. Locked-down admin, plugin hygiene, secrets handling, rate-limited forms and API routes, dependency updates, sensible headers. We'd rather you raise these issues before launch than after.

Systems, not one-offs. Templates, reusable components, documented conventions, a sane Git workflow, staging, CI. You should be trying to make the studio faster, not just the project you're on.





The basics done right. Semantic HTML, SEO fundamentals, accessibility. Our clients are in New Zealand and Australia, where accessibility standards are taken seriously.

Launch and infrastructure. Vercel, Netlify, or Cloudflare, DNS, SSL, staging environments, forms, analytics, and integrations with CRM or payment tools. You launch it, and you keep it running well afterwards.

Good to have : GLSL, physics, Blender basics and model optimization (Draco, KTX2), Storybook, testing, Astro, and anything experimental you've built for fun.

What AI-first means here

We use AI for the work AI is good at. Writing code, boilerplate, config, integrations, debugging, learning a recent library quickly. It is faster, and it lets a small team take on more.

What AI does not do is judge — not reliably, and not with your context. It will catch a security hole most of the time. Most of the time is the problem: the one time it doesn't, the only thing standing between that and production is you. And it has no idea what your traffic looks like, what the client can afford to maintain, or who is fixing this in six months.

So the judgement is the job. You need to be good enough at coding to look at what AI produces and know immediately whether it is right, whether it will hold, and whether it should be built that way at all. You also need to be the person who says "this is not doable like that" before it gets built, not after.

AI writes most of the code here. You are accountable for all of it.

Who we think you are

Around 3 to 5 years in. You have not just built sites — you have maintained them, fixed them at 11 p.m., and learned what causes problems later.

You are comfortable with AI writing most of

📌 Senior Creative Developer Headless Wordpress, Next.js & Webgl (India)
🏢 Young Pandas Private
📍 India