121

I would push back hard on this question. An interview question is a machine designed to extract a signal from a candidate. Let's examine the parts of this machine. "The most" has already been commented on. Why is it important that the answer be the most interesting? Why are you asking the candidate to solve an optimization problem in your interview? If ...


76

This may be culture-specific, but from my point of view, you’re asking for someone to work for free. The interview should be the interview; you don’t ask someone to do more work after the interview. And from your point of view, how do you know you can trust that the person in question was the one who did the homework? If you want them to do some live ...


36

In addition to what everyone else has said, it's absolutely realistic. With respect to what the hiring agencies are telling you, here are some reasons you could find difficulty convincing a developer that they want to be part of the test team: if your automation specialists are paid significantly less than your developers, you'll be asking any developer to ...


35

Continue testing in this situation would be counter-productive and may lead to a "deadlock" - when the reported issues would depend on each other recursively. make sure the management is aware of the situation sit down with the development team - determine the most critical and problematic areas and the step-by-step process to get out of the testing "...


35

IMO, your interview process shows that your company doesn't really understand QA to begin with. QA has specific goals. It isn't "sit here with our software for x hours and figure things out". It needs to be clearly categorized, and there should be a pass/fail list of objectives. Your scenario is unrealistic, because there is no way to ever finish. At ...


30

You know, the funny thing is, this almost became a good interview tool. If I walked in to a QA interview, and the interviewer said, "By the way, when you're done, we'd like you to bug-hunt our production product when you go home," my first thought would be: You clearly don't care about your QA programmers (Why would you? If you feel you can get random ...


26

To be honest, I wouldn't be able to come up with any defect in particular. If I were you, I'd rephrase my questions as situations, for example: What actions would you take if you had to reopen a defect for the fifth time? You need to retest a defect which has been resolved by a developer without any further comments or explanation. What actions would you ...


26

I have had about 4 QA automation jobs, about 10 interviews, and was on the other side of the interview table about 10 times. QA Automation involves writing automated testing projects. These are software projects which can be very complex, often requiring: Managing deployments of applications Starting and stopping application servers Setting up test data, ...


20

I came upon this idea because I find writing a sorting algorithm is much more exciting than testing it.Since testing it is just giving a set of values and verifying the result.Anybody can do that.But,writing algorithms not many can do. No, don't seek a test architect's position. If this is truly how you feel, you should strive to be in development, ...


19

If I was being interviewed and was asked this question, first of all i would start off by trying to quench my curiosity. How much time do i have? What type of a toaster is it? How much power limit does it operate on as per the vendor? Does the vendor provide any user manual or claims documentation? How does it work? Is it timer based or manual toaster? What ...


18

There are plenty of testers who have learned to develop and there are also many testers who began their careers as developers. It is absolutely possible to find these kinds of people. There may be other hindrances however, such as availability in your area who have all of the skill-sets that you require, especially when it comes to specialized skill-sets. ...


18

How you approach testing an API depends on a lot of things. Will the API be a public API that will be consumed by some external people/systems, or is it a part of a larger product's infrastructure? API is a general term that is sometimes used to describe anything from a COM interface, to a DLL or JAR you can reference, to a REST web service. Different ...


17

Could I suggest learning to test before diving into tools to automate tests and tools to manage them ? Read the books you have got, surf this site (and others such as Software Testing Club and SQA forums ) to get an idea of what people in the industry are doing and what problems they are facing.


16

Don't be afraid, finding someone more senior than you is fun, your finding a teammate you can learn from. Do understand X+ years does not mean more senior, experience is something that does not necessarily come with time. What do you expect from a candidate better then you? At-least same basic level A Senior should be able to teach, might need very good ...


15

I am terrible at recalling names, places, restaurants, and... bugs I have investigated. I usually ask my girlfriend or my friend to give me a name of a place we have been together or an actress in a movie with have seen. That's how my brain is wired. I don't like it but I get used to it. I guess some candidates might be like that. But if you task me with ...


15

Answering your particular question "Is it possible?" I would say "Yes, it is.". There are many aspects that could impact how active QA could be involved on the prior phases. For example: Is that an automation QA or manual QA How strong soft and hard skills of particular QA engineer are How well the job was done from the top bottom phases How well is the ...


14

Palindromes testing is very representative in terms of QA way of thinking. Moreover, writing tests dramatically increase the quality of task specification. When a QA engineer writes test cases, it well may happen that certain case is not covered in initial specs. This is a good reason for QA to come up with idea to improve those specs. So, when you are ...


14

I've been at companies where someone transitioned from another dept into a Testing / QA position and it was done intra-company. They found a position open, called the department manager and impressed him/her enough to get hired - without much experience. Does your current company provide that opportunity for you? It might be an easy way in. Like Phil K says ...


14

Systems testing is often performed against the whole platform, and treats the environment as a black box. system integration testing however, acts upon a subset of the whole system, and may mock other platforms, interact with databases, network sockets etc to evoke appropriate responses from the parts being validated. The objectives of system testing is to ...


14

This is a simple, if uncomfortable, situation to be in. Unfortunately, it does happen from time to time and you need to be ready for it. The fact that the defect has been found close to the deadline is, in the short term, irrelevant. Your team has found a high severity defect, so you report it. Given the short timescales, you ensure that everyone who ...


13

Yes, its realistic to find these folks. They form the majority of the teams that I've lead. You may want to adjust the title to be Software Engineer in Test, or just Software Engineer. In my org, the pay scale, and prestige for the software engineers in test are the same as software developers.


13

From my experience - Faster feedback and more testing (in the form of automated tests ideally). If behaviour doesn't change but code is refactored often, then behaviour of system should be covered by automated checks. We have unit tests, integration tests and ui tests that are run after every commit. If requirements and behaviour changes often, then ...


12

I agree with testerab that Cem Kaner, in his PDF, has outlined a good approach to hiring. Paul Carvalho also has a good PDF called Hiring Software Testers in an Information Age that he published in 2007. Besides conducting the interview, you as the interviewer should look for common attributes, be able to skim through resumes, identify the school of ...


12

As dzieciou commented, this can vary pretty dramatically. I will give you some ideas about what I look for when interviewing an experienced QA Engineer. One of the most important things I look for - whether the role is primarily manual or automated testing - is the ability to perform root cause analysis. For instance, if a candidate has experience ...


11

I am not expert in search engines, but there are many factors that contribute to how search results are displayed. The query is is essentially the starting point, and how the engine parses the query is important. Also some search engines will 'refactor' the query based on natural langauge algorithms. The order of returned results is often dependent on ...


11

Yes, it's certainly realistic to find such folks. I am one, and I've hired many. What is more difficult (and might be what the Agencies are saying), is to convince a current developer to become a tester. That sort of career change is a challenge, as is any career change. But there are many, many testers with automation experience who used to be developers ...


11

Deciding to release with severe bug (and escalate next release with a fix) or postpone release is business decision. It can be done only by someone who understands how customer works. Maybe it is not a big deal at the end, and you can go on with the release (and inform customers what bug is, and find workaround until bug is fixed. Maybe system is not safe ...


11

I was asked a question like this at my last interview, and it took me a bit of time to think back and come up with a good answer. This was partly due to a dearth of experience - at that time I had only held internship positions. After I read your question, I repeated the exercise, trying to come up with my favorite bug in a span of time that would be ...


10

Some folks will admire your initiative and skill. Others may be annoyed, depending on whether the bugs you find relate to their day-to-day concerns. In either case, unless you know what concerns plague the people who will receive your bug list, there's a chance that your testing will not relate closely to what's on their minds. If that happens, your ...


10

Telling the interviewer what is less important than telling them why. They asked for the two best cases - not just a list of cases. This means that you need to explain to them why these cases are "better" than the many other cases you could have offered up. It doesn't matter if you give good answers if you cannot also explain why they are good answers. A ...


Only top voted, non community-wiki answers of a minimum length are eligible