Accuracy you can audit
633 questions and 167 concepts, and the thing we are most careful about is whether each one is right. Interview preparation that teaches you something false is worse than no preparation, because you will say it out loud with confidence to someone who knows better.
So rather than claim we are never wrong, here is what we actually do, and what we will pay you if you catch us.
Report a mistake in any question, answer, code sample, SQL query or concept. If we verify it, we fix it and add one day of full access to your account, site wide. One day per verified error, checked by a person, however many you send.
If we think the content is right, we will tell you why rather than going quiet. That is the part of this we would want if we were you.
Report an inaccuracy →What we do before anything ships
Code is run, not read
Every Python snippet and SQL query in an answer is executed against the edge cases the answer claims to handle, before it ships. If an answer asserts that a naive version fails on some input, we produce that input and watch it fail. An example that cannot be run is an example we do not publish.
Arithmetic is recomputed
Worked numbers are recalculated independently rather than carried over from a draft. When a figure depends on an assumption, such as errors being independent, the answer says so next to the number instead of leaving the reader to guess which model produced it.
Machines check what machines can
The deploy refuses to continue unless the typecheck, the full test suite, every content linter and the AI-writing gate pass, and it runs them before it touches the database rather than after. It parses all 500-plus mermaid diagrams with the real renderer and validates company and interview data against a schema. After the release is live, a separate pass fetches every page and link in the sitemap, more than 1,600 URLs. That list used to be shorter than this paragraph claimed: an outside audit read this page in September 2026, checked the deploy script, and found the suite was not actually enforced. Rather than soften the sentence we moved the gate into the pipeline, which is the only version of this worth writing down.
The whole corpus gets re-read
In June 2026 the whole bank as it stood then, 687 questions and concepts, was fact-checked end to end twice without sampling, and 19 errors were corrected. The bank has grown since, so that is a dated pass over a smaller corpus rather than a standing claim about every page today. Newer material is covered by the checks above, by targeted audits, and by re-reads when we have reason to think something drifted. We would rather tell you the date than imply a coverage we cannot evidence.
We invite outside review
We commission independent audits of our own content and act on them. Three in September 2026 returned 97 findings. Some were wrong, and we said which and why. Three we declined on the record with reasons. Most we fixed, several in answers we had corrected days earlier, and a handful remain open and tracked rather than quietly closed. The third audit reviewed the work done in response to the second, and found real defects in it, including two factual errors on company pages written that same day and three overstatements on this page. Those are fixed and this paragraph is one of them.
Corrections are dated, not quiet
A fix lands as a commit that says what was wrong and how we verified the repair, and the page's updated date moves. We do not edit an error out and pretend the page was always right.
What earns the free day
- Code that does not do what the answer says it does
- SQL that returns the wrong rows, or silently returns none
- Arithmetic that does not recompute
- A factual claim about a company, tool or standard that is wrong or out of date
- An answer that contradicts itself, or contradicts another page
- A different valid approach to the same problem
- A design decision you would have made differently
- Style, tone or the depth we chose for a topic
- A claim you disagree with that we can still support
The second column is not a way out. If you think a design call is actually wrong rather than merely different, say why and we will treat it as a claim like any other. Several of our own corrections started that way.
Report an inaccuracy
Sign in first if you want the day credited to an account. You can report signed out, and we will still fix it.
Have a question from a real loop rather than a correction? Submit a question instead. That earns a day too, if we publish it.