Thanks for sharing your experience. Wow, that sounds like a super hard interview. Grrrr. :-||
I'm currently scheduled for my first phone interview with Google next week. They've already shared the whiteboard, but I'm concerned about using it during the interview.
Unfortunately, it doesn't provide me with all the tools I normally have, which can make it difficult and will probably make me more nervous. I use Eclipse, and I'm pretty dependent on the real-time error notifications that pop-up. I code both Java and Visual Basic.NET, and my common mistakes are similar to the following:
//VB code - loop 10 times
for x=1 to 10
//
next x
//Java code - loop 10 times
for (int i=1; 10; i++) {
//
} Here Eclipse would have highlighted the error on the 10 because I needed to write:
for (int i=1; i<=10; i++) {
//
}
But on a whiteboard I'm gonna look like an idiot. Wish it was a Skype/Webex/LiveMeeting/Whatever where I could share my desktop and use my tools of choice. I bet that would have helped you too.
I enjoyed hearing about your experiences. Keep interviewing the more you do it the better you get at it. Best of luck to you!
ReplyHey yvonnewatkins!!
I am glad you liked reading my blog. You are right, we have become so used to the coding tools we use that we do commit such silly mistakes while coding on whiteboard. But hey, don't worry about all this, interviewer will keep giving you hints if there will be such mistakes and i don't think these small mistakes will do u any harm (they understand). Just avoid big blunders though. Just ask for some extra time and run through your code quickly and if you you will be able to catch and correct your mistakes, it leaves a good impression.
All the best for your interview next week. And please do share your blog here so that i can read and learn from you interview :).
ReplyThat's y I always recommend students and fresher to start coding using vi and compile it manually . IDE are only good when you have big project . But I would still feel company would always look at pseudo code rather than programming errors
Replysure, thank you :)
Reply