AI mock interviews for freshers and job switchers

Start with 10 free credits.

Use them to analyse your résumé and run a shorter mock interview, spoken out loud, with every answer scored. Then pay as you go at ₹10 a credit.

  • No card needed
  • ₹10 a credit after that
  • Purchased credits never expire
Get 10 free credits How it works

The report

Scored. Answer by answer.

An overall score out of 100, a score for each skill, and notes on what went well and how to make every answer better.

Get 10 free credits See a sample report

Practice by role

Your role. Your questions.

Upload your résumé or paste the job description. Questions follow the skills in it: software, data, QA, DevOps, HR rounds and more.

Get 10 free credits Practise by role

Pricing

₹10 a credit. Nothing renews.

Start with 10 free credits. Then buy only what you need at ₹10 a credit: no packs, no plans. A 30-question interview typically uses about 11 credits, and purchased credits never expire.

Get 10 free credits See pricing
questions in a typical interview, written for your role
30
question types: HR, experience, aptitude, technical
4
point overall score, plus a score for each skill
100
free credits at sign-up: your résumé analysis plus a shorter mock interview. No card needed
10

The practice loop: Résumé, then Questions, then Answers, then Report, then Again.

Choose your interview

Practise for the role you want next

Pick a field, then a role, a round or your stage. Every card shows an example question, and every page explains what you will be asked and how to prepare.

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

Try one now

Can you answer this in 60 seconds?

“Describe a time you disagreed with a teammate. What happened, and what did you do?”

Say it out loud, then see how it scores. 10 free credits at sign-up: enough to analyse your résumé and run a shorter mock interview. No card needed.

Get 10 free credits

See all practice pages

How it works

One session, four steps

From sign-up to a scored report, without booking anyone’s time.

How it works, in detail

  1. Step 1: Set up in a minute

    Sign up with your email and verify it with a six-digit code. Upload your résumé as a PDF, or paste the job description you are applying for.

  2. Step 2: Get your questions

    Mockinto writes about 30 questions for that role: a mix of HR, experience, aptitude and technical questions. Each question is shown as text and read aloud.

  3. Step 3: Answer out loud

    Speak your answer as you would in the room. Your words are turned into text as you talk; only the text is kept.

  4. Step 4: Read your report

    Get an overall score out of 100, a score for each skill, and notes on every answer: what went well and what could be better. Then practise again.

Sample report

An honest report, not a pat on the back

Every interview ends with an overall score, a score for each skill and notes on every answer. These are sample reports from six fields, written on illustrative data, not real candidates.

Sample report · illustrative data, not a real candidate

Backend developer, fresher

Overall score

68 out of 100

Built from a sample résumé (Java, Spring Boot, MySQL) · 30 questions

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.

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.

Sample report · illustrative data, not a real candidate

Data analyst, fresher

Overall score

61 out of 100

Built from a sample résumé (SQL, Excel, Power BI) · 30 questions

Skill scores

  • SQL and databases 66/100
  • Analysis and problem solving 56/100
  • Dashboards and communication 62/100

Summary. Solid on SQL fundamentals, but answers stay at definition level. Tie each answer to a decision: who used the work and what changed. The skipped analysis question cost the most points.

Q3 Technical What is the difference between an INNER JOIN and a LEFT JOIN? When would the results differ? 6/10

Your answer (transcript)

“INNER JOIN gives the matching rows from both tables. LEFT JOIN gives all rows from the left table and the matching ones from the right. So the results are different when there is no match, I think the right side would be empty.”

What went well

Both definitions are correct, and you spotted that the difference shows up when there is no match.

What could be better

Give one concrete case: customers with no orders disappear in an INNER JOIN but appear with empty order columns in a LEFT JOIN. Say it with confidence instead of “I think”.

A model answer

An INNER JOIN returns only rows that match in both tables. A LEFT JOIN returns every row from the left table and fills the right side with NULLs when there is no match. With customers and orders, an INNER JOIN drops customers who never ordered; a LEFT JOIN keeps them, which is how I would find them.

Q8 Experience Walk me through a dashboard you built. Who used it, and what decision did it help with? 5/10

Your answer (transcript)

“I made a sales dashboard in Power BI for my project. It had charts for sales by month and region, and some filters. It looked good and my guide liked it…”

What went well

You name the tool and the charts, so the interviewer knows what was built.

What could be better

There is no user and no decision. Say who looked at it, which question it answered and one thing that changed because of it.

A model answer

For my project I built a Power BI sales dashboard for a small retailer’s manager. It showed sales by month and region, with filters for product category. It showed that two regions were falling behind, so the manager moved the next promotion there. I would add a quick data-quality check next time.

Q14 Technical Weekly sales dropped sharply last week. How would you check whether the drop is real before reporting it? 0/10, skipped

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

What could be better

Attempt it, even if only to say where you would start. A first step is enough to earn marks; a skip is not.

A model answer

First I would check the data, not the business: did every source load, did a filter or date range change, are there duplicates or missing days. Then I would compare with neighbouring weeks and the same week last year to see whether it is seasonal. Then I would split by region and product to see where it is concentrated. Only then would I report it, with what I checked.

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.

Sample report · illustrative data, not a real candidate

Product manager, three years’ experience

Overall score

72 out of 100

Built from a sample job description (product manager, consumer app) · 30 questions

Skill scores

  • Product thinking and metrics 66/100
  • Prioritisation and trade-offs 78/100
  • Stakeholder communication 72/100

Summary. Strong on trade-offs and on working with other teams. Weaker on measurement: say how you will know a decision worked. One question on success metrics was skipped and pulled the score down.

Q2 Experience Tell me about a product decision you made with incomplete information. 7/10

Your answer (transcript)

“We had to choose between in-app chat and better search. We had little data on chat, so I spoke to support agents and a few customers, and we shipped the search improvements first…”

What went well

You name both options and say what you did to reduce the uncertainty, instead of guessing.

What could be better

Say what “good” looked like before you shipped, and what happened afterwards. If you do not know the outcome, say so.

A model answer

We had to choose between in-app chat and better search, and had little data on chat. I spoke to support agents and a few customers, and search problems came up far more often. We shipped the search work first, with a success measure agreed in advance, and kept chat on the list for the next review.

Q6 Situational Engineering says a feature will take six weeks. Sales needs it in two. What do you do? 7/10

Your answer (transcript)

“I would try to understand why sales needs it in two weeks, and see if a smaller version can be done. Then talk to engineering about what we can cut.”

What went well

You ask about the reason behind the deadline and look for a smaller scope before pushing the team.

What could be better

Name what you would cut and what you would protect, and say what you would tell sales if the answer is still no.

A model answer

I would first ask sales what the two-week date is tied to, because it may not be fixed. Then I would ask engineering for the smallest version that solves that need, cutting extras but protecting quality and the core flow. If two weeks is still not possible, I would tell sales early, with the date we can hit and what they get on it.

Q11 Technical How would you decide whether a new feature was successful after launch? 0/10, skipped

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

What could be better

Attempt it. Metrics questions are common in product interviews, and a partial answer still shows how you think.

A model answer

I would decide the measure before launch: one main metric tied to the problem the feature solves, and one guardrail metric to catch harm. I would set a time window, compare with the period before or with a holdout group, and read user feedback alongside the numbers. Then I would decide to keep, change or remove the feature.

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.

Sample report · illustrative data, not a real candidate

Sales executive, inside sales

Overall score

77 out of 100

Built from a sample job description (inside sales, business software) · 30 questions

Skill scores

  • Discovery and questioning 82/100
  • Objection handling 70/100
  • Follow-up and ownership 78/100

Summary. Good preparation habits and clear questions. Under price pressure you moved to discounts too quickly: ask what “too high” means first. Skipping the lost-deal question left a gap in ownership.

Q4 Experience Walk me through how you prepare before a first call with a new prospect. 8/10

Your answer (transcript)

“I check their website and LinkedIn to understand what the company does and who I am speaking to. Then I write down two or three questions and a clear goal for the call, like booking a demo.”

What went well

Specific steps and a clear goal for the call. It sounds like a routine, not a guess.

What could be better

Add how you tailor the opening to this prospect, and mention checking the CRM for earlier contact.

A model answer

I read the prospect’s website and LinkedIn, check our CRM for earlier contact, and note anything recent about their business. I write two or three questions and one goal, usually a next meeting. I open by saying why I am calling them in particular, then ask before I pitch.

Q9 Situational A prospect says your price is too high. What do you say? 6/10

Your answer (transcript)

“I would say I understand, and then explain the value of the product, that it costs less than the problem in the long run, and offer a discount if needed.”

What went well

You acknowledge the concern first instead of arguing.

What could be better

You jump to value and a discount before asking what “too high” means. Ask what they are comparing against, then connect the price to the cost of their problem. Keep a discount as a last step.

A model answer

I would say I understand, and ask what they are comparing the price with: another vendor, a budget, or what they get today. Then I would link the price to what the problem costs them now. If price is still the blocker, I would look at scope or terms before a discount.

Q15 Behavioural Describe a deal you lost. What would you do differently? 0/10, skipped

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

What could be better

Attempt it. Interviewers expect everyone to have lost deals; they want to hear what you learned.

A model answer

I would pick one real deal and say what happened plainly: for example, I did not speak to the person who signed the budget. I would own my part, then name one change I made, such as asking early who else is involved in the decision.

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.

Sample report · illustrative data, not a real candidate

Staff nurse, new graduate

Overall score

83 out of 100

Built from a sample job description (general ward) · 30 questions

Skill scores

  • Patient communication 88/100
  • Teamwork and escalation 84/100
  • Prioritisation under pressure 76/100

Summary. Calm, specific answers that put the patient first. Say what you actually said to people, not just that you understood. The prioritisation question was skipped; it is a common one, so rehearse it.

Q1 HR Why nursing, and why this hospital? 8/10

Your answer (transcript)

“My grandmother had a long stay in hospital, and the nurses explained everything to her and to us. I wanted to do that. On my medical ward placement I took vitals and sat in on handovers…”

What went well

A personal reason, tied to what you did on placement.

What could be better

The answer is all about why nursing. Add one sentence on what draws you to this ward or hospital.

A model answer

My grandmother had a long hospital stay, and the nurses explained everything to her and to us. I wanted to be that person. On my medical ward placement I took vitals and joined handovers. I would like to join this ward because it would let me build those skills on a general medical team.

Q5 Behavioural Tell me about a time a patient or family member was upset with you. 8/10

Your answer (transcript)

“On placement a patient’s son was angry that his father had waited for a bed. I listened without interrupting, said I understood, told my supervisor, and went back with an update…”

What went well

You listened first, stayed calm and passed it to your supervisor instead of promising something you could not control.

What could be better

Say the words you used, not only that you understood. Finish with the outcome and what you learned.

A model answer

A patient’s son was angry that his father had waited for a bed. I listened without interrupting and said, “I can see how stressful this has been. Let me find out what is happening.” I told my supervisor, came back with an update, and he thanked me. I learned to give updates sooner, even when there is nothing new.

Q10 Situational Three patients need you at once. How do you decide who to see first? 0/10, skipped

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

What could be better

Attempt it. Even a short, structured answer shows how you think under pressure.

A model answer

I would go first to the patient at the greatest immediate risk, such as breathing difficulty or sudden deterioration. I would ask a colleague or senior to help with the others and tell those patients I will be with them shortly. I would follow my ward’s escalation protocol and document and hand over afterwards.

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.

Sample report · illustrative data, not a real candidate

Customer support executive, chat and email

Overall score

54 out of 100

Built from a sample job description (customer support, online store) · 30 questions

Skill scores

  • Empathy and tone 62/100
  • Problem solving 52/100
  • Process and product knowledge 48/100

Summary. Polite and willing, but the answers stay short and general. Do not promise outcomes you cannot control, and always give a next step with a time. A skipped question scores zero, and here it cost real points.

Q3 Situational A customer writes in angry that their order has not arrived. What do you say first? 5/10

Your answer (transcript)

“I would say sorry for the inconvenience and ask for the order number. Then I will check it, and if it is delayed I will tell them it will come soon.”

What went well

You apologise and ask for the order number straight away.

What could be better

“It will come soon” is a promise you cannot keep. Share only what the tracking shows, offer a next step such as a replacement or refund under the policy, and say when you will update them.

A model answer

I am sorry your order has not arrived. Could you share the order number? Let me check the tracking. If it is delayed, I will tell you exactly where it is, offer a replacement or refund as our policy allows, and update you by a time I give you today.

Q8 Behavioural Tell me about a time you dealt with a difficult person. 4/10

Your answer (transcript)

“In college, one member of my group project did no work. I was very frustrated and I told him to do his part. Later he did it.”

What went well

You chose a real situation and you are honest about being frustrated.

What could be better

There is no clear order or result. Say the situation, what you said and did, and what happened. In support the other person is a customer, so show how you stayed calm and respectful.

A model answer

In a college group project one member was not doing his share. I stayed calm, asked privately what was getting in his way, and split his tasks into smaller pieces with dates. He finished them and we submitted on time. I learned to ask before assuming.

Q12 Situational A customer asks for a refund outside the policy window. What do you do? 0/10, skipped

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

What could be better

Attempt it. In a live shift a non-answer helps nobody; a clear next step does.

A model answer

I would thank the customer, explain the policy plainly and why it exists, and check whether an exception applies, such as a damaged item. If it needs approval, I would pass it to my lead instead of promising, and offer an alternative like an exchange or store credit. I would note the conversation on the ticket.

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.

We don’t round up. Skipped questions score 0/10 and still count toward the overall score.

Open the full sample report

The interview room

The interview room

“Walk me through a decision you made that you would make differently today.”

Example question, written for this page.

Questions on screen and out loud
Every question is shown as text and read aloud, so you never depend on audio alone.
Answers by voice
Speak naturally. Your words become a live transcript; only the text is saved.
From your résumé or a job description
Upload a PDF résumé or paste the job description. Questions follow the skills in it.
Feedback on every answer
What went well and what could be better, for each question, plus skill scores.
History you control
Past interviews stay in your history until you delete them.
Where it runs today
The web app, in a current version of a modern browser on desktop or phone. Android and iOS apps are coming.

Trust

Plain answers about your data and your money

Your data

Your résumé and answers are used to write questions and your report. Mockinto keeps transcripts, not audio; in the web app your browser’s speech service turns speech into text. You can delete past interviews any time.

Privacy policy

Honest billing

No subscription. Purchased credits never expire. If an interview fails on our side, the credits come back automatically.

Pricing and billing rules

Real people behind it

Questions about your account or a charge go to a person. Write to support@mockinto.com.

About and contact

Pricing

Pay as you go. Nothing renews.

Start with 10 free credits. Then buy only the credits you need.

1 · At sign-up

10 free credits

Every new account gets them. No card, no conditions. That is enough to analyse your résumé and run a shorter mock interview.

₹0

Get 10 free credits

2 · After that

Buy what you need, at ₹10 a credit

Any number of credits from 10 to 2,000, in steps of 10. No packs, no plans. The app suggests these amounts.

50 credits

500 rupees

About 4 full 30-question interviews at about 11 credits each

100 credits

1000 rupees

About 9 full 30-question interviews at about 11 credits each

200 credits

2000 rupees

About 18 full 30-question interviews at about 11 credits each

500 credits

5000 rupees

About 45 full 30-question interviews at about 11 credits each

Purchased credits never expire and nothing renews. Credits are metered by usage: a 30-question interview typically takes about 11 credits and never more than 15, and the booking screen shows an estimate before you confirm. Prices are in rupees; pay with UPI, cards and more via Razorpay.

What an interview costs, and the billing rules

FAQ

Questions people ask first

All questions

What is Mockinto?

Mockinto is an AI mock interview. You upload your résumé or paste a job description, answer about 30 questions out loud, and get a report with an overall score out of 100, a score for each skill and feedback on every answer.

Is it free?

Every new account gets 10 free credits at sign-up, with no card and no conditions. That is enough to analyse your résumé and run a shorter mock interview of up to about 20 questions. A default 30-question interview typically needs about 11 credits, so it takes a small top-up. After that you buy credits at ₹10 each, and purchased credits never expire.

Which devices can I use?

Today you can practise in the web app. Mockinto works in a current version of a modern browser on desktop or phone. The Android and iOS apps are not public yet; until they are, the store buttons on this site open the web app.

What happens to my voice?

Your spoken answers are turned into text and only the text is saved. In the web app, your browser’s speech service does the conversion; in Chrome that is Google’s service. In the mobile apps, and as a web fallback, your answer is recorded and sent to our server, which passes the audio to OpenAI only to be transcribed. Mockinto does not keep audio recordings.

Can I delete my interviews and my account?

You can delete past interviews from your history at any time. To delete your account, email support@mockinto.com from the address you signed up with. We delete or anonymise your personal data, except records the law requires us to keep, such as payment and tax records. The privacy policy has the details; an in-app deletion option is on the way.

Does this website use cookies or advertising tags?

Yes. Google Tag Manager, Google Analytics, Google Ads and Meta Pixel load on every visit to this website, and there is currently no cookie banner or opt-out control. You can limit them with your browser settings or a tracker blocker, Google Ads Settings and Meta’s ad preferences. The privacy policy explains more.

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.

Get 10 free credits See a sample report

Or get the app