Reducing Cycle Time

Use efficient telephone screens
The general rule in processing candidates is to keep cycle time to an absolute minimum. This keeps costs down and contributes to a higher success rate. Good candidates are hard to find, and even harder to keep. Assessing skills and screening a candidate quickly puts them in front of your client or hiring manager before the competition, and before the candidate gets another offer. Make yourself available for a candidate screen at their first convenience.

If you are surfing the web and find an excellent candidate, especially if you have reason to believe they have only recently put their resume online, call them immediately if the hour is appropriate! If you get voicemail, leave them a message stating that you're sending them an e-mail about a great opportunity. When they receive your follow-up call the next day, they may have read the job description, and if possible, you should be prepared to phone screen them at that time.

Many firms use a scheduler to book large quantities of phone screens. However, if a candidate expresses a willingness to conduct the phone screen on the spot, the scheduler should transfer the call to a recruiter who can conduct the screen immediately. This is particularly important for hard-to- find, highly technical candidates as it can reduce a candidate's resume cycle time by a day or more.

Maintain control of the phone interview.
Even excellent candidates can sometimes be challenging to get detailed information from (e.g., scientists and other highly technical people.) These candidates can be reluctant to "talk technical" with a recruiter. Learning a few key technical terms relevant to the project, and asking open-ended questions will usually reverse the problem. "Tell me about an experience writing Perl or Bourne shell scripts..." will get a better response than a vague query about their programming experience.

Other types of candidates can to be too wordy (for example sales, marketing, and project management candidates.)
These candidates should ideally be very forthcoming with information, but articulate and able to "sell themselves" to the interviewer. In all situations, maintain control over the interview. If necessary, politely interrupt a long-winded response, indicating you need a little time to get all of the information down clearly. The implication that something of quality might be missed will accomplish this task. Keep the conversation moving, and digress into light conversation only long enough to establish rapport and trust.

Phone screens are not just a verbal re-hashing of the candidate's resume.
The phone screen, like the face to face interview, allows you to assess qualities in a candidate that are not fully apparent on paper. Even before the screen occurs, this process is in play. Did the candidate miss a scheduled appointment? If so, did they reschedule promptly and courteously? A phone screen gives you an excellent opportunity to assess a candidate's communication skills.

This is especially important for public relations, sales people, project managers and those expected to have contact with clients or the public.
These candidates should be able to present themselves especially well in a phone screen. If done well, the phone screen can help you quickly identify the key reasons why a candidate is considering a job change. Make note of these and periodically match the benefits, opportunities, and culture that your company offers that might specifically address those motivations.

Think of your job as a professional recruiter in terms of being a private investigator. You are constantly listening closely, gathering new information, asking inquisitive and open-ended questions, and assessing information to draw your conclusions.

When you've developed a sense of the attributes you are seeking in a candidate, create a screening template that lists the key skills, years of experience, certifications, etc. that are required for the position. Create fields for important information like full contact information, salary requirements, availability, relocation requirements and motivation for job change. Also be prepared to assess skills that are not obvious from the resume that may be useful in matching the candidate with more than one opening. For example, sales experience plus a technical background could add up to a good candidate for a presales engineering position.

When screening candidates, having a template of your most important questions provides a standardized form to evaluate candidates and make notes. Whether you take notes directly into the template on your computer or by hand on a print out of the template, all the information you need will be presented in an organized fashion. While taking notes directly into the computer may be more efficient, unless you are prone to saving your work regularly (every 5 minutes) a single computer crash or freeze up could wipe out all your data.

The best finished document will summarize only what is necessary to convey the quality and distinction of your candidate. Bullet point summaries are a good way to do this. Focus on a few major skills, supplying some detail below each. Highlight relevant recent experience, positions and projects in a concise manner. If you discover a secondary skill set in the candidate not relevant to the current position, include that in your personal notes. Your ultimate goal for the screen is that it be well organized, thorough yet concise, and easy to follow, so that the hiring manager feels he or she can make a next step decision without having to thoroughly comb the resume.

The Technical Pre-Screen

The initial candidate prescreen is essential to determining fit for the positions you are filling. Whether in person or over the phone, this assessment is a crucial step in gathering as much information about the candidate as possible. When screening technical and other scientifically-oriented candidates this is especially critical. While some technical recruiters originally come from a technical background, some of the best technical recruiters learned along the way. Many of the best technical recruiters have never taken a single class on technology. Instead they have an open mind, listen closely to what the candidates tell them, learn from their candidates, utilize all available resources and employ good interview techniques.

The first, and one of the most general techniques is to "let down your guard" with the candidate. Let them know that you are not a technical expert but thoroughly understand what it takes to be successful in this company. State that you have a strong conceptual understanding of technology but no specific experience. While you still retain control of the interview process, you allow the candidate to educate you on their technical skills and the technology in general. Make it understood that you need to clearly transcribe their skills and experience with technology. The benefits to this technique are that you become better educated on the subject as you perform each pre-screen and you encourage the candidate to be clear, complete and concise in their explanations to you.
Educate Yourself Access sources of information on the technology for which you are planning to screen. Talk to your client and have them explain exactly what the position's role in the organization is going to be and the key skill sets and experiences for which you should be looking. Take this information and access some resources to educate yourself on the technology. You need to know enough to ask intelligent, open ended questions relevant to the position you are filling. Start by prompting the candidate with questions like, "tell me about your experience in programming Informix databases". If you are asking "yes or no" questions, you will have to be very knowledgeable yourself to get all of the information you need. As you get better acquainted with a technology, you will find that you can hone in more quickly on a given point and use specific, direct questions such as "have you programmed 4GLs for Informix databases?" Take the terminology you hear from your best candidates back to your reference materials to use as a starting point for further investigation. We recommend that you use a simple 4 step interview methodology --- Identify, Quantify, Qualify and Verify. Identify the candidate's key skill sets, quantify the number of years they have with the technology, qualify whether they feel their skill with the technology is heavy, medium or light, and finally verify their experience with specific examples.

Certifications

Acquainting yourself with certifications appropriate to the skills you are screening for is a great way to determine a candidate's proficiency. Start by reviewing the resume for certifications, confirm this information during the pre-screen and inquire about any other certifications the candidate has that may be relevant. In many rapidly changing technologies, you'll also need to determine how recently the candidate was certified. If the certification was not recent, it is critical that the candidate has been working in this skill area in recent positions to insure that they are up to speed in a given technology. Increasingly, candidates and recruiters are using the resume as a "string" of searchable words, easily retrievable on the Internet. The tactical placement of technology buzzwords and certification acronyms will assure that resumes are matched and retrieved by automated agents or an ordinary search engine. This is a great starting point in finding the right resume, but only with intelligent questions can the recruiter ascertain if these terms are relevant, up to date, and truly representative of the right candidate. An added benefit to being familiar with appropriate certifications is that you'll have an extra "clue" in finding candidates on job boards and the Web because you can search for the certification name or acronym.

Group Think

If you are continually recruiting in the same technology area, "hang out" in a user or discussion group or subscribe to a mailing list relevant to the technology. This will provide you with information on some of the important buzzwords associated with that technology and may even clue you in to recent developments. Single out those regular contributors to the discussion, and if they seem to be helpful and open in their comments, you can contact them directly outside of the discussion to ask about a technical issue. If you do not interrupt the discussion list, and are frank yet courteous in your inquiry, many technical people will be more than happy to help you. Defer to their expertise and let them know that you are a recruiter seeking some information about a specific technological subject. Stay focused on information gathering and don't be tempted to directly solicit them for a job opening. However, you may find that a good relationship with one of these resident "experts" on a discussion list will yield an added benefit in the long term: referrals and requests for information from you about your current job openings.

Make Your Point

As in any pre-screen, the written document you send to your client or hiring manager is the critical step to moving the candidate forward in the interview process. Summarize the information you've gathered on the candidate in a form that conveys very clearly the exact level of competency in critical areas. If you've used the four-step interview method: identify, quantify, qualify and verify, your write up should be very simple and straightforward to complete. This presentation has three aspects: technical skills, actual experience, and certifications. It is not enough to say that the candidate "has experience with" a given technology; details about the number of years, and a simple, consistent scale (i.e., "light", "medium" or "heavy" experience) provides a great deal of information in a few words. Also include a few sentences on past projects the candidate has completed in relevant skill sets, including the scope of the project, the candidate's role, the length and technical parameters of the project, and details of the quality and success of the effort.

For Technical Recruiter - 1 (Interview Questions -ADO.NET and Database Questions

1. What is the role of the DataReader class in ADO.NET connections?
It returns a read-only, forward-only rowset from the data source. A DataReader provides fast access when a forward-only sequential read is needed.

2. What are advantages and disadvantages of Microsoft-provided data provider classes in ADO.NET?
SQLServer.NET data provider is high-speed and robust, but requires SQL Server license purchased from Microsoft. OLE-DB.NET is universal for accessing other sources, like Oracle, DB2, Microsoft Access and Informix. OLE-DB.NET is a .NET layer on top of the OLE layer, so it’s not as fastest and efficient as SqlServer.NET.

3. What is the wildcard character in SQL?
Let’s say you want to query database with LIKE for all employees whose name starts with La. The wildcard character is %, the proper query with LIKE would involve ‘La%’.

4. Explain ACID rule of thumb for transactions.
A transaction must be:
1. Atomic - it is one unit of work and does not dependent on previous and following transactions.
2. Consistent - data is either committed or roll back, no “in-between” case where something has been updated and something hasn’t.
3. Isolated - no transaction sees the intermediate results of the current transaction).
4. Durable - the values persist if the data had been committed even if the system crashes right after.

5. What connections does Microsoft SQL Server support?
Windows Authentication (via Active Directory) and SQL Server authentication (via Microsoft SQL Server username and password).

6. Between Windows Authentication and SQL Server Authentication, which one is trusted and which one is untrusted?
Windows Authentication is trusted because the username and password are checked with the Active Directory, the SQL Server authentication is untrusted, since SQL Server is the only verifier participating in the transaction.

7. What does the Initial Catalog parameter define in the connection string?
The database name to connect to.

8. What does the Dispose method do with the connection object?
Deletes it from the memory.
To Do: answer better. The current answer is not entirely correct.

9. What is a pre-requisite for connection pooling?
Multiple processes must agree that they will share the same connection, where every parameter is the same, including the security settings. The connection string must be identical.

AFTAB KHAN

For Technical Recruiter - 2 Interview Questions-Testing

Debugging and Testing Questions

1. What debugging tools come with the .NET SDK?
1. CorDBG – command-line debugger. To use CorDbg, you must compile the original C# file using the /debug switch.
2. DbgCLR – graphic debugger. Visual Studio .NET uses the DbgCLR.

2. What does assert() method do?
In debug compilation, assert takes in a Boolean condition as a parameter, and shows the error dialog if the condition is false. The program proceeds without any interruption if the condition is true.

3. What’s the difference between the Debug class and Trace class?
Documentation looks the same. Use Debug class for debug builds, use Trace class for both debug and release builds.

4. Why are there five tracing levels in System.Diagnostics.TraceSwitcher?
The tracing dumps can be quite verbose. For applications that are constantly running you run the risk of overloading the machine and the hard drive. Five levels range from None to Verbose, allowing you to fine-tune the tracing activities.

5. Where is the output of TextWriterTraceListener redirected?
To the Console or a text file depending on the parameter passed to the constructor.

6. How do you debug an ASP.NET Web application?
Attach the aspnet_wp.exe process to the DbgClr debugger.

7. What are three test cases you should go through in unit testing?
1. Positive test cases (correct data, correct output).
2. Negative test cases (broken or missing data, proper handling).
3. Exception test cases (exceptions are thrown and caught properly).

8. Can you change the value of a variable while debugging a C# application?
Yes. If you are debugging via Visual Studio.NET, just go to Immediate window.

For Technical Recruiter - 2 Interview Questions- Event & XML

Events and Delegates

What’s a delegate?
A delegate object encapsulates a reference to a method.

What’s a multicast delegate?
A delegate that has multiple handlers assigned to it. Each assigned handler (method) is called.

XML Documentation Questions

Is XML case-sensitive?
Yes.

What’s the difference between // comments, /* */ comments and /// comments?
Single-line comments, multi-line comments, and XML documentation comments.

How do you generate documentation from the C# file commented properly with a command-line compiler? Compile it with the /doc switch.

For Technical Recruiter - 1 (Interview Questions -Method and Property Questions

What’s the implicit name of the parameter that gets passed into the set method/property of a class?
Value. The data type of the value parameter is defined by whatever data type the property is declared as.

What does the keyword “virtual” declare for a method or property?
The method or property can be overridden.

How is method overriding different from method overloading?
When overriding a method, you change the behavior of the method for the derived class. Overloading a method simply involves having another method with the same name within the class.

Can you declare an override method to be static if the original method is not static?
No. The signature of the virtual method must remain the same. (Note: Only the keyword virtual is changed to keyword override)

What are the different ways a method can be overloaded?
Different parameter data types, different number of parameters, different order of parameters. If a base class has a number of overloaded constructors, and an inheriting class has a number of overloaded constructors;

can you enforce a call from an inherited constructor to a specific base constructor?
Yes, just place a colon, and then keyword base (parameter list to invoke the appropriate constructor) in the overloaded constructor definition inside the inherited class.

Aftab Khan

For Technical Recruiter - 2 Interview Questions-Class Questions

What is the syntax to inherit from a class in C#?
Place a colon and then the name of the base class.Example: class MyNewClass : MyBaseClass

Can you prevent your class from being inherited by another class?
Yes. The keyword “sealed” will prevent the class from being inherited.

Can you allow a class to be inherited, but prevent the method from being over-ridden?
Yes. Just leave the class public and make the method sealed.

What’s an abstract class?
A class that cannot be instantiated. An abstract class is a class that must be inherited and have the methods overridden. An abstract class is essentially a blueprint for a class without any implementation.

When do you absolutely have to declare a class as abstract?
1. When the class itself is inherited from an abstract class, but not all base abstract methods have been overridden.
2. When at least one of the methods in the class is abstract.

What is an interface class?
Interfaces, like classes, define a set of properties, methods, and events. But unlike classes, interfaces do not provide implementation. They are implemented by classes, and defined as separate entities from classes.

Why can’t you specify the accessibility modifier for methods inside the interface?
They all must be public, and are therefore public by default.

Can you inherit multiple interfaces?
Yes. .NET does support multiple interfaces.

What happens if you inherit multiple interfaces and they have conflicting method names?
It’s up to you to implement the method inside your own class, so implementation is left entirely up to you. This might cause a problem on a higher-level scale if similarly named methods from different interfaces expect different data, but as far as compiler cares you’re okay. To Do: Investigate

What’s the difference between an interface and abstract class?
In an interface class, all methods are abstract - there is no implementation. In an abstract class some methods can be concrete. In an interface class, no accessibility modifiers are allowed. An abstract class may have accessibility modifiers.

What is the difference between a Struct and a Class?
Structs are value-type variables and are thus saved on the stack, additional overhead but faster retrieval. Another difference is that structs cannot inherit.

AFTAB KHAN