Practice · Technical round

The technical round: explain it like you mean it

Technical interviews test knowledge and the way you explain it. Mockinto writes technical questions from the skills on your résumé, and you answer them aloud.

Get 10 free credits See a sample report

An example question

“Explain the difference between a process and a thread to someone who has never written code.”

Explaining a concept simply is a common technical question. It shows you understand it well enough to drop the jargon.

Example written by the Mockinto team. Your interview’s questions are written for your résumé or job description.

What you will practise

Topics that come up for technical round

Questions follow the skills in your résumé or the job description, so these are typical areas rather than a fixed script.

01 Core concepts from the skills on your résumé
02 Problem solving, explained step by step
03 Design questions at the level of your experience
04 Trade-offs: speed, cost, simplicity
05 Debugging and testing
06 Projects and the decisions behind them

How to prepare with Mockinto

Rehearse, read the report, rehearse again

How a session works

Upload your résumé as a PDF or paste the job description. Mockinto writes about 30 questions for that role, a mix of HR, experience, aptitude and technical questions, and you answer each one out loud. When you finish, you get a report with an overall score out of 100, a score for each skill and feedback on every answer.

Spoken, not written

There is no code editor or whiteboard. Mockinto focuses on the part of the technical round where you explain your thinking out loud.

Skill by skill

The report scores each skill separately, so you know which topic to revise before your next interview.

What you get back

A report on every answer

Sample report · illustrative data, not a real candidate

Overall score

68 out of 100

Role: Backend developer, fresher
Questions: 30
Built from: A sample résumé (Java, Spring Boot, MySQL)

Skill scores

Java and Spring Boot 74/100
Databases and SQL 61/100
API design 70/100

Summary. Clear on core Java and REST basics. Answers on databases stayed general: name the index or the query plan you would check. HR answers were honest but long; lead with the result. One question was skipped and scored zero.

Q1 HR Tell me about yourself. 7/10

Your answer (transcript)

“I am a final-year computer science student. I built a library management system in Spring Boot for my college, and I interned for two months at a small fintech where I wrote REST endpoints…”

What went well

Opens with who you are and two concrete projects. The internship gives the interviewer something to ask about.

What could be better

At nearly three minutes it runs long. End with one line on why this role, and cut the list of college clubs.

A model answer

I am a final-year computer science student who builds backend services. At college I built a library system in Spring Boot and MySQL, and at my internship I wrote REST endpoints for a fintech app. I want a junior backend role where I can ship APIs and learn how production systems run.

Q7 Technical How would you speed up a slow query that filters orders by customer and date? 5/10

Your answer (transcript)

“I would first check if there is an index. If not, I would add an index on the customer column. I would also try to fetch fewer columns…”

What went well

Checks indexing first, which is the right instinct, and mentions selecting fewer columns.

What could be better

Say how you would confirm the cause, for example with EXPLAIN, and consider one composite index on customer and date rather than a single column.

A model answer

I would start with EXPLAIN to see whether the query scans the whole table. If it does, I would add a composite index on customer and order date, in that order, so the filter and the sort can both use it. I would select only the columns I need, then run EXPLAIN again to confirm the plan changed.

This is a sample built by the Mockinto team from illustrative data to show the report format. It is not a real candidate’s result, and the answers are written for the example.

Questions

Technical round: common questions

Pricing

10 free credits at sign-up, enough to analyse your résumé and run a shorter mock interview. Then ₹10 a credit, with a 30-question interview typically about 11 credits.

See pricing

Does it include system design?

Design questions can come up when your résumé or the job description calls for them. There is no drawing tool; you explain the design aloud.

How hard are the questions?

Questions follow the skills and experience on your résumé or the job description. Difficulty selection is still being improved.

Which roles does it work for?

Any role with a technical round: software, data, QA, DevOps and more. See the practice pages for role-specific advice.

All practice pages · How it works

Your next interview is a rehearsal. Make it a good one.

10 free credits at sign-up: enough to analyse your résumé and run a shorter mock interview. No card, no subscription.