Skip to main content

10 Toxic Words you Must not Say in a Job Interview

There’s plenty advice out there to rehearse what you’re going to say in a job interview: research questions the interviewer might ask, practice your answers, come up with salient questions of your own…
But what about rehearsing what you’re not going to say?
I put together a list below of some words you’ll want to try to avoid at your next job interview, because even though they seem like just ordinary words, they could be major red flags for an interviewer or recruiter.

No.

First of all, if asked even a simple question, you don’t want to give a single word answer (yes or no). But when the answer is no, definitely don’t leave it there! For example, if asked if you know a particular computer program, and you don’t, you could say, “I haven't yet had a chance to learn it but would be interested to do so,” rather than simply saying “No.”

Er… Um…

That old saying, “If you don’t have anything to say, don’t say anything at all,” applies here a big. Rather than hemming and hawing while you try to think up an answer, just be silent and think. Saying er or um too much could make you seem unprepared or as though you’re not paying attention.

Whatever, OMG, bae… groovy?

Lose the slang when talking to an interviewer. You want to come across as polished and professional, and you don’t want them to have to dig out their urban dictionary to understand you.

Sure, cool, kinda…

These kinds of words are just too casual, even in a casual workplace. You should be presenting the best version of yourself, not the sloppy, casual version.

We

This one seems innocuous at first, but if you use it a lot when discussing job duties and accomplishments, the interviewer might start to wonder if it was you or your team that was responsible. Try to use “I” as much as possible.

Dedicated, motivated, team player...

Lose the resume speech and jargon. Besides the fact that these words are incredibly overused in interview situations, they’re also better demonstrated than just stated. If you want to convey your dedication or motivation, share an example from your past work experience; examples will go much further to making your claims believable.

Leverage, synergy, ideation…

I’d avoid using too much business jargon. The chances that you’ll come off sounding like an idiot are just too high. Too much business buzzwords or jargon tends to make people sound pretentious, or worse, downright stupid.

“Hit the ground running,” “Circle back…”

These kinds of cliches have little to no meaning, they’re just verbal fluff, and they don’t add anything to what you’re saying. So leave them out.

Hate

I can’t think of a single instance when saying you “hate” something in a job interview is appropriate, but it’s exceptionally inappropriate to say anything about hating your former job, co-workers, boss, etc.

Perfectionist

It’s become almost a cliche in and of itself to answer a question like, “What’s your biggest flaw?” with a positive flaw like, “I’m a perfectionist.” Any good interviewer will see right through that, so just don’t do it.

Source - Bernard Marr

Comments

Popular posts from this blog

[AIX] How to restart network service in AIX environment?

When network service like telnet connection hangs, then it is possible the inetd subsystem is not working properly. # refresh -s inetd 0513-095 The request for subsystem refresh was completed successfully. If the refresh hangs for some time and comes back with 0513-056 time out waiting for command response, then the inetd subsystem may not be working correctly and should then be killed nicely. Run #ps -ef | grep inetd and do a kill -15 on the process ID on the line that has /usr/sbin/inetd. Once inetd has been killed, type startsrc -s inetd. If inetd starts, try to telnet into the machine. If inetd does not start up successfully, or if telnet still hangs indefinitely, run kill -15 on the PID of inetd again. Back up the original /etc/inetd.conf file to a new file name by typing: # mv /etc/inetd.conf /etc/inetd.conf.backup The original template is in /usr/lpp/bos.net/inst_root/etc/. You can copy it by typing: # cp /usr/lpp/bos.net/inst_root/etc/inetd.conf /etc/inetd.conf Run start...

Configure Link based IPMP in Solaris

For long we used Tracking IP based IPMP wherein we track the availability of a gateway on the network using ICMP Echo request. When the gateway IP fails to respond it is considered link is unavailable and NIC fails over to the standby NIC in the IPMP group. The biggest disadvantage here is that we use 3 IP addresses: 1 for the Virtual IP 1 for the active NIC 1 for the Standby NIC and ofcourse the overhead of the ICMP echo requests sent every seconds. This can be overcome using the Link based IPMP configuration where you only need only IP Address and there is no overhead of ICMP messages and the failover delay is lot lesser than that of the tracking method. And the added advantage of a very simple configuration. To configure Link based IPMP, create the hostname.<int name> files for the Active NIC and the standby NIC. For instance here, we use the bge0 and bge3 NICs as the IPMP pair where bge0 is active and bge3 is standby and hence the files hostname.bge0 and hostname.bge3 . To...

Windows Server Backup Step-by-Step Guide for Windows Server 2008

The Windows Server Backup feature provides a basic backup and recovery solution for computers running the Windows Server® 2008 operating system. Windows Server Backup introduces new backup and recovery technology and replaces the previous Windows Backup (Ntbackup.exe) feature that was available with earlier versions of the Windows operating system. What is Windows Server Backup? The Windows Server Backup feature in Windows Server 2008 consists of a Microsoft Management Console (MMC) snap-in and command-line tools that provide a complete solution for your day-to-day backup and recovery needs. You can use four wizards to guide you through running backups and recoveries. You can use Windows Server Backup to back up a full server (all volumes), selected volumes, or the system state. You can recover volumes, folders, files, certain applications, and the system state. And, in case of disasters like hard disk failures, you can perform a system recovery, which will rest...