Tester interview questions and answers are completely based on the interview I and my friends attended during last years of working experience as Quality Assurance Testers. These SQA questions and scenarios are based only on real experience and were asked during actual QA interviews. Therefore, QA Tester who is looking for a Quality Assurance job will greatly benefit from this. If you are the first time job seeker as a QA Tester, then it can help you even better. Finally, if you are plant to attend an interview, you have to know these questions and answers by heart and must be very smooth in answering these questions. Practice in front of the friends or just a mirror, speak loud and clear. Most of the time, when you study the questions, you feel fine and feel relaxed, but the reality is, at the time of the actual interview, even though you feel you have the knowledge, cannot express it well. It may sound a little rough, but this is everyone’s hard experience. When you come out the interview door, you are deeply regretted. If you cannot remember these by heart, believe me, it may not work. Readers are welcome to post own questions and answers to the following SQA interview questions.

Tips for hiring good QA Tester

There could be a zillions reasons why flourishing QA Manager would wish for hiring crappy tester. May be QA Tester salary is not high enough, or there is a desire to increase the headcount of QA team. The most significant part for this would be to produce vague job posting for QA tester position, so that potential candidate would not figure out what the job is from the posting, so make the job posting count with these amazing features:

Programming experience :

No matter if you are planning to hire Quality Assurance Tester for manual QA tester job. Always demand several years of strong programming experience with C++, Java, Python, Perl, Ruby, C#, VB.NET, SQL and note that it should be requested as "Java or C++ or Python or Perl is required". It would help deliberately obscure what QA job actually entailed. It would be nice to use horrible spelling, for example "Pearl" instead of "Perl". You could also enhance requested for programming experience in QA Tester resume with listing of totally irrelevant acronyms, like "ASP.NET, Silverlight, WCF Services, J2EE, AJAX, ASP, HTML, DHTML, Web Services, ASP.NET AJAX, XML, XSL, IIS, LAMP, ZEND, AWT, SWT, J2EE, J2SE, J2ME, DHTML, HTML, XSLT, DTD, ASP, WAP, SOAP, JSON, SQL, EJB, JMS, MQ Series, JNDI, JDBC" and of course QA Tester should have experience on Window, Linux, Unix and Mac OS platforms with WebLogic, Tomcat, IIS, JBOSS and database knowledge with MS SQL, Oracle SQL, PostgreSQL and MySQL.

Defect tracking tools:

Always mention that several years of experience in the particular defect tracking tool is mandatory, from your Test Manager experience you know that it would take a years for QA tester who familiar with Bugzilla to find out how to submit bug report to Jira. In the same time try to never use any of the popular defect tracking tools like Jira, Bugzilla, Trac, FogBugz or at least specify a particular version number. For example, this would be the best "minimum of 3 years of Jira 4.2 experience" and it doesn't matter that this version hasn't been released yet.

Test automation tools:

QA job advertisement will be not complete without request for hands-on experience with test automation tools, framework and scripts. Once again it doesn't matter if QA Manager plans to hire manual QA Tester, test automation tools like HP QTP, SilkTest, Selenium, TestNg, TestNG, CPPUnit, Watir, JUnit, HTTpUnit, HTMLUnit, Mercury, Rational Robot, Eclipse TPTP, NUnit are required for any SQA Tester. One of the solutions would be to place request like "5+ years experience of writing, executing, and maintaining automated test in QTP or SilkTest or Selenium", but more winning would be to combine request for experience in one programming language, while requesting completely irrelevant testing framework. For example "Knowledge of Java and NUnit" or "Has knowledge of the entire Microsoft .NET + JUnit". You should never forget to indicate particular version number like HP QuickTest Professional 10.0, SilkTest 2010 or JUnit 5.

QA Testing terminology and methodology:

Test Manager always desire to hire SQA Tester who can embrace modern practices like agile and test-driven development, continuous integration. Why do not ask for several years of experience in the whole shebang of QA Testing methodology : white and black box testing experience, performance and load testing knowledge, proven track of exploratory and agile testing.

Quality Assurance and Software Testing Certification:

The certification is a must, every SQA Manager aware that QA certifications certifies that SQA Engineer is a great Tester who could test any application with the speed of light, so use the force and demand for

  • HP Certified QTP Professional
  • Certified Associate in Software Quality (CASQ)
  • Certified Associate in Software Testing (CAST)
  • Certified Test Manager (CTM)
  • Certified Software Quality Analyst (CSQA)
  • Certified Software Test Engineer (CSTE)
  • Six Sigma Black Belt Certification (SSBB)

Job posting buzzwords:

To increase the size of job posting for QA position, always include indication of HR department existence. Most likely every job application already developed a blind spot for these request, but you still must to have them:

  • Track record of completing tasks independently.
  • Ability to multitask several projects.
  • Strong attention to detail, quick learner, and ability to thrive in a fast paced, dynamic environment.
  • Must be responsible and accountable; enjoys managing and follows through on multiple complex projects with the involvement of multiple players.
  • Good communicator who possesses strong written and oral communication skills.
  • Enthusiastic and outgoing, excited about working at "company name" and possesses a positive attitude about the potential of this company.
  • Supportive, not just within the business unit but also cross-functionally supportive, with a "roll up your sleeves" attitude towards getting things done. Does not "pass the buck", even if it is not within your job description.
  • Must be an independent, self-motivated team player that is meticulous and methodical in creating solutions.
  • Produces high quality software within committed deadlines
  • Able to listen to and implement constructive criticism.
  • Well-organized and detail-oriented.
  • Demonstrates excellent analytical skills.
  • Thinks "out of the box" with ability to come up with creative solutions.
  • Strong team player.
  • Strong analytical and problem-solving skills.
  • Self starter that is process centric, standards and best practices driven.
  • Hands on and can give technical direction to the team.
  • Understands the importance of automation and know how to apply it to device testing.
  • Can effectively communicate across all levels within the company.

Job posting format:

Text of job posting should be crammed together, say no to bulleted lists, HTML, color or bold titles. It would make your job postings much more appealing to real QA Tester.

Submitting QA resumes:

In case a candidate got excited about future testing job and decided to click "Apply Now" button, make sure that QA Tester would be taken from job posting to your company website. It is crucial to artificially inflate the number of steps it takes to actually submit QA Tester resume. This could be done with forcing users to create accounts, lists of questionnaires and asking for proprietary and platform-specific QA resume format. For example, if you are hiring Unix/Linux QA Engineer request for resume in Microsoft Word format. It would be great idea for QA Manager to request submitting with resume samples of test plans, test cases, and bug reports from current or previous work

This post was made based on the actual job posting and I hope I didn't missed anything. In case QA tester would still decide to submit resume for this position, I will cover in the next part how to interview SQA Testers properly. If you really want to hire a good QA Tester, just do everything otherwise.

Related posts

  1. Top interview puzzle
  2. What makes a good QA Tester?

6 comments:

haroonmx said...

It seems like the writer is advocating a QA tester has to be a Jack of all trades. But in real life is it possible ? From employers' point of view, it's always nice to find someone who is capable of writing codes in C++ or Java but is it really possible to grab all the languages on which systems are developed ? We all have the idea how long it takes a programmer to be a "Programmer". In manual testing process, testers have to accomplish a series of works before actual testing is done with high level of accuracy and detailing to ensure system's expected quality. Though, I agree with some points that while doing automation, testers need to be excelled in Scripting language because of its undivided attachment to the testing tools.

Haron Deen
NY, USA

Anonymous said...

I am not agree ?? Knowledge of each field is preferable not a must.
A strong knowledge in Programming Tester can not test efficiently.
I agree that, knowledge of database is must, but not programming language is must.

Regards

Nihar Ranjan
QA Lead
Swash Convergence Technologies Limited.

Anonymous said...

I don't agree with 90 percent of this article. Additionally, i suggest the writer takes a course in English grammar.

Anonymous said...

The previous 3 commenters clearly have brilliant, analytical minds. Nothing at all wrong with their detection of sarcasm, no siree, nothing at all.

Anonymous said...

May be because of this article lots of company now demands Testers having programming language. If we love to do programming then why we choose to become tester, we choose Development.

And how can you be sure that who have knowledge of programming is better than who doesn't have programming skills.

Please change your thoughts and be practical.

Sorry for harsh comment.

Anonymous said...

Love this article and author's sarcasm and great effort to take a stab at how ridiculous and sometimes very thoughtless job descriptions are. I wouldn't be surprised if some mindless employer actually missed the sarcasm in this article and used material as-is in their job description... I have seen quite a few job descriptions like this.

Employers need to spend a little time in developing a reasonable job description which fits their needs and not an ambiguous copy/paste of random irrelevant technical jargon. It is very offensive and disrespectful.

I have abandoned many job applications because of vague and 'all over the place' job descriptions. I would rather work with an employer who respects my time as much as their own by providing clear and concise job description.

With all that said, I have come across some very well written job descriptions as well. So big thanks to those employers.

Common QA Tester interview questions