How to Rate Job Interview Process [closed]

Clash Royale CLAN TAG#URR8PPP

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;

up vote
0
down vote

favorite

Today I went for job interview (I'm fresh graduate Engineer). After having some question answer, one of interviewer ask me to rate the interview process out of 10. So, my question is how to rate interview program. Is there any basic for rating such a interview recruitment process.

interviewing recruitment

share|improve this question

asked Aug 22 '13 at 14:44

Lionel

1064

closed as primarily opinion-based by Jim G., Michael Grubey, CincinnatiProgrammer, jcmeloni, gnat Aug 25 '13 at 22:29

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  Rather than down voting the question, I will fell more happy if someone have leaved the comment to clarify the reason for down-voting.
  – Lionel
  Aug 23 '13 at 7:35
  

  
  
  
  

add a comment | 

up vote
0
down vote

favorite

Today I went for job interview (I'm fresh graduate Engineer). After having some question answer, one of interviewer ask me to rate the interview process out of 10. So, my question is how to rate interview program. Is there any basic for rating such a interview recruitment process.

interviewing recruitment

share|improve this question

asked Aug 22 '13 at 14:44

Lionel

1064

closed as primarily opinion-based by Jim G., Michael Grubey, CincinnatiProgrammer, jcmeloni, gnat Aug 25 '13 at 22:29

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  Rather than down voting the question, I will fell more happy if someone have leaved the comment to clarify the reason for down-voting.
  – Lionel
  Aug 23 '13 at 7:35
  

  
  
  
  

add a comment | 

up vote
0
down vote

favorite

up vote
0
down vote

favorite

Today I went for job interview (I'm fresh graduate Engineer). After having some question answer, one of interviewer ask me to rate the interview process out of 10. So, my question is how to rate interview program. Is there any basic for rating such a interview recruitment process.

interviewing recruitment

share|improve this question

asked Aug 22 '13 at 14:44

Lionel

1064

Today I went for job interview (I'm fresh graduate Engineer). After having some question answer, one of interviewer ask me to rate the interview process out of 10. So, my question is how to rate interview program. Is there any basic for rating such a interview recruitment process.

interviewing recruitment

share|improve this question

asked Aug 22 '13 at 14:44

Lionel

1064

share|improve this question

share|improve this question

asked Aug 22 '13 at 14:44

Lionel

1064

asked Aug 22 '13 at 14:44

Lionel

1064

asked Aug 22 '13 at 14:44

Lionel

1064

1064

closed as primarily opinion-based by Jim G., Michael Grubey, CincinnatiProgrammer, jcmeloni, gnat Aug 25 '13 at 22:29

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

closed as primarily opinion-based by Jim G., Michael Grubey, CincinnatiProgrammer, jcmeloni, gnat Aug 25 '13 at 22:29

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  Rather than down voting the question, I will fell more happy if someone have leaved the comment to clarify the reason for down-voting.
  – Lionel
  Aug 23 '13 at 7:35
  

  
  
  
  

add a comment | 

• 
  
  
  

  
  

  
  
  
  
  
  

  
  Rather than down voting the question, I will fell more happy if someone have leaved the comment to clarify the reason for down-voting.
  – Lionel
  Aug 23 '13 at 7:35
  

  
  
  
  

Rather than down voting the question, I will fell more happy if someone have leaved the comment to clarify the reason for down-voting.
– Lionel
Aug 23 '13 at 7:35

Rather than down voting the question, I will fell more happy if someone have leaved the comment to clarify the reason for down-voting.
– Lionel
Aug 23 '13 at 7:35

add a comment | 

3 Answers
3

active

oldest

votes

up vote
1
down vote



accepted

This is actually an interview question. They're trying to see if you can evaluate something on subjective criteria. Imagine that you had to 'reverse engineer' 'user experience' (UX) in order to improve it.

A good place to start is by figuring out whether your 'intake' (in which you are invited to the interview, show up at the work location, and navigate the building where you're being interviewed) contains anything confusing or ambiguous.

Then evaluate the interviewer on 'knowledge of topic' - did they ask relevant questions, did they understand your answers, did they communicate their employment objectives clearly, could they illustrate to your satisfaction how they felt you might fit in?

Then evaluate 'protocol'. Having properly covered the relevant material, did they introduce extraneous matters that were, at least on the surface, irrelevant? Did they hit you with a curveball 'out of the blue' to test your reaction to the unexpected? Were they asking questions that seemed focused on age, gender, marital status, or other things that shouldn't have come up?

Then evaluate 'wrap up'. Did they indicate when they would get back to you, how they would do so, who you would see next if they wanted another round, or when and where you would show up for your first day?

If all of these scored high you could rate it toward the 10 end of the spectrum, if it appeared weak then you could rate it lower. While they may initially simply want a number, be prepared to explain how you came to it.

share|improve this answer

answered Aug 22 '13 at 15:20

Meredith Poor

8,8661730

• 
  
  
  

  
  

  
  
  
  
  
  

  
  The question could also be a trap to see how likely you are to point out problems (in some--possibly most--workplaces, pointing out problems is not seen as a good thing)
  – Amy Blankenship
  Aug 22 '13 at 15:40
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  Pointing out problems and being vague about it is definitely a negative. If you didn't give full marks and can't say why, I can see why that might count against you.
  – Amy Blankenship
  Aug 22 '13 at 15:51
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  @Pattinson nobody here can give you the number you should have said. Meredith is telling you how to work out a number (and explain it) yourself. The explanation is the important part of the answer you would have given in the interview
  – Kate Gregory
  Aug 22 '13 at 15:54
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  @AmyBlankenship (Concerning the trap) That's actually a really great way to find out you don't want to work there! (The real trap is to accept the offer, IMO.) For a software engineer, at least, where problem solving is the name of the game, I'd be disappointed if my co-workers and especially boss discouraged feedback.
  – employee-X
  Aug 29 '16 at 0:55
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  @AmyBlankenship I hear you! In my last job search, I said, "Yes" to the first offer... but, while no company or culture is perfect, I'd like to think a "good fit" will pass an hour-long interview. (If the interviewers are aware of their downsides enough not to mention them, that's at least something.) The interviewee risks as much by saying, "Yes" as the hiring manager.
  – employee-X
  Aug 30 '16 at 17:58
  
  

  
  
  
  

 | 
show 1 more comment

up vote
2
down vote

Here's the way I would approach it.

I'd say: five is average. This interview was above average in these three ways.

And then make some specific statements about what just happened between you, for example:

1. You kept me informed about what was happening throughout the process


2. We had a good give and take


3. You explained these interesting details about your company (and then list them)


4. You gave me an opportunity to talk about my passion for X (repeat whatever that is)

And then say: I'm a tough grader. I'd have to give you an eight or nine.

share|improve this answer

answered Aug 22 '13 at 21:06

dcaswell

673313

• 
  
  
  

  
  

  
  
  
  
  
  

  
  woow great. Thanks for listing such a interesting answer.
  – Lionel
  Aug 23 '13 at 3:29
  

  
  
  
  

add a comment | 

up vote
1
down vote

I don't know if anyone has established rates like the star system for hotels with specific requirments to meet each level. Minimum would be for them to show some courtesy and hold the interview in an appropriate and comfortable place. I heard of one place that conducted the interview in a moldy basement.

The rest could depend what you think an interview should accomplish. That gets pretty subjective. There are some companies where I knew so little about them, I put a premium on getting information about the company, people and duties for the position. In others I wanted them to learn enough about me, so they could make a hiring decision. It's not an all or nothing thing but emphasising one side or the other.

Different stages of the hiring process can be a big factor on how the interview is conducted. Most initial interviews won't rate very high unless you consider this circumstance. This is driven by who is conducting the interview. An initial HR screening type interview won't be the same as that by the direct supervisor or especially another employee at the same level (They tend to come up with the 'gotcha' trivial technical questions.).

I usually come out of most interviews oblivious to how it went, so they just get a 5 or maybe a 6/7 if I'm in a good mood.

share|improve this answer

answered Aug 22 '13 at 15:44

user8365

add a comment | 

3 Answers
3

active

oldest

votes

3 Answers
3

active

oldest

votes

active

oldest

votes

active

oldest

votes

up vote
1
down vote



accepted

This is actually an interview question. They're trying to see if you can evaluate something on subjective criteria. Imagine that you had to 'reverse engineer' 'user experience' (UX) in order to improve it.

A good place to start is by figuring out whether your 'intake' (in which you are invited to the interview, show up at the work location, and navigate the building where you're being interviewed) contains anything confusing or ambiguous.

Then evaluate the interviewer on 'knowledge of topic' - did they ask relevant questions, did they understand your answers, did they communicate their employment objectives clearly, could they illustrate to your satisfaction how they felt you might fit in?

Then evaluate 'protocol'. Having properly covered the relevant material, did they introduce extraneous matters that were, at least on the surface, irrelevant? Did they hit you with a curveball 'out of the blue' to test your reaction to the unexpected? Were they asking questions that seemed focused on age, gender, marital status, or other things that shouldn't have come up?

Then evaluate 'wrap up'. Did they indicate when they would get back to you, how they would do so, who you would see next if they wanted another round, or when and where you would show up for your first day?

If all of these scored high you could rate it toward the 10 end of the spectrum, if it appeared weak then you could rate it lower. While they may initially simply want a number, be prepared to explain how you came to it.

share|improve this answer

answered Aug 22 '13 at 15:20

Meredith Poor

8,8661730

• 
  
  
  

  
  

  
  
  
  
  
  

  
  The question could also be a trap to see how likely you are to point out problems (in some--possibly most--workplaces, pointing out problems is not seen as a good thing)
  – Amy Blankenship
  Aug 22 '13 at 15:40
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  Pointing out problems and being vague about it is definitely a negative. If you didn't give full marks and can't say why, I can see why that might count against you.
  – Amy Blankenship
  Aug 22 '13 at 15:51
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  @Pattinson nobody here can give you the number you should have said. Meredith is telling you how to work out a number (and explain it) yourself. The explanation is the important part of the answer you would have given in the interview
  – Kate Gregory
  Aug 22 '13 at 15:54
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  @AmyBlankenship (Concerning the trap) That's actually a really great way to find out you don't want to work there! (The real trap is to accept the offer, IMO.) For a software engineer, at least, where problem solving is the name of the game, I'd be disappointed if my co-workers and especially boss discouraged feedback.
  – employee-X
  Aug 29 '16 at 0:55
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  @AmyBlankenship I hear you! In my last job search, I said, "Yes" to the first offer... but, while no company or culture is perfect, I'd like to think a "good fit" will pass an hour-long interview. (If the interviewers are aware of their downsides enough not to mention them, that's at least something.) The interviewee risks as much by saying, "Yes" as the hiring manager.
  – employee-X
  Aug 30 '16 at 17:58
  
  

  
  
  
  

 | 
show 1 more comment

up vote
1
down vote



accepted

This is actually an interview question. They're trying to see if you can evaluate something on subjective criteria. Imagine that you had to 'reverse engineer' 'user experience' (UX) in order to improve it.

A good place to start is by figuring out whether your 'intake' (in which you are invited to the interview, show up at the work location, and navigate the building where you're being interviewed) contains anything confusing or ambiguous.

Then evaluate the interviewer on 'knowledge of topic' - did they ask relevant questions, did they understand your answers, did they communicate their employment objectives clearly, could they illustrate to your satisfaction how they felt you might fit in?

Then evaluate 'protocol'. Having properly covered the relevant material, did they introduce extraneous matters that were, at least on the surface, irrelevant? Did they hit you with a curveball 'out of the blue' to test your reaction to the unexpected? Were they asking questions that seemed focused on age, gender, marital status, or other things that shouldn't have come up?

Then evaluate 'wrap up'. Did they indicate when they would get back to you, how they would do so, who you would see next if they wanted another round, or when and where you would show up for your first day?

If all of these scored high you could rate it toward the 10 end of the spectrum, if it appeared weak then you could rate it lower. While they may initially simply want a number, be prepared to explain how you came to it.

share|improve this answer

answered Aug 22 '13 at 15:20

Meredith Poor

8,8661730

• 
  
  
  

  
  

  
  
  
  
  
  

  
  The question could also be a trap to see how likely you are to point out problems (in some--possibly most--workplaces, pointing out problems is not seen as a good thing)
  – Amy Blankenship
  Aug 22 '13 at 15:40
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  Pointing out problems and being vague about it is definitely a negative. If you didn't give full marks and can't say why, I can see why that might count against you.
  – Amy Blankenship
  Aug 22 '13 at 15:51
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  @Pattinson nobody here can give you the number you should have said. Meredith is telling you how to work out a number (and explain it) yourself. The explanation is the important part of the answer you would have given in the interview
  – Kate Gregory
  Aug 22 '13 at 15:54
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  @AmyBlankenship (Concerning the trap) That's actually a really great way to find out you don't want to work there! (The real trap is to accept the offer, IMO.) For a software engineer, at least, where problem solving is the name of the game, I'd be disappointed if my co-workers and especially boss discouraged feedback.
  – employee-X
  Aug 29 '16 at 0:55
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  @AmyBlankenship I hear you! In my last job search, I said, "Yes" to the first offer... but, while no company or culture is perfect, I'd like to think a "good fit" will pass an hour-long interview. (If the interviewers are aware of their downsides enough not to mention them, that's at least something.) The interviewee risks as much by saying, "Yes" as the hiring manager.
  – employee-X
  Aug 30 '16 at 17:58
  
  

  
  
  
  

 | 
show 1 more comment

up vote
1
down vote



accepted

up vote
1
down vote



accepted

This is actually an interview question. They're trying to see if you can evaluate something on subjective criteria. Imagine that you had to 'reverse engineer' 'user experience' (UX) in order to improve it.

A good place to start is by figuring out whether your 'intake' (in which you are invited to the interview, show up at the work location, and navigate the building where you're being interviewed) contains anything confusing or ambiguous.

Then evaluate the interviewer on 'knowledge of topic' - did they ask relevant questions, did they understand your answers, did they communicate their employment objectives clearly, could they illustrate to your satisfaction how they felt you might fit in?

Then evaluate 'protocol'. Having properly covered the relevant material, did they introduce extraneous matters that were, at least on the surface, irrelevant? Did they hit you with a curveball 'out of the blue' to test your reaction to the unexpected? Were they asking questions that seemed focused on age, gender, marital status, or other things that shouldn't have come up?

Then evaluate 'wrap up'. Did they indicate when they would get back to you, how they would do so, who you would see next if they wanted another round, or when and where you would show up for your first day?

If all of these scored high you could rate it toward the 10 end of the spectrum, if it appeared weak then you could rate it lower. While they may initially simply want a number, be prepared to explain how you came to it.

share|improve this answer

answered Aug 22 '13 at 15:20

Meredith Poor

8,8661730

This is actually an interview question. They're trying to see if you can evaluate something on subjective criteria. Imagine that you had to 'reverse engineer' 'user experience' (UX) in order to improve it.

A good place to start is by figuring out whether your 'intake' (in which you are invited to the interview, show up at the work location, and navigate the building where you're being interviewed) contains anything confusing or ambiguous.

Then evaluate the interviewer on 'knowledge of topic' - did they ask relevant questions, did they understand your answers, did they communicate their employment objectives clearly, could they illustrate to your satisfaction how they felt you might fit in?

Then evaluate 'protocol'. Having properly covered the relevant material, did they introduce extraneous matters that were, at least on the surface, irrelevant? Did they hit you with a curveball 'out of the blue' to test your reaction to the unexpected? Were they asking questions that seemed focused on age, gender, marital status, or other things that shouldn't have come up?

Then evaluate 'wrap up'. Did they indicate when they would get back to you, how they would do so, who you would see next if they wanted another round, or when and where you would show up for your first day?

If all of these scored high you could rate it toward the 10 end of the spectrum, if it appeared weak then you could rate it lower. While they may initially simply want a number, be prepared to explain how you came to it.

share|improve this answer

answered Aug 22 '13 at 15:20

Meredith Poor

8,8661730

share|improve this answer

share|improve this answer

answered Aug 22 '13 at 15:20

Meredith Poor

8,8661730

answered Aug 22 '13 at 15:20

Meredith Poor

8,8661730

answered Aug 22 '13 at 15:20

Meredith Poor

8,8661730

8,8661730

• 
  
  
  

  
  

  
  
  
  
  
  

  
  The question could also be a trap to see how likely you are to point out problems (in some--possibly most--workplaces, pointing out problems is not seen as a good thing)
  – Amy Blankenship
  Aug 22 '13 at 15:40
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  Pointing out problems and being vague about it is definitely a negative. If you didn't give full marks and can't say why, I can see why that might count against you.
  – Amy Blankenship
  Aug 22 '13 at 15:51
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  @Pattinson nobody here can give you the number you should have said. Meredith is telling you how to work out a number (and explain it) yourself. The explanation is the important part of the answer you would have given in the interview
  – Kate Gregory
  Aug 22 '13 at 15:54
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  @AmyBlankenship (Concerning the trap) That's actually a really great way to find out you don't want to work there! (The real trap is to accept the offer, IMO.) For a software engineer, at least, where problem solving is the name of the game, I'd be disappointed if my co-workers and especially boss discouraged feedback.
  – employee-X
  Aug 29 '16 at 0:55
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  @AmyBlankenship I hear you! In my last job search, I said, "Yes" to the first offer... but, while no company or culture is perfect, I'd like to think a "good fit" will pass an hour-long interview. (If the interviewers are aware of their downsides enough not to mention them, that's at least something.) The interviewee risks as much by saying, "Yes" as the hiring manager.
  – employee-X
  Aug 30 '16 at 17:58
  
  

  
  
  
  

 | 
show 1 more comment

• 
  
  
  

  
  

  
  
  
  
  
  

  
  The question could also be a trap to see how likely you are to point out problems (in some--possibly most--workplaces, pointing out problems is not seen as a good thing)
  – Amy Blankenship
  Aug 22 '13 at 15:40
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  Pointing out problems and being vague about it is definitely a negative. If you didn't give full marks and can't say why, I can see why that might count against you.
  – Amy Blankenship
  Aug 22 '13 at 15:51
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  @Pattinson nobody here can give you the number you should have said. Meredith is telling you how to work out a number (and explain it) yourself. The explanation is the important part of the answer you would have given in the interview
  – Kate Gregory
  Aug 22 '13 at 15:54
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  @AmyBlankenship (Concerning the trap) That's actually a really great way to find out you don't want to work there! (The real trap is to accept the offer, IMO.) For a software engineer, at least, where problem solving is the name of the game, I'd be disappointed if my co-workers and especially boss discouraged feedback.
  – employee-X
  Aug 29 '16 at 0:55
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  @AmyBlankenship I hear you! In my last job search, I said, "Yes" to the first offer... but, while no company or culture is perfect, I'd like to think a "good fit" will pass an hour-long interview. (If the interviewers are aware of their downsides enough not to mention them, that's at least something.) The interviewee risks as much by saying, "Yes" as the hiring manager.
  – employee-X
  Aug 30 '16 at 17:58
  
  

  
  
  
  

The question could also be a trap to see how likely you are to point out problems (in some--possibly most--workplaces, pointing out problems is not seen as a good thing)
– Amy Blankenship
Aug 22 '13 at 15:40

The question could also be a trap to see how likely you are to point out problems (in some--possibly most--workplaces, pointing out problems is not seen as a good thing)
– Amy Blankenship
Aug 22 '13 at 15:40

2

2

Pointing out problems and being vague about it is definitely a negative. If you didn't give full marks and can't say why, I can see why that might count against you.
– Amy Blankenship
Aug 22 '13 at 15:51

Pointing out problems and being vague about it is definitely a negative. If you didn't give full marks and can't say why, I can see why that might count against you.
– Amy Blankenship
Aug 22 '13 at 15:51

@Pattinson nobody here can give you the number you should have said. Meredith is telling you how to work out a number (and explain it) yourself. The explanation is the important part of the answer you would have given in the interview
– Kate Gregory
Aug 22 '13 at 15:54

@Pattinson nobody here can give you the number you should have said. Meredith is telling you how to work out a number (and explain it) yourself. The explanation is the important part of the answer you would have given in the interview
– Kate Gregory
Aug 22 '13 at 15:54

@AmyBlankenship (Concerning the trap) That's actually a really great way to find out you don't want to work there! (The real trap is to accept the offer, IMO.) For a software engineer, at least, where problem solving is the name of the game, I'd be disappointed if my co-workers and especially boss discouraged feedback.
– employee-X
Aug 29 '16 at 0:55

@AmyBlankenship (Concerning the trap) That's actually a really great way to find out you don't want to work there! (The real trap is to accept the offer, IMO.) For a software engineer, at least, where problem solving is the name of the game, I'd be disappointed if my co-workers and especially boss discouraged feedback.
– employee-X
Aug 29 '16 at 0:55

1

1

@AmyBlankenship I hear you! In my last job search, I said, "Yes" to the first offer... but, while no company or culture is perfect, I'd like to think a "good fit" will pass an hour-long interview. (If the interviewers are aware of their downsides enough not to mention them, that's at least something.) The interviewee risks as much by saying, "Yes" as the hiring manager.
– employee-X
Aug 30 '16 at 17:58

@AmyBlankenship I hear you! In my last job search, I said, "Yes" to the first offer... but, while no company or culture is perfect, I'd like to think a "good fit" will pass an hour-long interview. (If the interviewers are aware of their downsides enough not to mention them, that's at least something.) The interviewee risks as much by saying, "Yes" as the hiring manager.
– employee-X
Aug 30 '16 at 17:58

 | 
show 1 more comment

up vote
2
down vote

Here's the way I would approach it.

I'd say: five is average. This interview was above average in these three ways.

And then make some specific statements about what just happened between you, for example:

1. You kept me informed about what was happening throughout the process


2. We had a good give and take


3. You explained these interesting details about your company (and then list them)


4. You gave me an opportunity to talk about my passion for X (repeat whatever that is)

And then say: I'm a tough grader. I'd have to give you an eight or nine.

share|improve this answer

answered Aug 22 '13 at 21:06

dcaswell

673313

• 
  
  
  

  
  

  
  
  
  
  
  

  
  woow great. Thanks for listing such a interesting answer.
  – Lionel
  Aug 23 '13 at 3:29
  

  
  
  
  

add a comment | 

up vote
2
down vote

Here's the way I would approach it.

I'd say: five is average. This interview was above average in these three ways.

And then make some specific statements about what just happened between you, for example:

1. You kept me informed about what was happening throughout the process


2. We had a good give and take


3. You explained these interesting details about your company (and then list them)


4. You gave me an opportunity to talk about my passion for X (repeat whatever that is)

And then say: I'm a tough grader. I'd have to give you an eight or nine.

share|improve this answer

answered Aug 22 '13 at 21:06

dcaswell

673313

• 
  
  
  

  
  

  
  
  
  
  
  

  
  woow great. Thanks for listing such a interesting answer.
  – Lionel
  Aug 23 '13 at 3:29
  

  
  
  
  

add a comment | 

up vote
2
down vote

up vote
2
down vote

Here's the way I would approach it.

I'd say: five is average. This interview was above average in these three ways.

And then make some specific statements about what just happened between you, for example:

1. You kept me informed about what was happening throughout the process


2. We had a good give and take


3. You explained these interesting details about your company (and then list them)


4. You gave me an opportunity to talk about my passion for X (repeat whatever that is)

And then say: I'm a tough grader. I'd have to give you an eight or nine.

share|improve this answer

answered Aug 22 '13 at 21:06

dcaswell

673313

Here's the way I would approach it.

I'd say: five is average. This interview was above average in these three ways.

And then make some specific statements about what just happened between you, for example:

1. You kept me informed about what was happening throughout the process


2. We had a good give and take


3. You explained these interesting details about your company (and then list them)


4. You gave me an opportunity to talk about my passion for X (repeat whatever that is)

And then say: I'm a tough grader. I'd have to give you an eight or nine.

share|improve this answer

answered Aug 22 '13 at 21:06

dcaswell

673313

share|improve this answer

share|improve this answer

answered Aug 22 '13 at 21:06

dcaswell

673313

answered Aug 22 '13 at 21:06

dcaswell

673313

answered Aug 22 '13 at 21:06

dcaswell

673313

673313

• 
  
  
  

  
  

  
  
  
  
  
  

  
  woow great. Thanks for listing such a interesting answer.
  – Lionel
  Aug 23 '13 at 3:29
  

  
  
  
  

add a comment | 

• 
  
  
  

  
  

  
  
  
  
  
  

  
  woow great. Thanks for listing such a interesting answer.
  – Lionel
  Aug 23 '13 at 3:29
  

  
  
  
  

woow great. Thanks for listing such a interesting answer.
– Lionel
Aug 23 '13 at 3:29

woow great. Thanks for listing such a interesting answer.
– Lionel
Aug 23 '13 at 3:29

add a comment | 

up vote
1
down vote

I don't know if anyone has established rates like the star system for hotels with specific requirments to meet each level. Minimum would be for them to show some courtesy and hold the interview in an appropriate and comfortable place. I heard of one place that conducted the interview in a moldy basement.

The rest could depend what you think an interview should accomplish. That gets pretty subjective. There are some companies where I knew so little about them, I put a premium on getting information about the company, people and duties for the position. In others I wanted them to learn enough about me, so they could make a hiring decision. It's not an all or nothing thing but emphasising one side or the other.

Different stages of the hiring process can be a big factor on how the interview is conducted. Most initial interviews won't rate very high unless you consider this circumstance. This is driven by who is conducting the interview. An initial HR screening type interview won't be the same as that by the direct supervisor or especially another employee at the same level (They tend to come up with the 'gotcha' trivial technical questions.).

I usually come out of most interviews oblivious to how it went, so they just get a 5 or maybe a 6/7 if I'm in a good mood.

share|improve this answer

answered Aug 22 '13 at 15:44

user8365

add a comment | 

up vote
1
down vote

I don't know if anyone has established rates like the star system for hotels with specific requirments to meet each level. Minimum would be for them to show some courtesy and hold the interview in an appropriate and comfortable place. I heard of one place that conducted the interview in a moldy basement.

The rest could depend what you think an interview should accomplish. That gets pretty subjective. There are some companies where I knew so little about them, I put a premium on getting information about the company, people and duties for the position. In others I wanted them to learn enough about me, so they could make a hiring decision. It's not an all or nothing thing but emphasising one side or the other.

Different stages of the hiring process can be a big factor on how the interview is conducted. Most initial interviews won't rate very high unless you consider this circumstance. This is driven by who is conducting the interview. An initial HR screening type interview won't be the same as that by the direct supervisor or especially another employee at the same level (They tend to come up with the 'gotcha' trivial technical questions.).

I usually come out of most interviews oblivious to how it went, so they just get a 5 or maybe a 6/7 if I'm in a good mood.

share|improve this answer

answered Aug 22 '13 at 15:44

user8365

add a comment | 

up vote
1
down vote

up vote
1
down vote

I don't know if anyone has established rates like the star system for hotels with specific requirments to meet each level. Minimum would be for them to show some courtesy and hold the interview in an appropriate and comfortable place. I heard of one place that conducted the interview in a moldy basement.

The rest could depend what you think an interview should accomplish. That gets pretty subjective. There are some companies where I knew so little about them, I put a premium on getting information about the company, people and duties for the position. In others I wanted them to learn enough about me, so they could make a hiring decision. It's not an all or nothing thing but emphasising one side or the other.

Different stages of the hiring process can be a big factor on how the interview is conducted. Most initial interviews won't rate very high unless you consider this circumstance. This is driven by who is conducting the interview. An initial HR screening type interview won't be the same as that by the direct supervisor or especially another employee at the same level (They tend to come up with the 'gotcha' trivial technical questions.).

I usually come out of most interviews oblivious to how it went, so they just get a 5 or maybe a 6/7 if I'm in a good mood.

share|improve this answer

answered Aug 22 '13 at 15:44

user8365

I don't know if anyone has established rates like the star system for hotels with specific requirments to meet each level. Minimum would be for them to show some courtesy and hold the interview in an appropriate and comfortable place. I heard of one place that conducted the interview in a moldy basement.

The rest could depend what you think an interview should accomplish. That gets pretty subjective. There are some companies where I knew so little about them, I put a premium on getting information about the company, people and duties for the position. In others I wanted them to learn enough about me, so they could make a hiring decision. It's not an all or nothing thing but emphasising one side or the other.

Different stages of the hiring process can be a big factor on how the interview is conducted. Most initial interviews won't rate very high unless you consider this circumstance. This is driven by who is conducting the interview. An initial HR screening type interview won't be the same as that by the direct supervisor or especially another employee at the same level (They tend to come up with the 'gotcha' trivial technical questions.).

I usually come out of most interviews oblivious to how it went, so they just get a 5 or maybe a 6/7 if I'm in a good mood.

share|improve this answer

answered Aug 22 '13 at 15:44

user8365

share|improve this answer

share|improve this answer

answered Aug 22 '13 at 15:44

user8365

answered Aug 22 '13 at 15:44

user8365

answered Aug 22 '13 at 15:44

user8365

add a comment | 

add a comment |