What will they ask me?

How to use the generator

Pick a company and a round. You get ten commonly reported questions for that pair, in a stable order, with a short approach under each prompt. The approaches are practice notes: how to open, what to make explicit, and what a careful interviewer listens for. They are a map for your own answer, and you should still be able to say the answer with the notes closed.

1. Choose the company you are interviewing with. The list follows the menu, including when you arrived on a company page and then switched.
2. Choose the round: behavioral, coding, system design, role, or culture. Coding includes the data-structure themes people practice for that company. Role is the judgment round for the job, not a second behavioral story with a new title pasted on.
3. Read a prompt, then say an answer out loud before you lean on the approach. The approach is there to check what you skipped.
4. Open the question title when you want the same prompt on the hub page, with the rest of that company's set.
5. Shuffle when you notice you remember position one better than the question. Copy when you want the ten prompts, the approaches, and the hub links in a notes doc. Share when you want a link that reopens the same company and round.

The catalog is already in the page. Switching rounds does not call a model, and it does not send the prompt anywhere. You do not need an account. The hub holds fifty prompts per company. This page holds a drill of ten so you can finish.

What commonly reported means

Commonly reported means the prompt is a representative practice question in the shape candidates describe in public. The theme, the product context, and the company's published values are the inputs. Luna wrote the wording so you can rehearse. It is a drill, and a real interview on a real day can phrase the neighbor of it. If your story or your design only works for this exact sentence, it is too brittle. Practice until a rephrasing still has an answer.

Not affiliated with the companies in the catalog. Those companies did not write this tool and did not review it. Luna publishes the pages so you can practice from public themes.

How to prepare for a behavioral round

A behavioral round goes flat when the story is a job description with a moral at the end. Pick one scene you were actually in. Give the situation in a single sentence. Spend the time on what you did, including the moment someone disagreed. End with a result you can point at: a number, a ship date, a cut you made, or a tradeoff you accepted. If you did not measure it, say what you observed. Inventing a metric in the hallway is easy to hear.

Read one public value the company talks about before you choose the story. If the story does not need that idea, choose a different story. Stapling the slogan on at the end is a tell. At some companies the value is a named leadership principle. At others it is a shorter line about users, craft, or speed. The behavioral ten in this generator put a value and a product in the prompt so you have a constraint, not a plot.

Say the story out loud once with a timer near two minutes, then say it again and cut the preamble. The second telling is the one you want in the room. Write down the sentence where you pushed back. People skip that sentence when they are nervous, and it is the sentence that makes the rest believable. If you want a template for the middle of the story, the note on keeping the action long is the one to read.

How to prepare for a coding round

Start by restating the input and the output in your own words. Offer a correct approach that might be slow, and say its time and space, before you reach for a smarter structure. A listener can follow an honest cost. A clever idea with no baseline is harder to trust, including when the clever idea is right.

Dry-run three cases before you say you are done: empty, a single element, and the boundary you are worried about. Talk while you do it. If you change approaches, say what the first one failed to handle. A clean correction is a better signal than a silent rewrite.

Treat the ten coding prompts as themes. They are phrased with data from that company's products — queries, trips, messages, listings — so you practice naming a structure in a domain the interviewer might use. You are not collecting them as puzzles to memorize line by line. When you finish one, close the page and explain the approach to an empty room. If you cannot explain it without looking, you do not have it yet. The first two minutes of a blank pad have a short checklist: restate, baseline, then the first line. Saying the plan out loud is the other half.

How to prepare for system design

Narrate the user and the API before you draw a box. Say which request has to be fast and which one can wait. Then name one failure you are willing to leave for a later version, and say that you are leaving it. A design that tries to cover every failure in the first five minutes sounds rehearsed and still misses the bottleneck that matters.

Put rough numbers down with units, and label every assumption. An estimate you can correct is more useful than silence. Split the hot path from reporting. Name the cache, say what it does not cover, and say how the product tells the truth when the data is stale. Authorization belongs in the same pass as the data model: who reads, who writes, who audits.

The design prompts use public products as the theme. You are not expected to know internal architecture. You are expected to make a proposal, notice the tradeoff, and stop. Practice stopping out loud. Narrating before you draw is the longer talk track if you want it.

How to prepare for a role round

Role questions ask for judgment in the job. Answer as a person who owned an outcome. Name the metric you checked after a change shipped, the request you made wait, and the work you refused to take over from another team. Stories where you quietly did everyone else's job tend to fall apart when someone asks what the other team did next.

Scope is the usual underlying question. What did you decide, who did you have to convince, and what did you cut? If the prompt names a role, use an example from that kind of work. If you are switching into it, say what transfers and what you would not pretend to know in the first month. A hiring-manager conversation is often this round with a sharper eye on taste and on the people who depended on the call. The hiring manager note is a useful companion, and the prompts themselves stay on this page.

How to prepare for a culture round

Culture questions go flat when they become a recitation of the careers page. Take one public value and turn it into a decision that cost you something: time, a feature, a comfortable agreement. Name the tension with speed directly. A definition with no cost sounds memorized, even when the definition is accurate.

Pick the value you actually find hard. One scene is enough. Practice the sentence you would say in the room when you disagree, and then the part where the working relationship stayed intact. If you would not tolerate a behavior because it breaks that value, say the calm sentence and the next step. Skip the speech about culture in the abstract. The full company set, including culture, lives on the interview questions hub when you want more than ten.

A ninety-minute practice loop

Give the evening ninety minutes, then close the tab. Twenty minutes on two behavioral stories, out loud. Twenty minutes on one coding theme: a baseline, a tighter pass, three dry runs. Twenty minutes on one design: the API, one bottleneck, one thing you will not build. Ten minutes on a role or culture prompt. Use the remaining time to practice the same list with Luna, in the Chrome extension or the Windows or Mac app, so you hear a question and answer in a full sentence instead of rereading the approach.

Then stop. A longer list the night before usually blurs the answers together. The point of the generator is to choose ten and finish them. If the interview is tomorrow, the ten you can say beat the fifty you saved.