Does this mean I'm not a team player? [closed]

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





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







up vote
0
down vote

favorite












After going through an interview which I thought I did pretty well, I received from HR the following review (an excerpt):



"Also, the team felt you made a lot of assumptions when going into the prioritization challenge and technical assignments"



After giving some thought on it, I realized that the team could possible thought that I'm not a team player, since I tried to fumble myself with the assignments and didn't ask for directions...



Does this mean I am not a team player?







share|improve this question














closed as unclear what you're asking by Jim G., Rhys, Michael Grubey, jcmeloni, jmort253♦ Sep 16 '13 at 1:48


Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. 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.














  • What was the prioritization challenge? In summary what did you tell them?
    – dcaswell
    Sep 13 '13 at 22:44










  • @user814064 the challenge was comprised of 5 options of how would I deal with problems happening in a e-commerce website in production. Since the website was live, what should I work on first to solve the issues...
    – Draconar
    Sep 14 '13 at 16:31










  • It would be interesting to find out, in general terms, what you suggested, for example did you say? 1) Determined impact on users 2) Prioritize issues. etc.
    – dcaswell
    Sep 14 '13 at 16:35
















up vote
0
down vote

favorite












After going through an interview which I thought I did pretty well, I received from HR the following review (an excerpt):



"Also, the team felt you made a lot of assumptions when going into the prioritization challenge and technical assignments"



After giving some thought on it, I realized that the team could possible thought that I'm not a team player, since I tried to fumble myself with the assignments and didn't ask for directions...



Does this mean I am not a team player?







share|improve this question














closed as unclear what you're asking by Jim G., Rhys, Michael Grubey, jcmeloni, jmort253♦ Sep 16 '13 at 1:48


Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. 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.














  • What was the prioritization challenge? In summary what did you tell them?
    – dcaswell
    Sep 13 '13 at 22:44










  • @user814064 the challenge was comprised of 5 options of how would I deal with problems happening in a e-commerce website in production. Since the website was live, what should I work on first to solve the issues...
    – Draconar
    Sep 14 '13 at 16:31










  • It would be interesting to find out, in general terms, what you suggested, for example did you say? 1) Determined impact on users 2) Prioritize issues. etc.
    – dcaswell
    Sep 14 '13 at 16:35












up vote
0
down vote

favorite









up vote
0
down vote

favorite











After going through an interview which I thought I did pretty well, I received from HR the following review (an excerpt):



"Also, the team felt you made a lot of assumptions when going into the prioritization challenge and technical assignments"



After giving some thought on it, I realized that the team could possible thought that I'm not a team player, since I tried to fumble myself with the assignments and didn't ask for directions...



Does this mean I am not a team player?







share|improve this question














After going through an interview which I thought I did pretty well, I received from HR the following review (an excerpt):



"Also, the team felt you made a lot of assumptions when going into the prioritization challenge and technical assignments"



After giving some thought on it, I realized that the team could possible thought that I'm not a team player, since I tried to fumble myself with the assignments and didn't ask for directions...



Does this mean I am not a team player?









share|improve this question













share|improve this question




share|improve this question








edited Sep 13 '13 at 21:02









jmort253♦

10.4k54376




10.4k54376










asked Sep 13 '13 at 16:29









Draconar

1265




1265




closed as unclear what you're asking by Jim G., Rhys, Michael Grubey, jcmeloni, jmort253♦ Sep 16 '13 at 1:48


Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. 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.






closed as unclear what you're asking by Jim G., Rhys, Michael Grubey, jcmeloni, jmort253♦ Sep 16 '13 at 1:48


Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. 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.













  • What was the prioritization challenge? In summary what did you tell them?
    – dcaswell
    Sep 13 '13 at 22:44










  • @user814064 the challenge was comprised of 5 options of how would I deal with problems happening in a e-commerce website in production. Since the website was live, what should I work on first to solve the issues...
    – Draconar
    Sep 14 '13 at 16:31










  • It would be interesting to find out, in general terms, what you suggested, for example did you say? 1) Determined impact on users 2) Prioritize issues. etc.
    – dcaswell
    Sep 14 '13 at 16:35
















  • What was the prioritization challenge? In summary what did you tell them?
    – dcaswell
    Sep 13 '13 at 22:44










  • @user814064 the challenge was comprised of 5 options of how would I deal with problems happening in a e-commerce website in production. Since the website was live, what should I work on first to solve the issues...
    – Draconar
    Sep 14 '13 at 16:31










  • It would be interesting to find out, in general terms, what you suggested, for example did you say? 1) Determined impact on users 2) Prioritize issues. etc.
    – dcaswell
    Sep 14 '13 at 16:35















What was the prioritization challenge? In summary what did you tell them?
– dcaswell
Sep 13 '13 at 22:44




What was the prioritization challenge? In summary what did you tell them?
– dcaswell
Sep 13 '13 at 22:44












@user814064 the challenge was comprised of 5 options of how would I deal with problems happening in a e-commerce website in production. Since the website was live, what should I work on first to solve the issues...
– Draconar
Sep 14 '13 at 16:31




@user814064 the challenge was comprised of 5 options of how would I deal with problems happening in a e-commerce website in production. Since the website was live, what should I work on first to solve the issues...
– Draconar
Sep 14 '13 at 16:31












It would be interesting to find out, in general terms, what you suggested, for example did you say? 1) Determined impact on users 2) Prioritize issues. etc.
– dcaswell
Sep 14 '13 at 16:35




It would be interesting to find out, in general terms, what you suggested, for example did you say? 1) Determined impact on users 2) Prioritize issues. etc.
– dcaswell
Sep 14 '13 at 16:35










1 Answer
1






active

oldest

votes

















up vote
4
down vote













I think you probably made a lot of assumptions when going into the prioritization challenge and technical assignments.



Seriously, what that means is you were jumping to conclusions and not asking questions to make sure you understood the situation properly. In a work situation, if you start trying to solve a problem before you fully understand it, then you risk solving the wrong problem and wasting a lot of time. That makes you less productive, and a less effective worker.



It's nothing to do with being a team player.






share|improve this answer






















  • how could I have avoided that? any tips?
    – Draconar
    Sep 13 '13 at 20:54










  • Make sure you understand the problem completely before you start solving it. Even if you think you understand it, try saying "so just to check I understand this" and restate it in your own words. Also think about what they might not be telling you that might make a difference.
    – DJClayworth
    Sep 13 '13 at 20:59










  • gee... and I thought I was demonstrating how good a independent thinker I was. Talk about self-delusion. Nevertheless, how can I improve on this, since it is a thought pattern I'm so used to that I can't even realize it...
    – Draconar
    Sep 14 '13 at 16:19










  • And tehse types of interview questions are often deigned deliberaltely with big gaping holes to see if you will ask for clarification. This is important in many organizations because they want developers who will push back rather than make unqwarrented assumptions when something is unclear.
    – HLGEM
    Sep 16 '13 at 18:56

















1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
4
down vote













I think you probably made a lot of assumptions when going into the prioritization challenge and technical assignments.



Seriously, what that means is you were jumping to conclusions and not asking questions to make sure you understood the situation properly. In a work situation, if you start trying to solve a problem before you fully understand it, then you risk solving the wrong problem and wasting a lot of time. That makes you less productive, and a less effective worker.



It's nothing to do with being a team player.






share|improve this answer






















  • how could I have avoided that? any tips?
    – Draconar
    Sep 13 '13 at 20:54










  • Make sure you understand the problem completely before you start solving it. Even if you think you understand it, try saying "so just to check I understand this" and restate it in your own words. Also think about what they might not be telling you that might make a difference.
    – DJClayworth
    Sep 13 '13 at 20:59










  • gee... and I thought I was demonstrating how good a independent thinker I was. Talk about self-delusion. Nevertheless, how can I improve on this, since it is a thought pattern I'm so used to that I can't even realize it...
    – Draconar
    Sep 14 '13 at 16:19










  • And tehse types of interview questions are often deigned deliberaltely with big gaping holes to see if you will ask for clarification. This is important in many organizations because they want developers who will push back rather than make unqwarrented assumptions when something is unclear.
    – HLGEM
    Sep 16 '13 at 18:56














up vote
4
down vote













I think you probably made a lot of assumptions when going into the prioritization challenge and technical assignments.



Seriously, what that means is you were jumping to conclusions and not asking questions to make sure you understood the situation properly. In a work situation, if you start trying to solve a problem before you fully understand it, then you risk solving the wrong problem and wasting a lot of time. That makes you less productive, and a less effective worker.



It's nothing to do with being a team player.






share|improve this answer






















  • how could I have avoided that? any tips?
    – Draconar
    Sep 13 '13 at 20:54










  • Make sure you understand the problem completely before you start solving it. Even if you think you understand it, try saying "so just to check I understand this" and restate it in your own words. Also think about what they might not be telling you that might make a difference.
    – DJClayworth
    Sep 13 '13 at 20:59










  • gee... and I thought I was demonstrating how good a independent thinker I was. Talk about self-delusion. Nevertheless, how can I improve on this, since it is a thought pattern I'm so used to that I can't even realize it...
    – Draconar
    Sep 14 '13 at 16:19










  • And tehse types of interview questions are often deigned deliberaltely with big gaping holes to see if you will ask for clarification. This is important in many organizations because they want developers who will push back rather than make unqwarrented assumptions when something is unclear.
    – HLGEM
    Sep 16 '13 at 18:56












up vote
4
down vote










up vote
4
down vote









I think you probably made a lot of assumptions when going into the prioritization challenge and technical assignments.



Seriously, what that means is you were jumping to conclusions and not asking questions to make sure you understood the situation properly. In a work situation, if you start trying to solve a problem before you fully understand it, then you risk solving the wrong problem and wasting a lot of time. That makes you less productive, and a less effective worker.



It's nothing to do with being a team player.






share|improve this answer














I think you probably made a lot of assumptions when going into the prioritization challenge and technical assignments.



Seriously, what that means is you were jumping to conclusions and not asking questions to make sure you understood the situation properly. In a work situation, if you start trying to solve a problem before you fully understand it, then you risk solving the wrong problem and wasting a lot of time. That makes you less productive, and a less effective worker.



It's nothing to do with being a team player.







share|improve this answer














share|improve this answer



share|improve this answer








edited Sep 13 '13 at 20:52

























answered Sep 13 '13 at 20:32









DJClayworth

41.6k989147




41.6k989147











  • how could I have avoided that? any tips?
    – Draconar
    Sep 13 '13 at 20:54










  • Make sure you understand the problem completely before you start solving it. Even if you think you understand it, try saying "so just to check I understand this" and restate it in your own words. Also think about what they might not be telling you that might make a difference.
    – DJClayworth
    Sep 13 '13 at 20:59










  • gee... and I thought I was demonstrating how good a independent thinker I was. Talk about self-delusion. Nevertheless, how can I improve on this, since it is a thought pattern I'm so used to that I can't even realize it...
    – Draconar
    Sep 14 '13 at 16:19










  • And tehse types of interview questions are often deigned deliberaltely with big gaping holes to see if you will ask for clarification. This is important in many organizations because they want developers who will push back rather than make unqwarrented assumptions when something is unclear.
    – HLGEM
    Sep 16 '13 at 18:56
















  • how could I have avoided that? any tips?
    – Draconar
    Sep 13 '13 at 20:54










  • Make sure you understand the problem completely before you start solving it. Even if you think you understand it, try saying "so just to check I understand this" and restate it in your own words. Also think about what they might not be telling you that might make a difference.
    – DJClayworth
    Sep 13 '13 at 20:59










  • gee... and I thought I was demonstrating how good a independent thinker I was. Talk about self-delusion. Nevertheless, how can I improve on this, since it is a thought pattern I'm so used to that I can't even realize it...
    – Draconar
    Sep 14 '13 at 16:19










  • And tehse types of interview questions are often deigned deliberaltely with big gaping holes to see if you will ask for clarification. This is important in many organizations because they want developers who will push back rather than make unqwarrented assumptions when something is unclear.
    – HLGEM
    Sep 16 '13 at 18:56















how could I have avoided that? any tips?
– Draconar
Sep 13 '13 at 20:54




how could I have avoided that? any tips?
– Draconar
Sep 13 '13 at 20:54












Make sure you understand the problem completely before you start solving it. Even if you think you understand it, try saying "so just to check I understand this" and restate it in your own words. Also think about what they might not be telling you that might make a difference.
– DJClayworth
Sep 13 '13 at 20:59




Make sure you understand the problem completely before you start solving it. Even if you think you understand it, try saying "so just to check I understand this" and restate it in your own words. Also think about what they might not be telling you that might make a difference.
– DJClayworth
Sep 13 '13 at 20:59












gee... and I thought I was demonstrating how good a independent thinker I was. Talk about self-delusion. Nevertheless, how can I improve on this, since it is a thought pattern I'm so used to that I can't even realize it...
– Draconar
Sep 14 '13 at 16:19




gee... and I thought I was demonstrating how good a independent thinker I was. Talk about self-delusion. Nevertheless, how can I improve on this, since it is a thought pattern I'm so used to that I can't even realize it...
– Draconar
Sep 14 '13 at 16:19












And tehse types of interview questions are often deigned deliberaltely with big gaping holes to see if you will ask for clarification. This is important in many organizations because they want developers who will push back rather than make unqwarrented assumptions when something is unclear.
– HLGEM
Sep 16 '13 at 18:56




And tehse types of interview questions are often deigned deliberaltely with big gaping holes to see if you will ask for clarification. This is important in many organizations because they want developers who will push back rather than make unqwarrented assumptions when something is unclear.
– HLGEM
Sep 16 '13 at 18:56


Comments

Popular posts from this blog

What does second last employer means? [closed]

List of Gilmore Girls characters

One-line joke