Behavioral Questions

Question 1

Tell me about yourself

Answer 1

“Thank you guys for giving me this opportunity. As you know, my name is Jamee Chowdhury. Currently I am working for Playball, an app that helps people organize and coordinate soccer/football matches. Past 6 months, I’ve been transitioning to automation

Some of the tools I use are:
* Jira for bug tracking
* Cypress for UI/API automation
* Postman for API testing
* QaseIO for test case management
* GitHub actions for CI/CD

Question 2

What is your role?

Answer 2

I am responsible for QA related processes such as:
* Testing and verifying functionalities
* Test case documentation
* Writing and documenting test cases for tickets
* Executing tests such as functional, end-to-end, smoke, regression
* Automating those tests in a way that makes sense
* Checking for bugs and filing bug reports
* Joining different type of meetings

Question 3

Why did you decide to become a QA/software tester?

Answer 3

I wanted to work in a field where I felt life I work mattered so when my cousin told me to look into QA, it made sense to me because I think QA engineers play a crucial role in the development process, which is to make sure the product is up to par and it meets the expectations of the consumers. That’s why I’m passionate about this field.

Question 4

Is there anything different that makes you different from other candidates?

Answer 4

• I care about my work, I want to do it well
• I am also a team player. I get along with people easily, and working with teammates improves my own quality of work

Question 5

How do you deal with criticism

Answer 5

• I generally appreciate criticism because without it, I would never grow as a person
• I appreciate constructive criticism as it gives me the opportunity to grow and improve
• and even if the criticism isn’t constructive, I try not to take it personally and would try to see things from the other person’s perspective

Question 6

Assuming you are hired, how long do you expect to work for us?

Answer 6

I prefer to grow with a company so if I am satisfied with my company and my company is satisfied with me based on culture, performance, and professional growth, then I will most likely stay with the company

Question 7

What is the difference between smart work and hard work?

Answer 7

• Hard work, to me, seems likes it about throwing yourself at a problem and going at it until you’ve fixed it
• Smart work is also getting results, but with intelligent thought. So perhaps the result can be achieved in an easier way, or with less resource consumption
• But the two are not always mutually exclusive

Question 8

What is your biggest achievement so far?

Answer 8

I’ve created cypress test automation framework for my team from scratch

Question 9

Describe the three things that are most important for you in a job?

Answer 9

• Work culture
• The team
• Professional growth

Question 10

What are your greatest strengths?

Answer 10

• I think my greatest strength is actually what used to be my greatest weakness, which is communication. I’ve worked at it and can now communicate much easier.
• I am also passionate about my work. I don’t just want to get my work done, but also want it to be done well

Question 11

Greatest weakness?

Answer 11

• Shyness, lack of communication skills

Question 12

Where do you see yourself in 5 years?

Answer 12

• That’s a difficult question because 5 years is a long time from now but I hope to be in a leadership/mentorship position
• Not for sense of self-importance, but because I’ve benefitted a lot from the guidance of others, and I want to do the same for the next generation

Question 13

How to manage time and ensure quality of work?

Answer 13

• It helps to keep a list of priorities and have them ranked, and then work on a top down approach
• I can focus more time and effort for higher quality items
• If there isn’t enough time for lower priority items, I can try to get help from other team mates

Question 14

Tell me about yourself (alt)

Answer 14

My name is Jamee Chowdhury. I am a Software QA Engineer at playball, an app that helps people organize and coordinate soccer/football matches. My responsibilities include but are not limited to:
*Tickets testing,
* test case creation,
* and automation running regression and
other types of testing when needed,
* release verification,
* and communication.

Tools:
I utilize Jira as a bug tracking system, testrail as a test case management system, postman for manual API testing, GitHub as a code repository, VS Code as an IDE, cypress for UI/API automation testing I’m also familiar with SQL in case database manipulation needed. That is pretty much it.

Question 15

Why should we hire you?

Answer 15

I think it’s not just about you hiring me, but also about me choosing to work for you. I think both of us are looking for a good team to work with. Myself, I’m not looking to jump into just any job, but rather to find a good team where I will be able to make a difference, grow, support others, and simultaneously bring value to the company. And I hope you guys are also looking for the same thing

Question 16

Why did you leave your last job?

Answer 16

It was a contract

Question 17

Tell us about the most interesting bug you found?

Answer 17

Since there are so many bugs I’ve discovered in my testing career that I can’t really remember most of them. One of the most recent ones would be the username boundary bug. When I was able to register with 18 characters username but wasn’t able to log in as 15 characters were max.

Question 18

Talk about a conflict or challenge you faced at work, and how you handled it?

Answer 18

I don’t take anything personally. If someone has an issue, I would simply listen to that person, see where they are coming from, and try to solve it to the best of my ability. If the person still feels like there is a conflict between, I would contact my manager and ask for assistance

Question 19

Are you better working in a team or working alone?

Answer 19

I get along with people very well and I like to work in a team, so I do think that the quality of my work improves when I am working with reliable teammates. I think tasks can be done more efficiently when you have access to the different perspectives different people bring

Question 20

What did you do in your last project?

Answer 20

In the last project, I was the only QA in the team, so I was responsible for all of the QA processes including but not limited to:
* tickets testing
* test case creation
* running regression upon every release
* automating test cases
* attending daily stand-ups to share our updates
* help new team members learn our application

Question 21

What personal qualities must be present in your potential manager

Answer 21

• Good interpersonal skills are the most important, which includes good communication skills
• Can adapt to different situations
• good technical skills - has understanding of testing methodologies, tools, and technologies to guide the testing process
• Looks out for their team, makes sure everyone has everything they need to perform to the best of their ability
• Quality advocate - committed to upholding quality standards

When communicating with the QA manager on a daily basis, the employee should feel confident and comfortable

A good skill for any manager is the ability and experience in managing a group of people who are previously united to solve a specific problem. In my understanding, this is a person who can prioritize and, with the help of their subordinates, achieve all assigned tasks

Question 22

To what extent should devs do their own testing or do you believe testing is the responsibility of the QA team?

Answer 22

I do think that if a dev does at least some testing, they develop a sense of ownership. I believe that that results will improve if all parties have access to test cases and can run and access them regularly to verify if the latest changes brought any regression

Question 23

Describe a challenge you faced during your last project?

Answer 23

During the last project, we had biweekly release, which would carry sometimes hundreds of tickets. And every time we would find on average 10-20 bugs. That was a very efficient process so after brainstorming, we decided to do daily releases which have decreased the amount of tickets tremendously and made everyone’s job easier