The technical round is where an interviewer checks that you can do the work, or learn it. It could be about programming, accounting, electrical wiring, customer support tools, design, laboratory methods or machine operation. The subject changes. The pattern stays the same: they test your basics, your projects and the way you think. Freshers are not expected to know everything. They are expected to know the basics well and to be honest and curious.
What interviewers look for in a fresher
- Strong basics. Not tricks. The core ideas from your degree or training, explained clearly.
- Your own work. Evidence that you have used what you learned: projects, practicals, a workshop, a lab.
- Clear thinking. How you approach a problem, even if you do not reach the answer.
- Honesty. Saying “I don't know” and then reasoning, instead of guessing wildly.
- Willingness to learn. Interest in the field outside class, such as reading, tools you tried, small experiments.
Prepare the basics properly
Go back to the main topics of your subject and the job advert. For each topic, you should be able to explain it simply, give an example, and say where it is used. Explaining to a friend or a younger student is a strong test. If you cannot explain a topic simply, you have not fully learned it yet.
Use a short list. Choose 15 to 25 core topics for the role. For a software role they could be variables and loops, functions, object-oriented ideas, a database basic, how the web works and one language in depth. For an accounts role: the accounting equation, debit and credit, journal and ledger, bank reconciliation and common spreadsheet functions. For an electrical or mechanical trade role: safety rules, tools, reading drawings, basic measurements and common faults. Revise one topic a day and say it aloud.
Explain your projects
Your resume projects are the most likely start of a technical conversation. Prepare them as in lesson 3, and also prepare the technical side: the tools you used and why, the design in simple terms, the part you found hardest, what you would improve, and how you tested that it worked. If you used a framework or tutorial, say so honestly, and be clear about what you built yourself.
Think aloud
When you get a problem, say what you are thinking. Silence is hard for an interviewer to judge. This is especially true for coding or calculation questions. A good pattern:
- Repeat the problem in your own words to be sure you understand. Ask a clarifying question if needed.
- Give a simple example to show you understand: “If the input is 3 and 5, the answer should be ...”.
- Start with an obvious approach, even if it is not the best, and say it.
- Work through it step by step while talking. If you hit a wall, say so and try a different angle.
- Check your answer with your example, and think of edge cases, such as an empty list or zero.
- Say how you could improve it if you have time.
Interviewers like candidates who stay calm, ask good questions and correct their own mistakes. That matters more than a flawless answer.
Coding and technical exercises
For programming roles, you may get a coding exercise on paper, on a whiteboard, in a browser or as a take-home task. Practise on small problems regularly in the language you list. Free practice sites exist for this. Start with simple loops and strings, then lists and dictionaries, then basic searching and sorting ideas. Type the code yourself rather than reading solutions. After you solve a problem, ask what edge cases you missed.
For take-home tasks, read the instructions carefully, keep the solution clear and simple, add a short README on how to run it, and submit before the deadline. Do not copy another person's solution. Interviewers often ask you to explain every line.
When you do not know the answer
It will happen. Here is a calm way to handle it.
- Say honestly: “I'm not sure about that.”
- Share what you do know that is related: “I know how X works, so I think Y may be similar.”
- Reason aloud to a sensible guess, and mark it as a guess.
- If you are stuck, ask for a hint. It is a normal thing to do, and how you use the hint is informative.
- Afterwards, look up the answer and add it to your notes. The same question may come back.
Never invent a confident wrong answer. A wrong answer said confidently is worse than an honest “I don't know, but here's how I would find out”.
Practical and trade interviews
For hands-on roles you may be asked about a job you did: “Tell me how you would fix a motor that won't start” or “What do you check before using this machine?”. Answer in order, in plain words, starting with safety. If you have worked on real equipment, describe it. If not, describe how you learned and what you practised.
Ask a good question at the end
A thoughtful technical question shows interest: “What tools does the team use day to day?” or “What would I learn in the first month?”. It is a chance to show you think about the work.
Your task
- List 15 to 25 core topics for the role you want. Mark each one as strong, medium or weak.
- Pick three weak ones and spend a week turning them to strong. Explain each aloud to someone.
- Write the technical summary for each of your projects: tools, design, hardest part, testing, improvement.
- Practise one problem aloud, using the six-step thinking-aloud method.
How to check it worked
- You can explain every item on your topic list in simple words.
- You have a technical summary of each project that you can say in two minutes.
- You have a calm plan for a question you cannot answer.