Delphi (23) windows (6) XE3 (5) Delphi 2007 (4) Rad Studio (4) XE (4) XE8 (4) Service (3) windows service application (3) Error (2) IIS (2) Manual (2) SQL (2) TTouchKeyBoard (2) Uninstall (2) XE7 (2) application (2) attach to process (2) batch file (2) cmd (2) date (2) delphi 2009 (2) delphi xe (2) excel (2) no-cache (2) .NET Globalization (1) .res (1) Application Events (1) AutoFit Height (1) AutoFit width (1) Borland.Common.Targets (1) Borland.Delphi.Targets (1) Cache-control (1) Clearing cache on IIS (1) Configure (1) DFM (1) DPR (1) DYNAMIC FORM IN DELPHI (1) Database (1) DateTime Issue (1) DateTime issue in IIS 7 (1) Delete cache (1) Delphi XE3 (1) Disable application from taskbar (1) Duplicate (1) Error 1053: (1) Events (1) Excel columns (1) Excel row (1) Export Excel (1) FD (1) FDDriversFireDac database connection error. (1) File (1) Firedac (1) Format Excel using delphi (1) GNU gettext (1) GPEDIT (1) Get ip address using Delphi (1) GetIPAddress (1) HTTP header (1) Hide Application button from Taskbar (1) Hide Application from TaskBar (1) Hide recycle Bin (1) Hint (1) Hint balloon (1) ICON GROUP (1) ID MAINICON (1) IIS Culture (1) IIS Date issue (1) IIS PHP (1) IIS Set DateTime Format (1) ISAPI extensions (1) Icon (1) Install (1) Install PHP (1) Joomla freezes while installing (1) Joomla taking more time to install (1) MAINICON (1) MYSQL (1) Modify (1) ORA-12516 (1) ORA-12520 (1) ORA-12520: TNS:listener could not find available handler for requested type of server (1) Oracle (1) Out of memory error in TstringList delphi (1) PHP (1) Parameterized queries (1) Php extension (1) Process Name Not Visible (1) Promote Websites (1) Query (1) Remove (1) Remove IIS Temp files (1) Remove Recycle Bin (1) Repair (1) Resource (1) Run php on IIS (1) SQl Injection (1) SQlText (1) Safe (1) Show recycle Bin (1) Simple Ways to Promote Blogs (1) Sortdate format (1) StringList limitations (1) System account setting (1) System locale in IIS (1) TNS listener could not find available handler with matching protocol stack (1) TStrings (1) TTrayIcon (1) TaskBar (1) Tform (1) The service did not respond in a timely fashion (1) TranslateComponent (1) Tray (1) Tray Application (1) TstringList (1) Type 14 (1) UnInstallation (1) Website (1) WinCache (1) Windows Application (1) XE2 (1) batch (1) c++ (1) c++Builder (1) cache (1) cache clear (1) cachecontrol (1) call (1) cannot load library (1) cd (1) cell format (1) clear (1) client (1) close cmd window (1) close program started by cmd (1) cmd.exe (1) command prompt (1) configure a php website on IIS (1) convert delphi color to html color (1) create (1) creating table (1) current (1) data format (1) dbx (1) dbx framework (1) dbx vs vcl (1) debug (1) debugger (1) debugging (1) debugging service application (1) delete IIS temp (1) delete temporary files on IIS (1) delphi color to html color (1) delphi debugger (1) delphi windows service debug (1) directory (1) disable cache (1) dll (1) duplicate resource (1) dynamic form (1) echo off (1) excel cells with mso-number-format (1) exit (1) exit /B (1) form (1) get directory (1) getip (1) group policy (1) hexa color (1) hexa color code (1) hide application (1) hostname (1) how to disable cache in indy (1) html (1) html color (1) html to excel (1) idhttp (1) indy (1) indy not clearing cache (1) inno (1) inno script (1) inno scripts (1) inno setup (1) instant (1) instant client (1) internalize (1) invalid pointer operation (1) invalid pointer operation error in inno (1) invalid pointer operation error in inno setup (1) ip (1) ip address (1) joomla (1) joomla 3 (1) joomla 3 not installing (1) joomla freezes (1) joomla hangs (1) joomla instalation (1) joomla not installing (1) keyboard (1) keystroke (1) libmysql.dll (1) libmysqld.dll (1) localization (1) localize (1) minimize (1) mso-number-format (1) numeric (1) parameters (1) params (1) path (1) pc ip address (1) php in Windows (1) php on IIS (1) prevent against SQL Injection (1) procedure (1) procedure call (1) process (1) program (1) pskill (1) remove cache on IIS (1) resource not found error (1) run as administrator (1) send (1) shortdate format (1) sortdate (1) sqlquery (1) styling excel (1) taskkill (1) tcolor to hexacolor (1) text (1) touchkeyboard (1) tranbslate (1) translate (1) translate component captions (1) unable to load project (1) unc (1) vcl (1) windows 10 (1) windows xp (1) winsock (1) without installing standard oracle (1)

Thursday, 2 August 2012

3 Interview Questions That Reveal Everything

Just start from the beginning of the candidate's work history and work your way through each subsequent job. Move quickly, and don't ask for detail. And don't ask follow-up questions, at least not yet.

Go through each job and ask the same three questions:
1. How did you find out about the job?
2. What did you like about the job before you started?
3. Why did you leave?
"What's amazing," Younger says, "is that after a few minutes, you will always have learned something about the candidate--whether positive or negative--that you would never have learned otherwise."

Here's why:
How did you find out about the job?
Job boards, general postings, online listings, job fairs--most people find their first few jobs that way, so that's certainly not a red flag.
But a candidate who continues to find each successive job from general postings probably hasn't figured out what he or she wants to do--and where he or she would like to do it.
He or she is just looking for a job; often, any job.
And that probably means he or she isn't particularly eager to work for you. He or she just wants a job. Yours will do--until something else comes along.
"Plus, by the time you get to Job Three, Four, or Five in your career, and you haven't been pulled into a job by someone you previously worked for, that's a red flag," Younger says. "That shows you didn't build relationships, develop trust, and show a level of competence that made someone go out of their way to bring you into their organization."
On the flip side, being pulled in is like a great reference--without the letter.

What did you like about the job before you started?
In time, interviewees should describe the reason they took a particular job for more specific reasons than "great opportunity," "chance to learn about the industry," or "next step in my career."
Great employees don't work hard because of lofty titles or huge salaries. They work hard because they appreciate their work environment and enjoy what they do. (Titles and salary are just icing on the fulfillment cake.)
That means they know the kind of environment they will thrive in, and they know the type of work that motivates and challenges them--and not only can they describe it, they actively seek it.

Why did you leave?
Sometimes people leave for a better opportunity. Sometimes they leave for more money.
Often, though, they leave because an employer is too demanding. Or the employee doesn't get along with his or her boss. Or the employee doesn't get along with co-workers.
When that is the case, don't be judgmental. Resist the temptation to ask for detail. Hang on to follow-ups. Stick to the rhythm of the three questions. That makes it natural for candidates to be more open and candid.
In the process, many candidates will describe issues with management or disagreements with other employees or with taking responsibility--issues they otherwise would not have shared.
Then follow up on patterns that concern you.
"It's a quick way to get to get to the heart of a candidate's sense of teamwork and responsibility," Younger says. "Some people never take ownership and always see problems as someone else's problem. And some candidates have consistently had problems with their bosses--which means they'll also have issues with you."
And a bonus question:

How many people have you hired, and where did you find them?
Say you're interviewing candidates for a leadership position. Want to know how their direct reports feel about them?
Don't look only for candidates who were brought into an organization by someone else; look for candidates who brought employees into their organization.
"Great employees go out of their way to work with great leaders," Younger says. "If you're tough but fair, and you treat people well, they will go out of their way to work with you. The fact that employees changed jobs just so they could work for you speaks volumes to your leadership and people skills."

No comments:

Post a Comment