Learn Selenium and Java for Selenium

Wednesday, 30 May 2018

How to explain a project in testing interview?


After giving introduction about yourself, the next question that will be asked to you is – Tell me something about the last project you worked on?

This is one of the most frequently asked question in any interview. Isn’t it? Have you goggled it anytime to find out the correct answer? 

Well, I have done that when I was a fresher. : ) Gradually, over a period of few years, I learnt the technique and now I think I can explain any project which is showing up in my resume in an understandable format to anyone.


Thinking, HOW?


It’s very SIMPLE. Your interview result depends upon a lot on the way you explain your project in the interview.


Work for you to do:  You must have worked for minimum 6 months or 1 year on this project, right? So, it’s your responsibility to understand the project architecture. Understand the application behaviour. How does your application (AUT) works? You should know how many modules are there in your project? How do they connect with each other? What happens when you click on module 1 and module 2 or module 3? Are they interconnected? What is end to end functionality? Even, if you have been assigned with only 1 module, you must know about other modules in the application as well. Once you are aware of these things, you can explain the project well.


Explain in this way: What was your role? What did you test? Which testing you performed? Which technology you worked on?Which tools were being used for test case/test script designing, test case/script execution? Which tool used for defect logging and tracking? Was it only manual testing or automation testing too?


If you know answers to all the above set of questions, you are good. 

KEY to this question is – Communicate in such a way that the interviewer understands what you are saying.

BE CONFIDENT. SPEAK CLEARLY AND SPEAK TO THE POINT.

Example: I worked on ABC Project. This project has total 4 modules. I worked on B module. Explain the functionality flow. I was involved in writing test cases/designing test scripts for which we used <tool name>, we executed the test cases/test scripts<tool name>and while testing, we found bugs. For bugs, we used <toolname>. You can explain the framework if worked on automation testing. 


Note: You have to give the answer within 2-3 minutes so that interviewer can ask you further questions. Do not spend 5 minutes or more in explaining the project. You will miss the opportunity. Please do not bore the interviewer. Thanks for reading! I hope, it will help you. 

0 comments:

Post a Comment

Popular Posts

Recent Posts



Newsletter

Join our newsletter to get secret tips directly in your inbox!


*We Hate Spam!

Powered by Blogger.