Associate Web Designer

The role

We build a horizontal platform made up of composable primitives, not feature-by-feature point solutions, and we take the same approach to design—especially on Web.

The website has become the company's largest owned channel: more than a dozen new sections in the last year, every existing page rebuilt and interlinked through a well-structured CMS, traffic more than doubled.

You'll own that surface end to end alongside Shaked Ginott, our Lead Web Designer — just the two of you, which means scope and seniority grow as fast as you can carry them. You'll design and build on it directly and be accountable for how what you ship performs in the market, working closely with product, commercial, marketing, brand, and SEO.

On a daily basis, you'll:

• Turn briefs from commercial, product, and marketing into pages that ship—across a breadth of styles including platform verticals, campaign support, product release pages and SEO infrastructure

• Design and build in components, rules, and the CMS rather than one-off pages, so changes compound across the site as brand and positioning evolve

• Monitor and maintain performance, find and fix bugs, and QA changes before they reach the live site

Why come in-house?

The strongest web talent usually gets pulled toward agencies. We think the better work is here. At an agency you hand a project off and move to the next client; in-house, you own one surface for years and your work compounds as the brand and positioning evolve. You sit inside the business, close to product and go-to-market, so the work is shaped by company strategy and measured on commercial results rather than sign-off. Studio Planhat runs with the discipline of a research team more than a traditional creative shop: brand here is built through cumulative effort over years, not campaigns over quarters. The line from what you ship to what it does in the market is short, and it's yours to close.

Competencies

To succeed in this role:

• You design in components and rules, not one-off instances, and you tidy as you go — you're impatient with fixes that solve one page and don't scale

• You have a clear eye for what's right and what's nearly right, and you can say what's missing and fix it yourself

• You reach for frontier technologies (e.g., code-gen, generative design, self-built apps and tools) early and build repeatable ways of working with them rather than prompting ad hoc

• You question decisions that were settled before you arrived, learn fast, and give and take feedback directly

Technically, you must be:

• familiar with building sites in a no-/low-code web builder such as Framer or Webflow — you understand components, variants, responsive behaviour, and publishing

• able to show a portfolio of aesthetically tight and systematically robust web work you've designed, built, and shipped

• comfortable enough with the HTML and CSS underneath to understand what the builder produces, rather than just prompting for it

• fluent with AI tools and excited to stay hands-on, leveraging them to accelerate workflows and increase ambition rather than holding onto old techniques

Experience with B2B or data-heavy products is a plus, but ability and judgment matter more than years.

Design Suite

Strong competence in, or a strong willingness to learn:

• Design & build — Framer (the site is built here)

• Design — Figma

• AI — Claude & Claude Code; ChatGPT & Codex; etc.

Definition of success

In a year, you're succeeding if:

• You own monitoring, improving, and reporting on the site's performance and technical health, without anyone having to ask

• Website bugs are found and fixed systematically, before they're reported

• Commercial and product requests land with you directly; you prioritise them sensibly, spec them precisely, and ship them reliably

• At least one core section of the website (e.g., Careers; Editorial; Features; Products) is yours end to end, from proposal through to a measured result and ongoing enhancement, both aesthetically and technically

• The site is more consistent across pages, and you can point directly to what you changed