Prepare a short and an extended self introduction using the same facts. The shorter version gives the interviewer a clear starting point. The longer version adds one relevant example when time and interest allow.

You do not need two different personal stories. You need a stable core and a removable layer of detail. That makes it easier to adapt when someone asks for a brief overview or interrupts with a follow-up.

What belongs in the stable core?

  • Your current role, study or professional focus.
  • One relevant strength supported by actual work.
  • Your reason for considering this role.

Write those facts before choosing a duration. A time target is a rehearsal aid, not a guarantee that every interviewer wants an answer of exactly that length.

Illustrative short version

Fictional sample: “I am a junior developer focused on user-facing web features. My recent project work includes form validation and accessible error feedback. I am interested in this role because I want to develop those skills in a team that reviews and tests features together.”

The sample is constructed. Replace the role, project and motivation with your own facts. Do not keep a claim merely because it sounds polished.

What can the extended version add?

Fictional extension: “In one practice project, I noticed that a failed save cleared the user's input. I changed the flow to retain the draft and show a retry message. I checked success and failure separately. That experience made me more interested in how small interaction choices affect whether a feature is usable.”

This adds a problem, an action and a check. It does not repeat the opening with more adjectives. In your own extension, use an experience you can explain under follow-up questions.

How do you shorten without losing meaning?

Remove background that does not affect the role connection. Replace a long tool list with the type of work you used the tools for. Keep the contribution and the reason for applying.

Do not remove all evidence until only “I am hardworking and passionate” remains. A short answer still needs one concrete anchor. The aim is selective detail, not a collection of generic traits.

How do you extend without rambling?

Add only the next useful layer. After the core, introduce one example and stop at its result. If the interviewer asks about another part of your background, follow their question instead of returning to the rest of your planned speech.

Keep the facts consistent across versions. If a short version says you led a project while the longer version reveals you only observed it, the shortening has changed the truth.

Practice switching versions

Ask a partner to say either “brief overview” or “tell me more.” Give the core first, then add or omit the example. Have them interrupt once with a natural question so you practice responding rather than reciting.

Afterward, check whether both versions communicate the same role, contribution and motivation. Keep a few prompts instead of memorizing every sentence. A flexible introduction is easier to deliver naturally and easier to keep accurate when the conversation changes.

References and next practice

careerservices.fas.harvard.edu — career

Browse interview topics · Practise a question in Interview Challenge · Tell Me About Yourself: An Answer Framework You Can Adapt