|
I need to select all these:
I participate in interviews for new team members
I get to meet new potentials
I get to review resumes, code or other work done by new potentials
I get to provide other input
I don't get to provide any input on new team members
|
|
|
|
|
Agreed on the multiple choice option - I've had a couple of these over the years. At one company the manager didn't even consider our feedback so it was pretty much a futile exercise.
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music."
-- Marcus Brigstocke, British Comedian
|
|
|
|
|
.. not only the guy with a degree of Ph.D in software engineering, and also isn't the hacker guy of your town.
I am a part of people who develop indie softwares, and mostly I am working alone so I might not be able to provide a best option and methodology to select the programmers for your company. But Bill Gates said,
Bill Gates: If you get to hire a programmer, look at his source code. If he writes a lot of code don't hire him.
Which means, that to tell that the programmer you're hiring is best just because he made an awesome software application is useless. You should keep a note of his reviews on other softwares, the critical he gets the better he would write the similar application. When I have to work with someone, I try to read his code, his postings, to understand the real he.
So, only one option to decide which programmer would be fit for job is not good choice. You need to create a set of requirements for a programmer, his mathematical decisions, his logic solving IQ level, his answering tactics and so on. These all combine to define a programmer. In my town there are many who call themselves to be the best I even praised them when I was 15, but as soon as I came to learn programming, I found the concept of writing lengthy code is not what matters. The concept of writing efficient application is what matters the most.
Good luck programmers.
You only get one shot, do not miss your chance to blow
This opportunity comes once in a lifetime, yo - Eminem
~! Firewall !~
|
|
|
|
|
But I think with some experience and research only we can write efficient and short code.
|
|
|
|
|
Not only we, but anyone with basic understanding of concepts of programming and a programming object model. Anyone can write an efficient code. For that, we first of all need to draw a pseudo- of our requirement. We then extract the objects required, their properties. Once the sketch has been drawn, we can come up with the most efficient way of doing the programming thing.
Not only we, but any programmer! Sorry to disagree!
You only get one shot, do not miss your chance to blow
This opportunity comes once in a lifetime, yo - Eminem
~! Firewall !~
|
|
|
|
|
I work for a consulting company and here we have a group of technologies where we can be recognized as experts.
If you're in the pool of experts then you're often requested to interview candidates.
If a candidate spans through more than one area of expertise then he might have multiple interviews.
Also, and before he get to the technical interviews, the candidate has to "pass" a non-technical interview.
|
|
|
|
|
I got to see all resumés and sat at an interview once, but now that I resigned and I'm in my two months notice and they're looking for a replacement it seems my opinion is slightly less valued
It's an OO world.
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
My blog[ ^]
|
|
|
|
|
I used to do the initial phone screen as well as sit in on interviews and ask technical questions.
Our IT hiring model has since changed, and I'm no longer doing either. I do miss it. You got to see how other people solved problems in a stressful situation (depending on how they usually do in interviews).
|
|
|
|
|
Interestingly enough, when I was leaving a previous employer, my very last task was to interview a candidate. After talking to him, I wrote a recommendation to the team, returned the badge, and then we left for the farewell beer. Well, beers
|
|
|
|
|
Did they tell you, they were getting you a new assistant!?!
|
|
|
|
|
I get to provide input to branch of ours in another City I use to work for... To the guys that is working at my current workplace who wants to relocate there.
"Program testing can be used to show the presence of bugs, but never to show their absence."
<< please vote!! >>
|
|
|
|