Kaya combines creative execution and productized tooling into a single compounding system. Our internal OS powers how we manage campaigns, and our competitor ad intelligence platform helps companies move fast with clarity. For customers, that means two paths: use our tools to run marketing like a top-tier squad, or have us run it for you, faster than any agency could. The frontend is how every piece of this system is accessed, understood, and used– by our team and our customers.

You’ll own the entire frontend– from ad intelligence workflows, to reporting systems, to the marketing ops engine. It’s been founder-built until now– you’ll take it from here, working directly with us to drive it forward.

You’ll define the spec, sketch the wireframe, and ship it fast. Polish, iteration, and performance are all yours to own. What you build is how campaigns launch, insights surface, and decisions get made, by us and our users.

If you do this well, you won’t just build UI– you’ll shape how Kaya operates and how our customers scale.

This role is for someone who wants to own what users see and touch– and has the technical judgment, taste, and grit to guard it.

Cool projects we’ve built

We don’t build features. We build leverage– systems that streamline execution, scale customer outcomes, and sharpen every time they run. These aren’t side projects. They’re Kaya’s engine room.

• Marketing Ops OS: Our internal command center for all live campaigns– tasks, KPIs, memos, and files, all stitched into one flow, and used daily by our team and customers. Think Linear × Notion, purpose-built for performance marketing.
• Ad Intelligence Engine: Visual research tool that helps teams reverse-engineer what’s working in their category– surfacing standout ads, creative patterns, and media strategy signals. Built on scraped data, with custom filters, visual tagging, and embedded insights designed for fast creative and targeting decisions.
• Proposal Generator: Creative automation system with two layers– an internal panel to manage visual assets and configure how ad copy appears, and a client-facing view that generates personalized marketing proposals with AI-written messaging
• Dynamic Reporting Builder: Schema-driven system that renders block-based reports– live charts, commentary, and KPI snapshots.

What you'll do

You’ll convert raw ideas into systems– translating inputs, insights, and ambiguity into tools people rely on to act fast and win. The UIs you build will power decisions, accelerate execution, and scale Kaya’s impact across product, growth, and internal ops.

1. Deliver systems that drive outcomes

You’ll ship fast, intuitive products that help users research, decide, and execute, enabling Kaya’s own team to run 10x faster.

• Build and evolve Kaya’s ad intelligence tooling: Ad libraries, creative boards, funnel benchmarks, and alerting systems.
• Extend our reporting and proposal stack: Client-facing reports that combine live charts, AI-written insights, and dynamic benchmarking.
• Build systems our team uses daily to manage live campaigns: Turn disconnected tasks, notes, and assets into fast, unified execution flows.

2. Make the Front-End fast, stable, and scalable

You’ll harden the core. Every system you touch should get faster, safer, and easier to build on.

• Maintain and evolve Kaya’s design system, component library, and shared UI logic across apps, all in Vue + Nuxt.
• Own the rendering experience for SSR reliability, hydration timing, visual consistency, and predictable UI load states.
• Implement and enforce testing, CI/CD, and error handling pipelines– no regressions, no silent failures.

3. Operate as Kaya’s Front-End brain

This isn’t a narrow execution role. You’ll define what “good” looks like– and raise the bar every time you ship.

• Turn incomplete inputs into functional UI, without spec dependency.
• Build fast, stable, and iterable systems– the kind that work on day 1 and scale without rewrites.
• Work directly with founders and engineers to define what gets built, how it works, and how it should feel.
• Set the culture for front-end execution at Kaya– the bar you set becomes our default.

Who this role is built for

• You’ve owned full systems. Not just components, but entire user-facing systems– shipped, used, and critical to daily execution.
• You move without waiting for a spec. You take partial inputs, make smart calls, and turn them into working product.
• You clean up chaos. Bad data, messy state, fuzzy UX– you make it production-ready and stable.
• You know Vue/Nuxt deeply. SSR, hydration, performance, state– you build for speed and durability.
• You ship when it counts. Launch windows, live bugs, moving targets– you move fast without breaking the outcome.
• You take full ownership of every user-facing surface. Not just code, but the design, product logic, and UX clarity behind it. If something’s broken or slow, you fix it or make the case.

Interview Process

1. Initial conversation (30 min): A fast call to align on expectations and assess for the autonomy, speed, and ownership this role demands.
2. Home challenge (async, 2–3 hrs): You’ll build a real-world frontend module that tests product sense, system composability, and how you make tradeoffs under constraints.
3. Problem-solving interview (45 min): You’ll walk through your home task, then work through a live extension– testing how you structure, reframe, and reason through edge cases.
4. Founder interview (60 min): A direct conversation about your trajectory, clarity, and ownership.