Whether you're a fresher or switching jobs, these 30 questions cover what interviewers in India are actually asking right now — across IT, Finance, Marketing, and general HR rounds. Each answer includes a structure you can adapt to your own experience.
This is not your life story. Structure it as: Present → Past → Future.
Example: "I'm a final-year Computer Science student at [College], where I've focused on backend development. During my internship at [Company], I built REST APIs handling 10,000+ daily requests. I'm looking to join a product team where I can work on scalable systems."
Keep it to 90 seconds. End with something that connects to the role you're interviewing for.
Never say "I'm a perfectionist" — every recruiter knows this is fake. Pick a real, minor weakness that isn't critical to the job, then show you're actively fixing it.
Example: "I used to struggle with delegating tasks — I wanted to do everything myself. Over the last year I've been working on it by clearly defining responsibilities in team projects, and it's significantly improved our delivery time."
Show you've done your homework. Mention something specific about the company — a product, a recent milestone, their culture.
Example: "I've been using [Product] for two years and I think the way you've approached [specific feature] is genuinely better than competitors. I want to be part of the team that builds things I'd use myself."
Be ambitious but realistic. Show growth within the field, not "I want to start my own company" (that signals you'll leave soon).
Example: "I see myself as a senior engineer with deep expertise in distributed systems, ideally having led a small team on a meaningful product. I want to grow technically and take on more ownership."
Never badmouth your current employer. Focus on what you're moving towards, not what you're running from.
Example: "I've learned a lot at my current role but I'm looking for a role with more ownership over the product lifecycle and the chance to work with a larger engineering team."
Research the market rate before going in. Give a range, not a single number. Always anchor higher.
Example: "Based on my skills and market research, I'm looking at ₹6–7 LPA. That said, I'm open to discussing the full package including growth opportunities."
Use Glassdoor, AmbitionBox, and LinkedIn Salary Insights for current market data for your specific role and city.
Use the STAR method: Situation → Task → Action → Result.
Example: "During my internship, our server went down 2 hours before a client demo (Situation). My task was to restore service within the deadline (Task). I quickly identified a database connection pool issue using logs, increased the pool size, and added an alert (Action). We were back online in 40 minutes and the demo went smoothly (Result)."
Show maturity — you listened, you found common ground, the project succeeded. Don't make yourself the villain or the perfect hero.
Example: "During a college project, two teammates disagreed on the tech stack. I organized a quick comparison of pros/cons and let the team vote. We went with the majority choice and everyone was aligned. The project was submitted on time."
Pick something with a measurable outcome. Numbers are powerful — revenue, users, time saved, percentage improvement.
Give a real example. Show you prioritize, communicate, and deliver — not that you "just work harder."
Example: "I break the work into daily milestones, flag blockers early to the team, and cut scope if needed rather than miss the deadline entirely."
Object-Oriented Programming organizes code into objects that have properties (data) and methods (functions). The four pillars are Encapsulation (bundling data with methods), Inheritance (child class inherits from parent), Polymorphism (same method, different behavior), and Abstraction (hiding complexity).
Example: A "Vehicle" class has speed and color. "Car" inherits from Vehicle and adds "number_of_doors." Polymorphism: both Car and Bike have a "move()" method but they behave differently.
SQL (MySQL, PostgreSQL): structured data in tables, fixed schema, ACID transactions, great for relational data. NoSQL (MongoDB, Redis, DynamoDB): flexible schema, document/key-value/graph stores, better for unstructured or rapidly changing data at scale.
Follow-up they often ask: "When would you choose one over the other?" — Answer: SQL for consistent transactions (banking, ecommerce orders). NoSQL for user activity logs, product catalogs, real-time feeds.
REST (Representational State Transfer) is an architectural style for web services. It uses standard HTTP methods: GET (read), POST (create), PUT/PATCH (update), DELETE (remove). Each URL represents a resource. Responses are typically JSON. It's stateless — the server doesn't remember previous requests.
A process is an independent program in execution with its own memory. A thread is a unit of execution within a process, sharing memory with other threads in the same process. Threads are lighter and faster to create, but shared memory can lead to race conditions.
Git is a distributed version control system. Common branching strategies: Feature branches — create a branch per feature, merge to main when done. Gitflow — main, develop, feature, release, hotfix branches. Trunk-based development — short-lived branches, frequent merges to main.
Income Statement: Revenue → Expenses → Net Profit. Shows profitability over a period. Balance Sheet: Assets = Liabilities + Equity. Snapshot at a point in time. Cash Flow Statement: Operating + Investing + Financing activities. Shows actual cash movement.
They connect: Net income from P&L flows into retained earnings on Balance Sheet; changes in Balance Sheet items appear in Cash Flow.
Working Capital = Current Assets − Current Liabilities. It measures a company's short-term liquidity — its ability to pay short-term obligations. Positive working capital means the company can cover its short-term debts. Negative working capital can signal cash flow problems.
Three main approaches: DCF (Discounted Cash Flow) — project future cash flows, discount to present value. Comparable Companies — use EV/EBITDA, P/E multiples of similar listed companies. Precedent Transactions — look at what acquirers paid for similar companies in M&A deals. In practice, use 2–3 methods and triangulate.
B2B: longer sales cycle, multiple decision-makers, relationship-driven, content-heavy, ROI-focused. B2C: shorter decision cycle, emotional triggers, mass reach, brand awareness, impulse-friendly. Channels differ too: B2B favors LinkedIn, email, webinars; B2C favors Instagram, YouTube, influencers.
Framework: Identify churn reasons (exit surveys, support tickets) → Segment users (active vs at-risk) → Personalize engagement (triggered emails, in-app nudges) → Improve onboarding (most churn happens in first 7 days) → Loyalty programs → Measure with cohort analysis.
21. What do you know about our company? — Research their products, recent news, founding story, and mention something specific.
22. Are you comfortable working in night shifts / travel? — Be honest. Don't say yes if you'll say no after joining.
23. Do you have any questions for us? — Always ask. Good ones: "What does success look like in the first 90 days?" or "What's the biggest challenge the team is facing right now?"
24. How soon can you join? — Give your actual notice period. Don't promise faster than you can deliver.
25. Sell me this pen. — Ask about the customer first, then pitch based on their need. Show you understand sales is about solving problems, not pushing products.
26. How do you prioritize when everything is urgent? — Use a framework: impact × effort matrix, or MoSCoW (Must/Should/Could/Won't).
27. Describe your management style. — Give a real example of how you've led a team or project. Mix of coaching and accountability.
28. Tell me about a time you failed. — Pick a real failure. Show what you learned. Interviewers want self-awareness.
29. How do you handle ambiguous requirements? — Clarify, prototype, get feedback fast. Don't spend 2 weeks building the wrong thing.
30. What makes you the best candidate for this role? — Connect your top 3 skills to the top 3 requirements in the JD. Be specific and confident.
Reading answers isn't enough. You need to say them out loud, get feedback, and fix your delivery. Book a 60-minute live mock interview with our team — get a detailed feedback report.
🎤 Book Mock Interview (₹99)