“Tell me aboutyourself” — solved.

A simple three-part formula for the question every interview opens with, built for candidates with only college projects and internships to draw on. Five sample scripts, by branch, to adapt.

60-90 secondspresent, proof, future
Five scriptsCSE, ECE, Mech, BCom, MBA
Common mistakesto avoid

~15 seconds

Present

Who you are, right now: your degree, branch, and the one area you have focused on. Not your whole academic history — one clear sentence.

~40 seconds

Proof

One project or internship, told as a small story: what the problem was, what you actually did, and a result — even a small, honest one (it worked, it got used, it was well received in a review).

~20 seconds

Future

The specific role or kind of work you want next, and why it connects naturally to what you just described. This is what turns the answer into a pitch, not just a summary.

Five sample scripts, by branch

Templates to adapt, not to read word for word. Fill in your own details and say it out loud until it sounds like you, not a script.

CSE / IT

“I'm a final-year Computer Science student, and over the last year I've focused mostly on backend development. My main project was a [type of app] built with [stack] — I designed the database schema and built the API layer, and by the end it was handling [a real, small result: a demo with real users, a specific feature working end-to-end]. I'm now looking to join a team as an SDE or backend developer where I can keep building things people actually use, and learn from engineers more experienced than me.”

ECE

“I'm a final-year Electronics and Communication student with a focus on embedded systems. For my final-year project, I built a [device/system] using [microcontroller/tools] — I handled the hardware interfacing and firmware, and got it to [a concrete result: reliably read sensor data, run for X hours on battery, pass a specific test]. I'm now looking for a role where I can work on embedded or hardware-adjacent systems and keep building things that operate in the real world, not just on a screen.”

Mechanical

“I'm a final-year Mechanical Engineering student, and I've spent most of my final year on design and simulation work. My main project was a [component/system] I designed in [CAD tool] and validated with [analysis method] — I iterated through a few designs before landing on one that met the [specific requirement: weight limit, stress tolerance, cost target]. I'm looking for a design or quality role where I can keep working hands-on with real hardware and see a project through from concept to something built.”

BCom

“I've just finished my BCom with a focus on finance and accounting. During my internship at [company/type of firm], I worked on [specific task: reconciling accounts, building a reporting sheet, assisting an audit], and by the end I was handling [a concrete responsibility] independently. I'm now looking for a role in finance or accounts where I can build on that and take on more responsibility, ideally somewhere I can also pick up a specific tool like [Tally/Excel/SAP] in more depth.”

MBA

“I've just completed my MBA with a specialisation in [marketing/finance/operations]. During my summer internship at [company], I worked on [a specific project: a market analysis, a process improvement, a campaign], which resulted in [a concrete outcome, even modest — a recommendation that was adopted, a process that saved time]. I'm now looking for a role where I can apply that same problem-solving approach, ideally in [specific function or industry], and grow into more ownership over time.”

Common mistakes

Starting from childhood or school. Interviewers want the last 2-3 years, not your entire biography.
Listing every project you have ever done instead of one, told properly. Breadth without depth is forgettable.
Ending with no clear direction — "I am open to anything" gives the interviewer nothing to connect you to the role.
Reciting the resume verbatim instead of telling it as a short story with a beginning, a decision, and an outcome.
Going over 90 seconds. Interviewers tune out a rambling opening answer, and it costs you time for the questions that actually differentiate you.
Memorising it so rigidly that it sounds robotic. Know the structure cold, but let the wording vary naturally each time.

Practise it out loud

Run this alongside the rest of the interview bank.

This is the opening question. The interview practice tool has role-specific questions to build the rest of your answers.

Practise interview questions

Keep going

Campus placement checklist Asking for a referral How large employers hire All fresher guides

QUESTIONS? WE'VE GOT ANSWERS

Common questions

The opening question, solved

Should the answer be exactly the same every time I interview?

The structure should stay the same, but tailor the "future" part to the specific role and company each time, and lead with whichever project is most relevant to that particular interview if you have more than one to choose from. A fixed script recited identically every time tends to sound rehearsed rather than confident.

What if I genuinely have no internship, only college projects?

That is completely fine — lead with your strongest project instead, told with the same structure: what the problem was, what you did, and a real result. A college project you can speak to in real depth is more compelling than an internship you can only describe vaguely.

Is it okay to mention a hobby or interest outside academics?

Only if it is genuinely relevant to the role or shows something useful about how you work (you run a small YouTube channel that taught you public communication, you organise a club that shows leadership). If it doesn't connect to anything the interviewer will care about, it uses up time better spent on your proof.

How do I practise this without sounding memorised?

Practise the structure and the key facts out loud several times, in slightly different words each time, rather than memorising one exact script word for word. Recording yourself and listening back is the fastest way to catch when it starts sounding robotic.

Should I mention weaknesses or gaps in this answer?

No — this question is an opening pitch, not a self-assessment. Weaknesses have their own separate question if the interviewer asks for one; folding them in here just weakens your opening unnecessarily.

What if the interviewer interrupts partway through?

That is normal and not a sign you did something wrong — interviewers sometimes redirect based on what interests them. Answer the interruption, then look for a natural moment to circle back to your "future" point if it didn't come up, since that is the part that sets up the rest of the conversation.

Still have questions? We're happy to help.

Email us We usually reply within a day