Opening - "You start your self-introduction. I check the time. You have 30 seconds to grab me."

You walk into the meeting room. I stand up to shake your hand and say, "Please, have a seat." You start your self-introduction. I check the time.

You have 30 seconds to grab me.

Not grab my attention—that's too easy. I'm talking about grabbing my interest.

Do you know how many people I've interviewed this year? 127. Do you know how many I've hired? 3.

So when you open with "My name is XXX, I graduated from XXX University, and I have X years of experience," my brain has already switched to autopilot. This information is all in your resume, which I reviewed before the interview.

What I'm waiting for is: Why are you sitting here?

Not "why do you want a job," but "why do you want to be at this company, in this role, at this moment in time, having this conversation with me?"

The first 10 seconds, I'm observing your eyes—are they steady or wandering? Your posture—are you relaxed or stiff? Your speaking pace—is it natural or rehearsed?

The next 20 seconds, I'm listening to your narrative arc. Does your life trajectory make sense? Do your choices have logic? Do you know what you want?

30 seconds have passed.

For some people, those 30 seconds feel like the opening of a brilliant TED talk that makes me want to hear more. For others, those 30 seconds feel like a looped recording that makes me start calculating how many minutes are left.

This isn't fair. But it's real.

Self-Introduction Phase - What Am I Listening For?

You're speaking, I'm listening. But I'm not listening to what you're saying—I'm listening to how you're saying it.

I'm Listening to Your "Meta-Information"

You say, "I was responsible for core projects at my last company." I'm listening to:

• Are you saying it with pride or with caution?
• How many times did you use "I" versus "we"?
• Are you stating facts or selling yourself?

A confident person doesn't need to emphasize confidence. A truly capable person is often more humble when describing achievements. It's the insecure ones who like to pile on adjectives.

I'm Listening to Your "Selectivity"

You have 3 minutes to introduce yourself. What do you choose to say?

• Some choose the chronological approach: university, internship, first job, second job...
• Some choose highlight moments: The most impressive project I worked on was...
• Some choose the growth narrative: I grew from a clueless newbie to...
• Some choose the fit angle: I read your job description, and I think my experience is particularly relevant...

There's no standard answer. But your choice reveals your thinking pattern: Are you self-centered or other-centered? Are you focused on the past or on the future?

I'm Listening to Your "Rhythm"

Some people speak like a machine gun, afraid that stopping means losing the opportunity. Some people speak like chanting, every word equally flat.

The best expression has breath. Fast and slow, high and low, key points and transitions. This isn't just presentation skills—it's a reflection of thinking clarity.

A person with confused thinking will speak with confusion.

You Start Coding - What Am I Watching For?

"Let's do a coding problem."

You take the whiteboard marker and walk to the whiteboard. I lean back in my chair and start observing.

I'm Not Watching for the Answer

If you think I'm waiting for the correct answer, you're wrong. I already know the correct answer. Google knows it. ChatGPT knows it.

What I'm watching is your thinking process.

• Do you start writing immediately, or do you clarify the problem first?
• Do you start with edge cases or with the general case?
• Do you explain while writing, or explain after you're done?
• When you get stuck, do you go silent, or do you verbalize what you're thinking?

I'm Watching Your "Toolkit"

What method do you choose to solve this problem?

• Some use the most direct approach, not efficient but clear
• Some use the most optimized approach, but the code is complex
• Some write test cases first, then code
• Some write pseudocode first, then translate to code

There's no best method, only the most suitable method. And your choice reveals your experience level and thinking habits.

I'm Watching Your "Engineering Mindset"

The code is done. What are you doing now?

• Some are checking boundary conditions
• Some are thinking about time complexity
• Some are considering readability
• Some are waiting for me to say "Okay, next question"

An excellent engineer doesn't stop when the code is written. They proactively think: What will happen to this code in production? Are there potential bugs? How to optimize? How to test?

You Get Stuck - What Am I Thinking?

You've stopped. The marker hovers in the air, your eyes start to wander.

This is my favorite moment.

Not because I enjoy seeing you struggle, but because this is when I can see who you really are.

I'm Thinking: How Do You Handle Difficulty?

• Some start to panic, speaking incoherently
• Some choose silence, withdrawing into their own world
• Some turn to me, seeking hints
• Some start talking to themselves, organizing their thoughts

The last type is often the most excellent.

Because they know how to externalize their thinking process. They're not asking for help—they're using me as a mirror for their thinking. They'll say, "I'm thinking this approach might not be right because... maybe I should try a different direction..."

At this moment, I'm not evaluating your IQ—I'm evaluating your metacognition: Can you monitor your own thinking process and adjust direction when needed?

I'm Thinking: How's Your Resilience?

How long have you been stuck? 5 minutes? 10 minutes?

• Some give up after 3 minutes
• Some are still trying different approaches after 10 minutes
• Some can quickly reset their mindset after failure and move to the next question

An interview isn't an exam—you don't have to get every question right. But your attitude when facing difficulty matters more than the answer itself.

You Ask Me Questions - What Am I Judging?

"Do you have any questions for me?"

This is the final stage of the interview, and also the most underrated one.

I'm Judging: How Much Homework Did You Do?

• "What does your company do?" — You didn't do your homework
• "What's your tech stack?" — You did basic homework
• "I saw you recently launched XXX feature. What were the technical challenges?" — You did deep homework
• "I saw your XXX project on GitHub. Why did you choose XXX architecture?" — You did exceptional homework

Question quality = Preparation depth + Curiosity

I'm Judging: What Are Your Values?

What you ask reveals what you care about:

• Only asking about compensation and benefits — You care about short-term returns
• Asking about team culture — You care about work environment
• Asking about technical challenges — You care about growth opportunities
• Asking about business direction — You care about company prospects
• Asking about my work experience — You care about authentic insights

There's no right or wrong, but fit matters.

I'm Judging: Your Social Intelligence

• Are you asking me questions, or having a conversation with me?
• Are you reading from a list, or naturally extending from our conversation?
• Are you showing off, or genuinely wanting to understand?

A person with high EQ can turn Q&A into a pleasant dialogue. Not a one-sided information gathering session.

You Say "I Don't Have Any Questions" - I've Already Decided

You say "I don't have any more questions." I smile and say, "Great, thank you for your time."

Actually, I had a preliminary judgment in the first 5 minutes after you walked in. The rest of the time was just validating or adjusting that judgment.

What Am I Doing?

I'm recalling key moments from the past hour:

• During your self-introduction, did I sense confidence or nervousness?
• While you were coding, did I sense logic or chaos?
• When you got stuck, did I sense resilience or fragility?
• When you asked questions, did I sense curiosity or perfunctoriness?

Every detail is casting a vote for my decision.

What Am I Thinking?

I'm thinking:

• Would I want to work with this person?
• Would I want this person on my team?
• Can this person make the team better?

This isn't an IQ test. This is a collaboration test.

Signals That I'll Hire You - Details You Might Not Notice

Some signals you might not notice, but I'm silently adding points:

Micro Signals

• When you entered, I stood up to shake hands, and you stood up too — You understand respect
• Before sitting, you asked "May I sit here?" — You're polite
• When speaking, your eyes meet mine, but you don't stare — You're confident but not aggressive
• When stuck, you proactively say "I need to think for a moment" — You manage expectations well
• After finishing code, you proactively say "Let me explain my approach" — You have communication awareness
• When leaving, you cleaned the whiteboard — You have a sense of responsibility
• After leaving, you sent a thank-you email — You're professional

Strong Signals

• Your question made me think — You have insight
• You went deeper on a problem than I expected — You have real skills
• You admitted not knowing something but expressed willingness to learn — You're honest and have a growth mindset
• You disagreed with me on something and could clearly articulate why — You can think independently
• You reminded me of an excellent colleague — You have cultural fit

These signals matter more than correct answers.

Signals That I'll Pass on You - Red Flags You Might Ignore

Some signals you might think are nothing, but I'm silently deducting points:

Weak Red Flags

• You were late but didn't notify me in advance — You don't respect my time
• During self-introduction, you were reciting from memory — You didn't prepare, or prepared wrong
• When speaking, your eyes kept avoiding mine — You lack confidence, or are hiding something
• You interrupted me — You don't know how to listen
• You said "I know this" but answered incorrectly — You pretend to know what you don't
• You complained about your previous company or boss — You lack professionalism
• You asked "Is there a standard answer for this question?" — You care too much about results, not process

Strong Red Flags

• You lied about something — Integrity issue, automatic disqualification
• You showed obvious impatience with a question — You lack patience
• You said "This technology is too simple, I don't want to do it" — You're arrogant and ungrounded
• You asked "If I join, how soon can I get promoted?" — You're too transactional
• You reminded me of a former colleague who gave me headaches — You have cultural misfit risk

One red flag can cancel out ten correct answers.

Advice for Candidates - Don't Just Prepare Answers, Prepare Your "Persona"

So, how should you prepare for interviews?

Don't Just Prepare Answers

Many people prepare for interviews by grinding problems, memorizing answers, and preparing project introductions. These are important, of course, but far from enough.

Because an interview isn't an exam. An interview is a conversation.

Prepare Your "Persona"

By persona, I don't mean fake packaging—I mean the version of yourself you want the interviewer to remember.

Ask yourself:

• How do I want the interviewer to evaluate me?
• "This person is smart"? Or "This person is reliable"?
• "This person has strong technical skills"? Or "This person communicates well"?
• "This person has potential"? Or "This person has experience"?

Different personas require different presentation styles.

Prepare Your "Stories"

Don't prepare a chronological list. Prepare stories.

• A story about how you solved a problem
• A story about how you faced failure
• A story about how you grew
• A story about why you chose this company

Stories are more persuasive than data.

Prepare Your "Questions"

Don't wait until the end of the interview to think of questions. Prepare 3-5 high-quality questions in advance:

• A question about technology
• A question about the team
• A question about the business
• A question about culture
• A question about me

Good questions impress me more than good answers.

Final Words

An interview is an asymmetric game.

You know I'm evaluating you, but you don't know what I'm evaluating. You think I'm listening to your answers, but I'm reading your thinking. You think I'm recording your performance, but I'm sensing your presence.

But this also means you can influence me.

You can make me feel your confidence through your expression. You can make me feel your logic through your thinking process. You can make me feel your curiosity through your questions.

An interview isn't a one-way judgment. It's a two-way conversation.

When you're speaking, what am I thinking? I'm thinking: Is this person worth my time investment?

Make me feel it's worth it.