A technical interview tests whether you can do the technical work of the role. Depending on the job, that can mean writing code, debugging a broken service, designing a system, reading a query plan or walking through past architecture decisions. The interviewer is usually a practitioner from the team you would join.
What Technical Interview means in practice
Technical interviews range from a thirty minute technical phone screen to a full day of consecutive sessions. A typical software loop includes one or two coding rounds, a system design round for mid level candidates and above, and a round on your past projects. Other functions have equivalents: SQL and case exercises for analysts, a portfolio critique for designers, a configuration or troubleshooting exercise for infrastructure roles. Interviewers usually score against a level based rubric covering correctness, communication and how you handle hints. Many teams care more about the reasoning you narrate than the finished artifact, because the finished artifact is easy to get from anywhere.
Why it matters for candidates
This is where most rejections happen, and where preparation converts most directly into offers. The bar is calibrated per level, so the same performance can pass for one title and fail for another. Silence is the common self inflicted wound: an interviewer cannot score thinking they cannot hear. Narrating your approach, checking assumptions and recovering gracefully from a wrong turn are all part of what is being measured.
How to prepare
- Confirm the format, language and tooling with the recruiter before the session.
- Practice out loud, narrating your reasoning as you work.
- Rebuild the fundamentals your daily job lets you skip.
- Prepare two projects you can explain end to end, including what you would change.
- Rehearse in the exact environment: shared editor, video call, or a physical whiteboard.
Example
A backend candidate gets a forty-five minute session: ten minutes on their last project, twenty-five minutes implementing a rate limiter with tests, and ten minutes of follow-up on how it would behave across multiple instances. The interviewer is scoring whether the candidate asks about the requests per second target before coding, handles the clock skew question honestly, and can describe the trade-off between a fixed window and a sliding one.
Know the format. Now know the questions. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questionsRelated terms
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it works