English job interview
“Tell me about a project you are proud of” – how to answer in an English interview
The interviewer wants evidence of your impact, ownership, and how you work with others.
Answer it out loud
Answer as you would in the interview (up to a minute). You see which parts of a good answer were there, fixes, and a stronger version of your own answer to say sentence by sentence.
Follow-up questions to practise
Words that fit this topic
Common exam vocabulary. Try to use some of them in your answer.
| initiative /ɪˈnɪʃɪətɪv/ | the willingness to take action without waiting to be toldI took the initiative to fix a reporting problem before it caused delays. |
| coordinate /kəʊˈɒːdɪneɪt/ | to organize people and tasks so they work well togetherI coordinated with finance and sales to collect accurate data. |
| deadline /ˈdedlaɪn/ | the final date by which something must be finishedWe finished the project two days before the deadline. |
| challenge /ˈtʃælɪndʒ/ | a difficult problem or situation that needs to be solvedThe biggest challenge was combining data from different systems. |
| efficient /ɪˈfɪʃənt/ | working well without wasting time or effortThe new process was much more efficient than the old one. |
| analyze /ˈænəlaɪz/ | to study something carefully in order to understand itFirst, I analyzed the errors in our monthly reports. |
| implement /ˈɪmplɪmənt/ | to put a plan or system into actionWe implemented the new dashboard after a short pilot. |
| measurable /ˈmeʒərəbl/ | able to be measured or clearly shown, often with numbersThe project had a measurable impact on accuracy and turnaround time. |
| outcome /ˈaʊtkʌm/ | the final result of an action or processThe outcome was faster reporting and fewer mistakes. |
| collaborate /kəˈlæbəreɪt/ | to work together with other peopleI collaborated closely with an analyst to build the template. |
A strong one-minute answer
One project I’m proud of was improving the monthly reporting process in my previous role. Our sales and operations data came from several spreadsheets, so preparing the final report took about three days and errors were hard to trace. I noticed the team was spending too much time checking numbers instead of using them, so I proposed building a shared dashboard and a standard template. I mapped the data sources, met with the main stakeholders to understand what they needed, and worked closely with an analyst to simplify the reporting flow. I also created a short user guide and walked the team through the new process. As a result, reporting time dropped from three days to one, and we had far fewer corrections. I’m proud of this project because it solved a daily problem, improved accuracy, and helped managers make decisions earlier.
Why it works
- It gives a clear situation, your specific actions, and a measurable result.
- It shows both technical problem-solving and teamwork across different functions.
- It sounds credible and concrete, with details that are easy for an interviewer to remember.
Common mistakes
- Describing the project too generally; instead, explain the problem, your role, and the result clearly.
- Talking only about the team and not yourself; instead, say exactly what you personally did.
- Choosing a project with no clear impact; instead, include numbers, changes, or business value.
More interview questions
Are you willing to relocate or travel?Can you explain the gap in your CV?Describe a time you worked in a team.Do you have any questions for us?How do you handle feedback and criticism?How do you handle stress and pressure?How do you prioritise your work?How do you work under tight deadlines?How would your colleagues describe you?Tell me about a challenge you overcame.Tell me about a conflict with a coworker and how you handled it.Tell me about a mistake you made at work.Interview practice