Google is HEAVY on Python... I have some experience working directly with Google engineers in their offices, and I can tell you the level of knowledge that they all have in their respective areas. It's significant, and they're going to want someone with a deep working knowledge of the technologies with which they are familiar. For Python, this includes things like knowing the interpreter, and how the interpreter handles memory, how different Python objects are handled in the background and their performance (such as iterators and generators... you should know the difference), GIL, etc.
Here are a few resources that have helped me BIG TIME with not only learning more specific (and often advanced) Python features/methodologies, but also with knocking out difficult Python job interviews.
Hidden features of Python: http://stackoverflow.com/questions/101268/hidden-features-of-python
Get to know that link well. Read through each one, and make sure you understand them. You may already know most of them, or you may not. Either way, it's likely that one or more of those will appear on someone's Python quiz.
Understand that. In fact, if you're a Python developer, you should make it a point to understand that. Interview or not.
What are good Python interview questions? http://www.quora.com/What-are-good-Python-interview-questions
There are only a couple here, but they definitely make you think about some of the core (and common) Python objects and how they're used, and why they work the way they do.
Above all else, many places (actually, every place except one) has required that I write code in order to complete the interview. I'm not sure if Google will ask you for this, but I don't see why they wouldn't. Be prepared to write code, and make sure it's readable (they'll likely want you on a team, so your code better be readable and "play well with others").
And if you do write code in the interview, most importantly... PEP8!! Learn PEP8, and show that you know it in your interview!
Django Coding style: https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/coding-style/
I hope this helps you. Good luck and let us know how it went!
On Thu, Jan 31, 2013 at 12:48 PM, Tom Evans <tevans.uk@googlemail.com> wrote:
On Thu, Jan 31, 2013 at 5:25 PM, Larry Martell <larry.martell@gmail.com> wrote:Don't google for 'interviewing at google', or they'll know what you
> Books have been written about interviewing at google. Google
> 'interviewing at google' and you'll find a plethora of stories. After
> reading them you may not want to interview there. I was offered a
> chance to interview there about 8 years ago, and I after reading what
> it would be like, I declined. YMMV
are up to! Best to use Bing for that.
Bad jokes aside, you should have a clear idea why you want to work
there, what you can bring to them, and why they would want it (this is
basically true of any interview). Work it out before you go there, so
you don't stammer around trying to figure it out on the spot!
Cheers
Tom
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
No comments:
Post a Comment