ANSWER GUIDE
Tell me about yourself
This is not an invitation to tell your life story. It is the interviewer’s first chance to see whether you can summarise your background in a way that is relevant to this job.
What the interviewer is checking
| Signal | What they listen for | What weakens the answer |
|---|---|---|
| Relevance | A background that connects to the role | A chronological tour of every job |
| Communication | A clear structure and a sensible length | Rambling until the interviewer interrupts |
| Career logic | Why this move makes sense now | “I just saw the job and thought I would apply.” |
| Evidence | One or two concrete achievements | Only adjectives and job titles |
| Fit | What you want to do next | No idea what the role involves |
The present–past–future structure
- Present. What you do now and the scope you own. One or two sentences. If you are a student or between roles, say what you are doing that is relevant.
- Past. The experience that makes you credible for this job. Pick the thread that connects to the role, not the most prestigious detour. One concrete result or decision.
- Future. Why this role, at this company, now. Connect to the job description without delivering a full “why this company” answer.
A good answer is 150–220 words. That is long enough to be specific and short enough that the interviewer can follow. If you are nervous, aim for 60 seconds and let the follow-up questions add depth.
Example: experienced candidate
I am a product manager on a B2B scheduling product, where I own the calendar and availability area. The work I am proudest of is a rebuild of the time-zone handling: we had a long tail of support tickets from teams booking across regions, and I worked with two engineers to simplify the model rather than patch each case. Tickets in that category dropped by about half, and the sales team stopped treating it as a demo risk. Before product, I spent three years in customer support, which is where I learned to read a ticket queue as a product signal. I am looking for a role where I can own a larger surface and work closer to the infrastructure, which is why this platform team role caught my attention.
Why it works: it establishes scope, gives one specific decision with a result, explains the unusual career path, and ends with a reason for this role. It does not list every job or every tool.
Example: fresher
I have just finished a degree in information systems, and for the last six months I have been building a booking tool for a local sports club as a side project. I handled the requirements, the data model and the user testing, and the part I learned the most from was discovering that the coach did not want a dashboard — he wanted a weekly email. I have also done a summer internship in IT support, where I learned how to write a ticket that someone else can act on. I am looking for a junior product or analyst role where I can work on a real product with feedback, rather than another standalone project.
Example: career changer
I have spent four years teaching secondary science, and for the last two I have also designed the revision programme for my department. That work taught me how to break a subject into sequenced practice and how to tell whether a lesson actually changed what students could do. I am moving into instructional design because I want to solve that problem at a larger scale, for adults who are retraining while working. I have completed a short course in assessment design, but my main evidence is the programme itself: completion improved and the department adopted it for three year groups.
Adapt the emphasis to the role
| Role | Lead with | Keep brief |
|---|---|---|
| Software engineer | One system you owned, the trade-off and the result | The full stack list |
| Sales | The segment you sold to, the cycle and a number you can explain | Every product you have represented |
| Customer service | The channel, the customer type and a resolution outcome | A list of employers |
| Nurse | Your registration, specialty and a patient-safety example | The full placement list |
| Fresher | A project, internship or transferable job and what you learned | Every course module |
| Career changer | The transferable mechanism and the evidence | An apology for changing careers |
The mistakes that cost you
- Starting at the beginning. “I was born in…” or a full chronological history loses the interviewer in the first 20 seconds.
- Reciting the resume. They have it. Use one detail per beat to make it memorable.
- Too much personal detail. Keep the answer professional unless the personal detail explains a career decision.
- No reason for the role. “I am looking for a new opportunity” is not a reason. Connect to the job description.
- Talking for three minutes. The interviewer will interrupt, and you will lose the structure. Practise a 60-second version.
Follow-up questions to prepare for
- “Why are you leaving your current role?” — answer forward-looking, without criticising your employer. Prepare the adjacent “why this company” answer with the why do you want to work here guide.
- “Walk me through your resume.” — have a 30-second version that connects the dots; do not repeat the full answer.
- “What gap are you worried about?” — name one real gap and the plan to close it.
- “Why this role now?” — connect the timing to something specific, not “I am ready for a new challenge”.
A 20-minute practice plan
- Write the three beats in note form, not a script. One line each.
- Say it out loud and time it. Cut anything over 90 seconds.
- Record it once and listen for filler, apology and unnecessary background.
- Rewrite the “future” beat so it mentions something specific from the job description.
- Ask a friend to interrupt after 45 seconds with “and then what?”; practise finishing cleanly.
These guides are written and maintained by MockInterview as original practice material. They are not leaked employer questions, and no employer has reviewed or endorsed them. Sample answers are illustrative; use your own examples and verify role requirements, licensing and local policy with the employer. Last updated 2026-11-03.