Interview questions, by role and by company
Interview questions grouped by role, by company and by question type, each with what the interviewer is checking and how to structure a strong answer. Use them to rehearse out loud, not to memorize scripts.
By Evin JohnPublished 3 min read
Questions by role
- Software engineer: coding, system design and behavioral rounds, with an approach for each question.
- Product manager: product sense, execution, metrics and stakeholder questions.
- Data scientist: statistics, experimentation, SQL and modelling questions.
- AI engineer: LLMs, retrieval-augmented generation, evaluation and MLOps.
Questions by company
- Google software engineer: algorithm depth and the hiring committee process.
- Meta software engineer: speed in coding rounds and product-minded design.
- Amazon SDE: the Leadership Principles behind every behavioral question.
- Microsoft software engineer: problem solving, design and collaboration.
Guides to the questions everyone gets
- Behavioral questionsWhat each question tests, STAR, and a reusable story bank.
- Tell me about yourselfA 60 to 90 second structure, with three example answers.
- Is AI in interviews cheating?When AI is allowed in interviews, how to ask, and the risks.
- Interview Coder alternativesFour options compared on price model, platforms, own keys and scope.
System design has its own library: the method, the core concepts and full walk-throughs are in system design interview guides.
How to use a question list well
- Find what is assessedBefore answering, write one line on what the question tests: ownership, depth in a technology, judgement under ambiguity. Your answer should prove exactly that.
- Draft from your own experiencePull real projects from your resume and match them to the job description. A specific story with numbers beats a polished generic one.
- Say it out loud, timedMost spoken answers should land in one to two minutes. Time yourself; long answers usually hide a missing point.
- Review and cutListen back or read a transcript of your practice. Cut the setup, keep the decision you made and the result.
Natively can sit in on that practice. In a mock interview it transcribes both sides as you talk and can draft answer suggestions; with Pro (or during the free trial) those suggestions can draw on the resume and job description you add; afterwards you have the transcript and notes to review. See how the interview assistant works.
Questions people ask
How many interview questions should I prepare?
Prepare stories rather than answers. Six to eight well-chosen stories from your own work, each with a clear decision and a measurable result, can be adapted to most behavioral questions. For technical rounds, practice the patterns behind questions rather than individual questions.
Should I memorize my answers?
Memorize the structure and the key facts (numbers, names, outcomes), not the wording. Word-for-word answers sound rehearsed and break as soon as the interviewer asks a follow-up you did not expect.
What is the best way to practice interview questions alone?
Answer aloud with a timer, record yourself or keep a transcript, then review it. Look for answers that ran past two minutes, stories without a result and technical answers that skipped trade-offs.
Where to go next
Practice with the same assistant you would use on a call: it listens, transcribes and suggests answers from your own resume and the job description.
Facts on this page were last checked on . Product details come from the Natively app itself; if something here is out of date, tell us at hello@heynatively.com.
