5 Common Interview Mistakes that Could Cost You Your Dream Job (and How to Avoid Them)--ref
There have been many articles on our site on software testing interviews. That is because, we, as IT professionals, have to experience and make it through many of them in many forms. At STH, we acknowledge this and we want to help our readers as much as we can.
Today, we will look at the 5 common interview mistakes that could cost us our dream job and how to avoid them.
We are not going to go into the obvious interview red flags- dressing sloppy, not being on time, not carrying a copy of your resume or identification when you were told to, etc. We are all better than that, right? This is more about the answers to some common interview questions that might come out wrong.
Let us get straight to these common interview mistakes:
#1. Negativity:
No complaints about your past. This might happen when answering questions like“Why are you looking for a change?” We can very easily say something ‘not nice’ about our previous work experience.
A small anecdote: My first job was with a major Indian IT consulting firm and I being an entry-level fresher, I was a buffer/shadow/non-billable resource in a testing project. I was not given any real work and all I had to do was “learn” by watching. My job was simply to consolidate all the bug reports created by the individual testers in the team at the end of the day. Trust me, it was pathetic. But, that’s not the point.
Say, this is the position you are trying to make a move from. When a question comes to you- “What was your role in the project?” What is your answer going to be? There are two ways to handle this- the optimist and the pessimist way. The pessimist way is to complain how you were not trusted with any important tasks and all you had to do was merge the individual bug reports. The optimist way is to explain how you were the quality representative for your team who made sure the bug reports were complete and had no duplicates/inaccurate information – or how you got a chance to look into the entire project related issues and in effect the entire AUT instead of being confined to a certain module. It is apparent which one is a better answer, correct?
So, no matter how bad the currentjob/company/boss/salary/project/process- it helps to find what is good about them and only choosing that part to include in your answers during an interview.
#2. Lying about your skills on the resume:
This is an aspect that cannot be reminded enough. We all want good jobs, we all want our resumes to be noticed and more than that, we want that lifeless-resume-search-engine to pick just us from all the 1000s of them out there. This often leads to a kind of passive desperation and compels us to put something on our resume that isn’t totally correct. E.g. adding automation tools when you don’t have any hands-on experience. We might successfully fool the machine, but we won’t be able to do that with an interviewer. Careful what you write in there.
Recommended read => How to prepare software testing QA resume?
#3. Talking endlessly:
Another personal experience to share here. There was this one interview a few years ago, when I almost had the job. It was a referral, a perfect fit to my skill set and the interview panel had a few of my friends. I still did not get the job. Frankly, I would not have hired myself. Why? I would not stop talking and I had no idea what I was talking. The very same day, I came back from an international business trip, was jet lagged and sleep-deprived- Traveled way too far on a hot summer afternoon in the busy city traffic and was out of breath when I got there. So, when the interviewer asked me questions, I was all about ‘just talking’ instead of saying anything meaningful. I learnt that day, when we can’t be “Present” we should not be. So, when you have an interview and you are serious about making it successful- be present, answer only appropriately and be professional. If you can’t be – respectfully reschedule.
Other common interview mistakes in conversational are:
Trying to use big words out of context: This will cause unnecessary follow up questions. Say, you have no idea but have heard about “Business continuity plan- BCP”. When you were asked about test planning, you said we also have to come up with a BCP- but not knowing the full extent on the topic. The interviewer, as expected, will ask you what BCP is and the rest, I don’t have to explain.
Filler words: There are a few filler words we use often-mostly when nervous- in conversations. One of my trainers always used the phrase “The one” and I have been told that I say “So” very often to keep the flow of a sentence going. Recognize if that’s happening and try to stay calm. It’s ok to be nervous, but the real trick is to camouflage it. Think of an interview as a professional conversation – listen and respond appropriately.
#4. Do not commit:
Commit to working hard. Commit to integrity. Commit to discipline. But do not commit to a time line, salary expectation or anything more serious. Let me give you an example, how long will you stay with the company? – try to say something non-committal- “as long as it takes (with a smile)” or “however long you would like me to stay” are all good, because you are not promising anything. If you say- “As long as I find it challenging” – this will mean, you will quit the minute work is more routine. “As long as it is good for my career”- means you are only interested in your welfare and do not care about the company. Really, there is no good way to answer questions like this- So, invite your sense of humor and stay on a neutral ground.
#5. What are your weaknesses?
Wait, don’t answer that. We are human, thus- not perfect. Also, we know our weaknesses best. It does not mean we have to go about letting everyone know of them. Especially not in an interview. Twist the answer around to mean that it is strength of yours. You can say “You can’t stand grammatical/spelling errors in reference documents”- this will mean you are diligent and want things to be in a standard way. Or you can say- “I often arrive at meetings early and have to wait for the others, which can be quite annoying”- shows punctuality. So, you get the picture, right?
Well, we hope we have conditioned you (just kidding) to spot these interview red flags early on and avert the danger.
reference :
Let us get straight to these common interview mistakes:
#1. Negativity:
No complaints about your past. This might happen when answering questions like“Why are you looking for a change?” We can very easily say something ‘not nice’ about our previous work experience.
A small anecdote: My first job was with a major Indian IT consulting firm and I being an entry-level fresher, I was a buffer/shadow/non-billable resource in a testing project. I was not given any real work and all I had to do was “learn” by watching. My job was simply to consolidate all the bug reports created by the individual testers in the team at the end of the day. Trust me, it was pathetic. But, that’s not the point.
Say, this is the position you are trying to make a move from. When a question comes to you- “What was your role in the project?” What is your answer going to be? There are two ways to handle this- the optimist and the pessimist way. The pessimist way is to complain how you were not trusted with any important tasks and all you had to do was merge the individual bug reports. The optimist way is to explain how you were the quality representative for your team who made sure the bug reports were complete and had no duplicates/inaccurate information – or how you got a chance to look into the entire project related issues and in effect the entire AUT instead of being confined to a certain module. It is apparent which one is a better answer, correct?
So, no matter how bad the currentjob/company/boss/salary/project/process- it helps to find what is good about them and only choosing that part to include in your answers during an interview.
#2. Lying about your skills on the resume:
This is an aspect that cannot be reminded enough. We all want good jobs, we all want our resumes to be noticed and more than that, we want that lifeless-resume-search-engine to pick just us from all the 1000s of them out there. This often leads to a kind of passive desperation and compels us to put something on our resume that isn’t totally correct. E.g. adding automation tools when you don’t have any hands-on experience. We might successfully fool the machine, but we won’t be able to do that with an interviewer. Careful what you write in there.
Recommended read => How to prepare software testing QA resume?
#3. Talking endlessly:
Another personal experience to share here. There was this one interview a few years ago, when I almost had the job. It was a referral, a perfect fit to my skill set and the interview panel had a few of my friends. I still did not get the job. Frankly, I would not have hired myself. Why? I would not stop talking and I had no idea what I was talking. The very same day, I came back from an international business trip, was jet lagged and sleep-deprived- Traveled way too far on a hot summer afternoon in the busy city traffic and was out of breath when I got there. So, when the interviewer asked me questions, I was all about ‘just talking’ instead of saying anything meaningful. I learnt that day, when we can’t be “Present” we should not be. So, when you have an interview and you are serious about making it successful- be present, answer only appropriately and be professional. If you can’t be – respectfully reschedule.
------------
Other common interview mistakes in conversational are:
Trying to use big words out of context: This will cause unnecessary follow up questions. Say, you have no idea but have heard about “Business continuity plan- BCP”. When you were asked about test planning, you said we also have to come up with a BCP- but not knowing the full extent on the topic. The interviewer, as expected, will ask you what BCP is and the rest, I don’t have to explain.
Filler words: There are a few filler words we use often-mostly when nervous- in conversations. One of my trainers always used the phrase “The one” and I have been told that I say “So” very often to keep the flow of a sentence going. Recognize if that’s happening and try to stay calm. It’s ok to be nervous, but the real trick is to camouflage it. Think of an interview as a professional conversation – listen and respond appropriately.
#4. Do not commit:
Commit to working hard. Commit to integrity. Commit to discipline. But do not commit to a time line, salary expectation or anything more serious. Let me give you an example, how long will you stay with the company? – try to say something non-committal- “as long as it takes (with a smile)” or “however long you would like me to stay” are all good, because you are not promising anything. If you say- “As long as I find it challenging” – this will mean, you will quit the minute work is more routine. “As long as it is good for my career”- means you are only interested in your welfare and do not care about the company. Really, there is no good way to answer questions like this- So, invite your sense of humor and stay on a neutral ground.
#5. What are your weaknesses?
Wait, don’t answer that. We are human, thus- not perfect. Also, we know our weaknesses best. It does not mean we have to go about letting everyone know of them. Especially not in an interview. Twist the answer around to mean that it is strength of yours. You can say “You can’t stand grammatical/spelling errors in reference documents”- this will mean you are diligent and want things to be in a standard way. Or you can say- “I often arrive at meetings early and have to wait for the others, which can be quite annoying”- shows punctuality. So, you get the picture, right?
Well, we hope we have conditioned you (just kidding) to spot these interview red flags early on and avert the danger.
5 Common Interview Mistakes that Could Cost You Your Dream Job (and How to Avoid Them)--ref的更多相关文章
- COMMON INTERVIEW QUESTIONS
1. What do you see yourself doing five years from now? 2. What motivates you to put forth your great ...
- Avoiding Common Networking Mistakes
https://developer.apple.com/library/content/documentation/NetworkingInternetWeb/Conceptual/Networkin ...
- Otto Product Classification Winner's Interview: 2nd place, Alexander Guschin ¯\_(ツ)_/¯
Otto Product Classification Winner's Interview: 2nd place, Alexander Guschin ¯\_(ツ)_/¯ The Otto Grou ...
- [Forward]Ten Caching Mistakes that Break your App
Caching large objects, duplicate objects, caching collections, live objects, thread unsafe caching a ...
- https那些事儿
(一)SSL/TLS协议运行机制的概述 一.作用 不使用SSL/TLS的HTTP通信,就是不加密的通信.所有信息明文传播,带来了三大风险. (1) 窃听风险(eavesdropping):第三方可以获 ...
- CG&Game资源(转)
cg教程下载: http://cgpeers.com http://cgpersia.com http://bbs.ideasr.com/forum-328-1.html http://bbs.ide ...
- Chapter 6 — Improving ASP.NET Performance
https://msdn.microsoft.com/en-us/library/ff647787.aspx Retired Content This content is outdated and ...
- (转)Awesome Courses
Awesome Courses Introduction There is a lot of hidden treasure lying within university pages scatte ...
- Why should I avoid blocking the Event Loop and the Worker Pool?
Don't Block the Event Loop (or the Worker Pool) | Node.js https://nodejs.org/en/docs/guides/dont-blo ...
随机推荐
- uva 12124 - Assemble
最大值最小的题: 直接用二分,比较简单: 不过我的二分老是不用好.有时间总结一下! #include<cstdio> #include<map> #include<vec ...
- Android MediaPlayer状态机
对播放音频/视频文件和流的控制是通过一个状态机来管理的.下图显示一个MediaPlayer对象被支持的播放控制操作驱动的生命周期和状态.椭圆代表MediaPlayer对象可能驻留的状态.弧线表示驱动M ...
- springboot + devtools(热部署)
技术介绍 devtools:是boot的一个热部署工具,当我们修改了classpath下的文件(包括类文件.属性文件.页面等)时,会重新启动应用(由于其采用的双类加载器机制,这个启动会非常快,如果发现 ...
- 代码演示C#中string和StingBuilder内存中的区别
关于 string和StringBuilder的区别参考MSDN.本文用程序演示它们在内存中的区别,及其因此其行为不同. //Demo string memory model namespace C ...
- wpa_supplicant 配置与应用
概述 wpa_supplicant是wifi客户端(client)加密认证工具,和iwconfig不同,wpa_supplicant支持wep.wpa.wpa2等完整的加密认证,而iwconfig只能 ...
- linux下出现+ ls --color=auto -l --color=auto...++ echo -ne '\033]0;root@imon-2:~'等
[root@imon-2 ~]# cd /root/ + cd /root/ ++ echo -ne '\033]0;root@imon-2:~' [root@imon-2 ~]# ll + ls - ...
- Mac下快捷键列表
主界面 command + tab 切换程序 command + ` 在程序内切换界面 command + w 关闭界面 command + q 关闭程序 command + option + esc ...
- [SAM4N学习笔记]UART的使用
一.准备工作: 将上一节搭建的工程复制一份,命名为"3.uart".这一节主要讲如何使用SAM4N的UART功能,实现串口的收发. 二.程序编写: 细心看数据手册的朋友也 ...
- 一步一步写一个简单通用的makefile(二)
这一篇源代码沿用上一篇的源代码hellomake.c hellofunc.c hellofunc.h makefile 但是代码内容和结构有变化,如下: . ├── include │ └── h ...
- Installing Ubuntu on a Pre-Installed Windows 8 (64-bit) System (UEFI Supported)
http://askubuntu.com/questions/221835/installing-ubuntu-on-a-pre-installed-windows-8-64-bit-system-u ...