Karrot grew from 10 to 70 employees in a single year, per its own Notion case study. That transparency is not a recruiting tactic; it is the operating system. This guide covers five things: who Karrot hires across six Seoul roles, what the compensation package signals without published bands, how to approach an interview process the company doesn't document, where the work actually happens on a cloud-native stack, and which traits let people thrive in a culture that treats autonomy as oxygen.
Who gets hired and onto which teams
Six roles are open as of this writing, all based in Seoul: a Merchandiser on contract for fresh-food commerce, an Operations Manager intern for the "Buy Now" flow, two Backend Software Engineers (one on infrastructure (common services and content serving), one on feed infrastructure), a Frontend Software Engineer for "Local Jobs," and a Design Engineer for the design system. Korean titles in the listings signal the primary market; English technical descriptors signal the stack. No hardware role appears.
The Notion case study shows a wiki that organizes "team profiles" alongside the company mission, and a weekly Monday meeting (notes linked in the wiki) where teams provide project updates and answer questions. New hires receive a Notion account on day one. "After a week, I was able to figure out almost everything about our company," says Chris Heo (Growth). "Notion shrank the learning curve."
The talent page, published from the same Notion workspace, leads with office photos, culture details, and team profiles. The company filters for alignment before the first screen.
What it pays
Karrot does not publish salary bands. The careers site, its job postings on the Zero G Talent board, and public filings all omit base-pay ranges for the roles it recruits: software engineers (backend, frontend, infrastructure), design engineers, merchandisers, and operations managers, all based in Seoul. That silence is not unusual for Korean tech companies, which rarely disclose compensation until the offer stage, but it means candidates must triangulate from benefits, equity signals, and peer-company data rather than from a posted grid.
What Karrot does document, on its Korean careers portal (careers.ca.karrotmarket.com), is a benefits package that leans heavily on autonomy and personal-growth budgets. Every employee gets unlimited vacation, flexible hours, and the option to work from home. Health coverage includes medical, dental, and vision insurance, plus parental leave, though the portal does not specify duration or pay rate. A separate "personal growth" budget covers conferences, classes, books, academic papers, and even cultural activities. The language is explicit: "We invest in our team's personal growth, because we believe Karrot grows when we grow."
Those perks match the broader philosophy the company advertises: radical transparency ("We are radically transparent with our information"), high autonomy ("We make our own decisions on how we work"), and proactive ownership ("We do not wait to be told what to do"). In practice, that translates to a compensation model where base salary is only one lever; the rest is time, trust, and learning budget.
A detailed benefits list from get-carrot.com, a U.S.-based fertility-and-family-building benefits platform, cites 14 weeks of fully paid parental leave, a monthly productivity stipend, a home-office setup allowance, 401(k) matching, telehealth via Modern Health, co-working access, and "generous time off" on top of company holidays. That company operates across 40-plus U.S. states and dozens of countries. It is not the same entity as the Seoul-based Karrot marketplace whose roles appear on the Zero G Talent board. The two brands share a similar name and emphasis on wellbeing, but their compensation structures are distinct. Candidates interviewing with the Korean Karrot should not assume the U.S. Carrot's 14-week leave or productivity stipend apply unless confirmed in writing.
There, Karrot's six most recent postings span backend infrastructure, feed infrastructure, frontend for local jobs, design systems, contract merchandising for fresh food, and an operations internship for instant purchase. None include a salary figure.
Equity is another blank. The careers site does not mention stock options, RSUs, or an employee-stock-ownership plan. A Blind review from June 2022 notes "stock options possibly being a great return," but vesting schedules, cliffs, and refresh policies stay private until the offer letter.
For a candidate, the practical takeaway is twofold. First, negotiate with market data in hand. Second, treat the documented perks — unlimited PTO, learning budget, full remote flexibility — as part of the total-package conversation. If the base offer lands below market, the autonomy and growth budgets are the leverage points Karrot's own culture page signals it respects.
How the hiring process works and what gets candidates through it
Karrot does not publish a public hiring playbook, and no first-party source details its stages, rubrics, or timeline. That silence is common among Korean tech companies that recruit domestically; the process is often transmitted through referrals and recruiter briefings rather than blog posts.
From the role types we can infer: backend candidates should expect system-design discussions around content serving and feed ranking at scale. Frontend applicants for "local jobs" will likely face questions about real-time mapping, geolocation, and Korean-market UX patterns. Design-system engineers will be evaluated on component-library governance, token architecture, and cross-platform consistency. The operations and merchandising roles point to a separate track emphasizing marketplace dynamics, seller onboarding, and fresh-food logistics, domains where domain knowledge outweighs algorithmic depth.
Absent Karrot-specific disclosures, the strongest signal comes from the job descriptions themselves. "공통 서비스 개발" (common service development) and "피드 인프라" (feed infrastructure) imply ownership of shared platforms, so candidates who demonstrate experience extracting reusable services from monoliths, defining contracts, and migrating traffic without downtime will map directly to those needs. "로컬 잡스" (local jobs) frontend work suggests familiarity with Korean address systems, Kakao/Naver map SDKs, and low-latency list rendering for high-density feeds.
Applicants should treat the process as opaque but the requirements as legible: build a narrative around the exact surfaces Karrot is hiring for, and prepare to discuss Korean-market constraints (payment, identity, logistics) that don't appear in LeetCode. The company's own careers page and recruiter conversations remain the only authoritative source for stage count, take-home policies, and offer timelines.
Where the work happens
Karrot's job postings on Zero G Talent list one location across every open role: Seoul. The careers page reinforces a culture built around that physical concentration. "At Karrot, everyone is an entrepreneur," it states, framing the office as a place where "we are continuously iterating, learning, and growing by identifying problems to solve and testing hypotheses."
What the research does document is the technical infrastructure those teams build on. A two-part AWS engineering series details Karrot's feature platform, which runs on three pillars: a feature-serving layer, a stream ingestion pipeline, and a batch ingestion pipeline. The first post explains the motivation: replacing a fragmented, hard-to-scale system with a unified platform that can serve real-time recommendations and search ranking across the marketplace. The second post covers the ingestion side: collecting features in real time and in batch, writing them to an online store, and the operational patterns that keep the pipeline stable. This is cloud-native infrastructure; the "facility" that enables the team's work is largely AWS, not a private data center.
That architectural choice shapes what the Seoul office actually needs to house. There's no mention of GPU clusters, hardware benches, RF chambers, or robotics bays, facilities that would appear in a company integrating custom silicon or physical devices. The roles on the board are software-heavy: backend services, feed infrastructure, frontend for a "local jobs" product, design systems. The Merchandiser and Operations Manager roles point to a marketplace operations team that likely sits alongside product and engineering, but the research provides no description of a warehouse, logistics center, or physical retail space in Seoul.
The AWS posts do reveal one concrete enablement: the feature platform lets product teams launch experiments without bespoke engineering support. That phrasing matches the platform's stated purpose.
What's absent from the record is any mention of satellite offices, remote-first policy, or hybrid arrangements. The job postings don't flag "remote OK" or list alternative cities. The AWS posts are authored by engineers writing from what reads like a single technical center. For a candidate, the takeaway is straightforward: the work happens in Seoul, on a cloud stack that the team owns end-to-end, in a culture that treats the office as the default collaboration surface. If you're not in Seoul — or willing to be — the current openings don't show a path in.
Who thrives here
Karrot's own careers page states the hiring bar plainly: "We push ourselves to hire people that are better than us. The growth and learning that comes from working with incredibly smart and driven teammates make working at Karrot fulfilling and rewarding." That sentence, posted on careers.ca.karrotmarket.com, functions as both manifesto and filter.
Blind reviews from 2022 through late 2023 reinforce the pattern. Multiple reviewers cite "passion for company growth" and "empowerment to drive change" as daily realities, not slogans. One June 2022 review calls out "lots of opportunities provided, especially in growth marketing area" and a "great Risk/Reward ratio as it is in its early days with that same equity upside." A March 2023 review summarizes the winning profile: "Total compensation and benefits. A lot of smart talents. Great culture." The same reviews flag the trade-offs — 60-plus-hour weeks, a 3.3-out-of-5 work-life-balance score, thin management layers, and sparse corporate benefits — which means the people who thrive are those who treat autonomy as oxygen and structure as optional.
First-party board data confirms the mix: current Seoul openings span backend (infra and feed), frontend (local jobs), design systems, merchandising, and operations. The roles are cross-functional by necessity: a frontend engineer touches the feed pipeline; a merchandiser coordinates with operations on fresh-food commerce. Success goes to people who communicate across those boundaries without being asked.
What the evidence does show is a company that rewards self-starters who learn fast, ship faster, and treat the inevitable chaos of an early-stage marketplace as the job itself.
The wiki that a candidate reads before applying becomes the same wiki they'll write into on day one — the operating system, transparent all the way through.
Working in frontier tech? Zero G Talent tracks the openings: see every open Karrot role, browse frontier tech jobs, the companies hiring, and the people building the field.