Nexon

Large Enterprises

Nexon is a South Korean-Japanese video game company known for developing and publishing online and mobile games, including popular titles such as MapleStory, Dungeon & Fighter, and KartRider. It is one of the largest game companies in Asia and pioneered the free-to-play business model with in-game microtransactions.

4 interview notes · updated Jul 2026

Nexon·Product Manager·Onsite - Product Sense / Strategy

Jul 2026

Nexon PM interview that was basically one big live-ops case study. The whole session revolved around a single scenario about an item usage spike in a game like MapleStory, broken into diagnosis, hypothesis, validation, and decision-making. Dense and pretty fun if you're into game economy stuff, but it moves fast.

An item in a live online game suddenly sees a massive spike in usage. How do you investigate what's happening, find the root cause, and decide whether to act?
What clarifying questions would you ask before diving into the investigation?
How would you confirm the spike is real and not just a data or instrumentation problem?
What hypotheses would you build around why the spike is happening?
Which teams would you loop in and what data would you pull from each?
How do you decide what action to take once you've identified the root cause?
What would make you push for an immediate hotfix rather than waiting?
If revenue is going up but player complaints are also rising, how do you handle that tension?
How would you detect whether the usage spike is being driven by bots rather than real players?
What would your ongoing monitoring dashboard look like after an incident like this?

“This is the main case and it ate up most of the session.”

View Post

Nexon·Product Manager·Hiring Manager Screen

Jun 2026

Went through a PM screen for Nexon focused almost entirely on background, motivation, and fit. Pretty standard behavioral territory but the gaming angle made it a bit more specific than your usual PM interview.

Walk me through your background and why you want this role.
Tell me about a project you're most proud of. What was the problem, your role, and what did it lead to?
What are your biggest strengths as a PM, and what's a real weakness you're working on?
Which project best demonstrates your product judgment?
What game or product metric do you care about most, and why?
How do you think about balancing player experience with monetization?
Tell me about a time you received critical feedback and what you did with it.
Why Nexon specifically, and why now?

“I went present-to-past instead of just listing jobs chronologically and it felt way more natural.”

View Post

Nexon·Product Manager·Onsite - Product Sense / Strategy

May 2026

Product sense interview at Nexon for a PM role, centered almost entirely on live-service game product thinking. The main question was a big open-ended case and they kept pushing with follow-ups. Felt more like a working session than a standard interview.

Walk through how you would come up with a new feature idea for a live-service game, from identifying the player problem all the way to defining what success looks like.
How would you find the right player problem to solve? What data and signals would you actually look at?
Once you've identified the problem, how do you generate multiple feature concepts rather than just jumping to the obvious solution?
How would you test a new feature without messing up the game economy?
What metrics would tell you the feature actually worked, and what guardrails would make you shut it down?
What if your highest-spending players love the feature but casual players hate it?
How would you avoid just copying what competitors are doing when generating feature ideas?
How would you bring design and live-ops teams into the feature development process?

“This was the whole interview basically.”

View Post

Nexon·Product Manager·Onsite - Cross-functional / Panel

Apr 2026

Nexon PM interview focused almost entirely on cross-functional conflict scenarios, specifically how you handle it when game designers or monetization teams push back on your proposals. Felt more like a leadership maturity test than a product sense interview.

When cross-functional partners like designers, engineers, or monetization teams push back on your proposal, how do you handle it?
How do you figure out what risk each partner is actually worried about when they disagree with you?
Once you understand the disagreement, how do you get the team aligned around a shared goal?
How do you actually move from debate to a decision and get execution going?
When would you escalate a disagreement versus continuing to resolve it yourself?
What do you do when design goals and monetization goals are directly in conflict?
How do you avoid falling into endless alignment meetings without making decisions?
How do you make a call when your data is inconclusive?

“This is the core question the whole interview orbited around.”

View Post