loading...
Interview Cake

First time going through coding interviews? Common questions and answers.

gameguy43 profile image Parker Phinney Originally published at interviewcake.com ・3 min read

What's the interview process like at a tech company?

It's actually pretty different from most other companies.

Here's what it's like to interview for a programming job.

Do I need to know this "big O" stuff?

Big O notation is the language we use for talking about the efficiency of data structures and algorithms.

Will it come up in your interviews? Well, it depends. There are different types of interviews.

There’s the classic algorithmic coding interview, sometimes called the “Google-style whiteboard interview.” It’s focused on data structures and algorithms (queues and stacks, binary search, etc).

That’s what our full course prepares you for. It's how the big players interview. Google, Facebook, Amazon, Microsoft, Oracle, LinkedIn, etc.

For startups and smaller shops, it’s a mixed bag. Most will ask at least a few algorithmic questions. But they might also include some role-specific stuff, like Java questions or SQL questions for a backend web engineer. They’ll be especially interested in your ability to ship code without much direction. You might end up doing a code test or pair-programming exercise instead of a whiteboarding session.

To make sure you study for the right stuff, you should ask your recruiter what to expect. Send an email with a question like, “Is this interview going to cover data structures and algorithms? Or will it be more focused around coding in X language.” They’ll be happy to tell you.

If you you've never learned about data structures and algorithms, or you're feeling a little rusty, check out our Intuitive Guide to Data Structures and Algorithms.

Which programming language should I use?

Companies usually let you choose, in which case you should use your most comfortable language. If you know a bunch of languages, prefer one that lets you express more with fewer characters and fewer lines of code, like Python or Ruby. It keeps your whiteboard cleaner.

Try to stick with the same language for the whole interview, but sometimes you might want to switch languages for a question. E.g., processing a file line by line will be far easier in Python than in C++.

Sometimes, though, your interviewer will do this thing where they have a pet question that’s, for example, C-specific. If you list C on your resume, they’ll ask it.

So keep that in mind! If you’re not confident with a language, make that clear on your resume. Put your less-strong languages under a header like ‘Working Knowledge.’

What should I wear?

A good rule of thumb is to dress a tiny step above what people normally wear to the office. For most west coast tech companies, the standard digs are just jeans and a t-shirt. Ask your recruiter what the office is like if you’re worried about being too casual.

Should I send a thank-you note?

Thank-you notes are nice, but they aren’t really expected. Be casual if you send one. No need for a hand-calligraphed note on fancy stationery. Opt for a short email to your recruiter or the hiring manager. Thank them for helping you through the process, and ask them to relay your thanks to your interviewers.


Get the free coding interview crash course

Don't leave your interviews to chance. I'll teach you the underlying patterns behind the clever algorithms you'll need to come up with during tricky coding interview questions.

Send me coding interview tips »


Posted on Sep 10 '18 by:

gameguy43 profile

Parker Phinney

@gameguy43

Founder of Interview Cake. I like riding bikes but I think it's bad for my back?

Interview Cake

The easiest way to get really freaking good at coding interviews. Don't just learn what the answer is, learn /the thought patterns/ that'll empower you to answer tricky technical interviews questions yourself.

Discussion

markdown guide
 

As someone who has conducted many tech interviews (for Microsoft), I agree with all you say here. And I want to underscore that the language you code in doesn't matter. You can even make up some pseudo-language on the fly.

I suppose it's possible some interviewers are specifically looking for C/C++ skills, and wanting to make sure you can use pointers coherently. If you are interviewing for a position like that, be ready.

I have heard of interviewers who ask you how good (on a scale of 1 to 10) your C++ skills are, and then grill you on obscure things if you say 10. But to me that sounds more like them showing off than them doing a good job interviewing in a meaningful way.