How do I evaluate a candidate for a junior position?
After working with my boss at a previous job he's decided to start a contracting firm and I'm in the first handful of people to help get things started. It's been a few months and now we're looking to expand and hire a more junior developer.
I've helped my boss hire knowledgeable senior level people that I was going to work directly with. It was easier to ask hard questions and if they had a correct answer then I could believe they were good for the job. If I ask a senior person hard questions that they don't know the answer to, I start to have a feeling it may not be a good fit.
Trying to come up with questions for a junior level has me second guessing how to receive their answer. If I ask a junior person easier questions and they don't have an answer, is it because I asked a slightly too hard question for a junior? Should they know this answer? If they got it right, did I ask too easy a question? In theory it makes sense to ask them some technical questions but also some "are you capable of learning what you need to know in order to do your job" kind of questions but that's turning out to be hard in practice.
How can I ask the right questions and set my own expectations properly for interviewing a junior candidate?
interviewing junior
New contributor
add a comment |
After working with my boss at a previous job he's decided to start a contracting firm and I'm in the first handful of people to help get things started. It's been a few months and now we're looking to expand and hire a more junior developer.
I've helped my boss hire knowledgeable senior level people that I was going to work directly with. It was easier to ask hard questions and if they had a correct answer then I could believe they were good for the job. If I ask a senior person hard questions that they don't know the answer to, I start to have a feeling it may not be a good fit.
Trying to come up with questions for a junior level has me second guessing how to receive their answer. If I ask a junior person easier questions and they don't have an answer, is it because I asked a slightly too hard question for a junior? Should they know this answer? If they got it right, did I ask too easy a question? In theory it makes sense to ask them some technical questions but also some "are you capable of learning what you need to know in order to do your job" kind of questions but that's turning out to be hard in practice.
How can I ask the right questions and set my own expectations properly for interviewing a junior candidate?
interviewing junior
New contributor
3
What are your current expectations regarding their role? If you don't have that figured out it will be tough to find candidates to fill the role.
– sf02
8 hours ago
Interviewing people demands a high responsibility. Make sure you guys have a clear notion of what you are looking for. Apply tests if necessary. The junior has expectatios just like you. And both expectations must be very well aligned. It sucks really bad for an enployee when he/she is not sure enough about his/her role at the company. It might drain the employe's enthusiasm and self-steem.
– wes85melis
8 hours ago
Finding programmers is the only thing harder than programming.
– Fattie
7 hours ago
add a comment |
After working with my boss at a previous job he's decided to start a contracting firm and I'm in the first handful of people to help get things started. It's been a few months and now we're looking to expand and hire a more junior developer.
I've helped my boss hire knowledgeable senior level people that I was going to work directly with. It was easier to ask hard questions and if they had a correct answer then I could believe they were good for the job. If I ask a senior person hard questions that they don't know the answer to, I start to have a feeling it may not be a good fit.
Trying to come up with questions for a junior level has me second guessing how to receive their answer. If I ask a junior person easier questions and they don't have an answer, is it because I asked a slightly too hard question for a junior? Should they know this answer? If they got it right, did I ask too easy a question? In theory it makes sense to ask them some technical questions but also some "are you capable of learning what you need to know in order to do your job" kind of questions but that's turning out to be hard in practice.
How can I ask the right questions and set my own expectations properly for interviewing a junior candidate?
interviewing junior
New contributor
After working with my boss at a previous job he's decided to start a contracting firm and I'm in the first handful of people to help get things started. It's been a few months and now we're looking to expand and hire a more junior developer.
I've helped my boss hire knowledgeable senior level people that I was going to work directly with. It was easier to ask hard questions and if they had a correct answer then I could believe they were good for the job. If I ask a senior person hard questions that they don't know the answer to, I start to have a feeling it may not be a good fit.
Trying to come up with questions for a junior level has me second guessing how to receive their answer. If I ask a junior person easier questions and they don't have an answer, is it because I asked a slightly too hard question for a junior? Should they know this answer? If they got it right, did I ask too easy a question? In theory it makes sense to ask them some technical questions but also some "are you capable of learning what you need to know in order to do your job" kind of questions but that's turning out to be hard in practice.
How can I ask the right questions and set my own expectations properly for interviewing a junior candidate?
interviewing junior
interviewing junior
New contributor
New contributor
New contributor
asked 8 hours ago
Corey OgburnCorey Ogburn
1675
1675
New contributor
New contributor
3
What are your current expectations regarding their role? If you don't have that figured out it will be tough to find candidates to fill the role.
– sf02
8 hours ago
Interviewing people demands a high responsibility. Make sure you guys have a clear notion of what you are looking for. Apply tests if necessary. The junior has expectatios just like you. And both expectations must be very well aligned. It sucks really bad for an enployee when he/she is not sure enough about his/her role at the company. It might drain the employe's enthusiasm and self-steem.
– wes85melis
8 hours ago
Finding programmers is the only thing harder than programming.
– Fattie
7 hours ago
add a comment |
3
What are your current expectations regarding their role? If you don't have that figured out it will be tough to find candidates to fill the role.
– sf02
8 hours ago
Interviewing people demands a high responsibility. Make sure you guys have a clear notion of what you are looking for. Apply tests if necessary. The junior has expectatios just like you. And both expectations must be very well aligned. It sucks really bad for an enployee when he/she is not sure enough about his/her role at the company. It might drain the employe's enthusiasm and self-steem.
– wes85melis
8 hours ago
Finding programmers is the only thing harder than programming.
– Fattie
7 hours ago
3
3
What are your current expectations regarding their role? If you don't have that figured out it will be tough to find candidates to fill the role.
– sf02
8 hours ago
What are your current expectations regarding their role? If you don't have that figured out it will be tough to find candidates to fill the role.
– sf02
8 hours ago
Interviewing people demands a high responsibility. Make sure you guys have a clear notion of what you are looking for. Apply tests if necessary. The junior has expectatios just like you. And both expectations must be very well aligned. It sucks really bad for an enployee when he/she is not sure enough about his/her role at the company. It might drain the employe's enthusiasm and self-steem.
– wes85melis
8 hours ago
Interviewing people demands a high responsibility. Make sure you guys have a clear notion of what you are looking for. Apply tests if necessary. The junior has expectatios just like you. And both expectations must be very well aligned. It sucks really bad for an enployee when he/she is not sure enough about his/her role at the company. It might drain the employe's enthusiasm and self-steem.
– wes85melis
8 hours ago
Finding programmers is the only thing harder than programming.
– Fattie
7 hours ago
Finding programmers is the only thing harder than programming.
– Fattie
7 hours ago
add a comment |
4 Answers
4
active
oldest
votes
As a slight frame challenge to your question, you need to get some clarity on what the role requires and then ask questions specific to that. In other words, I have the feeling that your real problem is that you don't have a clear idea of what skills you want in this person. Find that out and the questions will follow.
Stop over-thinking "easy" versus "hard" questions. Write down what the person needs to be able to do and then ask them questions about what you've written down.
2
Amazing answer Sir. How do you have so much wisdom?
– anonymous
8 hours ago
10
I've made lots of mistakes and done my best to learn from them.
– dwizum
6 hours ago
add a comment |
For a Junior, it's less about what they know, and more about who they are.
If they don't know the answer to a technical question, follow up with something like?
You said you don't know. How would you find out, and then implement it?
For the tech questions themselves, have sets of Basic, intermediate, and advanced. Climb the difficulty tree until you get an "I don't know, then ask that question above.
Ask more soft questions like:
Your senior has assigned you a task. You feel like it's beyond your abilities, what do you do?
or
How long do you see yourself staying as a junior? How would you hone your skills to be worth more to the company?
Also, keep in mind that the more junior people are also inexperienced in interviews and may blow tech questions that they know.
Go for more of the "How would you" type questions as opposed to "what is" type of questions.
most importantly
Interview for fit. Your eventual goal is to advance a junior in your company, the better a fit he is, the easier it will be to upskill him, and eventually train the next junior(s) that apply.
You can teach people more tech skills, you can't teach a jerk to be a decent person
Again, this is why you want to interview more for ability to expand and learn than for raw tech skill. If he's lacking in a few areas, you can get him up to speed. If he's going to be a disruption, nothing will cure that.
add a comment |
First, decide what you want the person you're hiring to actually do. Based on that, decide which skills and knowledge are important for this role. You probably want to align with your boss on those points.
Make sure that your job description and list of qualifications accurately reflect that. In terms of the job description, make sure that you accurately describe what you want the person to actually do and accomplish - describe the job, not the kind of person you're looking to hire. Once you have that, come up with your "people description" - i.e. what kind of person you're looking to hire and what your desired qualifications are. Make sure that that aligns with your job description. A good people description should describe someone who is likely to be able to do what your Job Description specifies.
A "qualified" candidate is someone who meets the requirements in your "people description."
Based on the job description and the people description, you should come up with a list of questions that'll help you know whether the person in question meets the requirements in your people description. Rank your questions in order of easiest to hardest, so that you can determine the person's skill level.
Some good questions could include, for example, reversing a string without using string.reverse
(yes, some people actually get this wrong), sorting a list, or the classic FizzBuzz challenge.
add a comment |
It's not a great idea to put a junior on the spot in an interview. I think a far better approach is to set them a simple coding task and give them a certain amount of time to complete it. It will show their ability to learn and solve problems. You could even set this test before inviting them in for a face to face interview.
I cannot code while people watch me, it's awkward. I have always hated interviews where I'm asked to do this. Of course asking some probing questions to judge someone problem solving abilities is good but try keep it general not specific, if that makes sense?
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "423"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: false,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Corey Ogburn is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f128769%2fhow-do-i-evaluate-a-candidate-for-a-junior-position%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
StackExchange.ready(function () {
$("#show-editor-button input, #show-editor-button button").click(function () {
var showEditor = function() {
$("#show-editor-button").hide();
$("#post-form").removeClass("dno");
StackExchange.editor.finallyInit();
};
var useFancy = $(this).data('confirm-use-fancy');
if(useFancy == 'True') {
var popupTitle = $(this).data('confirm-fancy-title');
var popupBody = $(this).data('confirm-fancy-body');
var popupAccept = $(this).data('confirm-fancy-accept-button');
$(this).loadPopup({
url: '/post/self-answer-popup',
loaded: function(popup) {
var pTitle = $(popup).find('h2');
var pBody = $(popup).find('.popup-body');
var pSubmit = $(popup).find('.popup-submit');
pTitle.text(popupTitle);
pBody.html(popupBody);
pSubmit.val(popupAccept).click(showEditor);
}
})
} else{
var confirmText = $(this).data('confirm-text');
if (confirmText ? confirm(confirmText) : true) {
showEditor();
}
}
});
});
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
As a slight frame challenge to your question, you need to get some clarity on what the role requires and then ask questions specific to that. In other words, I have the feeling that your real problem is that you don't have a clear idea of what skills you want in this person. Find that out and the questions will follow.
Stop over-thinking "easy" versus "hard" questions. Write down what the person needs to be able to do and then ask them questions about what you've written down.
2
Amazing answer Sir. How do you have so much wisdom?
– anonymous
8 hours ago
10
I've made lots of mistakes and done my best to learn from them.
– dwizum
6 hours ago
add a comment |
As a slight frame challenge to your question, you need to get some clarity on what the role requires and then ask questions specific to that. In other words, I have the feeling that your real problem is that you don't have a clear idea of what skills you want in this person. Find that out and the questions will follow.
Stop over-thinking "easy" versus "hard" questions. Write down what the person needs to be able to do and then ask them questions about what you've written down.
2
Amazing answer Sir. How do you have so much wisdom?
– anonymous
8 hours ago
10
I've made lots of mistakes and done my best to learn from them.
– dwizum
6 hours ago
add a comment |
As a slight frame challenge to your question, you need to get some clarity on what the role requires and then ask questions specific to that. In other words, I have the feeling that your real problem is that you don't have a clear idea of what skills you want in this person. Find that out and the questions will follow.
Stop over-thinking "easy" versus "hard" questions. Write down what the person needs to be able to do and then ask them questions about what you've written down.
As a slight frame challenge to your question, you need to get some clarity on what the role requires and then ask questions specific to that. In other words, I have the feeling that your real problem is that you don't have a clear idea of what skills you want in this person. Find that out and the questions will follow.
Stop over-thinking "easy" versus "hard" questions. Write down what the person needs to be able to do and then ask them questions about what you've written down.
answered 8 hours ago
dwizumdwizum
15.3k73153
15.3k73153
2
Amazing answer Sir. How do you have so much wisdom?
– anonymous
8 hours ago
10
I've made lots of mistakes and done my best to learn from them.
– dwizum
6 hours ago
add a comment |
2
Amazing answer Sir. How do you have so much wisdom?
– anonymous
8 hours ago
10
I've made lots of mistakes and done my best to learn from them.
– dwizum
6 hours ago
2
2
Amazing answer Sir. How do you have so much wisdom?
– anonymous
8 hours ago
Amazing answer Sir. How do you have so much wisdom?
– anonymous
8 hours ago
10
10
I've made lots of mistakes and done my best to learn from them.
– dwizum
6 hours ago
I've made lots of mistakes and done my best to learn from them.
– dwizum
6 hours ago
add a comment |
For a Junior, it's less about what they know, and more about who they are.
If they don't know the answer to a technical question, follow up with something like?
You said you don't know. How would you find out, and then implement it?
For the tech questions themselves, have sets of Basic, intermediate, and advanced. Climb the difficulty tree until you get an "I don't know, then ask that question above.
Ask more soft questions like:
Your senior has assigned you a task. You feel like it's beyond your abilities, what do you do?
or
How long do you see yourself staying as a junior? How would you hone your skills to be worth more to the company?
Also, keep in mind that the more junior people are also inexperienced in interviews and may blow tech questions that they know.
Go for more of the "How would you" type questions as opposed to "what is" type of questions.
most importantly
Interview for fit. Your eventual goal is to advance a junior in your company, the better a fit he is, the easier it will be to upskill him, and eventually train the next junior(s) that apply.
You can teach people more tech skills, you can't teach a jerk to be a decent person
Again, this is why you want to interview more for ability to expand and learn than for raw tech skill. If he's lacking in a few areas, you can get him up to speed. If he's going to be a disruption, nothing will cure that.
add a comment |
For a Junior, it's less about what they know, and more about who they are.
If they don't know the answer to a technical question, follow up with something like?
You said you don't know. How would you find out, and then implement it?
For the tech questions themselves, have sets of Basic, intermediate, and advanced. Climb the difficulty tree until you get an "I don't know, then ask that question above.
Ask more soft questions like:
Your senior has assigned you a task. You feel like it's beyond your abilities, what do you do?
or
How long do you see yourself staying as a junior? How would you hone your skills to be worth more to the company?
Also, keep in mind that the more junior people are also inexperienced in interviews and may blow tech questions that they know.
Go for more of the "How would you" type questions as opposed to "what is" type of questions.
most importantly
Interview for fit. Your eventual goal is to advance a junior in your company, the better a fit he is, the easier it will be to upskill him, and eventually train the next junior(s) that apply.
You can teach people more tech skills, you can't teach a jerk to be a decent person
Again, this is why you want to interview more for ability to expand and learn than for raw tech skill. If he's lacking in a few areas, you can get him up to speed. If he's going to be a disruption, nothing will cure that.
add a comment |
For a Junior, it's less about what they know, and more about who they are.
If they don't know the answer to a technical question, follow up with something like?
You said you don't know. How would you find out, and then implement it?
For the tech questions themselves, have sets of Basic, intermediate, and advanced. Climb the difficulty tree until you get an "I don't know, then ask that question above.
Ask more soft questions like:
Your senior has assigned you a task. You feel like it's beyond your abilities, what do you do?
or
How long do you see yourself staying as a junior? How would you hone your skills to be worth more to the company?
Also, keep in mind that the more junior people are also inexperienced in interviews and may blow tech questions that they know.
Go for more of the "How would you" type questions as opposed to "what is" type of questions.
most importantly
Interview for fit. Your eventual goal is to advance a junior in your company, the better a fit he is, the easier it will be to upskill him, and eventually train the next junior(s) that apply.
You can teach people more tech skills, you can't teach a jerk to be a decent person
Again, this is why you want to interview more for ability to expand and learn than for raw tech skill. If he's lacking in a few areas, you can get him up to speed. If he's going to be a disruption, nothing will cure that.
For a Junior, it's less about what they know, and more about who they are.
If they don't know the answer to a technical question, follow up with something like?
You said you don't know. How would you find out, and then implement it?
For the tech questions themselves, have sets of Basic, intermediate, and advanced. Climb the difficulty tree until you get an "I don't know, then ask that question above.
Ask more soft questions like:
Your senior has assigned you a task. You feel like it's beyond your abilities, what do you do?
or
How long do you see yourself staying as a junior? How would you hone your skills to be worth more to the company?
Also, keep in mind that the more junior people are also inexperienced in interviews and may blow tech questions that they know.
Go for more of the "How would you" type questions as opposed to "what is" type of questions.
most importantly
Interview for fit. Your eventual goal is to advance a junior in your company, the better a fit he is, the easier it will be to upskill him, and eventually train the next junior(s) that apply.
You can teach people more tech skills, you can't teach a jerk to be a decent person
Again, this is why you want to interview more for ability to expand and learn than for raw tech skill. If he's lacking in a few areas, you can get him up to speed. If he's going to be a disruption, nothing will cure that.
answered 6 hours ago
Richard URichard U
94.3k68247377
94.3k68247377
add a comment |
add a comment |
First, decide what you want the person you're hiring to actually do. Based on that, decide which skills and knowledge are important for this role. You probably want to align with your boss on those points.
Make sure that your job description and list of qualifications accurately reflect that. In terms of the job description, make sure that you accurately describe what you want the person to actually do and accomplish - describe the job, not the kind of person you're looking to hire. Once you have that, come up with your "people description" - i.e. what kind of person you're looking to hire and what your desired qualifications are. Make sure that that aligns with your job description. A good people description should describe someone who is likely to be able to do what your Job Description specifies.
A "qualified" candidate is someone who meets the requirements in your "people description."
Based on the job description and the people description, you should come up with a list of questions that'll help you know whether the person in question meets the requirements in your people description. Rank your questions in order of easiest to hardest, so that you can determine the person's skill level.
Some good questions could include, for example, reversing a string without using string.reverse
(yes, some people actually get this wrong), sorting a list, or the classic FizzBuzz challenge.
add a comment |
First, decide what you want the person you're hiring to actually do. Based on that, decide which skills and knowledge are important for this role. You probably want to align with your boss on those points.
Make sure that your job description and list of qualifications accurately reflect that. In terms of the job description, make sure that you accurately describe what you want the person to actually do and accomplish - describe the job, not the kind of person you're looking to hire. Once you have that, come up with your "people description" - i.e. what kind of person you're looking to hire and what your desired qualifications are. Make sure that that aligns with your job description. A good people description should describe someone who is likely to be able to do what your Job Description specifies.
A "qualified" candidate is someone who meets the requirements in your "people description."
Based on the job description and the people description, you should come up with a list of questions that'll help you know whether the person in question meets the requirements in your people description. Rank your questions in order of easiest to hardest, so that you can determine the person's skill level.
Some good questions could include, for example, reversing a string without using string.reverse
(yes, some people actually get this wrong), sorting a list, or the classic FizzBuzz challenge.
add a comment |
First, decide what you want the person you're hiring to actually do. Based on that, decide which skills and knowledge are important for this role. You probably want to align with your boss on those points.
Make sure that your job description and list of qualifications accurately reflect that. In terms of the job description, make sure that you accurately describe what you want the person to actually do and accomplish - describe the job, not the kind of person you're looking to hire. Once you have that, come up with your "people description" - i.e. what kind of person you're looking to hire and what your desired qualifications are. Make sure that that aligns with your job description. A good people description should describe someone who is likely to be able to do what your Job Description specifies.
A "qualified" candidate is someone who meets the requirements in your "people description."
Based on the job description and the people description, you should come up with a list of questions that'll help you know whether the person in question meets the requirements in your people description. Rank your questions in order of easiest to hardest, so that you can determine the person's skill level.
Some good questions could include, for example, reversing a string without using string.reverse
(yes, some people actually get this wrong), sorting a list, or the classic FizzBuzz challenge.
First, decide what you want the person you're hiring to actually do. Based on that, decide which skills and knowledge are important for this role. You probably want to align with your boss on those points.
Make sure that your job description and list of qualifications accurately reflect that. In terms of the job description, make sure that you accurately describe what you want the person to actually do and accomplish - describe the job, not the kind of person you're looking to hire. Once you have that, come up with your "people description" - i.e. what kind of person you're looking to hire and what your desired qualifications are. Make sure that that aligns with your job description. A good people description should describe someone who is likely to be able to do what your Job Description specifies.
A "qualified" candidate is someone who meets the requirements in your "people description."
Based on the job description and the people description, you should come up with a list of questions that'll help you know whether the person in question meets the requirements in your people description. Rank your questions in order of easiest to hardest, so that you can determine the person's skill level.
Some good questions could include, for example, reversing a string without using string.reverse
(yes, some people actually get this wrong), sorting a list, or the classic FizzBuzz challenge.
edited 7 hours ago
answered 7 hours ago
EJoshuaSEJoshuaS
621216
621216
add a comment |
add a comment |
It's not a great idea to put a junior on the spot in an interview. I think a far better approach is to set them a simple coding task and give them a certain amount of time to complete it. It will show their ability to learn and solve problems. You could even set this test before inviting them in for a face to face interview.
I cannot code while people watch me, it's awkward. I have always hated interviews where I'm asked to do this. Of course asking some probing questions to judge someone problem solving abilities is good but try keep it general not specific, if that makes sense?
add a comment |
It's not a great idea to put a junior on the spot in an interview. I think a far better approach is to set them a simple coding task and give them a certain amount of time to complete it. It will show their ability to learn and solve problems. You could even set this test before inviting them in for a face to face interview.
I cannot code while people watch me, it's awkward. I have always hated interviews where I'm asked to do this. Of course asking some probing questions to judge someone problem solving abilities is good but try keep it general not specific, if that makes sense?
add a comment |
It's not a great idea to put a junior on the spot in an interview. I think a far better approach is to set them a simple coding task and give them a certain amount of time to complete it. It will show their ability to learn and solve problems. You could even set this test before inviting them in for a face to face interview.
I cannot code while people watch me, it's awkward. I have always hated interviews where I'm asked to do this. Of course asking some probing questions to judge someone problem solving abilities is good but try keep it general not specific, if that makes sense?
It's not a great idea to put a junior on the spot in an interview. I think a far better approach is to set them a simple coding task and give them a certain amount of time to complete it. It will show their ability to learn and solve problems. You could even set this test before inviting them in for a face to face interview.
I cannot code while people watch me, it's awkward. I have always hated interviews where I'm asked to do this. Of course asking some probing questions to judge someone problem solving abilities is good but try keep it general not specific, if that makes sense?
answered 58 mins ago
PixelomoPixelomo
1,722719
1,722719
add a comment |
add a comment |
Corey Ogburn is a new contributor. Be nice, and check out our Code of Conduct.
Corey Ogburn is a new contributor. Be nice, and check out our Code of Conduct.
Corey Ogburn is a new contributor. Be nice, and check out our Code of Conduct.
Corey Ogburn is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to The Workplace Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f128769%2fhow-do-i-evaluate-a-candidate-for-a-junior-position%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
3
What are your current expectations regarding their role? If you don't have that figured out it will be tough to find candidates to fill the role.
– sf02
8 hours ago
Interviewing people demands a high responsibility. Make sure you guys have a clear notion of what you are looking for. Apply tests if necessary. The junior has expectatios just like you. And both expectations must be very well aligned. It sucks really bad for an enployee when he/she is not sure enough about his/her role at the company. It might drain the employe's enthusiasm and self-steem.
– wes85melis
8 hours ago
Finding programmers is the only thing harder than programming.
– Fattie
7 hours ago