What technical interviewers check in freshers, and how to answer when you know the concept, when you half-know it, and when you do not know it at all.
Last updated
Core concepts of your subject, explained simply and correctly.
What you built, the decisions you made and why.
How you approach an unfamiliar problem. Your process matters more than speed.
Can you explain technical ideas clearly to another person?
Don't narrate it chronologically. Use this order: the problem, what you specifically did, one real technical challenge and how you solved it, the result, and what you'd change. Expect follow-ups: why this technology, how you tested it, what breaks at scale, and what your teammates did.
On a problem-solving question, silence is the worst response. Say what you understand, state your first approach even if it's slow, then improve it. Interviewers routinely prefer a candidate who reasons clearly to a correct but unexplained answer.
Say so, then show what you do know: "I haven't used that directly, but I understand it's used for X, and I'd approach it by…" A confident guess that turns out wrong damages trust more than an honest "I'm not sure."
Explaining a concept in your head and explaining it to a person are different skills. A technical round in our AI mock interview asks you role-specific questions, you answer by voice, and you're scored on depth, structure and clarity. For role-specific practice, see software engineer interview practice.
Usually core fundamentals of your subject, detailed questions about your projects and internship, one or two problem-solving questions, and questions about the technologies on your résumé.
Start with the problem, then what you personally built, one real technical challenge and how you solved it, the outcome, and what you would do differently. Keep the first answer to about a minute and let follow-ups go deeper.
Say honestly that you are not sure, then share what you do know and how you would find the answer. Interviewers value honesty and reasoning over a confident wrong answer.
Answer role-specific technical questions out loud and see exactly where your explanations need work.
Get Started →