tideline

live · checked 03:02 UTC

Software engineer interview preparation

General preparation, not from any one company

Software interviews usually mix coding, a design conversation and questions about how you work with others. The themes below come up across most companies; the exact rounds vary, so check what each company publishes.

  1. Coding and problem solving

    What they’re checking: Whether you can turn a vague problem into working code, talk through trade-offs, and test what you wrote.

    • Walk through how you would find duplicates in a very large list. What changes if it doesn’t fit in memory?
    • Here is a function with a bug. How would you find it, and how would you stop it coming back?

    How to prepare: Practise out loud: say what you’re assuming, write a simple version first, then improve it and test edge cases.

  2. System design

    What they’re checking: How you break a system into parts, where you expect it to fail, and which trade-offs you accept on purpose.

    • How would you design a service that shortens links and counts clicks?
    • Your API is slow at peak times. Where do you look first, and what would you change?

    How to prepare: Pick two systems you know well and sketch them: data, traffic, failure points and what you’d change at ten times the load.

  3. Code quality and review

    What they’re checking: Whether your code is readable and safe to change, and how you give and take feedback.

    • What do you look for when you review someone else’s pull request?
    • Tell me about a time a review comment changed how you write code.

    How to prepare: Bring one real example of feedback you gave and one you received, and what changed after each.

  4. Debugging under pressure

    What they’re checking: Calm, methodical work when something is broken in production, and what you learn afterwards.

    • Tell me about the hardest production bug you’ve fixed. How did you narrow it down?
    • What do you do in the first fifteen minutes of an outage?

    How to prepare: Prepare one incident story in the STAR shape, with the cause, the fix and the follow-up that stopped a repeat.

  5. Working with others

    What they’re checking: How you handle disagreement, unclear requirements and deadlines with product, design and other engineers.

    • Tell me about a time you disagreed with a technical decision. What happened?
    • How do you decide what to build when the requirements are unclear?

    How to prepare: Choose stories where you changed your mind or someone else’s with evidence, not stories where you simply won.

Answering well

For “tell me about a time” questions, the STAR shape keeps an answer clear: the situation, your task, the action you took, and the result, with what you learned. Use your own stories; there is no right script to memorise.

Companies differ: check what each one publishes about its own interviews before you prepare for it.