views:

302

answers:

6

I've been offered an face-to-face programmer interview for an great company that is 8 hours time difference and 20 hours flight away. I'm being flown there having done an initial phone interview.

On arrival, I have 30 or so hours to recover/study/find food before the actual interview.

Having done a lot of travel before, I'm a little concerned my performance will suffer. I'd appreciate hearing from anyone who has done this, and especially on any strategies to help me get through.

+1  A: 

Yes, your performance WILL suffer. However, if they're going to the trouble to fly you out that far and put you up just for an interview, they're aware of it. Presumably, you performance will be somewhat graded on a scale because of it. Still, your concern is valid; you might try to get some melatonin to help you reset your sleep schedule, and make sure you avoid caffeine and alcohol for the period before the interview (although coffee right before and during would probably be a good idea).

Good luck!

McWafflestix
+1  A: 

Try to get a solid night of sleep and don't hit the books too hard. If you know your stuff, you do fine. Save the alcohol for after the interview. Good Luck

Captain Insano
+5  A: 

I did exactly this back in 2004 when I interviewed for Google (the firm I still work for), except for details such as that (since I lived in Italy and was flying to California) the time-zone difference was nine hours, not eight -- on arrival I had to get a rental car and drive from SFO to a hotel in Sunnyvale (at evening rush-hour on the bedraggled 101;-), and the interview was the very next morning.

All this, plus, I'm one of those people who suffer more than average from jet-lag effects. So, I'm entirely certain that my performance did suffer... but clearly the many interviewers who saw me in that long, exhausting day must have known about it, and compensated to some extent, since I was extended an offer (and accepted it).

I expect that this should generalize to any company who often flies candidates in from distant parts of the world for interviews -- they do, after all, want to pick the best candidate.

As for strategies, studying or cramming right before an interview is IMHO not a bright idea! What I did that night was instead to start reading this great book -- it had just been published, and I had Amazon deliver it at my hotel so I could dip immediately into reading. (If reading great programming books is not your idea of relaxing and resting, read a thriller, watch a movie, go bowling -- whatever it IS that refreshes and relaxes you!).

Alex Martelli
+2  A: 

There is some science to fighting Jet Lag. You could try one of the calculators that will tell you when to sleep and wake on those first two days to best adjust to the new time zone.

Here is one I found from a quick Google search: Lite Book Jet Lag App

cgyDeveloper
+2  A: 

I would suggest getting as much sleep as possible and not getting uptight about it. You are either what they're looking for...or not. Be who you are in an interview. While you may perceive this company as the perfect fit for you, that's your perception from the outside in. They may be a terrible employer for you.

That doesn't mean that I think you should take a flippant attitude about the interview. By all means, be prepared. But fretting about proper rest or cramming for a technical interview is a waste of time, IMO. You either know the material or...you don't. You're well rested...or not. There are far more important things in life.

Just my opinion. I could be wrong.

Bob Mc
+1 this is core issue to with all interviews. Easy to forget with all the excitement of travel.
Justicle
+1 you won't get through an interview by cramming the night before. Do they want to work with you? Do you want to work with them?
Jeremy McGee
A: 

Try not eating for 12 hours before your destination wake-up time.

I did on my last trip around the US.

Then you eat, and the idea is the blood sugar level change resets your body clock.

It seemed to work for me, but my digestion and therefore energy levels were still out of whack.

But I was alert.

Tim Williscroft