How this list is ranked and how to use it
The ranking comes from the question patterns reported by candidates in Indian IT services, campus, startup and corporate interviews, cross-checked against what our AI interviewers are briefed to ask for each role. The first six are near-universal: they appear in some form in almost every HR round and most hiring-manager rounds. Questions seven to fourteen appear in most interviews with any behavioural component. Fifteen to twenty are frequent but role- or stage-dependent. Each question is written with one fresher answer and one experienced answer so you can see how the same structure changes with evidence.
The three-step rule
Every common question has a three-step answer: the direct point, one specific example with a number or a name, and the link to this role. Thirty to seventy seconds. If you remember nothing else from this page, remember that the example is the step people skip, and it is the step that gets you hired.
Questions 1 to 5: asked in almost every interview
1. Tell me about yourself. Why it is asked: to let you set the agenda and to check whether you can summarise. Structure: present (who you are and what you do), past (one or two proof points), future (why you are here). Follow-up: 'Tell me more about that project' or 'Why did you leave that company?' Full treatment in tell me about yourself.
Tell me about yourself. (Fresher)
I am Ananya Joshi, a final-year computer science student at MIT Pune with a CGPA of 8.3. My main skills are Java and SQL, and my final-year project is an inventory app for a pharmacy chain in Pune that three of their stores are piloting. Last summer I interned for two months with a healthcare startup, where I wrote API tests and fixed four production bugs. I am applying here because I want to work on large client systems with a structured training path, and I am open to any location. Happy to go deeper on the project or the internship.
Follow-up: 'Why a pharmacy chain?' Have the story of how you found the problem ready.
Say this answer out loudTell me about yourself. (Experienced)
I am a backend engineer with five years of experience, currently at a Chennai fintech where I own the payouts service that processes about two lakh transfers a day. Before that I spent three years at an IT services company on a US banking client, where I moved from support to development. My strengths are Java, Spring and designing for reliability; the payouts service has had no failed-settlement incident in eighteen months. I am looking at this role because it combines backend ownership with a team-lead responsibility, which is the next step I want.
Follow-up: 'What caused the move from services to fintech?' Keep it positive and specific.
Say this answer out loud2. Why do you want to work here? Why it is asked: to check that you chose them, not just a job. Structure: one fact about the company, one link to your skills or plan, one honest personal reason. Follow-up: 'What do you know about our products or clients?'
Why do you want to work here? (Fresher)
Three reasons. Your company has a large retail and e-commerce practice, and my project and internship were both in inventory and order systems, so I can be useful quickly. Two seniors from my college who joined two years ago told me the training is rigorous and that freshers get onto live projects within six months, which is what I want. And your Hyderabad office is in a city where I have family, which makes the move easy. I applied to you specifically, not through a mass application.
Follow-up: 'Which seniors, which projects?' Only say it if it is true.
Say this answer out loudWhy do you want to work here? (Experienced)
Because the role matches the problem I want to solve next. You are moving your lending platform to event-driven microservices; I did exactly that migration for a payouts service, including the hard part of reconciling data during the cutover. I also want to work at a company where engineers talk to the business directly, and the people I spoke to during the screen confirmed that is how your product teams run. Finally, I have followed your engineering blog for a year; the piece on idempotent retries changed how I built ours.
Follow-up: 'What would you do differently in our migration?' Have one opinion ready.
Say this answer out loud3. What are your strengths? Why it is asked: to see whether you know yourself and can prove it. Structure: two strengths, one proof each, the one that matters most for this role. Follow-up: 'Give me another example of the first one.'
What are your strengths? (Fresher)
I finish things, and I explain things clearly. In our project, two teammates dropped out in the final semester and I completed the backend and the report alone, on time, with the project scoring an A grade. On explaining: I was the person who taught data structures to about forty juniors in our coding club, and six of them cleared the TCS NQT this year. For this role I think the first one matters more, because a fresher on a live project is valued for reliability before anything else.
Follow-up: 'What happened with the teammates who dropped out?' Answer factually, without blame.
Say this answer out loudWhat are your strengths? (Experienced)
Two. I design for failure: the payouts service I own handles bank timeouts and duplicate requests without manual intervention, which took a year of incidents and fixes to get right. And I am good at making a team's work visible; I introduced a weekly one-page status for our group that our director now forwards to the board. The first one is why I would be useful on your lending platform; the second is why I would be useful as a lead.
Follow-up: 'Tell me about one of those incidents.' Pick one with a clean fix.
Say this answer out loud4. What is your biggest weakness? Why it is asked: to check honesty and self-awareness. Structure: a real weakness, its concrete cost once, the fix you are applying. Follow-up: 'Has it improved? How do you know?'
What is your biggest weakness? (Fresher)
I over-prepare before speaking in groups. In my second year I sat through an entire GD on digital payments without saying a word because I was still arranging my points. It cost me that shortlist. Since then I have done one extempore a week in our club, and in my last two GDs I spoke in the first minute with a point I had not fully polished. It is still not natural, but I now know that a reasonable point said early beats a perfect point never said.
Follow-up: 'How did the last GD go?' Have the result ready.
Say this answer out loudWhat is your biggest weakness? (Experienced)
I used to hold on to tasks instead of delegating. Last year I was the bottleneck on three releases because I insisted on reviewing every change in the payouts service myself. My manager pointed it out in a one-on-one, and I set a rule: any change under a hundred lines is reviewed by one of two senior engineers I trained, and I only review the design. Release cycle time came down from nine days to five. I still catch myself wanting to look at everything; the rule is what keeps me honest.
Follow-up: 'How did your team react?' Say what the two engineers gained.
Say this answer out loud5. Why should we hire you? Why it is asked: to hear you summarise your fit under mild pressure. Structure: three needs of the role, your matching proof for each, one closing line. Follow-up: 'What would you need from us to succeed?' See also Why Should We Hire You, and Why This Company.
Why should we hire you? (Fresher)
Because I match the three things this role asks for. You need Java and SQL from day one; I have used both in a project that real stores are piloting. You need someone who will complete training and stay; I am not planning higher studies for three years and I am open to any location. And you need someone who communicates clearly with a team; teaching forty juniors and running a club has given me that. I will not be the most experienced person you interview today, but I will be one of the most ready.
Follow-up: 'What would you need from us?' Ask for a mentor and clear first-year goals.
Say this answer out loudWhy should we hire you? (Experienced)
Because I have done the specific thing you are about to do. Your job description asks for someone to lead the move of the lending platform to microservices and to grow two junior engineers into owners. I led that migration for payouts, with zero settlement incidents during cutover, and the two engineers I trained now own services of their own. I also know your domain; I have spent five years in payments and lending. You would be hiring someone who can start the migration in month one rather than spend month one learning what a migration is.
Follow-up: 'What went wrong in your migration?' Have one honest problem and its fix.
Say this answer out loudQuestions 6 to 10: the rest of the top ten
6. Where do you see yourself in five years? Why it is asked: to check that your plan fits their ladder and that you will stay. Structure: a role on their ladder, a skill you will add, a statement of stability. Follow-up: 'What if the company cannot offer that role?'
Where do you see yourself in five years? (Fresher)
In five years I would like to be a senior engineer or a technical lead on one of your client projects, owning a module end to end and mentoring two or three freshers the way my seniors will mentor me. Along the way I want to add a cloud certification, probably in the second year, because that is where your projects are going. I am not planning to switch fields or go for a full-time degree; I want depth in one domain, and I would like it to be banking technology.
Follow-up: 'What if you are put on a non-banking project?' Say you would take it and build depth there.
Say this answer out loudWhere do you see yourself in five years? (Experienced)
Leading a platform group of eight to ten engineers here, responsible for the lending services end to end, including their reliability and cost. To get there I need two things I do not fully have yet: experience managing people formally, which this role gives me, and a better grasp of credit risk, which I plan to learn from your risk team in the first year. I am looking for a long stint; I have had two employers in eight years and I would like this to be the third and longest.
Follow-up: 'Have you managed people before?' Be honest about informal versus formal management.
Say this answer out loud7. Why are you leaving your current job? For freshers this becomes: why were you not placed on campus, or why this job and not higher studies. Why it is asked: to check for problems that will follow you. Structure: a positive reason, a specific pull towards this role, no blame. Follow-up: 'Did you try to fix that where you are?'
Why a job now and not higher studies? (Fresher)
I considered an M.Tech seriously in my seventh semester and even started preparing for GATE. What changed my mind was the internship: in two months of real work I learnt more about building systems than in a semester of coursework, and I realised I wanted to learn by doing. If I study later, it will be part-time and with a clear purpose, probably after four or five years. For now I want to join a team, complete training, and get onto a live project as soon as I can.
Follow-up: 'Are you still registered for GATE?' Say the truth; HR will check attrition signals.
Say this answer out loudWhy are you leaving your current job? (Experienced)
My current company has been good to me, and I own a service I am proud of. The reason I am looking outside is that the platform is now stable and in maintenance mode, and the next large build has been pushed to late next year, so my learning has flattened. I asked for a move to the lending team internally, but that team is fully staffed. This role has the migration and the lead responsibility that I want next. I will leave with a full handover; my manager knows I am exploring.
Follow-up: 'What if we offered you the same stable work?' Say what you would want in return.
Say this answer out loud8. What are your salary expectations? Why it is asked: to check that an offer will be accepted. Structure: freshers accept the band and ask about higher tracks; experienced state current pay precisely, expected as a range with a reason, and flexibility on structure. Follow-up: 'Is that negotiable?' Details in Salary, Notice Period and Career Gaps.
What are your salary expectations? (Fresher)
I understand that the package for this role is fixed for the batch, and I am comfortable with the band you have shared. I did not apply expecting to negotiate as a fresher. If the company has a higher track for candidates with a strong test score or interview, I would be glad to be considered for it, but it is not a condition. What matters more to me is the training, the project I am put on, and how performance is reviewed in the first year.
Follow-up: 'What if the offer is lower than your friends' offers?' Say your decision is about the role, not comparison.
Say this answer out loudWhat are your salary expectations? (Experienced)
My current fixed pay is 18 lakh with a variable of about 2 lakh, so roughly 20 lakh in total. Given that this role adds a formal lead responsibility and a migration of this size, and what the market pays for six years of backend and payments experience in Bengaluru, I am looking at a fixed range of 26 to 28 lakh. I am flexible on how it is structured; if the fixed component is at the lower end, I would want to discuss a joining bonus or equity.
Follow-up: 'Can you share your payslip?' Yes, and make sure the numbers match.
Say this answer out loud9. Tell me about a challenge you faced and how you handled it. Why it is asked: to see how you behave when things go wrong. Structure: situation in one sentence, your actions in three, the result and the lesson. Follow-up: 'What would you do differently?' Drill the pattern in Behavioural Answers with STAR.
Tell me about a challenge you handled. (Fresher)
Three weeks before our project demo, the pharmacy chain changed their billing software, and our app's data import stopped working. I had two choices: build a new import for their new format, or ask them to export manually. I built the new import in four days, reusing the validation code, and set up a weekly check so a format change would show up as a warning rather than a crash. The demo went ahead on schedule and the stores continued the pilot. What I would do differently is ask the client early what systems might change during the project.
Follow-up: 'Did you tell your guide about the risk?' Say when and how.
Say this answer out loudTell me about a challenge you handled. (Experienced)
During a bank's year-end freeze, our payouts started failing for one partner bank at about two percent, which was enough to breach our SLA. The bank's team was unavailable for forty-eight hours. I traced it to a timeout change on their side, built a targeted retry with a longer window only for that bank, got it reviewed and deployed in six hours, and wrote to the bank with the evidence. Failure rate went back under 0.1 percent the same evening. The lesson was to keep per-partner configuration rather than global timeouts, which we did the following sprint.
Follow-up: 'Who approved the emergency deploy?' Show you followed process even under pressure.
Say this answer out loud10. Describe your project or your biggest achievement. Why it is asked: to find out whether you did what your resume says. Structure: the problem, your part, the result with a number. Follow-up: 'What was the hardest part?' or 'What did your teammates do?'
Describe your project. (Fresher)
A pharmacy chain in Pune was running out of common medicines at some stores while others had excess, because each store ordered independently. We built a web app that shows stock across stores and suggests transfers and reorders based on the last eight weeks of sales. I designed the database and built the reorder logic in Java; my two teammates built the front end and the sales import. Three stores piloted it for six weeks and stock-outs of the top fifty medicines fell by about a third. The hardest part was handling medicines with different pack sizes across suppliers.
Follow-up: 'How did you measure stock-outs?' Have the method ready, not just the number.
Say this answer out loudWhat is your biggest professional achievement? (Experienced)
Taking the payouts service from monthly incidents to eighteen months without a failed settlement. When I took it over it had global timeouts, no idempotency and manual reconciliation every morning. Over about a year I introduced idempotent request keys, per-bank configuration, automated reconciliation with alerts, and a runbook so that any engineer on call could handle the common failures. The team went from one person who understood it, me, to four. The business impact was that finance stopped a daily two-hour manual task and the service became the reference design for two other teams.
Follow-up: 'What did you not manage to fix?' Name one open item honestly.
Say this answer out loudQuestions 11 to 15: behaviour and fit
11. How do you handle pressure and deadlines? Why it is asked: to check whether you plan or panic. Structure: your method in one sentence, one real deadline, how you communicated. Follow-up: 'What if the deadline was non-negotiable?'
How do you handle pressure? (Fresher)
I make a list, decide what will not get done, and tell people early. During our college fest I was handling the registration website and three event schedules at the same time, with two days to go. I listed everything, dropped a feature nobody would miss, the photo gallery, and told the fest committee on day one that two schedules would be ready by the evening and the third next morning. All three went live before the fest. I still felt the pressure; the list and the early message made it manageable.
Follow-up: 'What did you cut and who agreed?' Show the decision was shared.
Say this answer out loudHow do you handle pressure? (Experienced)
By making the plan visible before the deadline arrives. When RBI changed a reporting format with a three-week window last year, I wrote the plan on day one: what we would change, what we would not touch, and the two risks. I shared it with compliance and my manager, got sign-off on the scope, and we delivered a day early. The pressure was real, but a written scope meant nobody added requests in week three. When I see a teammate under pressure, I do the same thing with them: list, cut, communicate.
Follow-up: 'What were the two risks?' Name them.
Say this answer out loud12. Tell me about a conflict with a colleague and how you resolved it. Why it is asked: to see whether you escalate, avoid or fix. Structure: the disagreement in one line, the conversation you had, the result. Follow-up: 'What if the person had refused to change?'
Tell me about a conflict in a team. (Fresher)
In our project one teammate wanted to use a NoSQL database because it was new and interesting, and I thought our data was relational and we had six weeks. We argued in the group chat for two days without progress. I suggested we each build the stock table both ways in one evening and compare. His version needed a workaround for the transfer logic; mine did not. He agreed to SQL and, importantly, I asked him to own the import module, which he did well. The lesson was to replace argument with a small test, and to make sure the person who loses the argument does not lose face.
Follow-up: 'What if the test had gone his way?' Say you would have switched.
Say this answer out loudTell me about a conflict with a colleague. (Experienced)
A senior QA lead blocked our releases for three weeks because she wanted full regression on every change, and my team was frustrated. Instead of escalating, I asked her for thirty minutes and listened; it turned out two production incidents from another team had been blamed on QA. We agreed on a risk-based rule: full regression for changes touching settlement, a smoke suite for the rest, and a shared log of what each release skipped. Release frequency doubled and QA was no longer the default blame. We still work together and she now reviews our risk tags.
Follow-up: 'Did you involve your manager?' Say when you informed and why not earlier.
Say this answer out loud13. What do you know about our company? Why it is asked: to check preparation and interest. Structure: three facts you can defend, one that links to you, one question back. Follow-up: 'What do you think of our recent announcement?'
What do you know about our company? (Fresher)
You are one of the top five IT services companies in India with large retail, banking and healthcare clients, mostly in the US and Europe. Your last annual report highlighted growth in cloud and data services and a company-wide training push on AI tools. Freshers join through a training programme and are then mapped to a business unit. The fact that connects to me is the retail practice, since my project is an inventory system. One thing I would like to know is how freshers are mapped to units after training, and whether there is a choice.
Follow-up: 'Which clients?' Name only what is public on their site.
Say this answer out loudWhat do you know about our company? (Experienced)
You are a lending-first fintech, about four years old, with a loan book that your last funding announcement put in the low thousands of crores, and you have been building your own core lending platform rather than using a vendor. Your engineering blog talks about moving to event-driven services this year, which is the work this role is for. You also opened a Pune engineering office last year. The question I have is how much of the legacy platform must stay live during the migration, because that decides the approach.
Follow-up: 'What approach would you take?' Have one concrete opinion.
Say this answer out loud14. Why did you choose this field or this role? Why it is asked: to check whether the choice is deliberate. Structure: the moment you chose, what you did since, why this role is the next step. Follow-up: 'What else did you consider?'
Why did you choose software? (Fresher)
I chose it in my second year, after a hackathon in which our team built a working bus-tracking app in a day. I had been average in programming until then; building something people used changed how I studied. Since then I have done two projects, an internship and about three hundred practice problems. I considered a core electronics role, since that is my branch, but the work I enjoyed most was the software side of every electronics project. This role, with its training and client projects, is the structured start I want.
Follow-up: 'Will you miss electronics?' Say what from it you still use.
Say this answer out loudWhy did you move into payments? (Experienced)
By accident at first and by choice since. My first project at the services company happened to be a banking client, and I found that money-movement systems have the clearest definition of correctness I have seen: every rupee must be accounted for. I moved to a fintech to work closer to the product, and I have stayed in payments for five years. I considered a move to a big-tech infrastructure team two years ago, but I would have lost the domain. This role keeps me in lending and adds the leadership step.
Follow-up: 'What do you dislike about the domain?' Give a real one, such as regulatory churn, and say how you handle it.
Say this answer out loud15. Are you willing to relocate, or to work shifts? Why it is asked: to avoid an offer being declined later. Structure: a clear yes or a clear constraint, the reason, one practical detail. Follow-up: 'What if the posting changes after a year?'
Are you willing to relocate? (Fresher)
Yes. I am from Indore and I have lived in a hostel in Pune for four years, so moving is not new. I have discussed it with my parents; their only request was a reputed company and a visit home twice a year. My preference would be Pune or Hyderabad because of friends and family there, but I understand allocation depends on project needs and I would accept Chennai or Kolkata as well. I would need about two weeks to arrange accommodation after the joining date is confirmed.
Follow-up: 'Night shifts?' Say yes only if true; give an example if you have one.
Say this answer out loudAre you willing to relocate? (Experienced)
For this role, yes. I am in Chennai now, the role is in Bengaluru, and my spouse's company has a Bengaluru office she can transfer to, so we have already discussed it. I would need about six weeks from offer to joining to manage the move alongside my notice period. The one thing I would ask is clarity on the hybrid policy, because we would choose where to live based on how many days a week the team is in the office.
Follow-up: 'What if we need you in Mumbai in two years?' Say what you would need to know and when.
Say this answer out loudQuestions 16 to 20: motivation, working style and the close
16. What motivates you? Why it is asked: to predict whether this job will keep you engaged. Structure: one honest driver, one example of it, how this role provides it. Follow-up: 'What demotivates you?'
What motivates you? (Fresher)
Seeing something I built being used. The pharmacy app was motivating not because of the grade but because a store manager in Kothrud told me he had stopped keeping his paper reorder list. I will work long hours for that feeling and I get bored by work nobody will see. This role puts freshers on live client projects within the first year, which is why I chose it over a research-oriented offer. What demotivates me is unclear goals, so I ask for them early.
Follow-up: 'What if your first project is internal and not client-facing?' Say what you would find in it.
Say this answer out loudWhat motivates you? (Experienced)
Making a system boring. The best compliment I got last year was from our on-call engineer, who said the payouts service had not paged her in three months. I am motivated by taking something fragile and making it reliable enough that people stop thinking about it, and by watching the engineers I train become people others go to. This role has both: a migration that needs to end in a boring system, and two juniors to grow. What demotivates me is rework caused by decisions made without data.
Follow-up: 'Give an example of a decision made without data.' Keep it about the decision, not the person.
Say this answer out loud17. How do you prioritise when you have several tasks? Why it is asked: to check whether you have a method. Structure: the rule you use, one example of applying it, how you communicate the order. Follow-up: 'What if two stakeholders both say theirs is urgent?'
How do you prioritise? (Fresher)
I rank by what blocks other people first, then by deadline, then by effort. In the final semester I had the project report, two end-semester exams and the club's annual event in the same fortnight. The report blocked my teammates' submission, so it came first; the exams had fixed dates, so they were next; the event had a committee that could run without me for a week, so I delegated it. I told each group the order so nobody was surprised. Everything got done, and the event was actually better because two juniors stepped up.
Follow-up: 'What did you drop?' Have one honest answer.
Say this answer out loudHow do you prioritise? (Experienced)
Impact on money and customers first, then regulatory deadlines, then everything else by effort against value. When a settlement bug, a compliance report change and a product feature request landed in the same week, the bug went first because customers were affected, the report second because of its fixed date, and the feature was moved a sprint, with the product manager told on day one and given the reason. When two stakeholders both claim urgency, I put the two items side by side with the cost of delay for each and let them see the comparison; it usually resolves itself.
Follow-up: 'What if your manager overrides you?' Say you would state your case once and then comply.
Say this answer out loud18. Describe your ideal manager or work environment. Why it is asked: to check fit with the team you would join. Structure: two things you need, one thing you can adapt to, an example of each. Follow-up: 'What kind of manager do you find hard to work with?'
Describe your ideal manager. (Fresher)
Someone who gives clear goals and honest feedback, even when it is uncomfortable. My internship mentor told me in week two that my test cases were too vague to be useful, and showed me one good one; that single comment improved everything I did after. I do not need constant attention, but I need to know what good looks like. I can adapt to a busy manager if there is a senior I can ask day to day. What I would find hard is a manager who says everything is fine and then marks me down at review.
Follow-up: 'How do you ask for feedback?' Describe a specific routine.
Say this answer out loudDescribe your ideal work environment. (Experienced)
One where decisions are written down and engineers can see the business numbers. At my current company every design decision has a one-page record, and I can see the daily settlement value my service handles, which changed how seriously I took reliability. I work well with a manager who sets the outcome and lets me plan the path, and I can adapt to a more hands-on style for the first few months while trust is built. I find it hard when priorities change weekly without a stated reason, so I ask for the reason.
Follow-up: 'Our priorities do change often. Problem?' Say what would make that workable.
Say this answer out loud19. What are your hobbies and interests? Why it is asked: to see you as a person and to check consistency with your resume. Structure: one or two real hobbies, something specific about each, one link to a work trait. Follow-up: 'How often do you actually do it?'
What are your hobbies? (Fresher)
I play table tennis, and I was in our college team for two years; we reached the state inter-college quarter-finals last year. I also sketch, mostly buildings, which is why I ended up designing most of our project's screens even though I was the backend person. Table tennis has made me comfortable with losing a point and resetting for the next one, which turned out to be useful in debugging. I play three evenings a week even now, at a club near my home in Indore.
Follow-up: 'Who is your favourite player?' Have a real answer; it is a consistency check.
Say this answer out loudWhat are your hobbies? (Experienced)
Long-distance cycling. I ride about a hundred kilometres most Sundays with a group in Chennai, and I did a 200-kilometre brevet last year. It is the only time I am away from a screen for six hours, and it has taught me to pace effort, which I apply to how I plan sprints. I also read history, mostly about Indian economic policy, which connects to the lending domain more than I expected. My wife would add that I cook badly but enthusiastically on weekends.
Follow-up: 'What does pacing look like in a sprint?' Give the concrete practice.
Say this answer out loud20. Do you have any questions for us? Why it is asked: to check interest and judgement. Structure: two questions about the work or the first year, never salary or leave in the first round, and a one-line close. Follow-up: usually none; the interviewer answers and the round ends. Forty options, grouped, in questions to ask at the end of an interview.
Do you have any questions for us? (Fresher)
Yes, two. What does the first year look like for a fresher in this role: how long is training, and when do people typically join a live project? And how is a fresher's performance measured in the first year, so I know what to focus on? Thank you for your time today; I enjoyed the discussion on the project, and I am keen on this role.
Follow-up: none, usually. Listen to the answer and respond to it in one line; do not read the next question off your list.
Say this answer out loudDo you have any questions for us? (Experienced)
Two questions. What would success look like for this role at the end of the first six months: is it the migration plan, the first service moved, or the team structure? And what is the biggest risk you see in the migration today, the one you would want the person in this role to handle first? Thank you; this has been one of the more useful conversations I have had about the role, and I am very interested in the next step.
Follow-up: 'What is your take on that risk?' Be ready to think aloud for a minute.
Say this answer out loudWhat the ExamPilot AI interviewer checks on these twenty
The ExamPilot mock for a job interview runs the full loop: an HR screen, a hiring-manager round and a role round, as a seventeen-minute panel or a twelve-minute one-on-one. The interviewers are briefed on these twenty questions and ask the versions that fit your profile, fresher or experienced, and they follow up with the questions listed above when an answer is vague.
You get a transcript, a score for each question and rewritten versions of your three weakest answers that keep your facts. Run it for your role in job interviews, start with the software engineering loop, or prepare the fresher versions in interview questions and answers for freshers. If your opening needs work first, see self introduction for interview.
Practise out loud
Practise the top 20 with the AI interviewer
A full HR, hiring-manager and role loop that asks the fresher or experienced version of each common question, follows up, and scores your structure and evidence.
Job interviews · Software engineering
Frequently asked questions
- What are the top 10 interview questions?
- Tell me about yourself; why do you want to work here; what are your strengths; what is your biggest weakness; why should we hire you; where do you see yourself in five years; why are you leaving your current job (or why not higher studies, for freshers); what are your salary expectations; tell me about a challenge you handled; and describe your project or biggest achievement. These ten cover the first fifteen minutes of nearly every Indian interview, and each has two full model answers above.
- Are common interview questions the same for freshers and experienced candidates?
- The questions are the same; the evidence expected is different. A fresher answers with a project, an internship, a college activity and a plan; an experienced candidate answers with work outcomes, numbers and team impact. A few questions change form: 'why are you leaving' becomes 'why not higher studies' or 'why were you not placed on campus' for freshers, and salary questions become a band-acceptance rather than a negotiation.
- How do I structure an answer to a common interview question?
- Three steps: the direct point in one sentence, one specific example with a number or a name, and a link to the role you are interviewing for. Thirty to seventy seconds. For behavioural questions, the example expands into situation, action, result and lesson. The step most candidates skip is the example, and it is the one interviewers remember.
- What follow-up questions should I expect?
- Almost every common question has a standard follow-up: 'give me another example', 'what would you do differently', 'what if that was not possible', or 'tell me more about that'. Interviewers use follow-ups to check whether the first answer was real. Each question above lists its usual follow-up; prepare a one-line response for every one of them and you will rarely be caught out.
- Which common interview questions are asked in the HR round versus the technical round?
- HR rounds concentrate on questions 1 to 8, 15, 19 and 20: introduction, why us, strengths and weaknesses, five-year plan, reason for leaving, salary, relocation, hobbies and your questions. Hiring-manager and technical rounds ask 9 to 14 and 16 to 18: challenges, your project, pressure, conflict, company knowledge, motivation, prioritisation and working style. In campus drives the rounds are often merged, so expect any of them at any time.
- How long should answers to common interview questions be?
- Thirty to seventy seconds for most, up to ninety for 'tell me about yourself' and 'describe your project'. 'Do you have any questions for us' should take under a minute including your close. If the interviewer wants more, the follow-up will ask for it; an answer that runs past ninety seconds without a concrete example is the most common reason candidates are cut off.
- How can I practise the most common interview questions out loud?
- Write a three-line skeleton for each of the twenty (point, example, link), record yourself answering, and cut anything over seventy seconds. Then run the ExamPilot job interview mock, which asks the fresher or experienced version based on your profile, follows up on vague answers, and scores structure, evidence, consistency and delivery with a transcript and rewritten answers. Three sessions are usually enough.