Lead Frontend Engineer

About INFINNI

INFINNI is the infrastructure behind the creator economy. We’re the leading CRM in our category, with thousands of creators and creator businesses running their operations on our platform. Now we’re building the next layer: AI-powered tools, big data and infrastructure built for creators.We’re a global team of 100+ engineers, designers, marketers and operators, with people from Meta, TikTok, Microsoft, N26, TIER and WeWork.

The role

This is a frontend lead who sits in Design, not Engineering. You’ll own how design becomes code at INFINNI.Today design reaches engineering the way it does almost everywhere: files, docs and threads that drift from each other and from what ships. AI made each of them faster to produce. It didn’t close the gaps between them.We’re changing that. Internally we call it Design Next: a new way for Design, Product and Engineering to go from idea to production, built around AI from the start. Code is the source of truth. Design tools are input, not the destination.Parts of it already run. Most of it is still to be built. You’ll be one of the few people building it, with a real say in how it works.

What you’ll own

• The frontend standards. Define what production-ready means for the work Design produces, and make it enforceable, not aspirational.
• The path to production. Make sure what Design builds reaches engineering ready to ship, without the usual back-and-forth.
• The agents and tooling. Design and build the AI agents, workflows and tools behind Design Next, with the Design team.
• The quality bar. Review designers’ code. Hold it to the same standard as anything in production.
• The design system, from the Design side. Work with the design-system team on components and tokens. Gaps found in product work go back into the system, not into a one-off.
• Teaching. Designers here ship code with AI. Help them do it well: rules that explain themselves, examples worth copying, reviews that teach.

What good looks like

• An engineer builds a feature from Design’s work without asking a single question.
• Design-system violations get caught before review, not after release.
• Designers ship with confidence, because the guardrails are right.

Who you are

• You’re AI native. AI isn’t a tool you picked up last year. It’s how you work, think and build.
• You care about design. You notice the 2px. You can argue for an interaction, not just build it.
• You think in systems. Tokens, components, rules, automation. You’d rather fix a class of bug than a bug.
• You have opinions on where AI should decide and where it should only advise, and you can back them.
• You write decisions down. In the repo, not in DMs.
• You’re comfortable owning something that isn’t built yet.

What you bring

• 7+ years in frontend, including 2+ as a tech lead: owning architecture, setting standards, reviewing others’ code.
• Hands-on experience designing and building AI agents and workflows: tool use, prompts, evaluation, guardrails, and wiring them into real development work like CI and code review.
• Advanced, daily use of AI coding tools (Claude Code or similar) beyond chat: skills, hooks, subagents, MCP.
• Expert React and TypeScript, in strict mode.
• Strong Tailwind CSS and shadcn/ui: theming with tokens, extending components without forking them.
• You’ve built or maintained a component library or design system: tokens (DTCG format, token pipelines), theming, component APIs, docs (Storybook or similar).
• Testing across the stack: unit, component, end-to-end (Playwright or similar) and visual regression.
• Accessibility in practice, not just on a checklist: semantics, keyboard, screen readers, contrast.
• Internationalisation at scale (i18next or similar): plurals, locale formatting, no hardcoded strings.
• Performance work: rendering, bundle size, profiling.
• Tooling: custom ESLint rules, dependency rules, pnpm monorepos, GitHub Actions.
• Git fluency. Code review that makes people better.
• Fluent written and spoken English.

Nice to have

• Electron or desktop app experience.
• Deep knowledge of accessibility and internationalisation standards: WCAG, WAI-ARIA, APCA, Unicode CLDR, the Intl APIs.
• Built internal dev tools, CLIs or codegen.
• SaaS, CRM or creator-economy products.
• Chinese or Spanish.

What’s in it for you

• A seat in Design. You shape the work before it becomes a ticket, not after.
• A real 0-to-1 problem. How a design team ships with AI, with guardrails that hold.
• Your standards become the system. What you decide gets enforced on every change, for everyone.
• A team that treats AI as a multiplier, not a buzzword.
• Competitive salary [and relocation package, with the Beckham Law tax rate if you’re moving to Spain for the first time - confirm]. Flexible hours. Yearly company offsite.

If you think design and code shouldn’t need a handoff at all, we should talk.