How to Answer Tell Me About Yourself in a Job Interview

Everyone tells you to use the present-past-future formula. I think that is overrated.

Not wrong. Overrated. The distinction matters. Present-past-future works. It produces a competent, organized answer. You describe your current role, mention how you got there, and connect it to the job you are applying for. It is clean. It is logical. And after a decade of career coaches recommending it, it is also what literally every other candidate in the waiting room is going to say.

The interviewer hears some version of "I am currently a [role] at [company], where I [responsibility]. Before that, I [past role]. I am now looking for [future goal], which is why I am excited about this opportunity" fifteen times a day during hiring season. By the fourth candidate, the words start to blur. By the tenth, the interviewer is listening for anything that sounds different. And all they are getting is the same structure, the same professional language, the same carefully rehearsed bridge from past to present to future.

So the question becomes: is there something better?

The Problem With Formulaic Answers

The present-past-future formula was good advice when it was new. It solved a real problem: candidates who rambled through their entire life history, starting with their tenth standard board results and ending somewhere around their latest project, leaving the interviewer buried under five minutes of chronological autobiography.

The formula gave structure to what was previously a mess. But now the structure has become its own kind of mess. Every prepared candidate delivers a version of the same template. The individual details differ, but the arc is identical. "I am currently... before that... and now I am looking for..." It is like watching contestants on a cooking show who have all been taught the same plating technique. The food might be different, but it all looks the same on the plate.

And this is the part I am genuinely uncertain about: does it actually matter? Do interviewers notice the sameness? Or is the formula so expected that deviating from it creates confusion rather than differentiation?

I think it depends on the interviewer. An HR screener who is running through 20 candidates in a day probably wants a clean, structured answer because it is easy to process. A hiring manager who has been in the industry for 15 years and has heard thousands of these answers might respond better to something that catches their attention. A startup founder conducting their own interviews might prefer a candidate who talks like a person rather than a prepared professional.

What Might Work Better (With Caveats)

One alternative is to lead with the thing you are most interested in right now, professionally. Not your title. Not your company. The actual problem or question that has your attention.

"For the last six months, I have been obsessed with reducing API response times at scale. Our team at [company] serves 200,000 merchants, and I redesigned the reporting module to cut load times by 60%. That project is what made me realise I want to work somewhere where performance engineering is not a side concern but a core part of the product. Which is why this role caught my attention."

This does several things the formula does not. It reveals what you actually care about, not just what you have done. It starts with a specific and memorable detail. It creates curiosity -- the interviewer wants to ask how you achieved that 60% improvement. And it connects to the role through genuine interest, not through the generic bridge of "which is why I am excited about this opportunity."

But here is my hesitation: I have seen this approach work well, and I have also seen it confuse interviewers who were expecting the standard format. One candidate I know tried a version of this at a large IT services company and the interviewer interrupted him to ask "But what is your current designation?" The deviation from the expected pattern was, for that interviewer, more disorienting than refreshing.

The Fresher Dilemma

For freshers, the present-past-future formula has a more specific problem: the "past" is thin and the "present" is barely started. A fresh B.Tech graduate applying to their first job does not have a professional present to describe or a career trajectory to narrate. So they fill the space with academic credentials, internship descriptions, and college project summaries. The result is often a list of items rather than a story.

"I completed my B.Tech from [college] with a CGPA of [number]. I did an internship at [company] where I worked on [technology]. My final year project was [description]."

Fine. Competent. Forgettable.

What if a fresher instead opened with what drew them to the field? "I got interested in backend development because of a problem I could not solve in my third year. A friend and I tried to build a small payment system for our college canteen, and the concurrency issues were so frustrating that I spent two months reading about distributed systems just to understand what was going wrong. I never fixed that canteen project, but that frustration is what led me to spend my final year interning at a fintech startup where I wrote APIs for their payment processing system."

That answer is less polished. It does not tick the boxes in the standard order. But it tells you something about the person -- what motivates them, how they think, what catches their attention. Whether an interviewer at TCS or Infosys would prefer it over the standard format, I genuinely do not know. At a product company or a startup, it would probably land well. Maybe.

The Experienced Professional Problem

Experienced candidates have the opposite issue: too much material. The standard advice is to be selective. Mention only the most relevant roles and achievements. Keep it to two minutes.

I mostly agree with this, but I think the conventional approach still misses something. Selectivity is necessary, but what you select matters more than how you order it. Most candidates select based on prestige -- their most impressive title, their biggest company name, their largest project. That makes sense from a credentialing perspective. But it does not tell the interviewer much about who you are as a professional.

An alternative selection principle: choose the moments that changed how you work. The project that taught you something you still use every day. The failure that altered your approach. The transition that forced you to rethink what you were good at. These moments tend to produce more interesting and more revealing answers than a highlight reel of titles and numbers.

"I spent five years at a services company writing code someone else designed. When I moved to a product company, I realised I had never made an architectural decision in my life. The first six months were humbling. I had to learn to think about systems differently -- not as something to deliver, but as something to own. That shift is the single biggest thing that has shaped how I work now."

Is that too vulnerable for an interview? Possibly. It admits a weakness. It describes a period of struggle. But it also demonstrates self-awareness and growth in a way that "I led a team of 12 and delivered the project on schedule" does not.

Tailoring vs Authenticity

Every guide on this topic tells you to tailor your answer to the role. Study the job description. Mirror its language. Connect your experience to their requirements. This is sound tactical advice.

But taken too far, tailoring becomes performance. If you study the job description so carefully that your answer echoes its keywords ("I am passionate about building scalable systems in a collaborative environment" when those exact phrases appear in the listing), you risk sounding like you reverse-engineered your personality to match their posting.

I do not have a clean solution to this tension. Tailoring is smart. Authenticity is persuasive. The two sometimes conflict. A candidate who is genuinely passionate about something the company does not care about faces a choice: suppress that passion in favour of alignment, or express it and hope the interviewer values the authenticity even if the topic is not directly relevant.

In practice, most people default to tailoring because it feels safer. And it probably is safer. But "safe" and "memorable" are different things, and the question of which one matters more in an interview is not as settled as most career advice suggests.

Practical Notes (Because Some Structure Is Still Useful)

Length: 90 seconds to 2.5 minutes. Shorter is thin. Longer tests patience.

Do not start with your name. The interviewer has your resume. "My name is..." wastes your opening.

Do not recite your resume. They can read it. Your answer should add something the resume cannot -- context, motivation, perspective.

Do not get personal unless it is relevant. "I was born in a small town in UP, my father is a government employee..." is a preamble that delays the useful content. Brief personal context is fine if it connects to your professional story.

Prepare multiple versions. A two-minute version for formal interviews. A 30-second version for networking. A technical version that emphasises skills and projects. An HR version that emphasises values and work style.

Practice aloud, not just in your head. An answer that reads well on paper can sound stilted when spoken. Record yourself, listen back, adjust. Three or four rounds of this makes the delivery natural.

Do not memorise word for word. Memorise the structure and the key points. Let the exact phrasing vary each time. Rehearsed scripts sound rehearsed.

Sample Answers That Break the Mold Slightly

For a developer role: "The thing I keep coming back to in my work is the question of how to make systems that do not break at scale. At Razorpay, I rebuilt the merchant dashboard's reporting module and brought load times down by 60%. That project taught me more about caching and database design than anything I had done in my previous four years. I want to keep working on problems where performance at scale is the central challenge, which is what this role seems to be about."

For a fresher: "I spent most of college thinking I wanted to do machine learning, and then during my internship at a fintech startup in Hyderabad, I discovered I liked building the infrastructure underneath it more than the models themselves. I wrote REST APIs for their payment system and got weirdly excited about getting the response times right. So now I am looking for a backend role where that kind of work is the main thing, not a side task."

For a career changer: "I worked in banking for six years. I was good at it -- I managed a portfolio of Rs. 800 crore and brought in Rs. 120 crore in new business last year. But what I actually spent my evenings doing was learning to code. I built a personal finance dashboard that started as a weekend project and turned into something that three of my colleagues used daily. That gap between what I was paid to do and what I chose to do in my free time told me something, and I am finally acting on it."

The Honest Position

I think the present-past-future formula is a useful default. If you are not sure what to do, it will produce a decent answer. It will not embarrass you. It will check the boxes that most interviewers expect. For high-stakes interviews at large companies with structured evaluation processes, it is probably the right call.

But I also think the best answers I have heard to this question did not follow a formula at all. They were specific. They revealed something about the person that was not on the resume. They made the interviewer lean forward instead of checking a box.

Whether taking that risk is worth it in your specific interview, at your specific company, with your specific interviewer -- that is a question I cannot answer for you. The safe path works. The interesting path might work better or might confuse the person across the table. The guides that tell you there is one right way to answer this question are oversimplifying something that is, in practice, a judgement call you make in the first 30 seconds of a conversation with a stranger.

I keep going back and forth on this. And I suspect that is the honest position.

How to Answer Tell Me About Yourself in a Job Interview