Mock Interview for Software Engineers: Adaptive Technical Rounds with a Code Editor and a Report

A software engineer interview is not a quiz. It is thirty to sixty minutes in which someone who writes code for a living watches you think: how you explain your project, whether you can write a working function while talking, whether you know why your query returns what it returns, and what you do when they say "can you do better?" Reading a hundred questions does not prepare you for that. Answering ten of them out loud, with a follow-up after each, does.

This page covers what technical interviewers actually ask software engineers at the fresher to three-year level in India, how a MockMate Practice session runs for this role, what the report tells you afterwards, and a seven-day plan that ends with a real round.

Who this is for

• Final-year students and recent graduates facing the technical round (TR round) at TCS, Infosys, Wipro, Cognizant, Accenture, Capgemini or HCLTech, after clearing the online test.
• Engineers with one to three years of experience interviewing for SDE-1 or SDE-2 roles at product companies and startups, where the round includes a coding problem and a design discussion.
• Anyone switching into software from testing, support or a non-CS degree who has learned to code but has never been interviewed on it.

If your next round is HR or managerial rather than technical, the HR mock interview page is the better fit.

What the interviewer actually asks

Ten questions that appear in almost every software engineer technical round, with what a strong answer contains.

1. "Walk me through your most significant project." Strong answer: the problem, your specific part, one technology choice with a reason, one thing that broke and how you fixed it, all in under two minutes.
2. "What is the difference between a process and a thread?" Strong answer: separate memory versus shared memory, cost of context switching, and one situation where you would use each.
3. "Reverse a linked list" or "find the first non-repeating character in a string." Strong answer: state the approach before typing, write clean code, then test it aloud with an empty input and a one-element input.
4. "What is the time complexity, and can you do better?" Strong answer: name the Big-O, point at the loop that causes it, and propose the hash map or two-pointer version.
5. "Explain OOP concepts using your own project." Strong answer: encapsulation, inheritance and polymorphism tied to actual classes you wrote, not the textbook Animal-Dog example.
6. "Write a SQL query for the second-highest salary" or "employees with no manager." Strong answer: a correct subquery or window function, a sentence on what happens with ties and nulls, and what the result set looks like.
7. "What happens when you type a URL into the browser?" Strong answer: DNS, TCP and TLS, the HTTP request, the server, the response, rendering; at the depth your level demands, and no deeper.
8. "Design a URL shortener" (for experienced candidates). Strong answer: requirements first, then the API, the data model, key generation, a rough scale estimate, and one trade-off you would revisit.
9. "Your code works locally and fails in production. What do you check?" Strong answer: logs first, then configuration and environment differences, data differences, dependency versions, reproduce, and roll back if users are affected.
10. "Why this company, and why are you leaving your current one?" Strong answer: one specific reason tied to the role, no complaints about anyone.

The pattern: every question has a follow-up, and the follow-up is where candidates are actually separated. "Can you do better?" after a correct answer is not a trick; it is the question.

How a MockMate Practice session runs for this role

Practice runs in the browser; nothing to install.

1. Attach your resume and the job description. The session is context-aware: questions reflect your resume, the target role, seniority, the job description and the focus areas you state (for example "data structures and SQL" or "backend design").
2. Choose the round. A technical round for a software engineer includes a code editor, so problem 3 above is something you write, not describe. Coding and system-design practice both exist; set the focus accordingly.
3. Answer with follow-up pressure. The interviewer persona responds to what you said. A vague complexity answer gets "which line makes it quadratic?"; a correct query gets "what if two people have the same salary?"
4. Ten minutes per free start. That is four to six questions with follow-ups, which is a realistic slice of a TR round. Eligible accounts get three free Practice starts, tracked server-side, so a reinstall or a new browser does not reset them.
5. The report arrives when the session ends. Details below.

For a first session, attach the exact job description of the drive you are preparing for. The difference between "software engineer" and "Java developer, Spring Boot, 2 years" changes every question.

What the report tells you

The Practice report is built to be read the next day, not admired. It contains:

• Question-level answers: each question, what you said, and coaching on what a stronger answer would have contained.
• Response timing: how long you took to start each answer and how long you spoke. Thirty seconds of silence before a project explanation is the most common fresher pattern, and it is invisible to you until you see the number.
• Coaching evidence: the specific words or omissions the coaching is based on, so it is not a generic "be more confident".
• Recurring weaknesses: across the session, for example "states complexity without justifying it" or "does not test edge cases".
• A recommended next practice: the focus area and round type to run next.

Run a second session after fixing the top weakness. The comparison between reports is the actual progress measure.

A 7-day prep plan

Do the coding on paper or in a plain editor at least once. Interviews still happen on whiteboards and shared docs without autocomplete.

Honest limits

• Practice is a browser product; Live is Windows-only. The mock interview works in any modern browser. MockMate's Live assistance companion runs only on Windows 10 and 11, and there is no Mac, iOS or Android app.
• Live is for permitted settings only. Use Live assistance only where the organisation, interviewer or applicable rules permit assistance and disclosure; use Practice when permission is unclear. Campus technical rounds and proctored coding tests are Practice territory.
• An AI interviewer is not your future team lead. It does not know the company's internal stack or read your body language. Pair it with one session with a senior or a mentor if you can.
• It does not replace problem volume. The session tells you that your complexity answers are weak; the fifteen problems on day 2 fix them.
• The free allowance is small by design. Three Practice starts of ten minutes each. After that, credits (as of September 2026: Starter ₹2,000 for 2 credits, Growth ₹5,000 for 5, Pro ₹10,000 for 12; one credit is about sixty minutes, billed in thirty-minute blocks with a ten-minute grace window). See pricing.

If you are preparing for a specific company, the TCS Ninja and TCS interview questions pages list the exact fundamentals those rounds cover, and the coding interviews use case explains how the technical Practice round is built.