How to Ask for Interview Feedback in Korean Without Sounding Pushy

How to Ask for Interview Feedback in Korean Without Sounding Pushy

The interview is over. You bowed, thanked everyone, made it out of the building — and now you’re checking your inbox a little more often than you’d like to admit.

Maybe you just want to know how it went. Maybe a rejection already arrived and you’d like to know what to fix next time. Either way, sending “Can I get feedback?” the same afternoon often lands blunter in Korea than you meant it to.

Today we’ll look at how to ask for feedback softly: when to send it, where to send it, and which Korean lines keep the door open.

Timing and channel matter as much as the words

Give it three to seven days after the interview, or wait until the decision date they already gave you has passed. Asking earlier can feel like you’re pushing for an answer they haven’t made yet.

Then pick the right door. Email or the recruiter portal is the safe route. A cold KakaoTalk message to someone who sat on the panel feels personal in a way most interviewers won’t welcome, even if you happen to have their ID.

The wording comes in two flavours. If you’re still waiting on a result, you ask about the outcome and, gently, for a little feedback. If you already know it’s a no, you frame it as learning — 다음 지원에 반영하고 싶어, “so I can reflect it in my next application” — not as a debate about the decision.

And if they’ve already said no: thank them once, ask once, then let it rest. No asking for scores, no arguing the rejection, no CC’ing the whole panel, no chain of follow-ups.

One honest note: many Korean employers give little or no written feedback at all. Silence after a polite ask is normal, not a sign you did something wrong. If you get even one line back, treat it as a win.

Lines you can borrow

  • 면접 기회 주셔서 감사합니다. — Thank you for the interview opportunity. (always open with this)
  • 결과가 어떻게 되었는지, 가능하시다면 간단히 피드백 주실 수 있을까요? — Could you let me know how it turned out and, if possible, share some brief feedback?
  • 다음 지원에 반영하고 싶어, 부족했던 점이 있으시면 조언 부탁드립니다. — I’d like to apply this to my next application, so if anything was lacking, I’d appreciate your advice.
  • 가능하시다면 — “if possible” — the small cushion that keeps an ask from sounding like a demand

Try it before your next interview

Write your thank-you-plus-feedback email now, before you need it, and save it as a draft. When the moment comes, check three things before you send:

  • Has it been 3–7 days, or past their stated decision date?
  • Is it going by email or the recruiter portal, not a cold Kakao?
  • Is it one thank-you and one ask — nothing more?

Asking well won’t guarantee an answer, but it leaves a good last impression — and in a small industry, that counts for more than you’d think.

Got an interview coming up? You can rehearse your answers with MOCKEE, an AI mock interview.

Related reads

If you want to practice these lines out loud:

Comments

Post a Comment

Popular posts from this blog

How Do You Ask for a Confirm, Reply, or Review in Korean at Work?

Image
Have you ever finished a Korean work email, then paused on the last line, not quite sure you asked for the right thing? You typed something polite that ends in 부탁드립니다 . It looks fine. A day later you get a short “확인했습니다” when what you needed was a yes or no — or silence, because they thought you were just looping them in. Today we’ll untangle three closers that sound almost the same in English, so you can pick the one that matches what you actually need. The three that get mixed up Korean workplaces lean hard on these: 확인 부탁드립니다 — “please confirm / take a look” 회신 부탁드립니다 — “please reply” 검토 부탁드립니다 — “please review” They are not interchangeable. 확인 is for eyes. Did the file arrive? Is the date okay? Please look once so we’re aligned. You’re not asking for a long answer — you’re asking them to check. 회신 is for words back. A decision, a yes/no, something written you can act on. If you need them to answer, this is the one. 검토 is for judgment on a document — a deck, a contract, a prop...
Read more

Graduating on a D-2 Visa: Should You Switch to D-10 or E-7?

Image
Graduation photos are done, friends are booking flights home, and someone finally asks what visa you’re moving to next. You realise the honest answer is still “I’ll figure it out after commencement.” That’s usually how the scramble starts. Today we’ll walk through the two routes the official guidance sketches for D-2 graduates, plus a few Korean terms that make the conversation with your school or immigration much smoother. Offer in hand, or still looking? One question decides your route: do you already have a signed employment contract? If you do , and the role fits an employment stay qualification — for example E-7 (Specific Activities) — you may be able to apply to change straight to that employment status, as long as you meet the rules for D-2 prospective graduates. The official guidance says a change to employment status (E-1 through E-7 as applicable) needs all three: legal stay on D-10 or D-2, a job field that matches that stay qualification and its requirements, and a signed em...
Read more

Ssi vs Nim: How Do You Address Coworkers in Korean?

Image
Someone on your team calls you 민수 씨 , so on Monday you greet your lead the same way. The room goes just a little quiet. Or the opposite: you learned “님 = polite” in class, so you attach it to everyone, until a peer laughs and tells you it sounds a bit stiff. This isn’t a full 존댓말 lesson. Today we’ll look at one small choice — how you attach something to a person’s name — and why it quietly ranks the room. 직함+님 vs 이름+씨 직함+님 (job title + 님) is your safe default for anyone above you and for any client: 팀장님 , 과장님 , 부장님 , 대표님 . You can add a surname in front — 김 과장님 , 박 팀장님 — and it still works. Bosses, clients, external partners, people you mainly know by their role: 직함+님 is never the wrong call. 이름+씨 (given name + 씨) is peer politeness. It’s fine when your workplace already uses it among equals or toward juniors — if a same-rank colleague calls you 민수 씨, it’s usually okay to call them the same way back. The trap is going upward. Calling a manager by name+씨 because a peer did it to you ...
Read more