Due to the recent project team staff shortage, need to recruit some of the testers. This week and last week, after another interview more than a dozen candidates, work experience in between 2 years to 9 years, but no one satisfied. During various laments, recalling the last interview of 60 people only three people to meet the requirements, if any lump in the throat, or Tucao about. If not please me too Kuangpen.
My demanding it?
In fact, my request is: there are fairly good communication skills, be familiar with common software development process, there are certain requirements analysis, design capability cases will be basic and sql linux operating with ability. There are some code capacity will be a plus. This is the result of long-term compromise with reality. If the person pretty clever, in fact, I am willing to take the time to train them.
interview result
It is regrettable that a suitable person is really hard to find. More regrettable is that I see a lot of peers into the line for many years, did not follow the work experience and the ability to grow together, some people did five or six years of sometimes giving the impression that turned out to be not as good as a young man a year or two into the line . Most regrettably, most of the students there is not even a clear career development ideas, if any, without some deep thinking, but a parrot.
Interview some of the details:
Because the work is intensive business, some business logic is very complicated, we have created a good needs (not taking into account the candidate's industry background, professional gives a detailed description and examples), and in accordance with this We need a few questions use case design. Less than a quarter of the candidate gives people a relatively satisfactory answer. Our internal assessment of the needs of this time, as long as there have been one or two years of design experience with cases, should be able to answer well.
I usually ask some questions based on your resume, take a look at the authenticity of the resume. We will ask some basic knowledge test, to see the professional quality of the candidate.
Common problems:
Tell me about your commonly used test method? 90 percent of people only know the result of the equivalence classes and boundary values. Only a few people can tell the other test case design method, but in-depth question, one can never have a satisfactory answer.
Give a very simple small example, such as landing operation, so that the candidate answer how case design method using the equivalent class. But it is still surprising that less than one-fifth can give a more satisfactory answer.
A defective statement of the life cycle (? How did you manage the bug) most people can say there is a common procedure, but in-depth and ask questions: how to combine with defects such as version, test round inferior, such as how to deal with some special cases, many people on the ignorant, and these are all basically work in common.
What do you do up a project? During this period you encounter any problems makes you the most headaches? How do you solve it? There are about ten people, only one person can give a pretty good answer to (be able to identify problems, propose what adverse effects it is, and can give some solution even if it is a good answer).
What are you interested in testing is that you want to grow in what areas? There are four ten people would say is automated testing, performance testing would say three, two will say is management would say is a white box. And hope to provide the appropriate training. Only a very few people can tell the specific ideas and technical terms.
If you continue to ask: What you say is the performance test it? Have you ever had to learn in this respect it? Half would say read some technical articles on the site, half of loadrunner would say read the book. If you continue to ask, what is this book? What kind of article is? What are the specific knowledge can talk about it? 90% could not answer.
Q: Have you seen what this test books? What technology blog? Which sites? 50% of people would say read the book of QTP (QTP usage has really fast to catch up with Nokia's usage, and the mainstream or even automate this book!), And not really used at work, then there would be no anything else. There are less than half of people in recent years, a technique books did not read it.
If you have management experience of the candidate, I will ask questions related to some of the test process management, such as to a simple question: what if the test is not enough time? Ten people will only have two or three mentioned prioritize and test cutting, the answer turned out to be most people must engage in overtime finish.
I want to say:
1. To your future, like him the ability to clear some personal thoughts of it. After you five years, ten years is what it is like? Is there a clear idea? There is no degree of someone you want to achieve in five years? If these ideas do not know, like him to see the outside world, doing some tests to see how people are working very nice, they have mastered what capacity? Learn them, and chased them and try to surpass them. They know best, can Kan Kanda Shan, hold together like-minded forward very well. Also not given abstract goal, it must be decomposed can be checked.
2.多读一些测试书籍，测试的书并不是只有QTP！看看微软测试专家史亮推荐的书单，这些都是不错的好书：http://www.cnblogs.com/liangshi/archive/2011/03/07/1973525.html 有些书能够帮助你把测试知识框架搭建起来，比照一下你还缺点啥？
3.多读一些其它书籍，不限于技术书籍。如果想读的书有利于工作，推荐一些如何做思辨思维的书。《思考的艺术》《六顶思考帽》《你的灯亮着么》 《学会提问》是我喜欢的4本书。它们会教你怎么独立思考，养成提问的习惯，而提问的习惯是我们现在的测试人员最缺乏的一件事情。人们往往拿了被测物就开始忙着写用例，忙着测试。而不是先探索它、研究它。当然IT技术也要掌握，如果你的IT技能能够赶上开发，你发现你做测试的思路会非常的宽广：）
4.把书籍中的东西跟你的工作对比，把好的东西引入工作（这点是检验书本质量的好方法，也是促进你思考，促进你能力提高的好方法。
5.关注大牛们的技术博客。国内写好测试博客的人不是很多（很多人其实很有水平，但是不喜欢写blog），但是国外有很多，有人整理了一个list也推荐给大家：http://ssnlove2008.blog.163.com/blog/static/3788942020093284842381/。
6.搞定你所在行业的领域知识：如常见IT技术，常见业务知识，这些知识掌握的越深，你的价值越高。测试技术是内功，但是你能直接为企业带来价值的最大之处是你对被测物熟悉程度，也就是你的领域知识！！！
7.没有方向？从你的工作入手，比如，你遇到的最大的难题是什么？我怎么解决它？我需要掌握什么样的技术解决他？我要推动什么样的组织改变来解决它？别人怎么解决它？有没有更好的方法？使用后我改进了那些？google一下别人有没有同样的问题？尝试作对比，如果觉得他做得好，尝试联系那个人讨论一下。看看对方的进展。尝试把活儿干得特别漂亮。你能解决10个中等问题以后，你的能力会有大幅度提高。
8.尝试做笔记。最好是在线的，推荐印象笔记和有道云笔记。
9.坚持。
10.保证身体健康，岁月会给你带来别人的信任感（当然能力要随着岁数增长）。
能做到这里面的一半，两年后你就能在专业上有高分通过我的面试：）当然肯定你也不见得会看得上我们的offer了。
11.对于没想好就跳槽，换行业的同学说：你再想想！你的很大价值是与你企业、行业绑定的。如：做了5年保险业务，你的领域知识至少值5w每年，换领域就没了。你在一家公司证明了你自己，到新公司要重新证明你一遍，有的时候外部环境、机遇等会让证明过程很痛苦，成本很高。
另外的吐槽：
野蛮生长没有经过系统训练的同学非常多。这其实有很多因素，分析起来觉得有以下几点：
1.大学或者职业教育没有非常好的课程体系（有些培训机构还行，但是也需要提高），其实测试技能需要系统训练和长时间磨练才能有根本的增长，我们的职业教育或者再教育体系其实还是有很大空白的。
2.说句实话，大家的读书氛围不够浓厚。大家不喜欢看书。而读书是再教育成本最低，又非常有效的途径。相比于程序员，测试同学喜欢读技术书籍的比率明显的低，这是一个让人悲伤的事实。真希望这种现象能够改变。
3.很多人是不喜欢coding才转测试，或者是因为IT产业普遍薪水高才来做测试。不是真正热爱这份工作，不热爱其实做不好，因为兴趣是最好的老师。
4.很多人认为测试门槛低，young talent 不愿意干，测试吸引人才有点儿困难（我初入行的时候也有这种想法，也是当时被强拉来做测试的，当时想做的是coding和数据DBA相关工作并已经有了一些积累，（我没说我是啥人才啊））。说实话测试的入门门槛的确有一点点低，但是做好测试的门槛确是相当的高，随着系统越来越复杂，测试逐渐会比开发还难做，更有挑战性，我这么说你信么？
5.专业化社区还没有形成规模，测试人员没有能有效交流的平台。这是跟美国和欧洲的一个挺大的差距。他们的社区做得挺好的，我们也有了一些很好的起步。如一些热衷测试公益的同学，一些不错的会议，一些不错的线下活动，但还需要大大的发扬光大。
真心希望测试行业的整体水平能够逐渐提高起来。
最后看一下测试大牛James Whittaker（Google测试之道 和 探索式软件测试 的作者）对职业路程发展的一篇文章吧，你会受益很多：http://www.cnblogs.com/skytraveler/p/3546703.html
