"Your HR round went well. Next is the technical round." For many candidates, that sentence brings more anxiety than any other. What will they ask? Will I have to write code in front of them? What if I go blank?
The technical round is not a memory test or a trap. It is the interviewer checking one thing: can you actually do the work this role needs? Once you understand how the round is structured and what interviewers look for, it becomes much easier to prepare for. This guide covers everything: formats, role-wise questions, a preparation plan and the habits that impress interviewers.
What is a technical round?
The technical round (also called the technical interview or "tech round") is the part of the hiring process where someone who does the job, usually a senior developer, team lead, architect or technical manager, checks your technical ability. It usually comes after an online test or HR screening, and before the managerial or HR round. Some companies hold two technical rounds; some combine technical and HR into one. See how to prepare for a combined technical + HR round.
What the interviewer is really checking
- Fundamentals: do you understand the basics behind the tools you use?
- Problem solving: how you approach something you have not seen before.
- Hands-on ability: can you write, test or troubleshoot, not just define?
- Depth of your own work: your project, your role, your decisions.
- Communication: can you explain your thinking clearly to a teammate?
- Honesty: do you say "I don’t know, but here is how I would find out" instead of bluffing?
Common formats of the technical round
| Format | What happens | How to handle it |
|---|---|---|
| Concept questions | Definitions and differences (OOP, SQL joins, testing types, networking basics) | Answer in one line, then give an example from your work or project |
| Live coding | Write code in a shared editor or on paper while the interviewer watches | Clarify the problem, explain your approach, start simple, test with examples |
| Project discussion | Deep questions on what you built | Use a clear structure. See how to explain your project |
| Scenario / troubleshooting | "The website is slow. What will you check?" or "A user cannot log in…" | Work step by step from the most likely cause, and say why |
| Take-home assignment | A small task to complete in a day or two | Write clean code with a README; be ready to discuss every line |
| System design (experienced) | Design a feature or system at a high level | Clarify requirements, sketch components, discuss trade-offs |
Typical questions by role
Software developer
- OOP concepts with examples; differences such as abstract class vs interface.
- Language-specific questions (Java collections, Python data types, JavaScript closures).
- SQL queries: joins, GROUP BY, second highest value.
- One or two coding problems: strings, arrays, hash maps.
- Your project: architecture, database design, a bug you fixed.
Detailed lists: Java interview questions · Python interview questions · SQL interview questions.
Software tester
- Testing types, bug life cycle, severity vs priority.
- "Write test cases for a login page" or "Test this pen".
- SQL and API testing basics; automation if on your resume.
See software testing interview questions.
IT support / service desk
- "A user’s laptop cannot connect to Wi-Fi. Walk me through your steps."
- IP address, DNS, DHCP, ping, ipconfig; Active Directory and password resets; ticket priorities and SLAs.
See IT support interview questions for freshers and L1, L2, L3 support explained.
Data / MIS analyst
- SQL queries, Excel functions (lookups, pivots), a dashboard you built.
- "Sales dropped 15% last month. How would you investigate?"
How to answer when you are coding live
- Repeat the problem in your own words and ask about edge cases (empty input, negative numbers, duplicates).
- Explain a simple approach first, even if it is not the fastest.
- Write clean, readable code with sensible names.
- Test it aloud with a small example and one edge case.
- Then improve it if time allows, and mention the time complexity.
A 7-day preparation plan
| Day | Focus |
|---|---|
| 1 | Read the job description; list every skill mentioned; mark weak areas |
| 2 | Core concepts of your main language or tool, with one example each |
| 3 | SQL practice: 15 queries including joins and GROUP BY |
| 4 | Coding or scenario practice: 5 problems, solved aloud |
| 5 | Your project: architecture, your modules, challenges, improvements |
| 6 | Mock interview with a friend or record yourself |
| 7 | Light revision; prepare questions to ask the interviewer; rest |
What to do when you don’t know an answer
Say so honestly, then show how you would think about it: "I haven’t used that directly. From what I understand, it is used for…, and if I had to find out, I would check the official documentation and try a small example." Interviewers respect this far more than a confident wrong answer. Never claim experience with a tool you have not used.
Mistakes that fail technical rounds
- Listing technologies on the resume that you cannot explain.
- Memorised definitions with no examples.
- Jumping into code without understanding the problem.
- Going silent for long periods.
- Arguing with the interviewer instead of discussing.
- For online interviews: poor internet, noise or reading from notes.
Questions to ask at the end
- "What would my first three months in this role look like?"
- "What technologies does the team use day to day?"
- "How are code reviews or testing handled in the team?"
Frequently Asked Questions
What is a technical round in an interview?
It is the interview round where a senior engineer, lead or technical manager tests your role-specific skills: concepts, problem solving, your projects and sometimes live coding or troubleshooting.
What questions are asked in a technical round for freshers?
Fundamentals of your main language or tool, SQL queries, one or two easy to medium coding problems, and detailed questions about your academic or personal projects.
How long is a technical interview?
Usually 30 to 60 minutes. Some companies hold two technical rounds, and experienced roles may include a separate system design round.
Is coding compulsory in a technical round?
For developer roles, usually yes. For testing, support and analyst roles, you may get scenario, SQL or test-case questions instead of full coding.
What should I do if I don’t know the answer?
Say so honestly and explain how you would approach or find the answer. Interviewers value honest reasoning over bluffing.
Which comes first, the technical or HR round?
In most IT companies the technical round comes before the final HR round, often after an online test or initial screening.