HR, Culture-Fit & Salary: real interview questions

Don't name a number first if you can avoid it; if pressed, give a researched range anchored high, and keep total comp (not just base) in play.

I'd say: 'I'm focusing on fit first — can you share the budgeted range for this role?' Most companies will share it (many are required to). If pressed for a number: 'Based on my research for this role and market, I'm targeting total compensation in the range of X to Y' — where X is at or slightly above the market midpoint you've researched (levels.fyi, posted ranges), because they negotiate down from your anchor, never up. Never give your current salary; the polite deflection is 'I'd rather anchor on the value of this role than my current package.' And note the phrase total compensation — base, bonus, and equity move independently, and the flexibility is usually in equity and sign-on.

Show 20 minutes of genuine research: one specific thing about their product/tech/culture, connected to your own trajectory. Never answerable-by-any-company.

The strong version names something real: 'I've followed your engineering blog's posts on your migration to cell-based architecture — that's exactly the class of reliability problem I want to work on, and it told me the bar here is high. I also use the product [genuine specific], and the roadmap around [specific] maps to experience I already have.' Then connect forward: 'At this stage I'm optimizing for [scale/ownership/domain], and this role is squarely that.' The template is: specific-thing-about-them + why-it-matches-your-goals. If you can swap in another company's name and the answer still works, it's not done yet.

Show direction without rigidity: deepening craft, growing scope, and (honestly) whether IC or management. Tie it to what this role builds toward.

In five years I want to be the person a team trusts with its hardest technical problems — a senior/staff-level IC who's gone deep in [domain] and has mentored a handful of engineers along the way. I'm deliberately on the IC track rather than management for now, though I'd revisit that if leading a team turned out to fit. What matters most is trajectory: this role gives me [scope/scale/domain] I don't have today, and that's the muscle I want to build next. I don't have a five-year script — the best opportunities in my career so far weren't predictable — but that's the direction I'm steering.

Always have 3+. Best ones extract real signal: how success is measured, why the role is open, what the team's hardest problem is. Skip perks questions.

Questions that both impress and genuinely inform: 'What would a great first 90 days look like in this role?' (reveals expectations), 'Why is this position open?' (growth vs backfill vs churn — very different signals), 'What's the team's biggest technical challenge right now?' (shows where you'd actually spend your time), 'How do decisions get made when engineers and product disagree?' (culture in one answer), and for the manager: 'How do you like to give and receive feedback?' Save compensation/perks for the recruiter, not the hiring manager. And listen hard to the answers — a hesitant answer to 'why is this open?' has saved many candidates from bad teams.

Pick feedback that stung and was fair. Show the sequence: listened without defending, verified it, changed something concrete, and thanked the person.

A peer review once said my design docs were thorough but 'exhausting — nobody finishes them.' It stung because thoroughness was my pride. Instead of defending, I asked two colleagues to be blunt: they agreed, kindly. So I changed the format: a one-page summary with the decision and trade-offs up front, details pushed to appendices. Engagement flipped — people actually commented on the decisions instead of skimming past them. I went back and thanked the original reviewer, which turned an awkward moment into a strong working relationship. What I learned: feedback about how your work lands is data, not an attack — and the fastest way to defuse your own defensiveness is to go verify the feedback yourself.

Brief, honest, unapologetic, forward-facing. One sentence on the why, one on anything you kept sharp, then pivot to readiness.

Directly and without over-explaining: 'I took eight months off — [caregiving for a family member / recovering from burnout / relocation / the layoff wave]. During that time I kept my skills warm with [a course, a project, freelance work — if true], and I'm now fully ready to commit to the right role, which is why I'm being selective in this search.' That's it — two or three sentences, no apology, no life story. Interviewers report that gaps themselves rarely sink candidates; evasiveness about them does. If the gap taught you something relevant (perspective, a new skill), one clause on that is a bonus — then redirect to what you'll do for them.