
Designer (Web)
Viktor
Posted 2 days ago
About Viktor
Viktor is the AI teammate. It lives in Slack and Microsoft Teams, connects to thousands of tools, and does real work for real companies: finance, marketing, ops, engineering. We're building the product that replaces half the SaaS stack.
The team is small. The scope is not.
The Short Version
Not a brand-system role. Not a product-app role. The web: every page on viktor.com, every campaign landing page, every A/B test that runs against real traffic. We have brand designers for the system and product designers for the app; we're hiring you because the web has to ship daily, and the page that converts won't design itself. If you don't open PostHog before opening Figma, this isn't the role.
What's Actually Going On Here
We just relaunched the brand. The marketing site has to express it across every surface a prospect lands on: home, pricing, comparison pages, vertical pages, paid LPs, partner micro-sites. Every campaign wants a new page, every cohort a different angle, and we test relentlessly: the page that won last month might not win next month. Run the web layer of Viktor. Templatize where speed wins, stay creative where it doesn't, test everything that touches revenue.
What You'll Actually Do
viktor.com end-to-end: home, pricing, comparison pages, integration pages, vertical pages, SEO landings. The site is the front door; make it earn its traffic.
Landing pages at volume. Campaign LPs, paid LPs, partner micro-sites, vertical pages. Multiple per week.
A/B testing. You write the hypothesis, design the variants, ship them, watch PostHog, call the winner, kill the loser. Not ship-and-forget.
Templates and the system. The 80% case is fast: a hero, a comparison block, a pricing block, a CTA. Build templates so a new LP takes a day, not a week.
One-offs. The 20% where templates don't work: new formats, custom layouts, interactive demos, launch pages.
Conversion surfaces. Signup, paywall, trial walls. The product team owns the app; you own the web side of the boundary.
The Bar
By month one, one A/B test you designed is live and reading data. By month three, every paid campaign launches with a purpose-built LP, home-page conversion is measurably better, the team ships new LPs in a day not a week, and the test backlog is yours to prioritize. This role doesn't work without daily AI use and daily vibe-coding: if shipping a frontend change through Cursor sounds new, you'll be behind on day one.
Day-1 Reality
Ship one landing page or one A/B test variant to production. Pick up the brand book, the Figma library, and the viktor-website repo, and start shipping.
Who You Are
5+ years of web / UI / UX design. Portfolio shows shipped websites and landing pages at scale: real live pages with real traffic, not just mockups.
You've built and tested LPs end-to-end and can name the experiments you ran, which won, and why.
You read PostHog / GA / Mixpanel without flinching. Conversion rates, drop-offs, statistical significance are part of the craft, not someone else's job.
Strong opinions on hierarchy, form, and conversion. You can defend a layout in a number, not a vibe.
Vibe-coding is core, not optional. You ship Next.js / React / Tailwind directly via Cursor or Claude Code. Design to code to PR to live, no handoff over the wall.
Hands-on fluency in Figma and Adobe CC where needed. Comfortable with light motion / Lottie.
Daily, hands-on AI use across your full workflow: ideation, copy, generation, code.
Bias toward shipping. You finish, measure, iterate.
Self-managed. Sharp written communication. Give and take feedback without ego.
Brand-system experience is a plus, not a requirement. A/B testing fluency is.
Why This Role Is Different
Embedded with Growth on campaign LPs, ads-to-landing flows, conversion targets, and the experiments that move the business. Founding Designer (Bartek Pierzchała) partners on the strategic web work.
Real ownership. You're the web designer for viktor.com.
Speed. LPs ship in days, tests run weekly, and you see what works in real numbers, not retros.
Vibe-coding loop. You design, ship, and measure, with no handoff to engineering for 90% of the work.
Fresh brand, real budget. You own the rollout and what the brand becomes on the web from here.
Even Better If
You've shipped your own product or side project end-to-end (web, design, code).
You've designed and shipped in no-code tools (Webflow or Framer).
You've run A/B tests with statistical rigor (you know what "underpowered" means).
You've worked on B2B SaaS websites where conversion = pipeline.
You're familiar with PostHog experiments specifically.
You've built or contributed to a design system used across a marketing site.
Tools
Figma, Cursor / Claude Code, Next.js + Tailwind (read + write), PostHog, Adobe CC, plus the AI tooling you already live in.
How we work
Small team, high trust, low process. Decisions are made by owners, not committees. You will ship your first week. You will talk to users your first day. We don't do alignment meetings or stakeholder syncs. We build things, see if they work, and iterate.
Everyone here owns something real. Not a task. A surface of the company that customers depend on. When it breaks, you fix it. When it wins, everyone knows whose work it was.
We use Viktor to build Viktor. You'll see what you're working on in action every day.
Why Viktor
This is a rare window. The product works. The market is pulling.