Interview Process

Keep in the mind role/ background of the interviewer during the conversations!

• You should answer questions from a recruiter differently from how you answer a technical interviewer!

The Interviewers (People)

Recruiter:

• Has read your resume
• Your advocate; thinks you’re a good fit
• Your primary liaison to the company
  • Ask them questions!¹1. e.g., “who am I going to talk to? what is my schedule for the day?”; but DON’T hound them with questions (poor soft skill), especially after an interview don’t accidentally seem impatient.

Technical Interviewer:

• Has technical background
• They may or may not be a person on your team
• Will ask you to write code and solve algorithms problems

Management:

• Whether you meet depends on the company size
• May or may not have technical background (find out!)

Technical Phone Screen

If you get a TPS it means recruiters think you may have promise based on your resume.

The TPS exists mainly to avoid costly unsuccessful in-person interviews.

• Basically, are you as good as you are on paper?

Format

Introduction followed by questions on:

1. Programming (often in a shared Google Doc)
2. Data Structure / Big-O
3. Object Oriented Principles
4. Other Core CS Topics (Bitwise Manipulation, Scripting, Proper Use of Libraries, Testing)

Practical Tips

• Make sure your internet/phone connection is solid; and that you have a backup.
• Have a Google Hang-out / Zoom / etc. account ready and client updated.²2. Test with a buddy!
  • Look at camera, not yourself
  • Avoid slight nonverbal cues³3. If you want to do nonverbal cues, use big ones like two thumbs up or exaggerate for the camera.
• If non-visual, you can have notes (but don’t rely too heavily).
  • If visual, you should still have your resume on hand.
• Take notes on the interview!
  • What’d you cover? Who interviewed you? etc.
• Find a way to relax beforehand.
• Be practiced and prepared.

Common Pitfalls

• Not talking!⁴4. Some candidates will be asked a question and go dead silent for several minutes. Sometimes the interviewer will ask, “can you tell me what you’re thinking?” and the candidate will brush them off (“yeah just give me a second…”)
• Not ensuring a two-way dialogue.⁵5. e.g., interviewer gives a problem and candidate immediately begins coding. Ask follow-ups! Make sure you understand the question properly! And also give them high-level ideas about your coding so they can give you feedback before you go down the wrong path.
• Not being prepared.⁶6. e.g., not having your account ready, not having the technical knowledge needed, etc.
• Resume errors.

In-Person Interview

Takeaway: They aren’t looking for engineers to solve problems they already know the answer to, but engineers who can solve novel problems.

Format

45 minutes with a Software Engineer⁷7. You may have several of these and meet with other people as well.

Quick introduction followed by questions on:

1. Whiteboard programming
2. Data Structure / Big-O
3. Building Complex Algorithms
4. Other Core CS Topics (Bitwise Manipulation, Scripting, Proper Use of Libraries, Testing)

Remember, ANYTHING on your resume is fair game!

Tips

1. It’s OK to question the interviewer!
2. When asked to provide a solution, first define and frame the problem as you see it.
3. If you don’t understand something, ask for help or clarification
4. If you need to assume something, verbally check if it’s a correct assumption!
5. Describe how you want to tackle solving each part of the question.
6. Always let your interviewer know what you are thinking so they can follow your train of thought.
7. Remember that if you get stuck, they can only give hints when they know your train of thought.
8. DON’T MISS A HINT IF YOUR INTERVIEWER IS TRYING TO ASSIST!

Other practical tips:

• Take care of yourself
  • Sleep and eat well prior.
• Be prepared
  • Have your clothes ready. If you’re flying, have your interview clothes in your carry-on.
  • Have copies of your resume.
  • Bring project you’ve done.
  • Talk to your recruiter (know who you are talking to and your schedule)
• Relax and mentally prepare.

See Power Pose! Ted Talk.