第四章 面面俱到,脱颖而出
4.1 软素质面试题
招聘过程中,除了会考查技术、了解
工作经验外,还会对应试者软素质进行衡量。本节列出面试中经常碰到的一些问题以及回答注意事项。
例题1.您之前的学业跟这个岗位不太合适,这个你怎么看?你学的是Java,但是我们用的是PHP语法,这个你怎么看?
分析:当面试官提出这样的问题,有可能是真不合适,但也有很大一部分原因是测您的心理压力承受能力。因为在日常工作中,除了工作上有压力,有时犯了错,需要承受更大的心理压力。面试官当然不希望自己招到一个犯了错就崩溃或者哭哭啼啼的学生。这个题目应该尽量积极回答。
答案:我的专业确实不对口,但是不影响我对这行的钟爱程度,希望面试官给我机会,我会证明给你们看我不比专业人员差。我自学能力很强,如果贵公司录用我,入职之前我可以自学PHP,应该不会耽误工作。
例题2.我们公司经常加班,你对加班问题怎么看?
分析:了解应聘者是否反对加班。
答案:理解,任务没完成或者要赶进度加班也是可以的,多劳多得。(我家里人很支持我的事业,不会反对我加班。加班对我成长有很大帮助,我不排斥。)
例题3.你为什么选择我们公司呢?
答案:贵公司在行业内领先,我可以学到很多东西。(贵公司处于发展期,我认为可以有很大的职业上升空间。)
例题4.你能为我们做什么呢?
答案:我办事效率高,能提高贵公司测试项目的效益。(我经验丰富,能提高贵公司测试项目的质量。)(我对管理流程很熟悉,能规范贵公司测试项目的流程。)(我开发能力强,对自动化又熟悉,能引进自动化技术,缩短测试周期)。
例题5.你是什么样的人呢?
分析:这等于在问,你的价值观是否跟公司的企业文化一致?答案别太离谱就行。
答案:乐观,不斤斤计较,上进等。
例题6.你还有什么问题要问我?
分析:这个问题若以积极的方式回答,会给面试官留下较好的印像。最好问工作相关的事情,别问工资之类。
答案:如果我想在这个行业发展下去,您作为资深人士,能给我点建议么?
例题7.谈一下你做过项目的产品功能架构、设计框架?
答案:根据考生自己情况作答。
例题8.你的测试职业发展是什么?
答案:测试经验越多,测试能力越高。所以我的职业发展是需要时间累积的,一步步向着高级测试工程师发展。而且我也有初步的职业规划,前3年积累测试经验,按如何做好测试工程师的标准要求自己,不断地更新自己、改正自己,做好测试任务。
例题9.你自认为测试的优势在哪里?
答案:优势在于我对测试坚定不移的信心和热情,虽然经验还不够,但我有信心在工作中发挥测试需要的基本技能。
例题10.当开发人员说不是
Bug时,你如何应付?
答案:开发人员说不是Bug,有2种情况。一是需求没有确定,所以我可以这么做,这个时候可以找来产品经理进行确认,需不需要改动,3方商定后再看要不要改。二是这种情况不可能发生,所以不需要修改,这个时候,我可以先尽可能说出是Bug的依据是什么?如果被用户发现或出了问题,会有什么不良结果?程序员可能会给你很多理由,你可以对他的解释进行反驳。如果还是不行,那我可以把这个问题提出来,跟开发经理和测试经理进行确认,如果要修改就改,如果不要修改就不改。如果有些真的不是Bug,我就以建议的方式写进TD中,开发人员不修改也没有大问题。如果确定是Bug的话,一定要坚持自己的立场,让问题得到最后的确认。
例题11.你找工作时,最重要的考虑因素为何?
答案:工作的性质和内容是否能让我发挥所长,并不断成长。
例题12.为什么我们应该录取你?
答案:您可以由我过去的工作表现所呈现的客观数据,明显地看出我全力以赴的工作态度。
例题13.如果和开发人员时间安排有矛盾,或者说开发者延迟开发时间,你会怎么做?
分析:以大局为重,先把事情弄完,再考虑内部矛盾。
答案:加班把测试工作完成,或者和开发人员商量,让开发人员分担一些测试任务。目的只有一个,务必准时上线。事后,分析开发延迟原因,下次尽量避免类似事情发生。
例题14.工作中,你和你平级同事竞争一个职位,你又跟他在一个团队,如何相处?
答案:作为同一个团队的成员,必然存在两层关系:竞争、合作。我认为作为一个专业人士,应该以合作第一、竞争第二为原则。因为在同一个团队,就一定有共同利益,大家都在同一条船上,必须把共同利益维持好,才会有更好的发展。另外,成功晋级也有两种结果,一种是伴随鲜花和掌声,另一种是带着同事的不屑和蔑视。我希望我是第一种。
例题15.如果我今天把你拒绝了,觉得你不适合干这行,你会怎么做?
答案:我喜欢这行,我会继续努力。另外,我想了解您拒绝我的理由,方便我出去后重整旗鼓。毕竟您是有经验的,经验比我丰富,一定能看到我自己看不到的缺点。
4.2 英文面试
外企要求工作中英文交流,英文面试题也需要好好准备一下。下面列出一些常见的英文面试题以及参考答案。
1.Could you please introduce yourself?
Answer:I am creative and motivated. Graduated from XX, I entered XX company at 2003. Having worked on several project, I can manage a team of 5~10 testers. I'm a good tester,and special at auto-test. I am looking for a challenging and promising position.
2.why do you think we should employ you?
Answer:I am suit for the position not only because I have 3 years experiences but also I can enhance work efficiency by introducing automatics to your project.
3.why didn't you like the job you have held?
Answer:I think it don't give me a promising future.Hardly can I get a promotion in 2~3 years.i have to go out and seek for a better way.I think××company is a good choice.(I want to gain more experience at a trading company.)
4.what did you do in your last job?
Answer:I have experienced on 3 product,pay, advertise, can. For my first year ,as a green one, I have learned how to do functional test at pay project. From the second year, I worked as a mentor of two freshers, I teach them how to test as I learned, and I do auto-test coding too.At the third year, I began to do system test,automatics,and mentor job.
5.what do you know about test plan?
Answer:Before test, test plan is needed. It includes test scope, test schedule, test approche, test tools,etc。
6.how do you design cases?
Answer:First,I write case according to MRD, make sure every scene is covered. Then, make up some cases according to RD's design by path-cover way.
7.Can you tell me about yourself?
Answer:In my QA career,I have been working on various system platforms and operating systems like Windows 95,Windows 2000,Windows XP and UNIX.I have tested applications developed in Java,C++,Visual Basic and so on.I have tested Web-based applications as well as client server applications.
As a QA person,I have written Test Plans,Test Cases,attended walk-through meetings with the Business Analysts,Project Managers,Business Managers and QA Leads.I have attended requirement review meetings and provided feedback to the Business Anal-ysts. I have worked in different databases like Oracle and DB2, wrote SQL queries to retrieve data from the database. As far as different types of testing are concerned, I have performed Smoke Testing, Functional Testing, Backend Testing, Black Box Testing, Integration Testing, Regression Testing and UAT (User Acceptance Testing).I have participated in Load Testing and Stress Testing.
I have written defects as they are found using ClearQuest and TestDirector. Once the defects were fixed, retested them and if were passed, closed them. If the defects were not fixed, then reopened them. I have also attended the defect assessment meetings as necessary. In the meantime, a continuous interaction with developers was necessary. This is pretty much what I have been doing as a QA person.
8.What you worked with Use Cases before?
Answer:I have written Test Cases using Use Cases.
9.Can you tell me what a Use Case is?
Answer: A Use Case is a document that describes the user action and system response for a particular functionality. See how a Use Case looks like.
10.What is Business Design Document?
Answer:It is the document that describes the application functionalities of the user in detail. This document has the further details of the Business Requirement Document. This is a very crucial step in Software Development Life Cycle (SDLC). Sometimes the Business Requirement Document and Business Design Document can be lumped together to make only one Business Requirement Document.
11.What is walk-through meeting?
Answer:Once the Business Analysts complete the requirement document, they call a meeting to explain how the functionalities work, what the process is in the designed application and other details. The Business Analysts explain the high level functionalities of the application (software) that is going to the built. The participant members in the meeting may provide feed back and various point of views are expressed. This is walk-through meeting.
12.What does the Build Deployment mean?
Answer: When the Build is prepared by the CMT (Configuration Management Team), it is deployed (put) to different Test Environments; it is called the Build Deployment.
13.What is a Test Strategy?
Answer: A Test Strategy is a document that describes the test efforts, test configuration, testing tools to be employed, test environments, exit criteria and entry criteria for testing, what different types of testing will be carried out (for example, Smoke Test, Regression, Load Testing, Functional Test and so on) types of testing to be carried out and system requirement. The Test Manager or Lead writes it. (Remember, the Tester does NOT write Test Strategy. A Tester writes Test Plans and Test Cases) See how a Test Strategy looks like.
14.What is the difference between Load Testing and Performance Testing?
Answer: Basically Load, Stress and Performance Testing are the same. However, Load testing is the test to check the users' response time of number of users of any one scenario of the application. Whereas Performance Testing is the test to check the user response time for multiple scenario of the same application.
15.From you resume, I see that you have been working in one place for a very short period of time. This raises my questions.Can you explain why?
Answer: As a consultant, I am hired for a certain period of time (for project duration only), normally for 6 months to 1 year. Once the project is over, I needed to move to another project. That's why you see me in the resume jumping frequently here and there.
16.What do you do on the job every day? What is the first thing you go when you go to work on a day? (What is your routine job?)
Answer:Go to work, have a cup of coffee (coffee is free in any work place), then check E-mails. I will check in my calendar whether there is any meeting for the day. If there is anything urgent work that needs to take care of, then I will start with that job. Otherwise, I will start what is left from yesterday on a priority basis.
(This question was asked to one of my friends while he was attending interview in one of the companies. When they asked him this question, his answer was, he said, I start testing. This was his wrong answer. The answer varies in which phase of testing the application is. If the application is in very beginning state-meaning that the coding has just begun, then the tester's job will be to analyze and read the requirement documents, write test plans and write test cases.
Probably attend walk-through meeting and so on. However, the daily routine job would be, as mentioned above, check E-mails, read documents, attend meeting and so on. It's not that as soon as you enter the office, you start testing。)
本文选自《软件测试工程师面试秘籍》,本站经作者的授权。
版权声明:51Testing软件测试网获作者授权连载本书部分章节。
任何个人或单位未获得明确的书面许可,不得对本文内容复制、转载或进行镜像,否则将追究法律责任。
相关文章:
临阵磨枪,不快也光—软件测试工程师面试秘籍(7)