Practice · Core engineers

Core engineering interviews: explain the fundamentals aloud

Core roles test whether you can explain your branch clearly, not only recall it. Mockinto writes questions from your résumé or a job description, and you answer them out loud.

Get 10 free credits See a sample report

An example question

“Explain a design or project from your degree to someone from another branch. What was the problem, what did you choose, and what trade-off did you accept?”

Core roles value engineers who can explain a choice and its trade-off in plain words. Saying it aloud shows whether your reasoning has a clear order.

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 core engineers

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

01 The fundamentals of your branch, explained in plain words
02 Design projects and the choices behind them
03 Internships, plant visits or site experience on your résumé
04 Software and tools named on your résumé, such as CAD or simulation packages
05 Safety, quality and working to a specification
06 Troubleshooting a fault or a failed test

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.

Explain it without the formula

Core interviews often start with a fundamental concept. Practise saying it in two or three plain sentences first, then adding detail. The feedback shows where an answer stays vague.

What Mockinto is not

It does not run calculations, draw diagrams or check technical correctness. It is practice for the spoken part of the interview: explaining your projects, choices and reasoning clearly.

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

Core engineers: 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

Which branches does it cover?

Any. Mechanical, civil, electrical and other branches work the same way: the questions are written from the skills on your résumé or the job description you paste.

Does it test calculations or drawings?

No. Mockinto is a spoken interview, with no calculator or drawing tool. Use it to rehearse explaining fundamentals, projects and decisions.

I only have college projects and one internship. Is that enough?

Yes. Projects, labs, internships and plant or site visits on your résumé are what the questions are built from.

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.