Why do interviewers penalize candidate questions that a two-minute search of public pages already answers?

## What "search-answerable" actually means A candidate question is search-answerable when the answer sits on a page anyone can open in roughly two minutes: the job description you were sent, the careers page, the product or pricing pages, the company's own engineering blog, a public docs site or status page. On an infrastructure team round, questions like *"What does the platform team build?"*, *"Which regions do you run in?"* and *"How big is the engineering organization?"* are all in that class. The test is not "is this fact obscure to me" but "is this fact published". A candidate who has never worked on infrastructure may genuinely not know what an internal deployment platform is — but if the company describes theirs publicly, asking what it is is still a preparation failure, not a curiosity signal. ## Why the panel weights it so heavily Three things happen at once when a search-answerable question lands. 1. **Preparation signal.** The panel infers how much of your evening this application got. Interest that does not survive two minutes of reading does not read as interest. 2. **Filtering signal.** Interviewers are also judging whether you can separate a good question from a weak one — the same judgment they will rely on when you triage an incident or review a design. A candidate who asks the weakest question on their own list has shown their filter. 3. **Opportunity cost.** A peer engineer on an infrastructure team knows things nobody publishes: what the last migration actually cost the on-call rotation while it was in flight, which parts of the platform people quietly route around, how a change to the deployment path gets agreed. You get one short window with that person. Spending it on a published fact is the expensive part. ## The discard pile Treat the cut list as a real working artefact rather than a mental note. A workable ratio: prepare six questions, discard four because a two-minute search answers them, and walk in with the two that survive plus one spare in case a survivor gets answered during the round. A prepared list for an infrastructure round, with the cuts marked: | Prepared question | Verdict | |---|---| | What does the platform team build? | discard — the careers page says | | Which regions does the platform run in? | discard — published | | Is there one shared deployment path for all services? | discard — the engineering blog describes it | | How many engineers are on this team? | discard — the posting says | | When a service owner needs a change to the deployment path, does your team do that work or do they? | survives | | What did the last big migration cost the on-call rotation while it was in flight? | survives | Keeping the pile matters because the cut question usually contains a strong question inside it. ## Converting instead of deleting The conversion is mechanical: cite the public fact in half a sentence, then ask for the part that cannot be published — the tradeoff behind it, the cost of living with it, or what it changed for the people who maintain it. - Discarded: *"Do you have one shared deployment path?"* - Converted: *"The public write-up describes one shared deployment path for every service. What does a team do when their service does not fit that path?"* The converted version proves you read the material and asks for something only someone inside can answer. That is the whole trick, and it works on almost every cut question. ## The line that ends a round badly The extreme version is the one interviewers repeat to each other afterwards: *"So... what does your company actually do?"* — the question that ends a round badly. It is rarely asked out of contempt; it is usually a candidate who applied broadly, ran out of prepared material and reached for something safe. It is not recoverable inside the round, which is why the prevention work happens the night before. ## When a fact question is legitimate Three honest exceptions: - **The fact is not actually published.** Internal team boundaries, who owns which service, how work reaches the team — these are usually invisible from outside, and asking is correct. - **You cite the source and ask for the update.** "The posting describes this role as split between platform work and support rotations — is that still the shape of it?" That is verification, not ignorance. - **The fact is material to your decision and this interviewer owns it.** Confirming something you will decide on is worth a plain question, as long as you address it to someone who can answer. ## If you realize mid-question Do not abandon the sentence — a stalled question is worse than a weak one. Land it, then add the insider half immediately: "...and more usefully, what does that look like on a bad week?" The recovery costs you a few seconds and turns a flat question into a real one.