We build Shopify stores, move them over from other platforms, and keep improving them once they are live. Premium brands where the design has to carry the price, and retailers with hundreds of thousands of SKUs, deep variant logic and an ERP with opinions of its own. Usually both in the same week. The same people who design and build the store run the SEO and CRO on it afterwards, so nothing sits waiting on a handover.

That only works if the person doing the design also understands two things: what happens to that design in the browser, and where the brand it belongs to came from. Most of our clients arrive with a brandbook, or with a logo and a feeling. Either way, somebody has to turn that into a store that still looks like them on a product page, in a filter, in a cart, and on a phone. And then keep testing it, because a store that looks right and converts badly is still a store that converts badly. That somebody is you.

What the work actually looks like

You get a catalog that does not fit a template, a client with a real commercial problem, and a deadline. You map the flow, decide how products, filters and templates relate to each other, design it in Figma, and then build it yourself. In Liquid when it is a theme, in Next.js when it is headless. Nobody hands your file to a developer and hopes.

This is a design job and a development job in one. Not a designer who can read code, and not a developer with taste. Both, properly.

Concretely:

UI/UX design for Shopify stores and B2B websites, from wireframe to live store
Translating a brandbook into a digital identity: type scale, colour on screen, spacing, imagery, motion, states, and the hundred decisions the book does not cover
Extending a brand where it runs out, and building one out from a logo when there is no book at all
User flows, information architecture, and PDP, PLP and checkout structure built on how people actually buy
Shopify theme development in Liquid: sections, blocks, metafields, and settings a merchant can use without calling us
Building the headless front-ends in Next.js and React: routing, data fetching from the Storefront API or a CMS, rendering strategy, and the performance budget that comes with it
CRO as a permanent part of the job, not a phase at the end. You form a hypothesis, design the variant, build it, run it, and read the result. A design that tests worse than what it replaced gets rolled back, including yours
UX research and usability work on stores we already run
Design systems and components that still hold up at 400,000 SKUs
Direct contact with clients, because there is no account layer to hide behind

Where you are after

One month.

You are on live projects. First wireframes and UI designs delivered. A Shopify template built or rebuilt by you is in production.

Three months.

You own complete store projects. You make the calls on UX, structure and conversion, and you defend them in the client call.

Six months.

Your work shows up in the numbers. Clients trust your judgement without checking it first. You set the standard the rest of the team builds against.

Three years, or hungry

Two ways in.

You have around three years behind you, ideally some of it in an agency, and you have already shipped stores that other people depend on. You know where Shopify bends and where it breaks. If you came out of an agency where the work got repetitive, where you were handed a Figma file and told to build it, or where you stopped learning about eighteen months ago, this is the opposite of that.

Here you sit on the strategy, the design, the code and the numbers of the same store.

Or you are junior, you are good, and you are willing to work hard to get there fast. We will teach you Liquid, the data modelling, the CRO and the SEO side. We cannot teach taste, curiosity or work ethic, so bring those. Show us what you have built, in a job, in school or on your own, and be honest about what you do not know yet.

A junior who asks the right question beats a senior who never does.. :)

What you bring

Shopify theme development in Liquid. Sections, blocks, metafields, the lot
Next.js and React. You have shipped something headless and kept it fast
HTML, CSS, JavaScript, Tailwind and JSON, solid
A real understanding of branding: you can read a brandbook, work out what it is trying to protect, and carry that into every screen without turning the store into a slideshow of the guidelines
Wireframing and user flow design for e-commerce
UX research you have actually run, not read about
Figma at a team level

If you are applying as a junior, read that list as where you will be in a year, not as a gate. Liquid and Next.js are the two we expect you to already be moving in.

The stack

Figma. Shopify and Liquid. Next.js and React. JavaScript and JSON for dynamic behaviour and integrations. Adobe (Photoshop, Illustrator, After Effects or similar).

Nice to have

Brand and identity work itself, not only applying someone else's
A headless CMS such as Sanity, and Shopify Hydrogen
Experience in an agency, and a clear opinion on what you would do differently
Performance work and technical SEO
Component-based design systems
Large catalogs or platform migrations
Premium or design-led brands, where the store is part of the product
Webflow experience

Who you are

A CNP, a certified nice person
You think in solutions, not tickets
You have taste, and you can explain where it comes from
You work independently and say what you need
You own the thing after go-live, not until handover
You want to know why something works, not just how

What we offer

Your own seat in the Wintercircus in Ghent
Homeworking, and a team that works fine with you not being in the room
A MacBook Pro and a phone subscription
Competitive salary with meal vouchers, eco vouchers, and pension saving through Warren
A small team of specialists, no layers and no briefing chain
Projects where design, development and performance sit at the same table
A very high level of autonomy
Direct collaboration with clients
Room to grow across UX, development, CRO and performance, and the work to actually do it on

We believe strong teams are built from different perspectives. Background matters less than skill, drive and impact.

Sounds like your next step? Send us what you have built.

hello@6thman.digital | 6thman.digital