Where does each question come from?
From the people who were asked it. Some candidates send us a question by email or as an upload, and we file it by company, format and round. Others write up their whole interview on the public interview experiences board, under their name or anonymously, and we summarize the questions it mentions into the bank. Both go through the same checks.
We also use interview experiences that candidates have published elsewhere in their own words. We summarize the questions they mention, check each one against the rest of the bank for that company and file it the same way. We never scrape these in bulk or copy them word for word.
A model may help edit a report into a clear, self-contained question, and every question edited that way is reviewed. What was asked always comes from the report, never from the model. No company supplies, reviews or endorses the bank. It records what candidates say they were asked.
What does the month on a question mean?
It is the latest month a candidate reported being asked the question, shown wherever a report gave one. A question last reported 18 months ago shows that month, so you can judge how current it is.
The "updated" stamp on a company page and the last-modified dates in the sitemap use a different date: the day the question was added to the bank.
How is a question checked before it is published?
A report is a candidate's memory of a question and is rarely usable as written. Before it goes in the bank, we rewrite it to stand on its own, with the full task, the inputs and their bounds, and worked examples.
- It is filed under a company, a round (online assessment, phone screen, take-home or onsite) and a format, so you can find it by the stage it was asked at.
- It is checked against the questions already filed for that company, and a repeat report updates the existing entry.
- A coding or SQL question gets test cases, and its reference solution is run through the same judge your submissions go to. A question whose own solution fails is not ready to publish.
- Anything that looks copied from a textbook, another site or a company's internal material is dropped. We do not reword it to keep it.
How are answers graded?
Coding and SQL solutions are judged on the server against hidden test cases, so a pass means the code ran and its output was judged correct. SQL runs on a full PostgreSQL engine, so window functions and CTEs behave as they will in the interview.
When a submission fails a case, you see that case: the input, the expected output and what your code produced, so you can reproduce the failure. Cases a submission passes stay hidden, so a working solution cannot be used to collect a question's test cases.
An AI reviewer can also score a finished solution against a rubric for its question type, such as correctness and code quality for a coding question. That score is a second opinion, separate from the pass or fail verdict.
What is refused?
We do not publish any of the following, whatever the source. The content guidelines give the rules in full.
- Anything covered by a non-disclosure agreement or any other confidentiality duty, including material a candidate was shown under one.
- A company's non-public or proprietary interview material, such as take-home briefs, scoring rubrics, internal question banks and application-form language.
- Verbatim or near-verbatim copies of anyone else's question, write-up or explanation.
- Anything that names an individual interviewer or identifies a candidate other than the person posting it.
A report that breaks one of these rules is refused outright. Published material found to break them is removed on notice.
- Content Submission GuidelinesWhat candidates may and may not post.
- DMCA PolicyCopyright complaints and the registered designated agent.
What the bank cannot tell you
The bank is a sample of what was asked. It is not a syllabus of what you will be asked, and because it comes from candidates who chose to report, it is not a random sample of any company's interviews.
A company page describes the questions filed there: how many, in which formats and rounds, and when they were reported. It does not describe the employer's hiring process, and no company reviews or endorses what is published here.
Rates and shares elsewhere on the site name the group they are measured over. When a figure rests on too few reports, it is shown as a count instead of a percentage.
How do I correct or remove something?
Email kevin@trueinterview.io with the URL and what is wrong, or which report of yours you want taken down. We correct the entry itself, so the fix shows on every page that uses it.
Send copyright complaints to the designated agent named in the DMCA policy, at kevin@trueinterview.io or +13022411713. An employer with a confidentiality complaint can write to kevin@trueinterview.io, and we act on it without waiting for a formal notice.