6 Types of Tech Interviewers, and How Each One Actually Grades You

Professional and even-handed. No single rubric dimension is weighted over another, and difficulty stays exactly at baseline.

What they actually grade you on

• A fair, well-rounded read across every round — nothing is over- or under-emphasized.

Curious about product impact and real user outcomes, not just technical correctness. Follows up for depth, not breadth.

What they actually grade you on

• WHY you made a choice, not just what you built — surface-level familiarity doesn't hold up to follow-ups.
• Whether your past work shows genuine ownership and user-impact thinking, not just execution.
• Code quality and edge-case handling over a merely-working happy path.

Conversational and fast-moving. Rewards breadth and pragmatism over deep specialization — the opposite instinct of an enterprise interviewer.

What they actually grade you on

• Comfort improvising with limited context, over narrow deep expertise.
• A working, pragmatic solution shipped fast — with awareness of what you'd harden later, not exhaustive edge cases upfront.
• Wearing-many-hats stories — someone who's only worked in one narrow, well-defined lane reads as a weaker fit here.

Formal and methodical. Values reliability, documentation, and structured reasoning over speed.

What they actually grade you on

• Structured, methodical problem-solving with clearly articulated trade-offs — process awareness is a real signal, not a nice-to-have.
• Maintainability, naming, and following conventions — as much as raw correctness.
• Designs that account for governance, compliance, and cross-team coordination, not just the happy-path architecture.

Supportive and fundamentals-focused. The only archetype with a negative difficulty bias — this interviewer isn't trying to trip you up.

What they actually grade you on

• Clear communication of your reasoning, and breadth across common technologies — over narrow, exotic tool knowledge.
• Correctness and following the given spec precisely — over clever optimization nobody asked for.
• Well-understood, standards-compliant designs over novel architecture.

Direct, with brief pleasantries before rigorous, depth-seeking probing. The only archetype with a positive difficulty bias.

What they actually grade you on

• Pushing past your first correct answer — trade-offs and edge cases at scale are where this interviewer actually listens.
• Near-production-quality code: complexity reasoning and clean structure, not just a passing happy-path solution.
• High-ownership stories with real, specific, quantified impact — vague or team-diffused answers get pushed on directly.