How to answer “Tell me about yourself”: examples with and without work experience

Choose what this employer needs to hear

Penn Career Services recommends connecting your qualifications and experience to the role when preparing this answer. Use the job description to select your material. A QA opening that mentions testing and clear bug reports calls for different examples from a customer support opening.

Try a draft that takes about a minute to say, then time yourself at a comfortable pace. This is a practice target, not a hiring rule. Follow an interviewer’s stated time limit. If they ask you to walk through your resume, explain the relevant progression between roles rather than reciting every bullet.

The people, employers and projects below are fictional teaching examples written by Evarlio. Use their structure with your own facts. The advice concerns job interviews; an academic interview or a structured recruitment process may give you different instructions.

Sample answer with no work experience

Riley Chen is a computer science student expecting to graduate in June 2027. Riley is applying for a junior QA role that involves checking user flows and writing reproducible bug reports. In a four-person course project, Riley wrote Python input checks and manually tested a booking demo. There has been no paid internship.

“I’m Riley, a final-year computer science student, and I’m applying for junior QA roles. In a four-person course project, we built a booking demo. I wrote Python checks for invalid inputs and tested six booking scenarios, including duplicate requests and missing dates. When I found a problem, I recorded the steps and expected result so a teammate could reproduce it. That work made me interested in testing how an application behaves when people do something unexpected. Your role includes testing user flows and documenting bugs, which is the work I’d like to develop further. My experience so far is from coursework, and I’m ready to learn your testing process.”

The answer gives the interviewer something to ask about: a failed test, a reproduction step or the division of work. If you have no course project, look for a relevant volunteer task, personal project or part-time responsibility. Use its real context. You can describe a small contribution without opening with an apology for your experience.

Sample answer for an applicant with work experience

Leah Park has been an accounts assistant at the fictional Alder Studio since March 2024. Leah checks supplier invoices against purchase records, maintains an Excel exceptions list and sends unresolved items to the finance manager. Payment approval belongs to the manager. The target accounts payable role involves invoice checks and supplier queries.

“I’m an accounts assistant at Alder Studio, where I check supplier invoices against our purchase records and keep track of items that need clarification. I’ve been in the role since March 2024. A regular part of my work is maintaining an Excel exceptions list and asking colleagues for missing references before sending unresolved items to the finance manager. I enjoy following a discrepancy through until the next person has the information they need. I’m interested in your accounts payable role because it combines those invoice checks with more direct supplier queries. I’d like to build on my current experience in that part of the process.”

Write your own version, then prepare a longer answer

Use this outline as a first draft: “I’m [current role or course]. In [relevant setting], I [specific action] and produced [deliverable or verified result]. I’m interested in this role because it involves [responsibility from the posting], and I want to [honest next step].” Remove a bracket if you cannot fill it with a fact. Read the result aloud and replace phrases you would never normally say.

If the interviewer requests a three-minute introduction, expand the relevant example. For Riley, that could mean explaining one booking problem, how it was reproduced and what happened after the handoff. Then add a second experience only if it contributes something different. Prepare these details separately so you can also answer a short opening question without rushing.

When moving into a different field, name the connection and the gap: “My customer support work involved documenting recurring errors. I’m now studying software testing, and I want to develop that experience in QA.” Use this wording only if both facts are true; the new job title is your target, not a title you have already held.

Practice the questions your introduction invites

Ask someone to listen once and tell you what they think you personally did. If their answer is broader than your actual role, revise the wording. Record a practice answer if useful, check its length and try again from a few notes rather than memorizing every word.

For Riley, useful follow-ups include “Which scenario failed?”, “What did your teammate do?” and “How would you test that next time?” For Leah, they include “What information was missing?” and “Who decided whether to pay?” Prepare an incident for these questions. The STAR guide can help you develop that incident after you have given the short introduction.

Questions about interview introductions

Should I repeat my resume? Use the same facts, but explain the connection to this role. You do not need to read every date and duty. If the interviewer asks about a particular period, answer that question directly.

What should I leave out? In an ordinary job introduction, keep personal details that do not help explain your suitability out of the opening. A separate application form or a specific interview instruction may ask for other information. Check the requirements for your actual recruitment process.

Can I use the same answer everywhere? Keep a factual base, then change the example and reason for applying when the job changes. In Evarlio, review the saved job description and interview prep brief in the relevant application. Open your locally saved copy of the PDF you submitted as well; later edits to a resume may change the current draft. Keep subsequent interview notes with the application.