Sunday meetings.
On this Sunday every one was cool and calm (My developer friends), but the topic wasn’t.
One of my developer friend started abusing the interviewer we all were clueless then,
abuser said: guys I had been to an interview day before yesterday and the interviewer was so dum.
I: (interrupted him and questioned) How can you say that?
Abuser: He asked me a question which he didn’t knew so he was trying his hands on me or you can say he was playing with all interviewee life, does that soundzz good.
That’s it! That’s how we got our topic for this Sunday obviously “INTERVIEWS”.
As usual we had a bad (I mean great) debate on this topic, following is my observation and learning from this Sunday.
Interviewer a great personality who knows every thing, this is what interviewee thinks.
On the other hand it wouldn’t be wrong if I say while taking interview, interviewer changes their personality (splits) and act what they are not.
Its we who make an interview either boring or interesting, now you might have a question what is boring interview and what is interesting interview.
First let me tell you, the meaning of interview “a conversation in which two well-known person share their views, knowledge, etc” but do we really follow this, No, I don’t think so.
Coming back to boring and interesting part, when only interviewer questions and only interviewee answers this is a boring interview. Interesting, when interviewer and interviewee cross questions each other and both try to find solution automatically this becomes interesting one.
I don’t understand why people get scared of interviews, in fact if we see the other way round, it’s a great opportunity to meet some one who is more experienced and might have better knowledge.
Again questions raised which were a bit controversial or one which were left with silence.
I promise my self to ask these questions to my interviewers. I’ll seriously like to do that because I want to see the difference between answers of two interviewers.
QUESTIONS...
1. What makes you decide the eligibility for a tester?
2. What are the basic qualities you expect in a tester even when the word quality cannot be defined?
3. What is the definition of quality for you?
4. How do you judge (differentiate) testers ability?
5. How do you motivate testers?
6. What is your definition of software testing?
7. Do you really implement your definition in your testing?
8. What is a tester’s job except testing, according to you?
9. Why do we need a tester?
10. Does a tester add value to your product?
11. What is your qualification and designation in this company?
12. How testing standards are created and maintained?
13. What made you choose testing field?
14. According to you who are a perfect tester?
15. One thing that you don’t like about a fresh and experienced testers.
This questions are not just for testing Profession, you can interchange the word "testing" to your profession and try to get answers for yourself.
Please leave back your comments if you get an answer for a single question, from your comments someone or I might get educated, so leave back your comments to educate others...
Showing posts with label sunday. Show all posts
Showing posts with label sunday. Show all posts
Saturday, May 30, 2009
Monday, April 27, 2009
What a tester does?
My main focus is on what does a tester do?
Actually, on Sunday I met my social friends which are mostly developers as well as been in developing for a long time (experience, mini=1 max=5). They thought to blast me with their developing idea as we are aware, all the developers think testers are devils for them, God knows why and what makes them think that…
I tried to explain them the whole concept of testing and even why testing field has got a different position.
The place we met was CCD (café coffee day) and before this discussion started we had planned to leave that place within next half an hour but, would you believe that discussion continued for two hours with 25 coffees and 60 cigarette between 6 people (5 developers 1 tester) no one realized when, where and how time went on…
We all where enjoying the discussion because we included waiter, shop manager, parents, teachers, boy walking on road and even Gandhi-ji in examples to prove our respective points…
Slowly and steadily the topic started heating up and we all started shouting like any thing, believe me we all where like politicians shouting in parliament but, suddenly from some where the speaker (shop manager) came into picture and requested us to calm down, manager was a nice person coz twice he tolerated our noise but third time he pleaded us to leave the café so, we finished our topic and decided to meet up again on next Sunday with the same topic and same café. Left for our respective home (God save the ccd manager)
While returning back home I realized a pattern in different question asked by developers,
Eventually question where many but motive was the agenda, I went into flashback and re-winded all question and you know the entire questions where revolving around different patterns of questions which are as follows….
Agenda
1. Who is a tester?
2. What does Software testing mean?
3. Why testing came in software?
4. How testing should be done?
5. Why not developers can do testing?
6. Why do we need testers?
7. Value of testing?
8. Is testing good or bad?
9. Whom exactly testing benefits?
10. Why there is no qualification for a tester.
11. What a software tester does?
I explained them the entire 10 question but got a bit confused when question 11 came up to me, what a tester does? (And added the following point)
What actually a software tester do to a product, add value, add confusion, add in an extra brain or create misunderstanding. What a tester does? (I thought the best suitable answer would be “ Testing ” that is what a tester does isn’t it? )
But would like to here your comments on this question…
What a tester does in testing?
Actually, on Sunday I met my social friends which are mostly developers as well as been in developing for a long time (experience, mini=1 max=5). They thought to blast me with their developing idea as we are aware, all the developers think testers are devils for them, God knows why and what makes them think that…
I tried to explain them the whole concept of testing and even why testing field has got a different position.
The place we met was CCD (café coffee day) and before this discussion started we had planned to leave that place within next half an hour but, would you believe that discussion continued for two hours with 25 coffees and 60 cigarette between 6 people (5 developers 1 tester) no one realized when, where and how time went on…
We all where enjoying the discussion because we included waiter, shop manager, parents, teachers, boy walking on road and even Gandhi-ji in examples to prove our respective points…
Slowly and steadily the topic started heating up and we all started shouting like any thing, believe me we all where like politicians shouting in parliament but, suddenly from some where the speaker (shop manager) came into picture and requested us to calm down, manager was a nice person coz twice he tolerated our noise but third time he pleaded us to leave the café so, we finished our topic and decided to meet up again on next Sunday with the same topic and same café. Left for our respective home (God save the ccd manager)
While returning back home I realized a pattern in different question asked by developers,
Eventually question where many but motive was the agenda, I went into flashback and re-winded all question and you know the entire questions where revolving around different patterns of questions which are as follows….
Agenda
1. Who is a tester?
2. What does Software testing mean?
3. Why testing came in software?
4. How testing should be done?
5. Why not developers can do testing?
6. Why do we need testers?
7. Value of testing?
8. Is testing good or bad?
9. Whom exactly testing benefits?
10. Why there is no qualification for a tester.
11. What a software tester does?
I explained them the entire 10 question but got a bit confused when question 11 came up to me, what a tester does? (And added the following point)
What actually a software tester do to a product, add value, add confusion, add in an extra brain or create misunderstanding. What a tester does? (I thought the best suitable answer would be “ Testing ” that is what a tester does isn’t it? )
But would like to here your comments on this question…
What a tester does in testing?
Subscribe to:
Posts (Atom)