Sample report · illustrative data

Sample interview report

This is what you get after an interview. It was built from sample data for a backend developer, fresher role, and is labelled as a sample throughout.

Get 10 free credits

The sample report

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.

Q9 Technical What is a database transaction, and when would you need one? 0/10, skipped

No answer given. Skipped questions score 0/10 and still count toward the overall score.

What could be better

Attempt it. A short answer gives the review something to assess; a skip gives it nothing.

A model answer

A transaction groups several statements so they all succeed or all fail together. You need one when a partial update would leave bad data, such as debiting one account and crediting another. In Spring Boot I would mark the service method @Transactional.

Q12 Experience Describe a bug you fixed during your internship. 7/10

Your answer (transcript)

“Our payment status API sometimes returned the old status. It turned out we were caching the response for too long, so I reduced the cache time…”

What went well

A specific problem, a cause and a fix: a good structure.

What could be better

Add the result, how you checked it was fixed, and what you would do to stop it happening again.

A model answer

Our payment status API sometimes showed an old status because responses were cached too long. I compared the API output with the database to find the cause, shortened the cache time and cleared the entry whenever the status changed. I added a test for it and a line to our release checklist.

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.

Reading your report

What each part tells you

Overall score
A number out of 100 for the whole interview.
Skill scores
A score for each skill found in your résumé or job description, so you can see which topic pulled the total down.
Every answer
Your answer as a transcript, what went well, and what could be better.
History
Reports stay in your history, so you can compare sessions. Delete any interview when you like.

How we score

The report is one review by an AI model of your transcript. It is not a human assessment, and scores can vary between sessions. It is practice feedback, not a prediction of an interview result.

Get a report like this on your own answers. Your free credits can cover one.

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

Get 10 free credits See a sample report

Or get the app