Understanding the Non-Technical Interview · Non-Technical Interview

Strong technical candidates are regularly passed over here — not for lack of ability, but because they could not show how they work.

When you meet your interviewers, you are assessed on more than technical skill. The interviewer is forming a judgement about how you operate: how you make decisions, how you work with others, how you handle ambiguity, and whether you will thrive on the team. Plenty of capable candidates lose offers at this stage simply because they never showed how they work.

The two competency areas

Competency	What it means	What the interviewer listens for
Leadership	Using communication and decision-making to mobilise others toward a goal — whether in a formal role or by helping a team succeed without being the official leader.	Stepping up, influencing others, making decisions under uncertainty, driving an outcome through people.
Googleyness	How you work individually and on a team: helping others, navigating ambiguity, and pushing beyond your comfort zone to grow.	Collaboration, helpfulness, adaptability, comfort with the unknown, humility and a drive to learn.

A note on the word 'Googleyness'

'Googleyness' is Google's own word for its culture-and-collaboration competency. When you interview elsewhere, treat it as the universal 'how you work with others and handle ambiguity' dimension — nearly every company assesses the same thing under a different name: 'culture fit', 'values', or 'teamwork'.

The two question types

Behavioral questions

These look at how you handled a specific challenge in the past to predict your future performance. They begin with 'tell me about a time when...', 'give me an example of...', or 'describe a decision you made.' The interviewer wants concrete examples of what you did and how, and will probe with 'what did you do then?' or 'what was the result?'

Hypothetical (situational) questions

These evaluate how you would approach a challenge you may not have faced yet. They begin with 'Imagine that...' and are designed to reveal your thought process, not a single right answer. They are realistic, role-relevant scenarios — not trick puzzles or brain teasers.

⚠ Watch out

Confusing the two and wasting a behavioral question on a hypothetical answer — saying 'I would...' when the question asked 'tell me about a time you did...'
Treating a hypothetical like a puzzle with one correct solution, instead of a chance to show your reasoning.

Drill the cue words

'Tell me about a time' → tell a real story. 'Imagine that' → walk through a structured plan. Catching the cue word in the first second tells you which mode to switch into.

Takeaways

You are being read, not tested. The interviewer is judging how you operate, not quizzing facts.
Match the mode to the cue. Past-tense story for behavioral; structured reasoning for hypothetical.
The same two competencies sit underneath every question, whatever its phrasing.