---
id: "lib-2026-10-21-ax-dissolves-job-family-boundaries-how-far-does"
type: "library"
title: "AX dissolves job-family boundaries: how far does the developer's role go?"
title_original: "카카오 AI 돛 Summit 26 | AX가 허무는 직군의 경계: 개발자의 역할은 어디까지인가"
lang: "KO"
org: "Kakao (AI 돛 Summit 26)"
source_type: "Talk"
date: "2026-10-21"
week: "2026-W43"
url: "https://nosov.ai/library/lib-2026-10-21-ax-dissolves-job-family-boundaries-how-far-does/"
original_url: "https://www.youtube.com/watch?v=2CElIVLgrio"
tier: "B"
tier_name: "Useful, limited"
tier_reason: "Kakao principal engineer reports first-hand on an internal vibe-coding platform with adoption figures and a clear design rule; useful, but sign-ups and app counts are self-reported activity metrics with no retention or quality data."
summary_basis: "transcript"
original_minutes: "19"
tags: ["citizen development", "vibe coding platform", "role boundaries", "governance"]
---

# AX dissolves job-family boundaries: how far does the developer's role go?

Original title: 카카오 AI 돛 Summit 26 | AX가 허무는 직군의 경계: 개발자의 역할은 어디까지인가

Tier B (Useful, limited): Kakao principal engineer reports first-hand on an internal vibe-coding platform with adoption figures and a clear design rule; useful, but sign-ups and app counts are self-reported activity metrics with no retention or quality data.

Summary based on the full transcript.

## In short

A 19-minute talk at Kakao's AI Summit 26 (published 21 October 2026) by Lim Hee-seok, principal engineer in Kakao Commerce's Boost AX squad. A Kakao Gift product manager with no development background built and deployed the admin site for the service's core settings; the process went from seven steps to three. Lim argues that what disappeared was the hand-off wait between people, and that developers' job now extends to encoding expert standards into a platform others build on. Kakao's internal platform, Vibe-king (바이킹), drew 2,800 sign-ups and 1,200 deployed apps in 45 days.

## Key numbers

- 2,800: Kakao staff signed up to the Vibe-king platform within 45 days of opening
- 1,200: new service apps deployed on the platform in those 45 days
- 7 to 3: steps in the admin-tool build process before and after a PM built it with AI
- 10 min: time to build and deploy a schedule-management bot in the demo
- 1,000+: apps served from one small shared server

## What it reports

- The PM case: define the work, build with AI, deploy; design, development and testing run in parallel. The speaker says "a month became a day".
- Lim frames agents as team members a person directs; skill is measured by how many such team members one can lead well.
- The catch: a developer can judge an AI's code but not its design or marketing output at expert level, and asking human experts brings the bottleneck back. His answer is to encode each discipline's standards (how to attach auth, what to check before deploy) into the system, as Spring hides HTTP detail or a Figma design system fixes buttons.
- Developer role extends two ways: providing the expert foundation other job families build on, and owning services themselves.
- Guidelines and shared harnesses vary by person and team and cannot be enforced uniformly; the minimum standard is enforced at the platform: required checks at deployment and code running only within granted permissions.
- Vibe-king bundles a shared agent harness (instructions, tools, context) with a deploy-and-run platform. People with no knowledge of Git, databases, caches, Kubernetes or networking create a domain and deploy with one click.
- A schedule bot (pull calendars, find owners via the org chart, notify, weekly weekday summary) was built and deployed in 10 minutes from a request with almost no technical language.
- Apps share servers; one small server serves more than 1,000 apps. After 45 days, 2,800 staff had signed up and 1,200 apps were deployed.
- Next: failed apps should leave context (why built, why not chosen) for later builders.

## How they got it

Conference talk by the platform team with a demo; figures come from platform sign-up and deployment counts. Transcript from Korean auto-captions; the total headcount figure is garbled.

## Limits

- Sign-ups and deployed apps measure activity, not use, retention or value.
- No data on security incidents, abandoned apps or support load.
- Self-reported by the team that built the platform.

## Why it matters for companies

The design rule is the transferable part: let people build however they like, but enforce security, permissions and deployment checks in the platform, not in guidelines. That is how a firm can open app building to non-developers without losing control. The figures show demand for this is high when the deployment barrier is removed. Companies should plan for app inventory and retirement from the start.

## Key passages in translation

> 근데 사실이 과정에서 줄어든 건 절차가 아니라 사람과 사람 사이의 병목입니다.

What actually shrank in this process was the bottleneck between people, more than the procedure itself.

> 반드시 지켜야는 최소한의 기준은 마지막 플랫폼에서 통제해야 합니다.

The minimum standards that must be kept have to be enforced at the platform, at the end.

> 오픈 45일 만에 ... 2,800명이 플랫폼에 가입했고 1200개 신규 서비스 앱이 배포됐습니다.

Within 45 days of opening, 2,800 people had signed up to the platform and 1,200 new service apps had been deployed.

Original: https://www.youtube.com/watch?v=2CElIVLgrio