|
On February 11 2015 08:00 onlywonderboy wrote:
Messed up cooking my dinner beyond salvage for the first time, guess this calls for pizza.
Cat on head. House burnt down. Better call domino's
|
On February 11 2015 07:52 Nos- wrote:Show nested quote +On February 11 2015 01:23 Nos- wrote:
Not sure what to do as a cs major that can't write code for shit :|, pretty sure this amazon interview's gonna roast me alive. pray for my safe return ot Uh... well I wrote correct programs for 3/4 coding questions and we ran out of time for the last one so the guy just made me describe what I would do. Is that good or bad? I don't know if taking too long to do coding questions during interviews is something they look at.
I normally just lurk this thread but I worked at/interviewed for Amazon for around two years so...:
It sounds like this was a phone interview? In that case it sounds like you did fine. Phone interviews are primarily for screening out people who straight up can't code, especially when you're talking about entry-level (or intern) positions.
Once this bar is passed we'll normally keep asking questions to get more data to support a hire/no hire decision because we'll typically be talking with at least 1 other interviewer and it's good to have extra data to support a decision in case we disagree. There's really not a downside to asking extra questions during an interview as long as you can end it on time, so interviewers will tend to ask more questions or make their existing questions harder unless you actually finish every question they're prepared to ask, which is super rare.
The same essentially holds true for in-person interviews except obviously we're not gonna leave you alone until the next person comes so it's even more likely that we'll keep asking questions/doing something until the end of the interview block.
Anyway I can answer other questions if you have them but really it sounds like you did fine and you can normally expect to hear back from them relatively soon.
|
Your username is my favorite.
|
I can always count on you to post these.
Apparently he's supposed to be collaborating with Giorgio moroder at some point so I look forward to that.
As far as moms not remembering stuff, people in general won't remember stuff they don't care about. It's the same reason why I forget names of people I meet in social settings;I subconsciously don't care about them/know I won't be seeing them ever/often so my wife has to make sure I don't embarassed myself the next time we run into them.
|
I live <20 miles from downtown Cincinnati which has a ton of cool shit, including a casino, like 2 minutes from 'downtown' of my little city which has an awesome strip of bars and restaurants, plus all my shopping stuff, and like 5 minutes from Grand Sands, which is the massive indoor beach volleyball place I told you guys about one time.
Sucks to be all of you I guess.
I still stay home and game quite a bit though because fuck it I love games.
|
|
|
Hey you're a LD GD guy. I know you.
I can't remember the birthdays in my family, despite having the conversation about once every two months with my mother. I think I got my father nailed, and maaaaaybe my surviving grandmother.
I remember my godfather's best because I chose a character's birthdate at random and I happened to pick his. I only remember it because of the coincidence though, not because of the actual date.
I'm working on a website pertaining to formations for the state's employees, divided between regions (districts?) and stuff, and I still couldn't put them well on a map.
|
I just won a game as support Terrorblade.
Sunder + Dagon 4 op.
|
you are truely cancer incarnate, even Roffles pales before you.
|
On February 11 2015 08:50 Crusnik wrote:
you are truely cancer incarnate, even Roffles pales before you.
If it makes you feel any better I randomed.
|
On February 11 2015 08:17 eieio wrote:Show nested quote +On February 11 2015 07:52 Nos- wrote:On February 11 2015 01:23 Nos- wrote:
Not sure what to do as a cs major that can't write code for shit :|, pretty sure this amazon interview's gonna roast me alive. pray for my safe return ot Uh... well I wrote correct programs for 3/4 coding questions and we ran out of time for the last one so the guy just made me describe what I would do. Is that good or bad? I don't know if taking too long to do coding questions during interviews is something they look at. I normally just lurk this thread but I worked at/interviewed for Amazon for around two years so...: It sounds like this was a phone interview? In that case it sounds like you did fine. Phone interviews are primarily for screening out people who straight up can't code, especially when you're talking about entry-level (or intern) positions. Once this bar is passed we'll normally keep asking questions to get more data to support a hire/no hire decision because we'll typically be talking with at least 1 other interviewer and it's good to have extra data to support a decision in case we disagree. There's really not a downside to asking extra questions during an interview as long as you can end it on time, so interviewers will tend to ask more questions or make their existing questions harder unless you actually finish every question they're prepared to ask, which is super rare. The same essentially holds true for in-person interviews except obviously we're not gonna leave you alone until the next person comes so it's even more likely that we'll keep asking questions/doing something until the end of the interview block. Anyway I can answer other questions if you have them but really it sounds like you did fine and you can normally expect to hear back from them relatively soon.
Hey man thanks for this, I was nervous as all hell for this interview. It was a 2 part in person interview where they asked a few technical questions about time complexity and 4 coding questions, the last of which I ran out of time so I just told the guy my solution instead of coding it up. I think I got the code down to O(nlogn) at worst for all of them. Asked them a little about what their work was like on a typical day, how the culture was at the company, and if they liked working there towards the end. Got the interviewers to laugh and talk about their personal backgrounds so that's good?
|
... man I forgot everything about these kind of considerations and code complexity.
|
On February 11 2015 08:52 Nos- wrote:Show nested quote +On February 11 2015 08:17 eieio wrote:On February 11 2015 07:52 Nos- wrote:On February 11 2015 01:23 Nos- wrote:
Not sure what to do as a cs major that can't write code for shit :|, pretty sure this amazon interview's gonna roast me alive. pray for my safe return ot Uh... well I wrote correct programs for 3/4 coding questions and we ran out of time for the last one so the guy just made me describe what I would do. Is that good or bad? I don't know if taking too long to do coding questions during interviews is something they look at. I normally just lurk this thread but I worked at/interviewed for Amazon for around two years so...: It sounds like this was a phone interview? In that case it sounds like you did fine. Phone interviews are primarily for screening out people who straight up can't code, especially when you're talking about entry-level (or intern) positions. Once this bar is passed we'll normally keep asking questions to get more data to support a hire/no hire decision because we'll typically be talking with at least 1 other interviewer and it's good to have extra data to support a decision in case we disagree. There's really not a downside to asking extra questions during an interview as long as you can end it on time, so interviewers will tend to ask more questions or make their existing questions harder unless you actually finish every question they're prepared to ask, which is super rare. The same essentially holds true for in-person interviews except obviously we're not gonna leave you alone until the next person comes so it's even more likely that we'll keep asking questions/doing something until the end of the interview block. Anyway I can answer other questions if you have them but really it sounds like you did fine and you can normally expect to hear back from them relatively soon. Hey man thanks for this, I was nervous as all hell for this interview. It was a 2 part in person interview where they asked a few technical questions about time complexity and 4 coding questions, the last of which I ran out of time so I just told the guy my solution instead of coding it up. I think I got the code down to O(nlogn) at worst for all of them. Asked them a little about what their work was like on a typical day, how the culture was at the company, and if they liked working there towards the end. Got the interviewers to laugh and talk about their personal backgrounds so that's good?
Running out of time is completely completely normal and it shouldn't worry you at all unless you ran out of time on the first question or something. Like I said we're basically just gonna keep asking questions until it's time for you to ask questions and stuff at the end. It sounds like you were able to provide reasonable (they don't have to be perfect) solutions to problems and that you were able to talk about the time complexity of the solutions (super important) so while there's always some randomness when it comes to competitive interviews it sounds to me like you'll be fine.
Also we're super super used to candidates being nervous and that's completely normal. Having a few questions for the interviewers at the end + having enough personality to get some laughs is always good.
Oh and if you have the chance work at AWS, EC2 for life~~
I swear LL GD is like 50x nicer than LD GD rofl
plus more pokemon and MTG which is nice
|
On February 11 2015 09:03 eieio wrote:Show nested quote +On February 11 2015 08:52 Nos- wrote:On February 11 2015 08:17 eieio wrote:On February 11 2015 07:52 Nos- wrote:On February 11 2015 01:23 Nos- wrote:
Not sure what to do as a cs major that can't write code for shit :|, pretty sure this amazon interview's gonna roast me alive. pray for my safe return ot Uh... well I wrote correct programs for 3/4 coding questions and we ran out of time for the last one so the guy just made me describe what I would do. Is that good or bad? I don't know if taking too long to do coding questions during interviews is something they look at. I normally just lurk this thread but I worked at/interviewed for Amazon for around two years so...: It sounds like this was a phone interview? In that case it sounds like you did fine. Phone interviews are primarily for screening out people who straight up can't code, especially when you're talking about entry-level (or intern) positions. Once this bar is passed we'll normally keep asking questions to get more data to support a hire/no hire decision because we'll typically be talking with at least 1 other interviewer and it's good to have extra data to support a decision in case we disagree. There's really not a downside to asking extra questions during an interview as long as you can end it on time, so interviewers will tend to ask more questions or make their existing questions harder unless you actually finish every question they're prepared to ask, which is super rare. The same essentially holds true for in-person interviews except obviously we're not gonna leave you alone until the next person comes so it's even more likely that we'll keep asking questions/doing something until the end of the interview block. Anyway I can answer other questions if you have them but really it sounds like you did fine and you can normally expect to hear back from them relatively soon. Hey man thanks for this, I was nervous as all hell for this interview. It was a 2 part in person interview where they asked a few technical questions about time complexity and 4 coding questions, the last of which I ran out of time so I just told the guy my solution instead of coding it up. I think I got the code down to O(nlogn) at worst for all of them. Asked them a little about what their work was like on a typical day, how the culture was at the company, and if they liked working there towards the end. Got the interviewers to laugh and talk about their personal backgrounds so that's good? Running out of time is completely completely normal and it shouldn't worry you at all unless you ran out of time on the first question or something. Like I said we're basically just gonna keep asking questions until it's time for you to ask questions and stuff at the end. It sounds like you were able to provide reasonable (they don't have to be perfect) solutions to problems and that you were able to talk about the time complexity of the solutions (super important) so while there's always some randomness when it comes to competitive interviews it sounds to me like you'll be fine. Also we're super super used to candidates being nervous and that's completely normal. Having a few questions for the interviewers at the end + having enough personality to get some laughs is always good. Oh and if you have the chance work at AWS, EC2 for life~~
I swear LL GD is like 50x nicer than LD GD rofl plus more pokemon and MTG which is nice
Well now, don't mistake us (OT) for GD. That place is a black hole where happiness goes to die.
|
On February 11 2015 09:10 jcarlsoniv wrote:Show nested quote +On February 11 2015 09:03 eieio wrote:On February 11 2015 08:52 Nos- wrote:On February 11 2015 08:17 eieio wrote:On February 11 2015 07:52 Nos- wrote:On February 11 2015 01:23 Nos- wrote:
Not sure what to do as a cs major that can't write code for shit :|, pretty sure this amazon interview's gonna roast me alive. pray for my safe return ot Uh... well I wrote correct programs for 3/4 coding questions and we ran out of time for the last one so the guy just made me describe what I would do. Is that good or bad? I don't know if taking too long to do coding questions during interviews is something they look at. I normally just lurk this thread but I worked at/interviewed for Amazon for around two years so...: It sounds like this was a phone interview? In that case it sounds like you did fine. Phone interviews are primarily for screening out people who straight up can't code, especially when you're talking about entry-level (or intern) positions. Once this bar is passed we'll normally keep asking questions to get more data to support a hire/no hire decision because we'll typically be talking with at least 1 other interviewer and it's good to have extra data to support a decision in case we disagree. There's really not a downside to asking extra questions during an interview as long as you can end it on time, so interviewers will tend to ask more questions or make their existing questions harder unless you actually finish every question they're prepared to ask, which is super rare. The same essentially holds true for in-person interviews except obviously we're not gonna leave you alone until the next person comes so it's even more likely that we'll keep asking questions/doing something until the end of the interview block. Anyway I can answer other questions if you have them but really it sounds like you did fine and you can normally expect to hear back from them relatively soon. Hey man thanks for this, I was nervous as all hell for this interview. It was a 2 part in person interview where they asked a few technical questions about time complexity and 4 coding questions, the last of which I ran out of time so I just told the guy my solution instead of coding it up. I think I got the code down to O(nlogn) at worst for all of them. Asked them a little about what their work was like on a typical day, how the culture was at the company, and if they liked working there towards the end. Got the interviewers to laugh and talk about their personal backgrounds so that's good? Running out of time is completely completely normal and it shouldn't worry you at all unless you ran out of time on the first question or something. Like I said we're basically just gonna keep asking questions until it's time for you to ask questions and stuff at the end. It sounds like you were able to provide reasonable (they don't have to be perfect) solutions to problems and that you were able to talk about the time complexity of the solutions (super important) so while there's always some randomness when it comes to competitive interviews it sounds to me like you'll be fine. Also we're super super used to candidates being nervous and that's completely normal. Having a few questions for the interviewers at the end + having enough personality to get some laughs is always good. Oh and if you have the chance work at AWS, EC2 for life~~
I swear LL GD is like 50x nicer than LD GD rofl plus more pokemon and MTG which is nice Well now, don't mistake us (OT) for GD. That place is a black hole where happiness goes to die.
That would imply that I'm never happy.
Which isn't really wrong....
|
On February 11 2015 09:10 jcarlsoniv wrote:Show nested quote +On February 11 2015 09:03 eieio wrote:On February 11 2015 08:52 Nos- wrote:On February 11 2015 08:17 eieio wrote:On February 11 2015 07:52 Nos- wrote:On February 11 2015 01:23 Nos- wrote:
Not sure what to do as a cs major that can't write code for shit :|, pretty sure this amazon interview's gonna roast me alive. pray for my safe return ot Uh... well I wrote correct programs for 3/4 coding questions and we ran out of time for the last one so the guy just made me describe what I would do. Is that good or bad? I don't know if taking too long to do coding questions during interviews is something they look at. I normally just lurk this thread but I worked at/interviewed for Amazon for around two years so...: It sounds like this was a phone interview? In that case it sounds like you did fine. Phone interviews are primarily for screening out people who straight up can't code, especially when you're talking about entry-level (or intern) positions. Once this bar is passed we'll normally keep asking questions to get more data to support a hire/no hire decision because we'll typically be talking with at least 1 other interviewer and it's good to have extra data to support a decision in case we disagree. There's really not a downside to asking extra questions during an interview as long as you can end it on time, so interviewers will tend to ask more questions or make their existing questions harder unless you actually finish every question they're prepared to ask, which is super rare. The same essentially holds true for in-person interviews except obviously we're not gonna leave you alone until the next person comes so it's even more likely that we'll keep asking questions/doing something until the end of the interview block. Anyway I can answer other questions if you have them but really it sounds like you did fine and you can normally expect to hear back from them relatively soon. Hey man thanks for this, I was nervous as all hell for this interview. It was a 2 part in person interview where they asked a few technical questions about time complexity and 4 coding questions, the last of which I ran out of time so I just told the guy my solution instead of coding it up. I think I got the code down to O(nlogn) at worst for all of them. Asked them a little about what their work was like on a typical day, how the culture was at the company, and if they liked working there towards the end. Got the interviewers to laugh and talk about their personal backgrounds so that's good? Running out of time is completely completely normal and it shouldn't worry you at all unless you ran out of time on the first question or something. Like I said we're basically just gonna keep asking questions until it's time for you to ask questions and stuff at the end. It sounds like you were able to provide reasonable (they don't have to be perfect) solutions to problems and that you were able to talk about the time complexity of the solutions (super important) so while there's always some randomness when it comes to competitive interviews it sounds to me like you'll be fine. Also we're super super used to candidates being nervous and that's completely normal. Having a few questions for the interviewers at the end + having enough personality to get some laughs is always good. Oh and if you have the chance work at AWS, EC2 for life~~
I swear LL GD is like 50x nicer than LD GD rofl plus more pokemon and MTG which is nice Well now, don't mistake us (OT) for GD. That place is a black hole where happiness goes to die.
Yup.
You're welcome to stick around here.
Infusions of fresh blood every now and then means it's less likely for us to get shut down for being an 'old boys' club.'
|
United States23745 Posts
On February 11 2015 09:14 WaveofShadow wrote:Show nested quote +On February 11 2015 09:10 jcarlsoniv wrote:On February 11 2015 09:03 eieio wrote:On February 11 2015 08:52 Nos- wrote:On February 11 2015 08:17 eieio wrote:On February 11 2015 07:52 Nos- wrote:On February 11 2015 01:23 Nos- wrote:
Not sure what to do as a cs major that can't write code for shit :|, pretty sure this amazon interview's gonna roast me alive. pray for my safe return ot Uh... well I wrote correct programs for 3/4 coding questions and we ran out of time for the last one so the guy just made me describe what I would do. Is that good or bad? I don't know if taking too long to do coding questions during interviews is something they look at. I normally just lurk this thread but I worked at/interviewed for Amazon for around two years so...: It sounds like this was a phone interview? In that case it sounds like you did fine. Phone interviews are primarily for screening out people who straight up can't code, especially when you're talking about entry-level (or intern) positions. Once this bar is passed we'll normally keep asking questions to get more data to support a hire/no hire decision because we'll typically be talking with at least 1 other interviewer and it's good to have extra data to support a decision in case we disagree. There's really not a downside to asking extra questions during an interview as long as you can end it on time, so interviewers will tend to ask more questions or make their existing questions harder unless you actually finish every question they're prepared to ask, which is super rare. The same essentially holds true for in-person interviews except obviously we're not gonna leave you alone until the next person comes so it's even more likely that we'll keep asking questions/doing something until the end of the interview block. Anyway I can answer other questions if you have them but really it sounds like you did fine and you can normally expect to hear back from them relatively soon. Hey man thanks for this, I was nervous as all hell for this interview. It was a 2 part in person interview where they asked a few technical questions about time complexity and 4 coding questions, the last of which I ran out of time so I just told the guy my solution instead of coding it up. I think I got the code down to O(nlogn) at worst for all of them. Asked them a little about what their work was like on a typical day, how the culture was at the company, and if they liked working there towards the end. Got the interviewers to laugh and talk about their personal backgrounds so that's good? Running out of time is completely completely normal and it shouldn't worry you at all unless you ran out of time on the first question or something. Like I said we're basically just gonna keep asking questions until it's time for you to ask questions and stuff at the end. It sounds like you were able to provide reasonable (they don't have to be perfect) solutions to problems and that you were able to talk about the time complexity of the solutions (super important) so while there's always some randomness when it comes to competitive interviews it sounds to me like you'll be fine. Also we're super super used to candidates being nervous and that's completely normal. Having a few questions for the interviewers at the end + having enough personality to get some laughs is always good. Oh and if you have the chance work at AWS, EC2 for life~~
I swear LL GD is like 50x nicer than LD GD rofl plus more pokemon and MTG which is nice Well now, don't mistake us (OT) for GD. That place is a black hole where happiness goes to die. Yup. You're welcome to stick around here. Infusions of fresh blood every now and then means it's less likely for us to get shut down for being an 'old boys' club.'
He's like the first fresh face I've seen aside from Marmy lol.
|
|
|
Only people who posted in the original megathread allowed!
|
I heard pokemon..
Anyone doing that online competition for oras?
|
|
|
|
|
|
EPT
