Discussion Locked

Recruitment: Skills Assessment

0 helpful
15 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We are in the process of recruiting developers
for windows platform and web development
particularly (C++, JSP/ASP/PHP, DHTML, Java,
SQL/MySQL, and windows development). I am task
to create an evaluation questionnaire or skill
test to evaluate the candidates (personality and
skills); I have no idea where to start, and if
there is an available one I can download I will
use that instead. Does any one know where these
might be available for download?

15 replies

by timwalsh

Don't know of any sights where you could download a ready-made evaluation guidline or skills test. Even if there are some available, they may or may not fit your specific situation.

Are you a developer or an HR/Admin person? If you are not a developer yourself, you need to ask the developers what skills they want new hires to have. They should develop the skills test. If you are a developer, approach the test from the point of view of: If you were hiring an assistant, what skills would you want that assitant to have?

Generally, skill areas to be tested would be familiarity with the particular programming language, familiarity with standards/common practices for that language, ability to write clean, well documented code, abilityto troubleshoot/debug code, etc.

On the personality side, much will depend on your company culture and what type of person will fit in well. Generally, you will want to find out such things as: general demeanor, ability to work with others, ability to work alone or without guidance, ability to interface with clients, ability to work under stress, ability to accept criticism, etc. (i.e. will this person fit into your company without making waves or becoming an embaressment to the company).
Hope this leads you in the right direction.

by hkray

I won't give you a direct answer as in a list, but what I would say would be a good approach would be to have the person give their opinion of how these skill "web development
particularly (C++, JSP/ASP/PHP, DHTML, Java,
SQL/MySQL, and windows development" fit together and how they see them evolving in the now near future.

Yes, you would need to have a clear understanding about this subject, as in a tech person giving you guidance or doing a little homework looking at the subject superficially.

Two things should arise from this.

1)This should identify the people that know where the field is and where it is going.

2) Since this field is in dramatic fluxs, you will be able to root out the forward thinking folks and along with your other skills assesment test be able to get someone that will be valuable today and tomorrow.

I know this may be off the subject, but the list that you have given is very broad and an expert in these subjects that may know the technical aspects may not be clear on how these tools are evolving and how they fit in the new modals that arise from this evolution. And also which tools will not be so valuable in the near future and what skills will be necessary to suppliment these changes...

by pm100

The following are the golden rules i follow when I recruit.

1) Education background
2) Kinds of Projects worked on including the client name
3) duration of employement
4) Roles in the projects handled.
5) Specific skills for your project

If you follow these as a base, your chances of getting the wrong persons in are less likely.
For example, if you look at pt 2 above, getting to know the previous clients and the type of project worked on gives you an idea of the capability of the person.

All the above is of course folloewd by the usual technical interview etc, and that acts like a filter to get the gems out of the chaff.

by pm100

The following are the golden rules i follow when I recruit.

1) Education background
2) Kinds of Projects worked on including the client name
3) duration of employement
4) Roles in the projects handled.
5) Specific skills for your project

If you follow these as a base, your chances of getting the wrong persons in are less likely.
For example, if you look at pt 2 above, getting to know the previous clients and the type of project worked on gives you an idea of the capability of the person.

All the above is of course folloewd by the usual technical interview etc, and that acts like a filter to get the gems out of the chaff.

by techrepublic

As a slight drift from the topic, the book "Hiring Systems Administrators" by Gretchen Phillips (ISBN 1-880446-38-3) has some interesting points regarding technical interviews.

I just thought it might give an interesting perspective for you.

This discussion is closed to new replies.