Career Advice

“Tell me about yourself” interview question (with answers)

The opening question that decides whether interviewers lean in or tune out—and how to answer it in 90 seconds.

UnoJobs Career Desk8 min read5.9K viewsWritten by Rhea AI

Career Advice

UnoJobs Desk

India hiring intelligence

“Tell me about yourself” interview question (with answers)

Practical hiring and career guidance from the UnoJobs editorial desk, built for India's fast-moving talent market.

You have 90 seconds to convince a stranger you're worth their company's time and money. That's the reality when an interviewer asks "Tell me about yourself"—the question that opens nearly every professional conversation in India's competitive job market.

This isn't small talk. It's a structured test of whether you can distill years of experience into a compelling narrative that matches what the company needs right now. Fumble it, and you spend the rest of the interview recovering lost ground. Nail it, and you've set the frame for everything that follows.

Why interviewers ask this question

Hiring managers use this opener for three specific reasons. First, they're evaluating your communication skills in real time. Can you organize thoughts clearly? Do you ramble or stay focused? Second, they're looking for narrative coherence. Does your career progression make sense, or does it look like random job-hopping? Third, they want to see if you've done basic homework about what matters for this role.

The question also serves a practical function. It gives interviewers time to settle in, review your resume one last time, and identify which areas to probe deeper. Your answer provides the roadmap for the next 45 minutes.

Companies hiring through UnoJobs report that candidates who structure this answer well tend to perform better throughout the interview. The correlation isn't mysterious. If you can't articulate your own professional story, you probably can't articulate solutions to business problems either.

The present-past-future framework

The most reliable structure follows a three-part sequence: where you are now, how you got here, and why you're interested in this specific opportunity.

Present (30 seconds): Start with your current role and your primary value proposition. "I'm a product manager at Razorpay, where I lead the merchant onboarding experience for our SMB segment. Over the past two years, I've shipped features that reduced drop-off rates by focusing on vernacular language support and simplified KYC flows."

Notice what this does. It names a recognizable company, specifies the function, and hints at measurable impact without drowning in numbers. You've immediately established credibility.

Past (30 seconds): Connect the dots backward. "Before Razorpay, I spent three years at Swiggy in operations, which taught me how to scale processes across tier-2 cities. I started my career at Deloitte doing supply chain consulting, which gave me the analytical foundation I use daily. The through-line has been solving problems for users who don't fit the typical metro, English-speaking profile."

This section should reveal intentionality, not accidents. Even if your path was messy, find the pattern. Interviewers want to believe you make deliberate choices.

Future (30 seconds): Tie it to the role you're interviewing for. "I'm here because your fintech infrastructure role combines my product experience with the technical depth I've been building. The challenge of designing for embedded finance particularly interests me, and from what I've read about your partnership with ONDC, you're working on exactly the kind of distribution problems I want to solve next."

This demonstrates you've researched the company and can articulate why this isn't just any job, but this job.

Sample answers for different experience levels

For early-career professionals (0-3 years):

"I'm currently an associate consultant at PwC in Bangalore, working primarily on digital transformation projects for retail clients. In the past year, I've been the lead analyst on three engagements, including a supply chain optimization project that I presented directly to the client's CXO team. I graduated from BITS Pilani with a degree in computer science, and chose consulting because I wanted broad exposure to business problems before specializing. I'm interested in this business analyst role at Flipkart because I want to go deeper on product and consumer tech, and your grocery vertical is tackling the exact kind of last-mile challenges I've been studying."

For mid-career professionals (4-8 years):

"I'm a marketing manager at Zomato, where I run growth campaigns for our Zomato Gold subscription product across six cities. My team's campaigns contributed to a 40% increase in Gold subscriptions in tier-2 markets last year. Before this, I spent four years at Unilever doing brand management for personal care products, which taught me mass-market consumer behavior. I started in advertising at Ogilvy right after my MBA from FMS Delhi. The common thread is understanding what drives consumer decisions in value-conscious markets. I'm exploring this role at Meesho because your focus on tier-3 and tier-4 commerce is where I think the next decade of Indian consumer internet gets built, and I want to be part of that."

For senior professionals (8+ years):

"I currently lead the engineering team for lending products at CRED, managing about 25 engineers across backend, mobile, and data. We've built the credit line product from zero to processing over ₹500 crore in disbursements monthly. Before CRED, I was an engineering manager at Ola, where I worked on the driver app and payments infrastructure. I started my career as a developer at Cisco in Bangalore after my engineering degree from NIT Trichy. What's drawn me through these roles is building reliable systems at scale for India's unique constraints—intermittent connectivity, diverse devices, complex regulatory requirements. This VP Engineering role at your company interests me because you're at the stage where foundational architecture decisions will determine whether you can scale, and that's the inflection point where I add most value."

For more guidance on structuring your overall interview strategy, see our guide on common interview questions and answers.

Common mistakes to avoid

The biggest error is treating this as an invitation to recite your entire resume chronologically. "I was born in Jaipur, then I went to school, then I did my engineering..." Stop. No one asked for your autobiography.

Another trap is being too modest or too vague. "I'm just a simple developer who likes coding" tells the interviewer nothing useful. Specificity builds credibility. Name technologies, projects, outcomes.

Equally damaging is the opposite: overselling with inflated claims. "I single-handedly increased revenue by 300%" raises immediate skepticism. If you're going to cite impact, make it believable and acknowledge team contributions.

Many candidates also make the mistake of not tailoring the answer. Using the same script for a startup and a multinational corporation signals you haven't thought about cultural fit. A startup role might value scrappiness and wearing multiple hats, while an enterprise role might prioritize process discipline and stakeholder management.

Finally, avoid ending weakly. Don't trail off with "So, yeah, that's about it." End with energy and intention. Your last sentence should reinforce why you're sitting in that room.

Handling follow-up questions

Your answer will trigger follow-ups. Prepare for them. If you mentioned a specific project, be ready to go three levels deeper: What was the problem? What alternatives did you consider? What would you do differently now?

If you cited a number, expect questions about methodology. "You said you increased engagement by 35%. How did you measure that? What was the baseline? What other factors might have contributed?"

If you mentioned a skill gap you're trying to fill, they might probe your self-awareness. "You said you want to build more technical depth. What have you been doing to develop that? What's your learning approach?"

The best defense is honesty and preparation. Don't claim expertise you don't have. If you mentioned something on your resume or in your intro, you've made it fair game for questioning.

For more on handling behavioral questions that often follow this opener, check out our article on behavioral interview questions.

Adapting for virtual interviews

In 2026, many first-round interviews still happen over video. The core structure stays the same, but delivery matters more. You don't have physical presence to carry you, so vocal energy and eye contact with the camera become critical.

Keep your answer slightly shorter in virtual settings—closer to 75 seconds than 90. Screen fatigue is real, and attention spans are compressed. Practice looking at the camera, not the screen, when delivering your key points.

Have a clean, distraction-free background. Technical glitches happen, so if your internet cuts out mid-answer, don't panic. Reconnect and offer to briefly recap. Interviewers are humans who've dealt with the same issues.

Key takeaways

  • Structure your answer in three parts: current role and value, career progression with intentionality, and specific interest in this opportunity
  • Keep it to 90 seconds maximum—long enough to establish credibility, short enough to maintain attention
  • Use specific examples, recognizable company names, and realistic impact claims rather than vague generalities
  • Tailor your narrative to match what the role and company actually need, not a generic script
  • Prepare for follow-up questions on anything you mention, especially quantified achievements or skill gaps

Ready to put this into practice? Explore opportunities matched to your experience level and career goals on UnoJobs, where you can filter roles by function, location, and company stage to find positions where your story will resonate.

Share

Keep growing with UnoJobs

Want more career insights like this?

Explore hiring intelligence, interview playbooks, and job-ready guides from the UnoJobs editorial team.