# Korea Tech Jobs in English — Coupang, Krafton, Daangn & more (`seoulsmith/korea-tech-jobs`) Actor

Korea-based tech job postings from company career systems (Greenhouse, Lever, Ashby public APIs), in English fields with the original apply link.

- **URL**: https://apify.com/seoulsmith/korea-tech-jobs.md
- **Developed by:** [Seoul Smith](https://apify.com/seoulsmith) (community)
- **Categories:** Jobs
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Korea Tech Jobs in English — Coupang, Krafton, Daangn & more

**Korea Tech Jobs in English** collects the open tech jobs based in South Korea from the companies' own career systems: Coupang, Krafton, Daangn (Karrot), 42dot, FuriosaAI and 36 more, including global companies with a Seoul team such as Agoda, Airwallex, Anthropic, Databricks, Datadog and OpenAI. You get one dataset with English field names, a normalized city (Seoul, Pangyo, …) and the original apply link for each job.

- **41 companies, about 750 Korea-based jobs** (758 on 2026-11-12)
- Data comes straight from the companies' public job boards on **Greenhouse, Lever and Ashby**, not from a job platform
- Filter by company, keyword, city and remote. You can also return **only jobs that are new since your last run**
- No login, no API key, no proxy. Free to use

### What can I use it for?

- **Job seekers and people moving to Korea:** list every open role at Seoul and Pangyo tech companies in one table, with the apply link.
- **Recruiters and HR analysts:** track which teams Korean tech companies are hiring for, and how fast.
- **Newsletters, communities and job boards:** schedule a weekly run with *Only new since last run* to post "new tech jobs in Korea this week".
- **Market research and investors:** see which global companies are building teams in Korea, and for which functions.

### How to use it

1. Click **Start**. With the default empty input you get every Korea-based job from all companies.
2. To narrow it down, fill in **Companies**, **Keywords** or **Cities** (see below).
3. Download the results as JSON, CSV or Excel, or read them through the Apify API.
4. For a new-jobs feed, turn on **Only new since last run** and add a [schedule](https://docs.apify.com/platform/schedules) (for example every Monday).

A full run takes about a minute and makes about 44 requests (one per company, plus robots.txt once per API host).

### Input

| Field                                           | What it does                                                                                                                                                 |
| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Companies (`companies`)                         | Only these companies. Matches the company name or its board token, case-insensitive, part of the name is enough (`"coupang"`, `"Daangn"`). Empty = all.      |
| Keywords (`keywords`)                           | Only jobs whose title, department or team contains one of these words (`"backend"`, `"data"`, `"백엔드"`). Empty = all.                                      |
| Cities (`cities`)                               | Seoul, Pangyo, Seongnam, Busan, Incheon, Daejeon. Jobs that only say "South Korea" have no city and are left out when you pick a city.                       |
| Remote only (`remoteOnly`)                      | Only jobs the company marks as fully remote.                                                                                                                 |
| Only new since last run (`onlyNewSinceLastRun`) | Skip jobs this Actor already returned in your earlier runs with this option on. The seen IDs are kept in your named key-value store `korea-tech-jobs-state`. |
| Include job description (`includeDescription`)  | Add the full job description as plain text. Off by default to keep the dataset small.                                                                        |
| Maximum results (`maxItems`)                    | Stop after this many jobs, newest first. Default 1000.                                                                                                       |

Example input:

```json
{
    "companies": ["Coupang", "Krafton", "Daangn"],
    "keywords": ["backend", "data"],
    "cities": ["Seoul"],
    "onlyNewSinceLastRun": true
}
```

### Output

One item per job. Example (Palantir, from Lever):

```json
{
    "id": "lever:palantir:1bb19522-3936-4adc-9ced-c3df8b5900b9",
    "company": "Palantir",
    "title": "Forward Deployed Software Engineer",
    "department": null,
    "team": "Delta",
    "location": "Seoul, South Korea",
    "city": "Seoul",
    "country": "KR",
    "remote": "hybrid",
    "employmentType": "Full-time",
    "employmentTypeNormalized": "full-time",
    "postedAt": "2022-04-22T15:31:39.656Z",
    "updatedAt": null,
    "applyUrl": "https://jobs.lever.co/palantir/1bb19522-3936-4adc-9ced-c3df8b5900b9",
    "source": "lever",
    "postingLanguage": "en",
    "salary": null
}
```

| Field                      | Meaning                                                                                                                     |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| `id`                       | Stable job ID: `source:boardToken:jobId`. The same job keeps the same ID between runs.                                      |
| `company`                  | Company name                                                                                                                |
| `title`                    | Job title exactly as posted (Korean or English)                                                                             |
| `department`               | Department as the company names it                                                                                          |
| `team`                     | Team (Lever and Ashby only)                                                                                                 |
| `location`                 | Location as posted. When a job lists several locations, this is the one in Korea.                                           |
| `city`                     | Normalized city: Seoul, Pangyo, Seongnam, Busan, Incheon, Daejeon, or `null` when only the country is named                 |
| `country`                  | `KR` for Korea-based jobs. `APAC` for remote jobs open to Asia-Pacific (see the rules below)                                |
| `remote`                   | `true` remote, `false` on-site, `"hybrid"`, or `null` when the job does not say                                             |
| `employmentType`           | As posted, e.g. `Full-time`, `FullTime`, `Contractor`, `정규직`, `인턴`                                                     |
| `employmentTypeNormalized` | One of `full-time`, `part-time`, `contract`, `internship`, `temporary`, or `null` when the company does not say (see below) |
| `postedAt`                 | First published (Greenhouse, Ashby) or created (Lever), ISO 8601 UTC                                                        |
| `updatedAt`                | Last updated, ISO 8601 UTC (Greenhouse only, otherwise `null`)                                                              |
| `applyUrl`                 | The original job page on the company's career site. Every item has one.                                                     |
| `source`                   | `greenhouse`, `lever` or `ashby`                                                                                            |
| `postingLanguage`          | `ko` when the title contains Korean, otherwise `en`                                                                         |
| `salary`                   | Pay range only when the company publishes it in the career system's pay field. Never estimated, so it is usually `null`.    |
| `description`              | Plain-text job description, only with *Include job description*                                                             |

**What "in English" means:** field names, cities, countries and the structure are in English, so you can sort and filter. Job titles and descriptions stay exactly as the company wrote them. About half of the jobs are posted in Korean; `postingLanguage` tells you which.

### Employment type

`employmentType` is always the company's own value. `employmentTypeNormalized` maps it to one of five values so you can filter across companies:

- `full-time`: Full-time, FullTime, Regular, Permanent, 정규직
- `contract`: Contract, Contractor, Professional Contractor, 계약직
- `internship`: Intern, Internship, 인턴
- `part-time`: Part-time, PartTime, 파트타임
- `temporary`: Temporary, Fixed-term, Seasonal

Many companies do not state an employment type (about two thirds of the jobs on 2026-11-12), so the field is often `null`. Nothing is guessed, with one exception: when the company gives no type and the title explicitly says "Intern", "Internship" or "인턴", the job is marked `internship`.

### Companies covered

Counts are the Korea-based jobs found on 2026-11-12 and change every day. A company with 0 today stays on the list, because its Korea team may post again.

| Company                 | Type                     | Career system | Korea jobs |
| ----------------------- | ------------------------ | ------------- | ---------- |
| Coupang                 | Korean / Korean-founded  | Greenhouse    | 350        |
| 42dot                   | Korean / Korean-founded  | Ashby         | 79         |
| Krafton                 | Korean / Korean-founded  | Greenhouse    | 64         |
| FuriosaAI               | Korean / Korean-founded  | Greenhouse    | 54         |
| Daangn (Karrot)         | Korean / Korean-founded  | Greenhouse    | 48         |
| Moloco                  | Korean / Korean-founded  | Greenhouse    | 11         |
| FriendliAI              | Korean / Korean-founded  | Ashby         | 10         |
| Sendbird                | Korean / Korean-founded  | Greenhouse    | 2          |
| Musinsa                 | Korean / Korean-founded  | Ashby         | 1          |
| Databricks              | Global with a Korea team | Greenhouse    | 18         |
| Agoda                   | Global with a Korea team | Greenhouse    | 15         |
| Airwallex               | Global with a Korea team | Ashby         | 13         |
| Anthropic               | Global with a Korea team | Greenhouse    | 13         |
| Datadog                 | Global with a Korea team | Greenhouse    | 12         |
| OpenAI                  | Global with a Korea team | Ashby         | 9          |
| Riot Games              | Global with a Korea team | Greenhouse    | 7          |
| Notion                  | Global with a Korea team | Ashby         | 5          |
| Palantir                | Global with a Korea team | Lever         | 5          |
| Snowflake               | Global with a Korea team | Ashby         | 5          |
| Cohere                  | Global with a Korea team | Ashby         | 4          |
| GitLab                  | Global with a Korea team | Greenhouse    | 4          |
| Airbnb                  | Global with a Korea team | Greenhouse    | 3          |
| AppsFlyer               | Global with a Korea team | Greenhouse    | 2          |
| Braze                   | Global with a Korea team | Greenhouse    | 2          |
| Celonis                 | Global with a Korea team | Greenhouse    | 2          |
| ElevenLabs              | Global with a Korea team | Ashby         | 2          |
| Everpure (Pure Storage) | Global with a Korea team | Greenhouse    | 2          |
| Okta                    | Global with a Korea team | Greenhouse    | 2          |
| Payoneer                | Global with a Korea team | Greenhouse    | 2          |
| The Trade Desk          | Global with a Korea team | Greenhouse    | 2          |
| Aptos Labs              | Global with a Korea team | Greenhouse    | 1          |
| Dataiku                 | Global with a Korea team | Greenhouse    | 1          |
| Elastic                 | Global with a Korea team | Greenhouse    | 1          |
| Figma                   | Global with a Korea team | Greenhouse    | 1          |
| Liftoff                 | Global with a Korea team | Greenhouse    | 1          |
| MongoDB                 | Global with a Korea team | Greenhouse    | 1          |
| Roblox                  | Global with a Korea team | Greenhouse    | 1          |
| Tenstorrent             | Global with a Korea team | Greenhouse    | 1          |
| UiPath                  | Global with a Korea team | Ashby         | 1          |
| Zscaler                 | Global with a Korea team | Greenhouse    | 1          |
| Binance                 | Global with a Korea team | Greenhouse    | 0          |

Many Korean companies (Naver, Kakao, Toss and others) run their own career sites or use other hiring systems, so they are not included. Want a company added? Open an issue (see *Contact* below). We add it if its jobs are on a public Greenhouse, Lever or Ashby board.

### Which jobs count as Korea-based

- The job's location names a Korean place (Korea, Seoul, Pangyo, Seongnam, Busan, Incheon, Daejeon, in English or Korean), or the career system gives the country as Korea.
- A job with several locations counts when one of them is in Korea.
- A remote job counts only when it says Korea (`country: "KR"`) or APAC (`country: "APAC"`). "Remote" alone or "Remote - US" does not count.
- On Greenhouse the location shown on the job decides. The office list is used only when the location is blank, because it often names every office in a region.
- "Koreatown" and "North Korea" do not count.

### Data source and method

- **Sources:** only the public job-board APIs of [Greenhouse](https://docs.greenhouse.io/job-board.html), [Lever](https://github.com/lever/postings-api) and [Ashby](https://developers.ashbyhq.com/docs/public-job-posting-api). These APIs exist so that a company's jobs can be shown outside its own site. Lever's documentation says its postings "may be scraped by third parties".
- **Polite access:** the Actor sends an honest User-Agent (`SeoulsmithKoreaTechJobs/0.1 (+https://seoulsmith.com)`), waits at least 1 second between requests to the same host, makes at most 2 requests at a time, checks each API host's robots.txt first, and stops using a host that answers 403 or 429.
- **No personal data:** only the job fields listed above are kept. Recruiter and hiring-manager names or emails are never stored.
- **As published:** jobs are returned as the companies publish them. Titles are not translated and salaries are not estimated. The apply link always points to the original job page. Check it there before you apply.

### Pricing

Free. You only pay for the Apify platform usage of your runs, which is very small (one run uses about 44 HTTP requests and little memory).

### FAQ

**Why is a job title in Korean?** The company posted it in Korean. Use `postingLanguage` to filter, or turn on *Include job description* to read the full text.

**Why is `city` null?** Some jobs only say "South Korea". They are still Korea-based jobs.

**How often is the data updated?** Every run reads the live job boards, so the data is as fresh as your run.

**Can I get jobs from other countries?** No. This Actor is only for jobs in Korea.

### Learn more

How this dataset is built, and what the first week of data shows: [715 tech jobs in Korea, straight from company job boards](https://seoulsmith.com/blog/korea-tech-jobs-in-english/) on the Seoulsmith blog.

### Contact, removal and stop requests

This Actor is not affiliated with, endorsed by or sponsored by Greenhouse, Lever, Ashby or any of the companies listed. Company names are used only to say whose public jobs are included.

If you represent a listed company and want your board removed, or want us to stop requesting it, open an issue in this Actor's **Issues** tab on Apify Store. We remove the board from the list in the next build. Bug reports and company requests go there too.

# Actor input Schema

## `companies` (type: `array`):

Only these companies, one per line. Matches the company name or its career-board token, case-insensitive, part of the name is enough. Examples: "Coupang", "Krafton", "Daangn". Leave empty for all covered companies (see the README for the list).

## `keywords` (type: `array`):

Only postings whose title, department or team contains one of these words, case-insensitive. Examples: "backend", "data", "machine learning", "백엔드". Leave empty for all postings.

## `cities` (type: `array`):

Only postings in these Korean cities. Example: Seoul and Pangyo. Pangyo postings are listed as Pangyo, not Seongnam. Postings that name only "South Korea" have no city and are left out when a city is chosen. Leave empty for all.

## `remoteOnly` (type: `boolean`):

Only postings marked fully remote (remote = true) by the company. Example: turn on to skip office and hybrid roles. Remote postings are included only when Korea or APAC is stated.

## `onlyNewSinceLastRun` (type: `boolean`):

Skip postings this Actor already returned in your earlier runs with this option on. Example: schedule a daily run to get only new openings. The list of seen posting IDs is kept in your named key-value store "korea-tech-jobs-state".

## `includeDescription` (type: `boolean`):

Add the full job description as plain text (description field). Example: turn on for keyword analysis. Off by default to keep the dataset small.

## `maxItems` (type: `integer`):

Stop after this many postings (newest first). Example: 100.

## Actor input object example

```json
{
  "companies": [],
  "keywords": [],
  "cities": [],
  "remoteOnly": false,
  "onlyNewSinceLastRun": false,
  "includeDescription": false,
  "maxItems": 1000
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `overview` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("seoulsmith/korea-tech-jobs").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("seoulsmith/korea-tech-jobs").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call seoulsmith/korea-tech-jobs --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,seoulsmith/korea-tech-jobs"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/fVZu3gySKMu56vp2A/builds/wLnmYYxTq1fHCHyVk/openapi.json
