Question bank

Interview questions, with guidance on how to answer

834 questions across 64 roles. Open one to see what a strong answer includes and common slips, then drill it out loud with Ava. New to answer structure? Start with the learning hub.

572 questions match your filters.

TechnicalAny levelIT Support Specialist
When you don't know the answer to a user's problem, what do you do?
Tests: Troubleshooting methodology
TechnicalEntry levelSoftware Engineer
When would you pick a hash map over a list to store data, and what does that choice cost you?
Tests: Coding fundamentals & data structures
TechnicalEntry levelSoftware Engineer
Imagine your code works on your laptop but fails in the test environment. Walk me through how you would start figuring out why.
Tests: Debugging & troubleshooting
TechnicalEntry levelSoftware Engineer
How do you usually use Git day to day, from starting a piece of work to getting it merged?
Tests: Version control & delivery
TechnicalMid levelSoftware Engineer
How do you decide what to test in a new feature, and how do you balance unit tests against integration tests?
Tests: Testing & code quality
TechnicalMid levelSoftware Engineer
Tell me about the trickiest bug you have tracked down. How did you find the root cause?
Tests: Debugging & troubleshooting
TechnicalMid levelSoftware Engineer
When you review a teammate's pull request, what do you look for, and how do you give feedback they will actually act on?
Tests: Code review & collaboration
TechnicalMid levelSoftware Engineer
What makes a deployment pipeline trustworthy to you, and how do you roll back safely when something goes wrong?
Tests: Version control & delivery
TechnicalSeniorSoftware Engineer
Tell me about a technical decision where you chose a simpler design over a more flexible one. How did it play out?
Tests: System design
TechnicalSeniorSoftware Engineer
Your codebase has growing technical debt and there's pressure to ship features. How do you make the case for paying some of it down?
Tests: Testing & code quality
TechnicalEntry levelFrontend Engineer
Can you explain what happens when you await a promise in JavaScript, and how you handle errors from it?
Tests: JavaScript & TypeScript
TechnicalEntry levelFrontend Engineer
What are some simple things you do to make sure a form can be used by someone on a screen reader or only a keyboard?
Tests: Accessibility
TechnicalMid levelFrontend Engineer
How do you decide where a piece of state should live in a React or similar app, and when do you reach for a global store?
Tests: Component architecture & state
TechnicalMid levelFrontend Engineer
A product page feels slow to load on mobile. How would you find out why, and what would you try first?
Tests: Web performance
TechnicalMid levelFrontend Engineer
How do you test a component that fetches data and shows loading and error states?
Tests: Frontend testing
TechnicalMid levelFrontend Engineer
How do you use TypeScript types to prevent bugs, and when do you think strict typing gets in the way?
Tests: JavaScript & TypeScript
TechnicalMid levelFrontend Engineer
Tell me about a tricky styling bug, like something breaking in only one browser, and how you solved it.
Tests: CSS & responsive layout
TechnicalSeniorFrontend Engineer
If you were setting up a shared component library used by several product teams, how would you design it to stay consistent but flexible?
Tests: Component architecture & state
TechnicalSeniorFrontend Engineer
How would you choose between server rendering, static generation and client-side rendering for a new product? What trade-offs matter most?
Tests: Web performance
TechnicalSeniorFrontend Engineer
How would you bring accessibility into a team's regular workflow so it isn't just a last-minute audit?
Tests: Accessibility