Tags |
|
|
Links |
|
|
Hub You - Surviving The Technical Interview
I am having a hard time understanding why a valuable resource such as the “over qualified employee is having such a hard time getting a job. Something seems to be out of whack here. How is that as a society we deplore people who live on welfare and rape our system, but at the same time, refuse to hire people who are out of work because they are seemingly over qualified for the job, EVEN when they are willing to work for thousands of dollars less than they would normally receive.Now this seems really weird to me. I can understand on the one hand why an employer may not want to hire the perso
The applicant fielded four questions from the rest of us flawlessly, then faced this particular tech for a question. The threatened tech had a list of questions for the interview, but decided to ad lib. Big mistake. He asked a convoluted question that Rube Goldberg would have been proud of. When he was done, the applicant answered:
'You can't do what you just described.'
The tech started defending his question, an
For people who are serious about their career, continuous career training is essential. The more professional their career, the more important career training is. Lawyers need to be up to date with the law, doctors need to be up to date with medical knowledge and treatments, and computer systems analysts need to keep track of all developments in the computer world, and in that of their particular markets; their careers demand it, otherwise they become incompetent.Even for those who have studied hard at college, school and university, study of some form or another is unlikely to come to an end
How many people will be asking questions? From experience I can tell you there's nothing like walking into a room and seeing nine people on the other side of the table.
Second, what will you be asked? You'll sometimes hear people say the questions they were asked in a technical interview were 'easy', which translated means 'they asked me stuff I happened to know'. Sometimes you'll hear people say the questions were 'hard', which translated means 'they asked me stuff I didn't know', or 'they asked me about stuff I've never even heard of'.
Having been on both sides of the technical interview table, I'd like to share some tips for those being interviewed. In doing so, I'll share some of the more memorable interviews I've been involved in.
No good interviewer expects you to know everything. The problem is, you're not always going to be interviewed by someone who's good at it.
Sometimes, the person who's giving you a technical interview was asked to do it about ten minutes before you showed up. Maybe they've never interviewed anyone before, or maybe they're just in a bad mood. I've heard of technical interviewers where the interviewer derided an answer, and that's totally unprofessional. I've had many a job candidate give a bad answer to a question, and my only response was silence followed by moving on to the next question. If your interviewer mocks any of your answers, you didn't want to work there anyway.
None of us know everything. If you're asked a question you just don't know the answer to, don't try to BS your way past it. This is a good opportunity to tell the interviewer how you would research that particular question. It's not about knowing everything, it's about being able to find out anything.
If your interviewer acts like he/she already dislikes you, that's because they do. I once worked with a technician who felt threatened by anyone who applied for a job there, but especially if the applicant had a professional certification and then had the nerve to know what they were doing.
This technician participated in a group technical interview where the applicant was an incredibly bright guy, and had a particular skill that the department really needed. Problem was, the technician considered himself 'the man'? when it came to that skill. Recipe for disaster, right?
The applicant fielded four questions from the rest of us flawlessly, then faced this particular tech for a question. The threatened tech had a list of questions for the interview, but decided to ad lib. Big mistake. He asked a convoluted question that Rube Goldberg would have been proud of. When he was done, the applicant answered:
'You can't do what you just described.'
The tech started defending his question, an
Everyday myself and my colleagues see large numbers of enquiries from translators seeking work. I hope that some of my observations will help you be more successfull.1) Update and scan your computer for virusesHow many translators CV’s get caught by a translation agencies firewall? I don’t know. It seems to happen in waves. We will have a batch of translators emails in a few days and then none for ages. But generally the email is deleted!2) Put your details in the subject section of the emailIf you are applying for a translation project posted on the web, put a reference t
Having been on both sides of the technical interview table, I'd like to share some tips for those being interviewed. In doing so, I'll share some of the more memorable interviews I've been involved in.
No good interviewer expects you to know everything. The problem is, you're not always going to be interviewed by someone who's good at it.
Sometimes, the person who's giving you a technical interview was asked to do it about ten minutes before you showed up. Maybe they've never interviewed anyone before, or maybe they're just in a bad mood. I've heard of technical interviewers where the interviewer derided an answer, and that's totally unprofessional. I've had many a job candidate give a bad answer to a question, and my only response was silence followed by moving on to the next question. If your interviewer mocks any of your answers, you didn't want to work there anyway.
None of us know everything. If you're asked a question you just don't know the answer to, don't try to BS your way past it. This is a good opportunity to tell the interviewer how you would research that particular question. It's not about knowing everything, it's about being able to find out anything.
If your interviewer acts like he/she already dislikes you, that's because they do. I once worked with a technician who felt threatened by anyone who applied for a job there, but especially if the applicant had a professional certification and then had the nerve to know what they were doing.
This technician participated in a group technical interview where the applicant was an incredibly bright guy, and had a particular skill that the department really needed. Problem was, the technician considered himself 'the man'? when it came to that skill. Recipe for disaster, right?
The applicant fielded four questions from the rest of us flawlessly, then faced this particular tech for a question. The threatened tech had a list of questions for the interview, but decided to ad lib. Big mistake. He asked a convoluted question that Rube Goldberg would have been proud of. When he was done, the applicant answered:
'You can't do what you just described.'
The tech started defending his question, an
Recently, I decided to enlarge my sales and marketing efforts through outsourcing, so I contacted a number of service bureaus about promoting my successful line of customer service and sales training videos. I have found very few organizations that are willing to truly satisfy my needs by working on a pay-for-performance basis.Everyone else insists on being paid, on the clock, for their time and for administration.It reminds me of my former college students who claimed they deserved a better grade on an assignment because they “tried so hard!” They wanted to be rewarded for mere effort.
None of us know everything. If you're asked a question you just don't know the answer to, don't try to BS your way past it. This is a good opportunity to tell the interviewer how you would research that particular question. It's not about knowing everything, it's about being able to find out anything.
If your interviewer acts like he/she already dislikes you, that's because they do. I once worked with a technician who felt threatened by anyone who applied for a job there, but especially if the applicant had a professional certification and then had the nerve to know what they were doing.
This technician participated in a group technical interview where the applicant was an incredibly bright guy, and had a particular skill that the department really needed. Problem was, the technician considered himself 'the man'? when it came to that skill. Recipe for disaster, right?
The applicant fielded four questions from the rest of us flawlessly, then faced this particular tech for a question. The threatened tech had a list of questions for the interview, but decided to ad lib. Big mistake. He asked a convoluted question that Rube Goldberg would have been proud of. When he was done, the applicant answered:
'You can't do what you just described.'
The tech started defending his question, an
It is paramount that your advertising and marketing in your company that you put out into the public talks to the customer. So often, small business brochures and advertising talks about the company and not about what is in it for the customer. You may have a great company and you may be very proud of this fact. But your customer cares what you can do for them not which you can do for yourself. Let's face it you are asking the customer to come to your store and buy something from you or to purchase services.When the customer does business with you it will cost them money and for this exchang
If your interviewer acts like he/she already dislikes you, that's because they do. I once worked with a technician who felt threatened by anyone who applied for a job there, but especially if the applicant had a professional certification and then had the nerve to know what they were doing.
This technician participated in a group technical interview where the applicant was an incredibly bright guy, and had a particular skill that the department really needed. Problem was, the technician considered himself 'the man'? when it came to that skill. Recipe for disaster, right?
The applicant fielded four questions from the rest of us flawlessly, then faced this particular tech for a question. The threatened tech had a list of questions for the interview, but decided to ad lib. Big mistake. He asked a convoluted question that Rube Goldberg would have been proud of. When he was done, the applicant answered:
'You can't do what you just described.'
The tech started defending his question, an
The Internet can promote your services in unlimited relevant areas that buyers are looking forEven when they both have a website, a service business (like window blinds) has to use the Internet differently than an online business does. For example, a chiropractor needs to provide different information a trucking firm, to supply what customers search for. While they both can benefit from Local Search exposure, what information they need to provide about themselves varies greatly.Break down the limitations imposed by category thinkingWe've been trained by the Yellow Page directory
The applicant fielded four questions from the rest of us flawlessly, then faced this particular tech for a question. The threatened tech had a list of questions for the interview, but decided to ad lib. Big mistake. He asked a convoluted question that Rube Goldberg would have been proud of. When he was done, the applicant answered:
'You can't do what you just described.'
The tech started defending his question, and it became obvious that he hadn't been able to follow his own question! The interview went into a bit of a meltdown from there.
Realize right now that there are some unprofessional people out there giving technical interviews. Be prepared for it, but remain professional yourself.
Be prepared for a practical technical interview. The best technical interviewers find a way to get you in front of the technology you'll be working with. A great way to quickly find out whether you know what you're talking about is to ask you to actually perform common and perhaps some not-so-common tasks. We can talk about technology and take all the computer-based exams we want, but it all comes down to performance. Be prepared to prove you belong on your interview day.
Be professional. This covers a lot of ground, so let me make a quick list for you.
Show up 15 minutes early. Nothing makes a technical interviewer more surly than waiting for the applicant.
Dress for success. The way you look when you walk into a room leads to your interviewer's first impression of you.
Don't chew gum during the interview.
Don't be arrogant. Look, there's nothing wrong with having an ego and acting confident. I do, and you should. But don't come into the interview room acting like you're too good to be there.
Finally, relax. Easy to say, hard to do? Not really. Realize that the majority of interviewers you'll ever meet are going to be professional about the entire thing. The world's not going to end if you miss a question. If you were not qualified on paper for the job, you wouldn't be in there.
Do not look upon the interview as something negative. Rather, look at it as an opportunity to prove you know what you're talking about. With the proper mental attitude, your technical interview will be a springboard to the next step in your career!
HTTP = HTML link (for blogs, profiles,phorums):
<a href="http://www.iadvice.info/article/13517/iadvice-Surviving-The-Technical-Interview.html">Surviving The Technical Interview</a>
BB link (for phorums):
[url=http://www.iadvice.info/article/13517/iadvice-Surviving-The-Technical-Interview.html]Surviving The Technical Interview[/url]
Related Articles:
Problems When Importing from China
Restaurant Employee Tip Tracking Through A Point Of Sale System
Electrical Jobs: Electrical Engineer
Bookmark it:
|