Are the questions invented by an AI?

No. Every question in the bank is one we have either been asked ourselves in a real interview, seen on Glassdoor's public company pages, or pulled from canonical sources (the STAR behavioral classics, the standard Big Tech coding-interview question set, the well-known product case rubric questions). We do not call an LLM to dream up new questions. The reason is simple — fake questions waste your time. You drill an invented question for an hour, walk into the real interview, and get something different shaped.

What is the answer framework field for?

Most candidates lose interviews because their answers ramble rather than because they lack content. For each question we tag the framework the strongest answers use. STAR (Situation, Task, Action, Result) for behavioral. 5W1H (who, what, when, where, why, how) for product and case. MECE (mutually exclusive, collectively exhaustive) for analytical breakdowns. PREP (Point, Reason, Example, Point) for opinion questions and culture fit. The bullet outline fills the framework in — you can practice it out loud instead of memorizing a script.

What is the difference between bonus and pitfall?

Bonus is what pushes a passing answer into a memorable one: a real metric, a counter-intuitive lesson, naming a tradeoff you owned. Pitfall is the specific trap most candidates fall into on that question — for example, on "tell me about a time you failed" the pitfall is naming a fake-humble failure that is actually a strength ("I work too hard"); on system design questions the pitfall is jumping to a database before clarifying read and write patterns. Read the pitfall first — it tells you what not to do, which usually matters more than what to do.

Do you cover non-engineering roles?

Yes. Product (30+), marketing and ops (30+), culture fit (30+) and the full behavioral set (80+) are role-agnostic. You can filter by category to see only those, or use the role tag on each question to narrow further. Frontend and backend specifically have separate buckets (40+ each) because the canon is large enough to deserve its own section — generalist tech-screen questions live under tech general.

How should I use this the week before an interview?

Filter to the category that matches the round (behavioral / system design / product case). Star the 10-15 questions most likely to come up for the company and level. Practice the starred set out loud, one per day — not by memorizing the bullets verbatim but by hitting the framework, the strongest 3 points, and avoiding the named pitfall. The night before, re-skim only the bonus and pitfall lines for the starred questions. Memorizing word-for-word answers is the second-most-common reason smart candidates bomb interviews.

Is my favorites list synced or uploaded?

No. Favorites live entirely in your browser's localStorage. The bank ships as a static JavaScript array, the search and filter are client-side, and starring a question writes to a single localStorage key. There is no account, no server call, no analytics on which questions you starred. Clear your browser data and the favorites are gone — they live only on your device.

Why no model answers, only outlines?

A word-for-word model answer in someone else's voice is worse than no answer. Interviewers can tell when a candidate is reciting versus thinking. The outline gives you the 3-5 points the strongest answers all hit, in the order that works best for the framework. You supply the specific story, the specific number, the specific name. That is the part that is actually yours.

Stress-test your three STAR stories the weekend before an onsite

You have a Friday onsite and three rehearsed stories. Filter to behavioral, star the 12 questions the recruiter hinted at, and run each story against three different prompts. If "tell me about a conflict" and "a time you disagreed with your manager" both pull the same story, you have a coverage gap. The pitfall line catches the fake-humble failure before the interviewer does.

Prep a system-design round without re-reading a 600-page book

You got a backend loop with one system-design round in three days. Filter to backend and tech general, star the 8 design questions, and read the framework plus pitfall on each. The recurring pitfall here is jumping to a database before clarifying read and write patterns, so you drill the clarifying-questions habit instead of memorizing a URL shortener diagram you will never get asked verbatim.

Switch from IC to a product round you have never done

An engineer moving toward PM gets a product-sense screen and panics. Filter to product, read the 5W1H framework on each of the 30+ questions, and notice the outline forces you to size the market and name a metric before proposing a feature. You practice the structure on "how would you improve Google Maps" until the shape is automatic, not the specific answer.

Skim bonus and pitfall lines the night before, nothing else

It is 11pm, the interview is at 9am, and cramming new content now hurts more than it helps. Open your starred set, hide everything except the bonus and pitfall line on each question, and read for 15 minutes. You are not learning answers, you are loading the two traps and two differentiators per question into short-term memory so they surface under pressure tomorrow.

300+ Real Interview Questions — Behavioral, Tech, Product, Culture

Interview questions bank — 300+ real questions across behavioral / technical / case / culture, with strong answer frameworks.

Runs locally
Category Text
Best for Removing repetitive cleanup work from everyday writing and operations.

460 questions

Tell me about yourself.

Framework

PREP (Point/Reason/Example/Point)

Outline

1.Current role in one sentence (title, company, scope)
2.Two career arcs that connect to this role
3.One signature shipped result with a real number
4.Why you are interviewing now: pull, not push

+ Bonus

End with a hook tied to the company: "which is why this role caught me".

! Pitfall

Reciting your resume in chronological order; the interviewer can read.

Roles:all

Questions are taken from public sources (Glassdoor pages, classic STAR sets, standard coding-interview canon). Bonus and pitfall lines are based on common loop feedback. No AI-fabricated questions.

What this tool does

A hand-curated bank of 300+ real interview questions pulled from public sources we have actually been asked in, or sourced from published Glassdoor compilations, classic STAR question lists, and well-known coding-interview canon. Nothing here is invented by an LLM. The questions cover seven categories job seekers actually run into: behavioral (80+), tech general (60+), frontend (40+), backend (40+), product (30+), marketing/ops (30+), and culture fit (30+). Every question ships with four things you do not get in a regular question list: an explicit answer framework (STAR, 5W1H, MECE, PREP), a 3-5 bullet outline of the strongest points to make, a bonus line that pushes the answer from "passes" to "stands out", and a pitfall line that names the trap most candidates fall into on that specific question. Search ranks by title, framework and outline body. Filter by category. Star the ones you want to drill — favorites live in localStorage on your machine, never uploaded. No login, no AI call, no answers generated on the fly. Use it the week before an interview to stress-test your stories, or the night before to skim the bonus and pitfall lines for the role you are interviewing for.

Tool details

Input: Text; The page exposes text boxes, numeric controls, file pickers, or structured inputs depending on the tool.
Output: Live result + Copy + Preview; The result area focuses on usable output, with copy, download, or preview actions when supported.
Privacy: Browser-side processing; The main tool logic does not call an external API, so inputs normally stay in the current tab.
Save / share: Local preference storage; Preferences, history, or drafts are saved in this browser without an account.
Performance budget: Initial JS <= 35 KB; No WASM budget is declared, keeping the tool quick to open on mobile.
Best fit: Text · Developer; Category and role tags drive related tools, internal links, and quick fit checks.

How to use

1. Input

Paste or drop your content into the tool panel.
2. Process

Click the button. All processing is local in your browser.
3. Copy / Download

Copy the result or download to disk in one click.

How Interview Questions Bank fits into your work

Use it to clean, compare, reshape, or extract plain text before it goes into a document, CMS, spreadsheet, or prompt.

Text jobs

Removing repetitive cleanup work from everyday writing and operations.
Making text easier to compare, paste, publish, or feed into another tool.
Working with content locally when the text is private or unfinished.

Text checks

Scan for unintended whitespace, duplicate lines, and lost punctuation.
For long text, test the first few lines before applying the whole change.
Copy the final output only after checking the preview.

Good next steps

These links move the current task into a more complete workflow.

Real-world use cases

Stress-test your three STAR stories the weekend before an onsite
You have a Friday onsite and three rehearsed stories. Filter to behavioral, star the 12 questions the recruiter hinted at, and run each story against three different prompts. If "tell me about a conflict" and "a time you disagreed with your manager" both pull the same story, you have a coverage gap. The pitfall line catches the fake-humble failure before the interviewer does.
Prep a system-design round without re-reading a 600-page book
You got a backend loop with one system-design round in three days. Filter to backend and tech general, star the 8 design questions, and read the framework plus pitfall on each. The recurring pitfall here is jumping to a database before clarifying read and write patterns, so you drill the clarifying-questions habit instead of memorizing a URL shortener diagram you will never get asked verbatim.
Switch from IC to a product round you have never done
An engineer moving toward PM gets a product-sense screen and panics. Filter to product, read the 5W1H framework on each of the 30+ questions, and notice the outline forces you to size the market and name a metric before proposing a feature. You practice the structure on "how would you improve Google Maps" until the shape is automatic, not the specific answer.
Skim bonus and pitfall lines the night before, nothing else
It is 11pm, the interview is at 9am, and cramming new content now hurts more than it helps. Open your starred set, hide everything except the bonus and pitfall line on each question, and read for 15 minutes. You are not learning answers, you are loading the two traps and two differentiators per question into short-term memory so they surface under pressure tomorrow.

Common pitfalls

Starring 60 questions and drilling none of them deeply. Pick 12-15 for the actual company and level, then practice those out loud one per day instead of skimming all sixty.
Memorizing the bullet outline word-for-word. The outline is the order of the points, not a script — interviewers can hear recitation, so fill each bullet with your own specific story and number.
Reading only the question and skipping the pitfall line. The pitfall names the exact trap for that question (like a fake-humble "I work too hard" failure), and avoiding it usually matters more than the perfect answer.

Privacy

Everything runs in your browser. The 300+ question bank ships as a static JavaScript array, search and category filters are client-side, and starring a question writes to a single localStorage key on your device. There is no login, no server call, no AI request, and no analytics on which questions you star or search. Nothing you type or favorite enters the URL or leaves your machine. Clear your browser data and your favorites are gone.

FAQ

Tool combos

Folks in your role tend to reach for these alongside this tool.

Browse all tools for this role

300+ Real Interview Questions — Behavioral, Tech, Product, Culture

Tell me about yourself.

What this tool does

Tool details

How to use

1. Input

2. Process

3. Copy / Download

How Interview Questions Bank fits into your work

Text jobs

Text checks

Good next steps

Real-world use cases

Stress-test your three STAR stories the weekend before an onsite

Prep a system-design round without re-reading a 600-page book

Switch from IC to a product round you have never done

Skim bonus and pitfall lines the night before, nothing else

Common pitfalls

Privacy

FAQ

Weekly Report Generator

Resume Template Builder

Cover Letter Generator

MBTI Quick Test (28 Questions, 16 Personality Types)

Prompt Template Library

Chinese Name Generator

Invoice Generator

Slogan Generator

A1Z26 Cipher (Letter ⇄ Number)

Chinese Acupoint Locator

Add Line Numbers

Aesthetic Text Generator