Launch Pad Blog
Interview Prep: Starting the Interview Process with a Bay Area Start-up
by Cody Voellinger | Wednesday, July 10th, 2013
The start-up wants to interview you – great! But one common pitfall is not putting the effort in prior to the interview because you aren’t sold on the opportunity yet. After the interview you love the team, mission, culture, and schwag. Unfortunately they felt you were unprepared and uninterested... preparation must happen prior to the interview!
This link has great general start-up interview advice. Mine is written assuming you are an engineer preparing to start the interview process with a Bay Area start-up.
Before the Interview:
Before the first interview, 30 minutes is a good amount of time to allow you to:
Interview Style & Tactics:
You may notice “your relevant experience” as a pattern above. An entire interview process lasts maybe 5-6 hours into which you need to explain all of your years of experience. This is impossible, so determine what you have done that is most relevant and beneficial to the company you are interviewing with.
Whenever possible, use the STAR Technique:
This technique works well to answer Behavioral Interview questions; use it to describe the 4-5 stories you prepared.
Give examples! “I am a quick learner - when our DevOps engineer was sick for a week, I took over Chef and AWS responsibilities without prior experience.”
When discussing failures or weaknesses, quote lessons learned - “…the project was delivered late, but I used it as a chance to implement Agile.”
Think before you answer! Fight the urge to start talking right away, since a couple seconds of forethought will save you back-tracking later.
Talk through your answers as you whiteboard, code challenge and pair program. Generally start-ups are looking for someone who can work in teams to solve problems, and sometimes parameters are purposefully ambiguous to prompt questions. Teamwork and culture fit are usually 30-60% of the evaluation.
The interview is a communication experience. Don’t feel that you can only answer questions when asked – instead, create a dialogue. After answering a question, follow-up with: “Did I answer your questions? How would you have answered that?”
If the interviewer gives you a choice which language to code in, choose your strongest. Your ability will be judged assuming this is your best.
If you list a tool, tech, or skill on your resume, expect to be asked about it. If you claim to be an expert and can’t answer basic questions, interviewers will assume all of your “expert” level knowledge is questionable. Be confident in what you know and modest about what you don’t.
Show your personality! Talk about your interests (and list them on your resume): sports, hometown, hobbies, volunteering, gaming, travels, etc. Sharing an interest is an easy small-talk topic and a great way to find common ground with your interviewer.
Keep an open-mind regarding title and responsibilities. Save that discussion until a bond is established. At most start-ups, if they want to bring you onboard, a position can be created to meet your needs.
Towards the end of an interview, you should close. This means listening to the challenges of the position, team, and company, and recapping your relevant experience by circling back to:
Of course, with interviews come the topics of salary discussions and negotiations. These topics are important enough to deserve their own blog entries, so stay tuned.