You can always ask your interviewer for permission to look something up. They could say no, but if your request is reasonable they might allow it, or they might indicate that they don't care about whatever detail you're about to look up (the exact names of certain functions, the exact order of arguments to certain functions, and so on).
is a comprehensive book on getting a job at a top tech company, while focuses on dev interviews and does this for PMs.
CareerCup's interview videos give you a real-life look at technical interviews. In these unscripted videos, watch how other candidates handle tough questions and how the interviewer thinks about their performance.
Most engineers make critical mistakes on their resumes -- we can fix your resume with our custom resume review service. And, we use fellow engineers as our resume reviewers, so you can be sure that we "get" what you're saying.
Our Mock Interviews will be conducted "in character" just like a real interview, and can focus on whatever topics you want. All our interviewers have worked for Microsoft, Google or Amazon, you know you'll get a true-to-life experience.
If all you need to lookup the internet is for whether in strcpy src comes before destination or not etc, you should not worry. Since these are the type of things you can actually lookup in real life, you can tell the interviewer you are assuming a certain signature. Skipping over the irrelevant details like these shows maturity, and show that you know to focus on what is important.
- Anonymous March 11, 2013In fact, I would strongly discourage you from try to look things up on the internet (unless required/explicitly told by the interviewer). If the interviewer gets any such inkling, he might think you are trying to google the answers...