Mixing
How can I properly set boundaries and expectations during an interview process? [on hold]
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
1
down vote
favorite
I have had a couple of experiences and would like some suggestions as to how to set boundaries right away and before I get to that point, actually vet them out.
The most recent one was where the startup upon the first phone call, does a 3 minute get to know you and then decided to start blitzing me with technical questions that were out of context for me. I must admit, I do not dream of code, if I don't have a white board, a code editor, something to work with, I am afraid Guantanamo Bay style technical questions just leaves me in shock and awe.
If I am going to be joining a company, I hope to be among respected colleagues, if not future friends that I hope to work with for many years to come.
The funny thing is, I stated the above to the interviewer and then he starts hammering at me with interrogation style technical questions. He did not seem self-aware enough to say, well, if thats what you are looking for then, we are not for you, because I am about to release a high-tech barrage of Stage 1 rendition style questioning on you which shows I really could care less about you.
To which I would have just said, thanks for your honesty and sparing me your nonsense, have a great day.
I know I am not asking for a lot here because I have worked with some awesome companies in the past, who actually make it a point to not be that guy.
interviewing company-culture
asked yesterday
Daniel
242110
put on hold as too broad by Philip Kendall, gnat, Dukeling, Richard U, IDrinkandIKnowThings 6 hours ago
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
 |Â
show 1 more comment
up vote
1
down vote
favorite
I have had a couple of experiences and would like some suggestions as to how to set boundaries right away and before I get to that point, actually vet them out.
The most recent one was where the startup upon the first phone call, does a 3 minute get to know you and then decided to start blitzing me with technical questions that were out of context for me. I must admit, I do not dream of code, if I don't have a white board, a code editor, something to work with, I am afraid Guantanamo Bay style technical questions just leaves me in shock and awe.
If I am going to be joining a company, I hope to be among respected colleagues, if not future friends that I hope to work with for many years to come.
The funny thing is, I stated the above to the interviewer and then he starts hammering at me with interrogation style technical questions. He did not seem self-aware enough to say, well, if thats what you are looking for then, we are not for you, because I am about to release a high-tech barrage of Stage 1 rendition style questioning on you which shows I really could care less about you.
To which I would have just said, thanks for your honesty and sparing me your nonsense, have a great day.
I know I am not asking for a lot here because I have worked with some awesome companies in the past, who actually make it a point to not be that guy.
interviewing company-culture
asked yesterday
Daniel
242110
put on hold as too broad by Philip Kendall, gnat, Dukeling, Richard U, IDrinkandIKnowThings 6 hours ago
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
4
What do you have in mind for vetting? In your first example, 5 minutes into the phone interview you knew this wasn't a company you'd work for. That sounds like pretty good vetting to me.
– Dan Pichelman
yesterday
@DanPichelman, I think you are right. I guess I just need the courage to say to end the conversation. Perhaps you can offer a suggestion on what to say, that I could practice.
– Daniel
yesterday
1
You may be significantly limiting your career prospects if a few impromptu technical questions during an interview is a red flag for you (although perhaps that's acceptable for you). You should always be prepared to answer technical questions during any type of interview (unless you were explicitly told it's non-technical with non-technical interviewers).
– Dukeling
yesterday
@Daniel - once you hear something that tells you it isn't the right place for you, just end the interview. Say something like "Thanks for your time but I can tell this isn't the right place for me."
– Joe Strazzere
yesterday
@JoeStrazzere, thank you for that comment. That has always been my biggest challenge in life in general, knowing when to set boundaries like that.
– Daniel
23 hours ago
 |Â
show 1 more comment
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have had a couple of experiences and would like some suggestions as to how to set boundaries right away and before I get to that point, actually vet them out.
The most recent one was where the startup upon the first phone call, does a 3 minute get to know you and then decided to start blitzing me with technical questions that were out of context for me. I must admit, I do not dream of code, if I don't have a white board, a code editor, something to work with, I am afraid Guantanamo Bay style technical questions just leaves me in shock and awe.
If I am going to be joining a company, I hope to be among respected colleagues, if not future friends that I hope to work with for many years to come.
The funny thing is, I stated the above to the interviewer and then he starts hammering at me with interrogation style technical questions. He did not seem self-aware enough to say, well, if thats what you are looking for then, we are not for you, because I am about to release a high-tech barrage of Stage 1 rendition style questioning on you which shows I really could care less about you.
To which I would have just said, thanks for your honesty and sparing me your nonsense, have a great day.
I know I am not asking for a lot here because I have worked with some awesome companies in the past, who actually make it a point to not be that guy.
interviewing company-culture
asked yesterday
Daniel
242110
I have had a couple of experiences and would like some suggestions as to how to set boundaries right away and before I get to that point, actually vet them out.
The most recent one was where the startup upon the first phone call, does a 3 minute get to know you and then decided to start blitzing me with technical questions that were out of context for me. I must admit, I do not dream of code, if I don't have a white board, a code editor, something to work with, I am afraid Guantanamo Bay style technical questions just leaves me in shock and awe.
If I am going to be joining a company, I hope to be among respected colleagues, if not future friends that I hope to work with for many years to come.
The funny thing is, I stated the above to the interviewer and then he starts hammering at me with interrogation style technical questions. He did not seem self-aware enough to say, well, if thats what you are looking for then, we are not for you, because I am about to release a high-tech barrage of Stage 1 rendition style questioning on you which shows I really could care less about you.
To which I would have just said, thanks for your honesty and sparing me your nonsense, have a great day.
I know I am not asking for a lot here because I have worked with some awesome companies in the past, who actually make it a point to not be that guy.
interviewing company-culture
interviewing company-culture
asked yesterday
Daniel
242110
asked yesterday
Daniel
242110
edited 6 mins ago
asked yesterday
Daniel
242110
asked yesterday
Daniel
242110
asked yesterday
Daniel
242110
242110
put on hold as too broad by Philip Kendall, gnat, Dukeling, Richard U, IDrinkandIKnowThings 6 hours ago
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
put on hold as too broad by Philip Kendall, gnat, Dukeling, Richard U, IDrinkandIKnowThings 6 hours ago
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
4
What do you have in mind for vetting? In your first example, 5 minutes into the phone interview you knew this wasn't a company you'd work for. That sounds like pretty good vetting to me.
– Dan Pichelman
yesterday
@DanPichelman, I think you are right. I guess I just need the courage to say to end the conversation. Perhaps you can offer a suggestion on what to say, that I could practice.
– Daniel
yesterday
1
You may be significantly limiting your career prospects if a few impromptu technical questions during an interview is a red flag for you (although perhaps that's acceptable for you). You should always be prepared to answer technical questions during any type of interview (unless you were explicitly told it's non-technical with non-technical interviewers).
– Dukeling
yesterday
@Daniel - once you hear something that tells you it isn't the right place for you, just end the interview. Say something like "Thanks for your time but I can tell this isn't the right place for me."
– Joe Strazzere
yesterday
@JoeStrazzere, thank you for that comment. That has always been my biggest challenge in life in general, knowing when to set boundaries like that.
– Daniel
23 hours ago
 |Â
show 1 more comment
4
What do you have in mind for vetting? In your first example, 5 minutes into the phone interview you knew this wasn't a company you'd work for. That sounds like pretty good vetting to me.
– Dan Pichelman
yesterday
@DanPichelman, I think you are right. I guess I just need the courage to say to end the conversation. Perhaps you can offer a suggestion on what to say, that I could practice.
– Daniel
yesterday
1
You may be significantly limiting your career prospects if a few impromptu technical questions during an interview is a red flag for you (although perhaps that's acceptable for you). You should always be prepared to answer technical questions during any type of interview (unless you were explicitly told it's non-technical with non-technical interviewers).
– Dukeling
yesterday
@Daniel - once you hear something that tells you it isn't the right place for you, just end the interview. Say something like "Thanks for your time but I can tell this isn't the right place for me."
– Joe Strazzere
yesterday
@JoeStrazzere, thank you for that comment. That has always been my biggest challenge in life in general, knowing when to set boundaries like that.
– Daniel
23 hours ago
4
4
What do you have in mind for vetting? In your first example, 5 minutes into the phone interview you knew this wasn't a company you'd work for. That sounds like pretty good vetting to me.
– Dan Pichelman
yesterday
What do you have in mind for vetting? In your first example, 5 minutes into the phone interview you knew this wasn't a company you'd work for. That sounds like pretty good vetting to me.
– Dan Pichelman
yesterday
@DanPichelman, I think you are right. I guess I just need the courage to say to end the conversation. Perhaps you can offer a suggestion on what to say, that I could practice.
– Daniel
yesterday
@DanPichelman, I think you are right. I guess I just need the courage to say to end the conversation. Perhaps you can offer a suggestion on what to say, that I could practice.
– Daniel
yesterday
1
1
You may be significantly limiting your career prospects if a few impromptu technical questions during an interview is a red flag for you (although perhaps that's acceptable for you). You should always be prepared to answer technical questions during any type of interview (unless you were explicitly told it's non-technical with non-technical interviewers).
– Dukeling
yesterday
You may be significantly limiting your career prospects if a few impromptu technical questions during an interview is a red flag for you (although perhaps that's acceptable for you). You should always be prepared to answer technical questions during any type of interview (unless you were explicitly told it's non-technical with non-technical interviewers).
– Dukeling
yesterday
@Daniel - once you hear something that tells you it isn't the right place for you, just end the interview. Say something like "Thanks for your time but I can tell this isn't the right place for me."
– Joe Strazzere
yesterday
@Daniel - once you hear something that tells you it isn't the right place for you, just end the interview. Say something like "Thanks for your time but I can tell this isn't the right place for me."
– Joe Strazzere
yesterday
@JoeStrazzere, thank you for that comment. That has always been my biggest challenge in life in general, knowing when to set boundaries like that.
– Daniel
23 hours ago
@JoeStrazzere, thank you for that comment. That has always been my biggest challenge in life in general, knowing when to set boundaries like that.
– Daniel
23 hours ago
 |Â
show 1 more comment
2 Answers
2
active
oldest
votes
up vote
3
down vote
accepted
In my opinion, interviews exist to answer the following questions:
- Is there a technical fit between the candidate and the company?
- Does the candidate have the needed skills?
- Does the company have the ability to best make use of those skills?
- Is there a social/communications fit?
- Will the candidate be able to communicate effectively? Will he understand assignments and be able to raise issues when needed?
- Will the company listen to the candidate, treat him with respect, and value his input?
- Will this relationship benefit both sides, and will it grow?
As soon as you reach a "no", your vetting process is complete and you can comfortably end the conversation.
One way to do that is to wait for the interviewer to pause for air and announce
"You know, this job isn't for me. Thanks for your time".
You don't owe them an explanation.
answered yesterday
Dan Pichelman
26.1k127386
Dan, this is perfect, I will keep what you wrote above in my notes. It will come in handy for years to come IMO.
– Daniel
yesterday
Just as an aside, where I believe I excel or I am comfortable are in interview questions that are thoughtful such as "Explain to me some of the benefits of Redux"? As opposed to, "quick, where in the DOM is the users' id stored!? Go!" The latter gets a WTF reaction from my brain and immediately shuts down.
– Daniel
yesterday
add a comment |Â
up vote
2
down vote
Unfortunately, some companies are very aggressive and arrogant in interviewing candidates. The only way I know of to vet companies before the interview process is to check out glassdoor.com and other similar websites to try to find out what their interview process is like before you talk to them.
I guess I could have said, "no, I did not understand this initial phone call to be a technical interview"?
There's nothing wrong with this. If you aren't prepared for and aren't going to do well in a technical interview, probably your best bet is to just inform them that you aren't prepared and didn't expect it, and that you'd like to reschedule. I believe that will give you the best chance of having a better experience.
answered yesterday
dbeer
4,6032619
Thank you dbeer. I appreciate your answer. I did try looking up this startup on Glassdoor, unfortunately, they do not have a presence on Glassdoor. Nevertheless, your answer is helpful.
– Daniel
yesterday
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
In my opinion, interviews exist to answer the following questions:
- Is there a technical fit between the candidate and the company?
- Does the candidate have the needed skills?
- Does the company have the ability to best make use of those skills?
- Is there a social/communications fit?
- Will the candidate be able to communicate effectively? Will he understand assignments and be able to raise issues when needed?
- Will the company listen to the candidate, treat him with respect, and value his input?
- Will this relationship benefit both sides, and will it grow?
As soon as you reach a "no", your vetting process is complete and you can comfortably end the conversation.
One way to do that is to wait for the interviewer to pause for air and announce
"You know, this job isn't for me. Thanks for your time".
You don't owe them an explanation.
answered yesterday
Dan Pichelman
26.1k127386
Dan, this is perfect, I will keep what you wrote above in my notes. It will come in handy for years to come IMO.
– Daniel
yesterday
Just as an aside, where I believe I excel or I am comfortable are in interview questions that are thoughtful such as "Explain to me some of the benefits of Redux"? As opposed to, "quick, where in the DOM is the users' id stored!? Go!" The latter gets a WTF reaction from my brain and immediately shuts down.
– Daniel
yesterday
add a comment |Â
up vote
3
down vote
accepted
In my opinion, interviews exist to answer the following questions:
- Is there a technical fit between the candidate and the company?
- Does the candidate have the needed skills?
- Does the company have the ability to best make use of those skills?
- Is there a social/communications fit?
- Will the candidate be able to communicate effectively? Will he understand assignments and be able to raise issues when needed?
- Will the company listen to the candidate, treat him with respect, and value his input?
- Will this relationship benefit both sides, and will it grow?
As soon as you reach a "no", your vetting process is complete and you can comfortably end the conversation.
One way to do that is to wait for the interviewer to pause for air and announce
"You know, this job isn't for me. Thanks for your time".
You don't owe them an explanation.
answered yesterday
Dan Pichelman
26.1k127386
Dan, this is perfect, I will keep what you wrote above in my notes. It will come in handy for years to come IMO.
– Daniel
yesterday
Just as an aside, where I believe I excel or I am comfortable are in interview questions that are thoughtful such as "Explain to me some of the benefits of Redux"? As opposed to, "quick, where in the DOM is the users' id stored!? Go!" The latter gets a WTF reaction from my brain and immediately shuts down.
– Daniel
yesterday
add a comment |Â
up vote
3
down vote
accepted
up vote
3
down vote
accepted
In my opinion, interviews exist to answer the following questions:
- Is there a technical fit between the candidate and the company?
- Does the candidate have the needed skills?
- Does the company have the ability to best make use of those skills?
- Is there a social/communications fit?
- Will the candidate be able to communicate effectively? Will he understand assignments and be able to raise issues when needed?
- Will the company listen to the candidate, treat him with respect, and value his input?
- Will this relationship benefit both sides, and will it grow?
As soon as you reach a "no", your vetting process is complete and you can comfortably end the conversation.
One way to do that is to wait for the interviewer to pause for air and announce
"You know, this job isn't for me. Thanks for your time".
You don't owe them an explanation.
answered yesterday
Dan Pichelman
26.1k127386
In my opinion, interviews exist to answer the following questions:
- Is there a technical fit between the candidate and the company?
- Does the candidate have the needed skills?
- Does the company have the ability to best make use of those skills?
- Is there a social/communications fit?
- Will the candidate be able to communicate effectively? Will he understand assignments and be able to raise issues when needed?
- Will the company listen to the candidate, treat him with respect, and value his input?
- Will this relationship benefit both sides, and will it grow?
As soon as you reach a "no", your vetting process is complete and you can comfortably end the conversation.
One way to do that is to wait for the interviewer to pause for air and announce
"You know, this job isn't for me. Thanks for your time".
You don't owe them an explanation.
answered yesterday
Dan Pichelman
26.1k127386
answered yesterday
Dan Pichelman
26.1k127386
answered yesterday
Dan Pichelman
26.1k127386
answered yesterday
Dan Pichelman
26.1k127386
26.1k127386
Dan, this is perfect, I will keep what you wrote above in my notes. It will come in handy for years to come IMO.
– Daniel
yesterday
Just as an aside, where I believe I excel or I am comfortable are in interview questions that are thoughtful such as "Explain to me some of the benefits of Redux"? As opposed to, "quick, where in the DOM is the users' id stored!? Go!" The latter gets a WTF reaction from my brain and immediately shuts down.
– Daniel
yesterday
add a comment |Â
Dan, this is perfect, I will keep what you wrote above in my notes. It will come in handy for years to come IMO.
– Daniel
yesterday
Just as an aside, where I believe I excel or I am comfortable are in interview questions that are thoughtful such as "Explain to me some of the benefits of Redux"? As opposed to, "quick, where in the DOM is the users' id stored!? Go!" The latter gets a WTF reaction from my brain and immediately shuts down.
– Daniel
yesterday
Dan, this is perfect, I will keep what you wrote above in my notes. It will come in handy for years to come IMO.
– Daniel
yesterday
Dan, this is perfect, I will keep what you wrote above in my notes. It will come in handy for years to come IMO.
– Daniel
yesterday
Just as an aside, where I believe I excel or I am comfortable are in interview questions that are thoughtful such as "Explain to me some of the benefits of Redux"? As opposed to, "quick, where in the DOM is the users' id stored!? Go!" The latter gets a WTF reaction from my brain and immediately shuts down.
– Daniel
yesterday
Just as an aside, where I believe I excel or I am comfortable are in interview questions that are thoughtful such as "Explain to me some of the benefits of Redux"? As opposed to, "quick, where in the DOM is the users' id stored!? Go!" The latter gets a WTF reaction from my brain and immediately shuts down.
– Daniel
yesterday
add a comment |Â
up vote
2
down vote
Unfortunately, some companies are very aggressive and arrogant in interviewing candidates. The only way I know of to vet companies before the interview process is to check out glassdoor.com and other similar websites to try to find out what their interview process is like before you talk to them.
I guess I could have said, "no, I did not understand this initial phone call to be a technical interview"?
There's nothing wrong with this. If you aren't prepared for and aren't going to do well in a technical interview, probably your best bet is to just inform them that you aren't prepared and didn't expect it, and that you'd like to reschedule. I believe that will give you the best chance of having a better experience.
answered yesterday
dbeer
4,6032619
Thank you dbeer. I appreciate your answer. I did try looking up this startup on Glassdoor, unfortunately, they do not have a presence on Glassdoor. Nevertheless, your answer is helpful.
– Daniel
yesterday
add a comment |Â
up vote
2
down vote
Unfortunately, some companies are very aggressive and arrogant in interviewing candidates. The only way I know of to vet companies before the interview process is to check out glassdoor.com and other similar websites to try to find out what their interview process is like before you talk to them.
I guess I could have said, "no, I did not understand this initial phone call to be a technical interview"?
There's nothing wrong with this. If you aren't prepared for and aren't going to do well in a technical interview, probably your best bet is to just inform them that you aren't prepared and didn't expect it, and that you'd like to reschedule. I believe that will give you the best chance of having a better experience.
answered yesterday
dbeer
4,6032619
Thank you dbeer. I appreciate your answer. I did try looking up this startup on Glassdoor, unfortunately, they do not have a presence on Glassdoor. Nevertheless, your answer is helpful.
– Daniel
yesterday
add a comment |Â
up vote
2
down vote
up vote
2
down vote
Unfortunately, some companies are very aggressive and arrogant in interviewing candidates. The only way I know of to vet companies before the interview process is to check out glassdoor.com and other similar websites to try to find out what their interview process is like before you talk to them.
I guess I could have said, "no, I did not understand this initial phone call to be a technical interview"?
There's nothing wrong with this. If you aren't prepared for and aren't going to do well in a technical interview, probably your best bet is to just inform them that you aren't prepared and didn't expect it, and that you'd like to reschedule. I believe that will give you the best chance of having a better experience.
answered yesterday
dbeer
4,6032619
Unfortunately, some companies are very aggressive and arrogant in interviewing candidates. The only way I know of to vet companies before the interview process is to check out glassdoor.com and other similar websites to try to find out what their interview process is like before you talk to them.
I guess I could have said, "no, I did not understand this initial phone call to be a technical interview"?
There's nothing wrong with this. If you aren't prepared for and aren't going to do well in a technical interview, probably your best bet is to just inform them that you aren't prepared and didn't expect it, and that you'd like to reschedule. I believe that will give you the best chance of having a better experience.
answered yesterday
dbeer
4,6032619
answered yesterday
dbeer
4,6032619
answered yesterday
dbeer
4,6032619
answered yesterday
dbeer
4,6032619
4,6032619
Thank you dbeer. I appreciate your answer. I did try looking up this startup on Glassdoor, unfortunately, they do not have a presence on Glassdoor. Nevertheless, your answer is helpful.
– Daniel
yesterday
add a comment |Â
Thank you dbeer. I appreciate your answer. I did try looking up this startup on Glassdoor, unfortunately, they do not have a presence on Glassdoor. Nevertheless, your answer is helpful.
– Daniel
yesterday
Thank you dbeer. I appreciate your answer. I did try looking up this startup on Glassdoor, unfortunately, they do not have a presence on Glassdoor. Nevertheless, your answer is helpful.
– Daniel
yesterday
Thank you dbeer. I appreciate your answer. I did try looking up this startup on Glassdoor, unfortunately, they do not have a presence on Glassdoor. Nevertheless, your answer is helpful.
– Daniel
yesterday
add a comment |Â
4
What do you have in mind for vetting? In your first example, 5 minutes into the phone interview you knew this wasn't a company you'd work for. That sounds like pretty good vetting to me.
– Dan Pichelman
yesterday
@DanPichelman, I think you are right. I guess I just need the courage to say to end the conversation. Perhaps you can offer a suggestion on what to say, that I could practice.
– Daniel
yesterday
1
You may be significantly limiting your career prospects if a few impromptu technical questions during an interview is a red flag for you (although perhaps that's acceptable for you). You should always be prepared to answer technical questions during any type of interview (unless you were explicitly told it's non-technical with non-technical interviewers).
– Dukeling
yesterday
@Daniel - once you hear something that tells you it isn't the right place for you, just end the interview. Say something like "Thanks for your time but I can tell this isn't the right place for me."
– Joe Strazzere
yesterday
@JoeStrazzere, thank you for that comment. That has always been my biggest challenge in life in general, knowing when to set boundaries like that.
– Daniel
23 hours ago