Korea Tech Jobs in English — Coupang, Krafton, Daangn & more
Pricing
Pay per usage
Korea Tech Jobs in English — Coupang, Krafton, Daangn & more
Korea-based tech job postings from company career systems (Greenhouse, Lever, Ashby public APIs), in English fields with the original apply link.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Seoul Smith
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Features
Share
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
- Click Start. With the default empty input you get every Korea-based job from all companies.
- To narrow it down, fill in Companies, Keywords or Cities (see below).
- Download the results as JSON, CSV or Excel, or read them through the Apify API.
- For a new-jobs feed, turn on Only new since last run and add a schedule (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:
{"companies": ["Coupang", "Krafton", "Daangn"],"keywords": ["backend", "data"],"cities": ["Seoul"],"onlyNewSinceLastRun": true}
Output
One item per job. Example (Palantir, from Lever):
{"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, Lever and Ashby. 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 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.