Bought Pro? It is on your account. Sign in
AnswerDrill Start practising

Practice for

Software engineer interview practice, out loud

Short answer

Engineering interviews test how you explain, not only what you know. AnswerDrill asks the software engineering questions below at entry, mid or senior level and scores how clearly you structure the explanation. It does not run code: use it for the talking parts, alongside coding practice.

What interviewers look for

Every software engineer question in the bank, with how to prepare

These are the technical questions AnswerDrill asks for this role, with the levels each one is asked at. A technical session picks up to four of them for your level and adds general questions that name your role.

  1. Explain the difference between a process and a thread, and when you would use each. All levels

    Cover memory isolation versus shared memory, the cost of creating and switching each, and one example of each choice, such as separate processes for isolation and threads for parallel work on shared data.

  2. Walk me through what happens when you type a web address into a browser and press Enter. All levels

    Go in order: DNS lookup, TCP and TLS connection, the HTTP request, the server response, then parsing and rendering. Pick one step to go deeper on, such as caching or the TLS handshake.

  3. How do you approach debugging a bug that only happens in production? All levels

    Start with logs, metrics and the exact conditions; reproduce safely; narrow down with recent changes. Mention protecting users first (rollback or feature flag) and adding a test once fixed.

  4. What makes code easy to maintain? Give an example from your own work. All levels

    Name two or three principles (clear names, small functions, tests, consistent structure) and back them with a real refactor you did and what it made easier.

  5. How do you decide what to test, and at which level: unit, integration or end to end? All levels

    Explain the trade-off: many fast unit tests for logic, fewer integration tests for boundaries, a few end-to-end tests for critical journeys. Mention testing by risk.

  6. Explain Big O notation and give an example of improving an algorithm. Entry

    Define it as how cost grows with input size, then give one concrete change, such as replacing a nested loop with a hash map lookup, and state the before and after complexity.

  7. How would you design a URL shortener? Talk me through the main parts. Mid and senior

    Clarify scale first, then cover key generation, storage, the redirect path, caching for hot links and analytics. Name one trade-off, such as random keys versus counters.

  8. Explain how you would choose between a SQL and a NoSQL database for a new feature. Mid and senior

    Base the choice on the data and access patterns: relationships and transactions favour SQL; flexible documents or very high write throughput may favour NoSQL. Mention what the team already runs.

  9. Describe a time you improved the performance of something you built. How did you measure it? Mid and senior

    Give the metric before and after and the tool you used to measure it. Explain how you found the bottleneck rather than guessing.

  10. How would you review a pull request from a teammate? What do you look for? Mid and senior

    Correctness and tests first, then readability and design, then style. Mention giving specific, kind comments and separating blocking issues from suggestions.

  11. How would you design a system to handle ten times today's traffic? Senior

    Find the current bottleneck with data, then discuss horizontal scaling, caching, queues for slow work and database limits. Mention load testing before the traffic arrives.

  12. How do you make technical decisions in a team when engineers disagree? Senior

    Describe a process: write down the options and trade-offs, agree on the criteria, try a small spike if needed, decide, and record the decision. Give a real example.

Behavioural questions for this role

Expect stories about technical disagreements, production incidents, code review and deadlines. Prepare them with numbers (latency you cut, errors you removed) and the STAR shape. See the STAR method and common behavioural questions.

How to practise this role in AnswerDrill

  1. Open the practice app, choose the role, your level and "Technical".
  2. Answer each question out loud, up to two minutes by default, or type it.
  3. Read the scores, your filler words, your pace and the stronger answer, then answer your weakest question again.

AnswerDrill does not run or check code, and its AI can be wrong about technical details. Treat its feedback as a second opinion on clarity and structure, and verify technical points yourself.

Practise it out loud. Answer five questions for your role and get scores, tips and your filler words. 2 free AI sessions a week, no sign-up; your history stays on your device.

Start a practice interviewHow it works

Questions

Does AnswerDrill run coding challenges?

No. It is for the spoken parts of the interview: explaining designs, debugging approaches and behavioural stories.

Are there senior-level questions?

Yes. At senior level the bank adds questions about scaling systems and making technical decisions in a team.