How to Talk About Resume Projects in an Interview

To talk about a project from your resume, lead with the project that matches the job, give a two-minute answer that is mostly about what you did and why, and say plainly which part was yours when it was a team effort. Then expect follow-up questions on your contribution, your reasoning, what went wrong and what you would change.

This page goes deeper on projects than the general guide to interview questions based on your resume. The guidance comes from university career centers and departments, all listed in the sources.

What does an interviewer want from a project answer?

More than a description of the project. Three university sources describe what interviewers listen for when they ask about past work:

• Columbia University’s Department of Computer Science tells students to be ready to discuss the resume in depth: “The interviewer isn’t going to just ask about what you did in previous jobs or projects. They are going to want to hear about challenges you faced, failures you overcame, successes that you are particularly proud of, leadership roles you took on, etc.”
• The University of Texas at Austin’s College of Natural Sciences career office advises students to go through their technical projects and “be prepared to answer questions regarding your contribution, learning and how you dealt with any issues that arose.” In its notes on answering technical questions, the same page adds: “The reasons for the choice are more interesting than the choice.”
• Princeton’s Center for Career Development, on the question “Tell me about your senior thesis,” says interviewers “may be intrigued by the process as well as the content of your study.” That line is about independent research. This guide applies the same point to other projects.

Taken together, a project answer has four jobs: show your own part, show your reasoning, show how you handled a problem, and show what you took from it. A tour of the project’s features does none of the four.

Which project should you lead with?

When the question is open (“Tell me about a project you worked on”), you choose. Choose by the job, not by pride.

1. Read the posting first. MIT’s career office recommends reviewing the job description and role responsibilities, “paying close attention to the usage and frequency of certain action verbs.” The verbs that repeat tell you which skills the answer has to show.
2. Prefer the bigger, longer project. Washington State University Vancouver’s School of Engineering and Computer Science tells graduating students to highlight “larger projects that spanned longer periods of time” and that built skills “directly relevant to the jobs and internships to which you are applying.”
3. Check that your own share is large enough. Most of the answer will be about your actions, so a well-known project where you did a small piece is a weaker choice than a modest one you drove.
4. Check that you can explain every decision in it. If you cannot say why something was done the way it was, the follow-up questions will show that.

Keep a second project ready. The interviewer may pick a different line from your resume, or ask for another example after the first.

A structure for a two-minute project answer

Why two minutes. Ohio State’s Fisher guide tells students practicing STAR answers to aim for “two to three minutes per question”, and the University of Chicago’s career office says to use STAR while “aiming for 2–3 minutes per response.” None of the pages checked sets a length for project answers in particular. Two minutes is the short end of that range, and it leaves the interviewer time to ask about the parts they care about.

How to divide it. MIT’s career office attaches percentages to the four parts of the STAR method and says they “represent the time to dedicate to each section of your story.” The seconds in the table are plain arithmetic on those percentages for a two-minute answer.

Part	MIT’s share	In a two-minute answer	What goes in it for a project
Situation	20%	about 24 seconds	What the project was, who it was for, team size, how long it ran
Task	10%	about 12 seconds	The part you were responsible for, and the goal
Action	60%	about 72 seconds	The steps you took, how you took them, and why
Result	10%	about 12 seconds	What happened, how you know, what you learned

MIT adds that the numbers are a guide and that “most of your response should focus on your Actions.”

Three details from other career centers adapt the structure to projects:

• Give scale in the setup. Princeton’s interview guide, in its advice for “Tell me about yourself,” suggests giving context such as “how much time went into a project or the level of autonomy and responsibility you had.” The same context fits the setup of a project answer.
• Say why, not only what. Princeton’s version of STAR breaks the action into “Steps you took,” “How you took them” and “Why you took them.”
• End by tying back to the job. UC Irvine’s career office teaches a variant it calls B-A-R-T: Background, Action, Results, Tie Back. In its sample answer, the last step says what the student learned and links it to the role being interviewed for.

Example answer — new graduate, software role, “Tell me about a project on your resume.” This example was written for this guide. The course project and the clinic are generic, not real.

Situation

Task

Action

Result

1. Situation

   In my senior capstone course, a team of four built an appointment scheduling tool for a local nonprofit clinic that was booking visits by phone and on paper. It ran over two semesters.

2. Task

   I owned the booking logic and the database. The goal was a tool the front desk could actually use by the end of the course.

3. Action

   I interviewed two front-desk staff to learn how double bookings happened, then designed the tables so a time slot could only be held once. I first checked for conflicts in the application code, found it failed when two people booked at the same moment, and moved the rule into the database as a unique constraint. I wrote the tests for booking and cancelling. The reminder emails and the calendar screen were my teammates' work, and I reviewed their code.

4. Result

   We delivered the tool and presented it to the sponsor in April. In a two-week trial the front desk recorded no double bookings. If I did it again I would put it in front of the staff a month earlier, because the biggest changes came from watching them use it.

A tie-back sentence to finish: “That is the kind of work I would want to do here: learning how people really use a system before deciding how to build it.”

Team projects: how do you state your own share honestly?

Three career centers give the same instruction in different words:

• MIT: show ownership with “I” statements, because using “we” statements “can make it difficult for an employer to have a clear understanding of what your skills are. Instead, focus your response on how you contributed to the outcomes of the team efforts.”
• Princeton: “If the story involves being part of a group, be careful not to overuse ‘we’ - focus most of your response on your individual role/contributions.”
• Ohio State’s Fisher guide: in the Action step, “be sure to emphasize your individual contributions.”

Honesty cuts both ways. Overclaiming carries a risk: MIT warns that an answer that is not truthful “may not match up with your application materials” or with “what a referral has shared about you,” and Washington State University Vancouver tells students that a resume “should be 100% honest.” Underclaiming, by hiding behind “we”, leaves the interviewer with nothing to assess.

A pattern that does both:

1. One sentence for the team. Size, goal and result. For a question about a group project where one member was not carrying their weight, Princeton’s advice is to frame the story “with the context of the group’s goals and your individual role in the group.”
2. Switch to “I” for your part. Name the piece you owned and the decisions you made in it.
3. Say what the others did. Naming a teammate’s part shows where your own part ends.
4. Attach the result to the right owner. The team’s result is the team’s. Your result is what your part made possible.

Example — experienced candidate, marketing analyst at an invented regional grocery chain. Written for this guide.

If the interviewer asks about a teammate who did not deliver, Princeton’s guide says interviewers are looking at “how you position yourself in the group, how you communicate with your peers, and how you embrace or resolve conflict,” and advises: “Display empathy for the team member who held up the project or take ownership if it was you.” There is a full example under tell me about a successful team project. When a number on your resume was a team number, see how to defend the numbers on your resume.

Course, capstone and personal projects for new graduates

A class project is an expected example, not a fallback. Washington State University Vancouver’s engineering school writes that employers hiring soon-to-be and recent graduates “often expect to see project-based experience on their resumes,” and that class projects are “a great way to help employers understand how the skills you gained in college have helped prepare you” for the job.

• Call it what it is. The resume format that guide recommends names the class and the dates. Do the same aloud: “In my senior capstone course…” Presenting an assignment as something more is the kind of stretch the same guide warns against.
• Capstones with a sponsor. The guide says “Be discrete and maintain confidentiality, you may not be able to identify the company you worked with,” and suggests generic identifiers “such as local electronics or manufacturing company.” That advice is written for the resume. It applies equally when you speak, so check what you agreed to before you name a sponsor.
• A thesis or independent research. Princeton’s guide advises students to speak concisely “about why you chose this topic and summarize the major steps you took and research sources you used,” and to quantify “the length or scope of your project.”
• Software course projects. UC Irvine’s career office lists this sample technical question: “Have you been involved in any school project that included all phases of the software development life cycle?” Be ready to say which phases you did yourself.
• Say what you learned. In the Washington State guide, the Result step includes “what you learned from this experience and how you would approach a similar situation in the future.”

Personal projects. The career center pages checked for this guide give no separate advice for personal projects, so this paragraph applies the guidance above and is not a sourced rule. Nobody assigned the project, so “Why did you build this?” is the natural first follow-up, much like Princeton’s “why you chose this topic.” State its real status: finished or not, and whether anyone besides you uses it.

Before you apply, make the resume and your spoken account agree. Our recommendation is to identify a course project as coursework, name your own deliverable and separate team outcomes from individual work. A project that is not deployed should not be described as serving real customers. You can use the resume builder to edit the project section, but its rule-based score cannot verify that a claim is true.

If projects are your main evidence for a move into a new field, see how to explain a career change against your resume.

What follow-up questions does a project answer invite?

A two-minute answer is the start of the conversation. The wording of each follow-up is this guide’s own. The second column gives the source line it is inferred from.

Follow-up	Why to expect it	What to prepare
“What exactly was your part?”	UT Austin lists “your contribution” first. MIT and Princeton both warn about “we”.	A one-sentence split: your piece, then your teammates’ pieces
“Why did you do it that way?”	UT Austin, on technical answers: the reasons are “more interesting than the choice.” Columbia’s computer science department, on software design: “expect to have to defend your design choices.”	One alternative you considered and why you rejected it
“What went wrong?”	UT Austin: “how you dealt with any issues that arose.” Columbia: “challenges you faced, failures you overcame.”	One real problem, what you did about it, how it ended
“What would you change?”	Princeton’s STAR outline has candidates cover “What might you change if faced with the same situation” in the Result step.	One specific change, not “nothing”
“How big was it?”	Princeton, on thesis questions: “Quantify the length or scope of your project.”	Duration, team size and the real scale of the work
“How did the team work together?”	Princeton: interviewers watch “how you communicate with your peers.”	How the work was divided, and one disagreement and how it was settled

How to prepare your project answers

1. Outline, do not script. MIT recommends preparing 3 to 5 stories as bulleted outlines, because scripting or memorizing “may limit your ability to adapt as needed in an interview.”
2. Write the six follow-up answers under each outline. One or two lines each.
3. Say each answer aloud with a timer. If it runs past two and a half minutes, cut the setup, not the actions.
4. Check what your resume invites. The free resume interview questions tool turns a resume into the questions it is likely to raise, each tied to the resume line behind it, which shows the projects an interviewer is likely to open.

For the opening question that asks for your whole background, see walk me through your resume.