Yep didn't go through. Knocked out by the awkward phone screen. Pretty sad.
The feedback was "we wanted more depth in the answers". You know I actually asked if that's what they wanted and didn't get a reply.
Sorry to hear dude, don't give up though. Apply, apply, apply! Something will turn up.
It's all good guys
I've actually already had a job offer for 80k doing something I really like. I ended up not settling with it to go for a bigger fish.
Touching back on this, at the end of the day you do whatever you want, but sometimes you've got to momentarily settle for something you don't want before you get what you want. (in other words, you could have accepted the job and still applied to spacex and other places)
None.
It's all good guys
I've actually already had a job offer for 80k doing something I really like. I ended up not settling with it to go for a bigger fish.
Touching back on this, at the end of the day you do whatever you want, but sometimes you've got to momentarily settle for something you don't want before you get what you want. (in other words, you could have accepted the job and still applied to spacex and other places)
That is true, thanks for the advice. For record when I turned down the previous position I was still in school. Soon after school abruptly ended due to unforeseen circumstances.
Minor update on the job search: Did a practice interview with a friend of mine that works at game studio nearby as a senior engineer. I did really well! After the practice interview we chatted about the SpaceX screen. Conclusion was that I got weirded out by the SpaceX's unusual phone screen format. Oh well, moving along.
It'll be fun to post more updates as more interviews come along at different places.
None.
Okay so I just send a sincere email to the recruiter saying how freakin awkward I was, and that I'd love a chance to really live up to my ability's potential.
She responds with OK, what time can I schedule a 1hr tech phone call?
LOL
None.
... did you just follow up an interview by
negging disparaging yourself and actually have it work?
Post has been edited 1 time(s), last time on Nov 16 2015, 9:27 pm by Mini Moose 2707.
Find Me On Discord (Brood War UMS Community & Staredit Network)
Haha this is gonna be good.
Minor update on the job search: Did a practice interview with a friend of mine that works at game studio nearby as a senior engineer. I did really well! After the practice interview we chatted about the SpaceX screen. Conclusion was that I got weirded out by the SpaceX's unusual phone screen format. Oh well, moving along.
See if he can get someone you don't know to give you a practice interview. It'd be helpful to try with someone you're not already comfortable with.
tits
Okay so I just send a sincere email to the recruiter saying how freakin awkward I was, and that I'd love a chance to really live up to my ability's potential.
She responds with OK, what time can I schedule a 1hr tech phone call?
LOL
DAT HOW ITS DUN YUNG BULL
None.
... did you just follow up an interview by negging yourself and actually have it work?
I know what negging is, but I fail to see how this is negging.
I think recruiters prefer you to be honest and besides, if you're actually an awkward person they probably already know.
Did the 1 hr call with senior engineer. Sounded like it went pretty dang well. Got to impress him a couple times. He really liked that I knew about pointer aliasing, and that I had worked on a pet compiler recently.
I did flounder a bit when he asked how I'd design a huge simulation where real pilots would eventually ride a vehicle supported by my code. Such an open-ended question, I tried to scope it down into pieces as best I could. In the end I think he was decently satisfied with my answer.
Couldn't quite answer what volatile meant in C, but the context kinda matters. Interviewer wanted to shoot through questions quickly, and told me to say "pass" if I was stumped or didn't really know an answer. I can roughly explain volatile (signals to compiler that this value can just suddenly change, so it needs to be constantly re-fetched into any caches, like CPU cache), but I haven't actually used or studied volatile in detail. Oh well!
Waiting for results from recruiter.
Edit: Passed! Moving onto the long 6 hr technical test.
Post has been edited 1 time(s), last time on Nov 16 2015, 8:43 pm by CecilSunkure.
None.
>be faceless void >mfw I have no face
Sweet, sounds really good man!
Red classic.
"In short, their absurdities are so extreme that it is painful even to quote them."
... did you just follow up an interview by negging yourself and actually have it work?
I know what negging is, but I fail to see how this is negging.
You are correct. I have edited my post.
Post has been edited 1 time(s), last time on Nov 16 2015, 10:42 pm by Mini Moose 2707.
Relatively ancient and inactive
Congrats, Cecil! Good luck on that six-hour! Amazing call on calling the recruiter back, those are the kinds of things I wish I'd have thought of doing months after the fact.
None.
Took a 6 hour programming challenge via email. The problem they gave me required integer sorting, string sorting and implementing data structures of choice. My code passed 6/34 of their tests. I chose too complex of a solution to finish in time. The test was in C++, I could use std::string, but nothing else from the STL or later than C++98.
I predict I'll rather quickly get a response from the recruiter saying they aren't interested. Oh well! It happens
None.
Find Me On Discord (Brood War UMS Community & Staredit Network)
Well, at least now you know that you didn't get the job based on your own lack of skill rather than unfairness by the recruiter. So that's something.
Damn, why am I not surprised that some NASA-type job requires some hardcore programming shiz. Can't believe you've got to take six hours out of your day just to TEST to see if you get the job.
Did you use test-driven development? Eg focus on passing each test 1 at a time?
None.
Well, at least now you know that you didn't get the job based on your own lack of skill rather than unfairness by the recruiter. So that's something.
Damn, why am I not surprised that some NASA-type job requires some hardcore programming shiz. Can't believe you've got to take six hours out of your day just to TEST to see if you get the job.
Well it was actually a communication error, not a tech error. I was supposed to be continually emailing the test proctor for questions and advice, but I had assumed I wasn't supposed to do this until the test ended. I just didn't really have experience with this kind of thing and didn't think to ask about what is appropriate.
Did you use test-driven development? Eg focus on passing each test 1 at a time?
Not allowed to see the test, just a raw number of how many I pass/fail. I spent too much time on a solution that would take too long to implement. I've never sorted strings before, so I was unaware how long it would take. This could easily be solved by asking for advice from the proctor (see above), which I did not do.
None.
CecilSunkure
