Key Takeaways

  • Puzzles test how you reason out loud, not whether you already know the answer.
  • A small set of recurring types covers most of what is asked — weighing, crossing, switches, probability.
  • Saying nothing while thinking is the most common failure, because the interviewer cannot score silence.
  • Structure beats cleverness: state assumptions, try a small case, then generalise.
  • If you already know a puzzle, say so rather than pretending to derive it.

Puzzles occupy an odd place in campus hiring. They appear in aptitude rounds as logical reasoning questions and in interviews at some companies, and students either dismiss them as unfair or try to memorise hundreds.

Neither works. Interviewers are watching your reasoning process, which means the same puzzle can score well or badly depending entirely on how you approach it out loud.

This guide covers the recurring types and the method.

While you prepare, make sure your resume clears screening — the free ATS score checker.


What is actually being assessed

Can you decompose a problem? Breaking something unfamiliar into parts you can handle.

Do you state assumptions? Most puzzles are deliberately underspecified, and asking what you may assume is part of the test.

Do you think out loud? Silence is the most common failure. An interviewer cannot assess reasoning they cannot hear, and a candidate who sits quietly for two minutes and produces the right answer scores worse than one who reasons aloud and nearly gets there.

Do you handle being stuck? Being stuck is expected. What matters is whether you try a smaller case, a different angle, or ask a clarifying question — rather than freezing.

Do you take hints? They are offered deliberately. Missing one is worse than needing one.


The recurring types

Weighing puzzles

You have nine balls, one heavier. Find it in two weighings with a balance scale.

The pattern: divide into three groups, not two. A balance comparison has three outcomes — left heavier, right heavier, balanced — so three-way division extracts maximum information per weighing.

Generalises to: finding one item among 3ⁿ in n weighings.

River crossing and transport

A farmer with a wolf, a goat and a cabbage must cross a river; the boat holds one item; wolf eats goat, goat eats cabbage.

The pattern: track forbidden states and work out which item must return. The insight is usually that something has to be brought back.

Switch and bulb puzzles

Three switches outside a room, three bulbs inside. One visit. Identify which switch controls which bulb.

The pattern: use a property other than the obvious one — heat as well as light. Turn one on and leave it, turn a second on then off shortly before entering, leave the third off. The warm-but-off bulb identifies the second switch.

Generalises to: when the obvious channel gives insufficient information, look for a second channel.

Measuring with jugs

Measure exactly four litres using a five-litre and a three-litre jug.

The pattern: fill, pour between, empty, repeat. Track states systematically rather than guessing.

Probability and expectation

Two children, one is a boy. Probability both are boys?

The pattern: enumerate the sample space explicitly. These questions are designed so that intuition misleads, and writing out the possibilities is what saves you.

Truth-tellers and liars

The pattern: construct a question whose answer is the same regardless of who you ask — usually by asking what the other would say.

Rate and work

Two people fill a tank at different rates. Frequently overlaps with quantitative aptitude — see the campus placement aptitude test guide.


One puzzle, solved out loud

The method matters more than the answer, so here is what a scoring response actually sounds like. The puzzle is the nine balls.

Candidate: So — nine balls, one is heavier than the other eight, which are all identical. I have a balance scale, and I need to find the heavy one in two weighings. Can I assume the scale only tells me which side is heavier, not the actual weights?

Interviewer: Correct.

Candidate: Right. My first instinct is to split them in half, but nine is odd, and more importantly a balance gives me three outcomes, not two — left heavy, right heavy, or balanced. If I only split into two groups I am throwing away one of those outcomes. So three groups of three feels better.

Let me try a smaller version to check. Three balls, one weighing. I put one on each side. If one side drops, that is the ball. If they balance, it is the one I left out. So three balls take one weighing.

That generalises. Nine balls: weigh three against three. If one side drops, the heavy ball is in that group of three. If they balance, it is in the group I set aside. Either way I am down to three balls after one weighing, and I already showed three balls take one more. Two weighings total.

Checking it against the constraints — two weighings, balance scale only, works regardless of which group it lands in. That holds.

What scored there, in order: restating the problem, asking a clarifying question, rejecting the obvious approach with a reason, trying a smaller case, generalising from it, and checking against the constraints at the end.

What did not happen: two minutes of silence followed by "three groups of three".

The candidate who already knew the answer and said "divide into three groups of three" in four seconds scores worse than this, because none of the reasoning was visible. If you know it, say so and offer to walk through the logic anyway.


The method

1. Restate the problem. Confirms you understood it and buys thinking time.

2. Ask clarifying questions. Can the boat carry two? Are all balls identical in size? Underspecification is usually deliberate.

3. State your assumptions explicitly. "I'm assuming the scale gives exact comparisons, not weights."

4. Try a smaller case. If nine balls is hard, solve three. The structure of the solution usually reveals itself, then generalises.

5. Think out loud throughout. "One approach is splitting into two groups, but that only gives me one bit per weighing — a balance actually has three outcomes, so three groups should be better."

6. Check the answer against the constraints before declaring it.

If you already know the puzzle, say so: "I've seen this one — should I walk through the reasoning, or would you prefer a different problem?" Interviewers respect it, and pretending to derive a memorised answer is transparent and damaging if caught.

What to say when you are stuck

Being stuck is expected. Freezing is what costs you. Have these ready.

Instead of silence Say
(thinking with no sound) "Let me think about a smaller version of this first"
"I don't know" "I can see two approaches — can I talk through why I'm unsure about both?"
(starting over silently) "That direction isn't working because X, so let me try Y"
"Is it 4?" "I think it's 4, and here's the reasoning — can I check it against the constraints?"
(waiting for a hint) "I'm stuck on how to handle the case where they balance. Any nudge?"

Asking for a nudge is allowed and is not a failure. What is scored is whether you had located where you were stuck. "I'm stuck on the balanced case" shows you have understood the structure; "I don't know" shows nothing.


Preparing efficiently

Learn the patterns, not the puzzles. Roughly six or seven underlying structures cover most of what is asked, and recognising the structure is what transfers to an unfamiliar question.

Practise out loud. Solving silently builds a different skill from explaining under observation, and only one is tested — the same principle as campus placement communication skills.

Do not memorise hundreds. Diminishing returns arrive quickly, and interviewers frequently choose obscure ones deliberately.

Ask what your target companies actually ask. Some use puzzles heavily, many not at all — placement cells and seniors usually know, and it tells you how much time this deserves relative to the DSA roadmap.


Common Mistakes

Sitting silently while thinking. The interviewer cannot score reasoning they cannot hear, and this is the most common failure by a wide margin.

Answering instantly because you knew it. A four-second correct answer with no visible reasoning scores worse than a slower one that showed the route.

Jumping to an answer without stating assumptions. Most puzzles are deliberately underspecified, and asking is part of the assessment.

Not trying a smaller case when stuck. Solving three balls before nine usually reveals the structure of the whole solution.

Pretending to derive a puzzle you already know. It is transparent, and saying you have seen it costs you nothing.

Saying "I don't know" instead of naming where you are stuck. "I'm stuck on the balanced case" shows structure; "I don't know" shows nothing.

Ignoring hints. They are offered deliberately, and missing one scores worse than needing one.

Memorising hundreds of puzzles. Returns diminish fast, and interviewers frequently pick obscure ones on purpose.

Freezing when stuck. Being stuck is expected; how you move — smaller case, different angle, clarifying question — is what is scored.

Not checking the answer against the constraints. Declaring a solution that violates a stated rule undoes the reasoning that preceded it.


Frequently Asked Questions

Do all companies ask puzzles?

No. Some use them heavily in interviews and aptitude rounds; many do not ask any. Check with your placement cell and seniors before investing heavily.

What is actually being tested?

Your reasoning process — decomposition, stating assumptions, thinking aloud, and how you handle being stuck. The answer matters less than the route.

Should I memorise puzzles?

Learn the underlying patterns instead. Six or seven structures cover most questions, and pattern recognition transfers to unfamiliar problems in a way memorisation does not.

What if I already know the puzzle?

Say so. Offer to walk through the reasoning or take a different question. Answering instantly from memory actually scores worse, because no reasoning was visible.

What if I get stuck?

Name where you are stuck rather than saying you do not know, try a smaller case, and ask for a nudge if you need one. Interviewers give hints to candidates who are visibly reasoning.

Is it bad to need a hint?

No. Missing one that has been offered is far worse than needing one.

Is it acceptable to ask for a hint directly?

Yes, provided you can say which part you are stuck on. That sentence demonstrates you have understood the structure of the problem.

How much time should I spend on puzzles?

Considerably less than on aptitude and DSA, unless your target companies specifically use them. Check before allocating time.


Preparation matters only if your resume gets you the interview. Check your ATS score free.

Make This Practical

Take the nine-balls transcript above and say it out loud, to another person, at normal speaking pace. That is what a scoring answer sounds like — restate, clarify, reject the obvious approach with a reason, try a smaller case, generalise, check. Solving quietly at a desk trains precisely the wrong habit.

Then prepare the stuck phrases, because that is where most rounds are lost. "Let me try a smaller version", "that direction isn't working because X", and "I'm stuck on the balanced case — any nudge?" all keep you scoring while you think. Silence and "I don't know" score nothing.

Finally, learn the six or seven structures rather than memorising puzzles, and ask your placement cell whether your target companies use them at all — for many, this deserves far less of your time than aptitude and DSA.

Was this guide useful?

Be the first to rate it.