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 ...
随机推荐
- POJ 1778 All Discs Considered(拓扑排序)
点我看题目 题意 :其实题意我也说不清楚,因为比赛的时候我盯着看了1个小时也没看懂....就是两个磁盘,第一个有n1的安装包,编号为1~n1,第二个有n2个安装包,编号为n1~n2.给你d对关系,(x ...
- UserMailbox 必须强制使用 Database---Database is mandatory on UserMailbox error
XX搞了接近一天,终于搞定. 不只是在查看用户邮箱里发现这样的情况,就连在PS里执行GET-MAILBOX之类,都有这个报错. 跟网上所有的解决方法都不一样. 重新了系统邮件都不行,重新了ADMINI ...
- 李洪强漫谈iOS开发[C语言-026]-符合赋值表达式
- 谈谈SpringMVC Validation
2016-10-12 19:26:08,897 [INFO ] [http-nio-8032-exec-1] HttpHeaderValidator:84 - HttpHeaderValidator. ...
- Rocky(dfs)
题目描述 Sylvester Stallion is an old horse who likes nothing better than to wander around in the fields ...
- C# 利用BarcodeLib.dll生成条形码
首先效果: 1:首先下载BarcodeLib.dll 下载地址 http://pan.baidu.com/share/link?shareid=2590968386&uk=2148890391 ...
- java线程(2)-线程间通信
方法一 通过访问共享变量的方式(注:需要处理同步问题) 方法二 通过管道流 其中方法一有两种实现方法,即 方法一a)通过内部类实现线程的共享变量 public class Innersharethr ...
- android Permission 访问权限许可
程序执行需要读取到安全敏感项必需在androidmanifest.xml中声明相关权限请求, 完整列表如下: android.permission.ACCESS_CHECKIN_PROPERTIES允 ...
- wpa_supplicant对wep,wpa,wpa2的psk和隐藏ap的scan_ssid扫描配置
# 请不要修改下面这一行内容,否则将不能正常工作ctrl_interface=/var/run/wpa_supplicant # 确保只有root用户能读取WPA的配置ctrl_interface_g ...
- Oracle体系结构图
1 oracle数据库主要有数据文件database和数据库实例instance组成.用户通过用户进程链接到server process.在数据库启动的时候,需要依赖于参数文件parameter fi ...