Interview questions by role — and the CV claims behind them
Anyone can hand you a list of questions. These pages say what each question is actually probing for — and name the claim on your CV that role's interviewers open on, because that is where most interviews quietly go wrong.
- Account Executive interview questionsWhether you can explain how you actually win deals — and whether the quota attainment on your CV survives being broken down by year, territory and deal source.
- Business Analyst interview questionsWhether you elicit requirements or transcribe them — and whether the process improvements on your CV were implemented or merely recommended.
- Customer Success Manager interview questionsWhether you manage accounts proactively or react to fires — and whether the retention numbers on your CV reflect your book or the whole company's.
- Data Analyst interview questionsWhether you can turn a vague business question into a defined one — and whether the impact on your CV is impact your analysis actually caused.
- Data Scientist interview questionsWhether you can tell a model that works from a model that shipped — and whether the accuracy figures on your CV came from a validation set or from production.
- Financial Analyst interview questionsWhether you understand the business behind the numbers — and whether the models on your CV are ones you built or ones you maintained.
- Marketing Manager interview questionsWhether you can separate what you ran from what the market did — and whether the growth figures on your CV can survive a question about attribution.
- Product Manager interview questionsWhether you make decisions or describe them — and whether the outcomes on your CV are outcomes you caused or outcomes you were nearby for.
- Project Manager interview questionsWhether you can run a project that is going wrong — and whether the budgets and team sizes on your CV are ones you controlled or ones you were adjacent to.
- Registered Nurse interview questionsWhether you escalate appropriately under pressure — and whether the clinical exposure listed on your CV matches the level of independence you actually had.
- Software Engineer interview questionsWhether you can reason about a system you did not design, and whether the work on your CV is work you actually did rather than work your team did.
- UX Designer interview questionsWhether you can defend a design decision against a constraint you didn't choose — and whether the shipped work in your portfolio shipped in the form you're showing.
Why there are ten of these and not five hundred
Producing a page per job title is the easiest thing on the internet, and it is why this particular corner of the web is so bad. A list of questions generated from a job title tells you nothing you could not guess, and five hundred of them on a small site is how a domain teaches a search engine that it is not worth crawling.
So a role gets a page when there is something specific to say about what its interviews are really testing, and the build refuses to emit one that falls below a real word count or carries fewer than five questions with a genuine probe attached. If your role is missing, that is the honest reason. Much of what is here generalises — theinterview prep hub covers the parts that are not role-specific.
The pattern that runs through all of them
Every role page names a different claim, and they fail the same way. The number that cannot be reconstructed. The verb that is one level too strong. The outcome that had four causes. The seniority word that means something more specific to the person reading it than it did to the person who wrote it.
None of those are lies, exactly. They are claims written to sound like the strongest true version, and they survive the CV screen easily — the screen is not where they fail. They fail when a person picks the best-looking line on the page and asks you to walk through it, which is the one thing every interview in every function has in common.