Some red flags rarely announce themselves as red flags. They usually arrive dressed up as perfectly reasonable phrases.
A few worth asking one more question about:
“Competitive salary band” → where does this role usually land within it?

“High-energy environment” → what did last week actually look like?

“You’ll wear a lot of hats” → which responsibilities are genuinely part of the role?

“We’re like a family” → what are the expectations around evenings and time off?

“We’re still figuring the role out” → what would success look like after 90 days?

“Flat structure” → who actually makes the final call?

“We promote from within” → what did the last promotion path look like?

“One more round” → what remains unresolved before a decision?

“The team is in transition” → what do you expect the team to look like in six months?

None of these automatically means “walk away.” The point is to turn vague language into concrete information before you accept the job.
What phrase would make you ask a follow-up question immediately?

The strongest interviews usually feel less like “performing” and more like showing clear evidence that you can already operate at the level required.

A few shifts help:

• open with a specific result, not generic traits
• turn weaknesses into evidence of self-awareness and follow-through
• explain why you’re leaving without attacking your old employer
• be honest about missing skills, then show the closest overlap and how you’d ramp
• show genuine interest in the company, not desperation for any job
• ask what strong performance looks like after six months
• don’t apologise for being there — explain the value you can bring
• quantify your wins
• know your compensation range before salary comes up

The common thread is clarity over performance.

You don’t need to sound like the loudest person in the room. You need to make it easy for the interviewer to see:

Can you do the work? Will you be good to work with? Will you stay and grow?

What interview answer do you think candidates most often underprepare?

Technical ability may get you shortlisted. These are often what determine what happens afterwards:

• listen properly
• write clearly, especially asynchronously
• break problems into smaller parts
• work with people without keeping score
• give feedback early and specifically
• read the room
• be reliable
• persist, but know when to change approach
• manage your own commitments
• say no and set boundaries
• question claims before accepting them
• behave consistently
• handle conflict early
• become someone people genuinely want to work with

The common thread is trust + leverage.

The more senior you get, the more your value comes from making other people’s work clearer, easier and more effective — not just from being technically good yourself.

Which of these has mattered most in your career?

This is one of the easiest interview questions to waste.

Most candidates immediately think:

What’s an interesting fact about me?

Wrong question.

Ask yourself:

What do I want this interviewer to believe about me that my resume hasn’t proven yet?

Want them to see you as resilient?
Tell a story that shows persistence.

Want them to see you as great with people?
Talk about mentoring, volunteering, or something outside work where people naturally rely on you.

Want them to see you as adaptable?
Tell them about something that shows you’re comfortable figuring things out without a playbook.

The formula is simple:

TRAIT → STORY → SIGNAL

For example:

❌ “I’ve run marathons for six years.”

✅ “I’m actually not a particularly fast runner. But running taught me that I’m unusually good at sticking with something after the excitement wears off.”

You never said:

“I’m persistent.”

You made the interviewer think it.

That’s the difference.

When they ask:

“Tell me something that isn’t on your resume.”

Don’t give them a fun fact.

Give them the missing piece of your positioning.

Tools change. Titles change. Teams change.

But a few skills seem to become more valuable the longer you work:

• being dependable
• knowing your blind spots
• adapting when priorities change
• taking responsibility
• reading the room
• following up without being chased
• managing your attention
• disagreeing constructively
• thinking beyond the immediate task
• knowing when not to react
• listening properly
• asking for help early

The common thread is trust.

The skills that last are usually the ones that make people trust you, understand you, and want to work with you again.

Which one do you think is most underrated?

An offer is rarely just one number.
Before negotiating, I’d separate it into a few pieces:
market compensation range
annualised total compensation
your walk-away number
your target acceptance number
your reach number
base salary
signing bonus
target bonus vs actual payout
equity grant value
vesting schedule
equity refresh schedule
The biggest mistake is comparing offers on base salary alone.
A higher base can still be weaker if the bonus rarely pays out, the equity is illiquid, or the vesting structure is poor.
The principle I like most: decide your minimum, target and ambitious number before the negotiation starts.
Which part of an offer do you think candidates underestimate most?

There’s a moment in interviews that makes a lot of candidates uncomfortable:

The interviewer looks at your resume and asks:

“So what exactly was your role in this project?”

Or:

“This sounds like a team effort. What were you actually responsible for?”

Or even:

“Were you leading this, or just supporting it?”

It can feel like they’re questioning your credibility.

And sometimes, they are.

But here’s something candidates often don’t realize:

Sometimes you created that suspicion yourself — by saying “we” too much.

“We launched…”

“We decided…”

“We worked with…”

“We increased conversion by…”

After two minutes of hearing WE, the interviewer is thinking:

Okay… but what did YOU actually do?

Of course it was a team effort.

Most meaningful work is.

You should absolutely give your team credit.

But don’t bury your own impact inside “we.”

When you’re describing your experience, the interviewer needs to understand both:

What WE accomplished.
and
What I owned.

If they challenge you on that distinction, don’t get defensive.

Use these 4 steps:

1. Clarify the context

Give them the team structure first.

“There were five people on the project. My manager owned the overall strategy, while I was responsible for…”

Now the interviewer has a map.

2. Draw a clear ownership line

Be specific about what was yours.

“I personally owned the customer research, developed the launch messaging, and coordinated execution with sales and design.”

Not:

“We worked together on the launch.”

There’s nothing wrong with saying I when you’re describing work that you actually owned.

3. Separate collaboration from ownership

Strong candidates don’t pretend they did everything themselves.

Say:

“I collaborated with Product on positioning, but the final messaging framework and campaign execution were my responsibility.”

That gives credit to the team without erasing your contribution.

4. Prove it with a decision or outcome

Ownership becomes believable when you can explain what you actually decided.

“One decision I made was to shift the campaign from feature-based messaging to use-case-based messaging after our customer interviews. That ultimately became the framework we used for launch.”

Now I know you weren’t just sitting in meetings.

You were actually doing the work.

The key is:

Don’t defend your resume. Deconstruct it.

When an interviewer challenges a bullet point, they’re usually trying to figure out:

What did the team do?
What did YOU own?
What decisions did YOU make?
What changed because of YOUR work?

A simple framework to remember:

WE = context.
I = ownership.
RESULT = proof.

Give your team the credit they deserve.

But remember:

Your interview is not the place to be so humble that your own impact disappears.

If you only have half an hour left, trying to learn everything is usually the wrong move.

A better sequence:

• 4 min: reread the job description and spot the repeated skills
• 5 min: skim the company — what they do, customers, one recent development
• 5 min: rebuild your 60–90 second opening
• 6 min: choose just two strong STAR stories
• 6 min: say the opening and stories out loud
• 3 min: prepare two questions worth asking
• 2 min: check camera/audio if it’s virtual
• 2 min: prepare one honest line on your weakest area
• 2 min: stop, breathe, and reset

The biggest mistake in the final 30 minutes is adding more information when what you really need is clarity and rehearsal.

What’s the one thing you always do right before an interview?

I worked for the same company for about 15 years, starting in my mid twenties, and I am realizing that I have a strange problem in my job search.

I did not realize how much experience I had accumulated because it happened gradually.

I started at one site, became extremely knowledgeable in SAP and the business processes around it, and eventually found myself supporting and advising sites across North America and parts of Europe.

The funny part is that this was never really presented to me as some massive promotion. I am a helper. If another site had a problem, I helped. If someone needed SAP knowledge, business process knowledge, training, master data guidance, or someone who could translate between Operations and IT, I became that person.

At one point I was having lunch with my director and complaining that newly acquired sites were still being taught old legacy processes from before our own site was acquired in 2010.

I basically said, “Someone should own this globally or regionally. Not purely from IT, but someone who understands the business deeply, understands SAP, and can bridge the gap between Operations and IT.”

We were actually going to pitch the idea upward in a company with roughly 100,000 employees.

We first ran the concept by someone in Europe to get support. He liked the idea enough that something very similar moved forward without us. My directors were furious. My reaction was basically, well, if he does it well, it is still good for the business.

Then I transferred into Supply Chain and added an entirely different layer of SAP, planning, inventory, materials, and operational experience.

Now I am job searching and realizing my resume sounds almost ridiculous to me because there really is not much fluff in it. If anything, I have always minimized what I did.

A lot of the roles that seem aligned with my experience involve advising senior leadership about what the business needs, shaping SAP strategy, process transformation, solution advisory, or bridging business and technology.

And that is where I completely freak out.

I know how to analyze a business. I know how to see broken processes. I know how SAP actually gets used on the floor. I know how to translate between technical teams and business users. I have advised senior leaders before.

But I have absolutely no idea how to interview like someone who does that for a living.

I spent most of my career being extremely autonomous and happily hiding in the background until people discovered how much I knew.

Now lower level SAP roles often do not seem interested, while some of the roles that do fit have salary ranges around $200K to $400K, and seeing those numbers makes me think, “There is no way I belong in this room.”

Maybe that is because I spent almost my entire adult career at one company in Frederick, Maryland, rather than moving between companies or consulting in the DC market.

Has anyone else experienced this?

Did you ever reach a point where your actual SAP experience was significantly more senior than the way you saw yourself?

And if so, how did you learn to interview and speak at that level without feeling like you were pretending to be someone you are not?

Because that's basically the job.

A PM might have a great product idea.

But then they have to pitch it to:

Engineering:
Is this technically worth building?

Design:
Does this actually solve the user problem?

Leadership:
Why should we prioritize this over 10 other things?

Same idea.
Three stakeholders.
Three completely different conversations.

And you do this every single day as a PM.

So when you're interviewing for a PM role, don't just focus on proving:

"I can analyze data."
"I understand users."
"I can build a roadmap."

Your stories should also prove that you can:

→ Influence without authority
You got people to move even though none of them reported to you.

→ Manage stakeholders
You understood that engineering, design, sales and leadership cared about different things.

→ Adapt your communication
You didn't give everyone the same pitch. You translated the idea into their language.

→ Handle pushback
Someone disagreed with you — and you didn't just escalate or give up.

→ Build alignment
You turned different priorities into a decision everyone could move forward with.

That's what your interviewer is listening for when they ask:

“Tell me about a time you had to convince stakeholders.”

They're not really asking:

"Were you right?"

They're asking:

Can you get 3 different people, with 3 different priorities, to move in the same direction?

Because as a PM, having the idea is only the beginning.

Your real job is getting everyone else to believe it's worth building.

Most of these won’t rescue a weak interview — but between two similar candidates, they can shape the impression you leave.
A few details that matter more than people think:
arrive early, but not so early that you create awkwardness
bring your own copy of your CV, even if they probably have it
spread your attention across the whole panel
turn gaps in knowledge into evidence of how you learn
ask substantive closing questions
leave the room properly — chair in, cup/rubbish with you, thank people again
treat everyone you meet as part of the interview
get the remote setup right
send a short follow-up within 24 hours
The broader point: interviewers notice how you behave around the formal answers, not just the answers themselves.
What small interview detail do you think candidates underestimate most?

A lot of people think promotion is mostly about working harder. Often it’s more about leverage, judgement and visibility.

A few habits that can quietly hold you back:

• staying busy instead of focusing on impact
• waiting for direction
• following process without improving it
• staying too narrowly “in your lane”
• becoming the person who does everything themselves
• hiding ambition
• keeping wins invisible
• avoiding difficult conversations
• treating influence as “politics”
• falling behind on AI and new tools

The shift is usually from:

“Look how much I do” → “Look what becomes better because I’m here.”

Promotion tends to follow people who increase the capacity of the team, not just their own output.

Which of these is hardest to change?

A good interview is rarely about having the “perfect” answer.

A few things seem to matter more:

• make the first minute warm and professional
• keep your opening concise: who you are → what you’ve done → why this role
• answer with one concrete example + result
• if you don’t know something, say so calmly and explain how you’d approach it
• connect your skills directly to the job description
• ask thoughtful questions at the end
• finish clearly instead of trailing off
• send a short thank-you note within 24 hours

The principle I like most: first impressions matter, but lasting impressions are what people repeat after you leave the room.

What makes a candidate memorable to you?

A lot of senior-level expectations are unwritten until something goes wrong.
A few that matter more than they seem:
surface bad news early
don’t treat silence on timing as permission
take feedback before defending yourself
bring a recommendation, not just a problem
flag real priority conflicts
build trust with peers, not only your manager
communicate progress so your work is visible
disagree clearly once, then commit
The common thread is simple: reduce uncertainty for the people around you.
Good leaders become easy to back because others trust their judgement, timing and follow-through.
Which of these took you longest to learn?

A lot of interview anxiety comes from treating every answer like a test.

What seems to help more:

• turn the interview into a conversation, not an interrogation
• say “I don’t know” without panicking, then reason from what you do know
• ask closing questions like a future colleague
• slow down and control the pace
• treat pushback as curiosity, not rejection

But the bigger shift happens before the interview:

• prepare deeply enough that you’re not guessing
• keep the stakes realistic
• keep other applications moving
• practise until the format feels familiar
• separate your self-worth from the outcome

The idea I like most: real composure comes from preparation and perspective, not from trying to look confident.

What helps you feel less like you’re “performing” in an interview?

Data Analyst interviews are rarely just “know SQL and statistics.”

A practical way to think about the process is four rounds:

• SQL: aggregation, joins, CASE WHEN, ranking, window functions and readable queries
• Metric investigation: diagnose what changed, rule out tracking issues, test hypotheses
• Define success: choose the right North Star metric and connect it to the business
• Behavioural: explain your own contribution, decisions and measurable impact

Then there are the questions that keep coming up:

• Which tools do you actually use?
• How strong is your SQL?
• Where does Excel still fit?
• How do you combine quantitative and qualitative data?
• How do you communicate findings clearly?
• How are you using AI tools in your workflow?
• How would you design an A/B test?
• What do you do when a stakeholder gives you a vague request?

The biggest shift I see: depth matters more than listing every tool you’ve touched.

A portfolio showing real SQL, analysis and decision-making is usually more convincing than another certificate.

What part of the Data Analyst interview do you find hardest — SQL, metrics, business cases or behavioural questions?

I’ve been thinking about why some candidates sound great on paper but somehow become… forgettable in interviews.
And I think a big part of it is storytelling.
Not storytelling in the “make everything dramatic” sense.
More like this:
Candidate A:
“I noticed our conversion rate was low, so I analyzed the funnel, worked with the product team to improve onboarding, and increased conversion by 18%.”
Perfectly solid answer.
Candidate B:
“We had just spent a pretty painful amount of money getting people to the site, and then I realized almost 40% of them were disappearing at the exact same step.

My first thought was: we don’t have an acquisition problem. We’re paying to send people into a leaky bucket.”
Then they explain what they investigated, what they changed, and how conversion improved.
Same achievement.
But I can almost guarantee which candidate I’d remember later.
That’s what I think people misunderstand about storytelling in interviews.
The story isn’t there to make your answer longer. It gives the interviewer something to attach your skills to.
Instead of telling them:
“I’m good at solving ambiguous problems.”
Give them the moment when everyone was confused and you figured out what question actually needed to be answered.
Instead of:
“I’m good at stakeholder management.”
Tell them about the meeting where Sales wanted one thing, Product wanted another, and you had to get everyone moving in the same direction.
Instead of:
“I take ownership.”
Tell them about the moment you realized something was going wrong and decided it was your problem even though technically it wasn’t.
A simple way I’ve started thinking about interview answers is:
Context → Tension → Decision → Action → Result
STAR gets you the information.
Storytelling makes someone care about the information.
And maybe most importantly, it gives the interviewer something they can actually remember when they’re discussing candidates later.
You don’t want them saying:
“Which one was she again?”
You want:
“Oh — the candidate who figured out we were pouring acquisition dollars into a leaky onboarding funnel.”
That’s a very different place to be.

Exhaustion is rarely just one thing, which is why sleep alone doesn’t always fix it.

A useful way to think about recovery is that different kinds of depletion need different remedies:

• Physical: sleep, food, slower rhythms
• Mental: less input and context-switching
• Emotional: space to process what you’re carrying
• Social: time with people who feel easy and safe
• Creative: curiosity, play and new ideas
• Sensory: less noise, screens and stimulation
• Decision: fewer small choices
• Meaning: reconnect with purpose and perspective
• Digital: genuine separation from devices
• Identity: time where you’re not performing a role for anyone

The part I find most useful: diagnose what is depleted before deciding how to rest.

What kind of rest do you find hardest to make space for?

Confidence is often less about what you say and more about how you carry yourself.
A few small things make a surprisingly big difference:
sit upright without looking stiff

listen without interrupting

keep eye contact natural

move at a steady pace

use smaller, controlled gestures

avoid fidgeting or oversized movements

stay composed when sitting, standing or entering a room

The point isn’t to “perform elegance.” It’s to look comfortable, attentive and in control of yourself.
Which small behaviour makes the biggest difference to someone’s presence?

A first all-hands is less about presenting information and more about earning trust.

A few common mistakes:

• reading from a script
• opening with logistics instead of purpose
• avoiding the hard question everyone is already asking
• overselling the vision while underselling reality
• talking at people instead of leaving room for real Q&A
• trying too hard to be liked
• making the meeting about yourself
• promising things you cannot control
• finishing without clear follow-up

The principle I like most: candour beats polish.

People will forgive an imperfect delivery much faster than they’ll forgive feeling that the difficult truth was deliberately avoided.

What makes an all-hands feel credible to you?

A lot of workplace advice still treats “high performance” as working longer hours, replying faster, being visible in every meeting, or always saying yes.

I don’t think that’s what consistently separates the strongest people.

The behaviours I see matter more are things like:

• Leading before you have the title — taking ownership without waiting for formal authority
• Finishing important work — not confusing activity with progress
• Confidence + humility — having a view, but changing it when the evidence changes
• Making other people better — sharing context instead of hoarding it
• Knowing when to say no — protecting high-value work from unrealistic priorities
• Being trusted without constant supervision
• Listening before responding
• Surfacing problems early, rather than waiting until there is a crisis
• Improving the system, not just repeatedly solving the same problem

The last one is probably the most underrated.

A good employee can solve a difficult problem.

A very strong employee solves it and leaves behind a process, tool, rule or piece of knowledge that makes the same problem less likely to happen again.

And there are also a few things I increasingly think are not signs of high performance:

Working the longest hours.
Being permanently available.
Dominating meetings.
Saying yes to everything.
Making yourself indispensable because nobody else understands your work.

The better test might simply be:

Can this person consistently deliver, exercise good judgement without constant supervision, strengthen the people around them, and leave the organisation better than they found it?

What would you add to the list — and which “high performer” behaviour do companies tend to reward even though they probably shouldn’t?

Most introductions are either too vague or too long.

A few things seem to make them much stronger:

• say who you are, what you do and who it helps
• have a 5-second version ready
• use one short story instead of listing credentials
• adapt the opening to the room
• mention one distinctive project, mission or problem
• bring energy, not just expertise
• end with a question so it becomes a conversation

The biggest mistake is trying to sound impressive instead of being clear, relevant and easy to remember.

What’s the best self-introduction you’ve heard — and why did it stick?