Interviewing skills are an important part of a job search. At Epicodus, you'll have the opportunity to participate in a mock interview with a member of our staff, and practice answering some typical questions. The more seriously we take it, the more we can learn as we move forward. There are some basics to consider as you prepare for any interview.
During the mock interview, we'll have questions that cover a few areas. These are by no means formal interview sections, and some interviews may focus on one area or another, but as a general rule these are present in one form or another in just about every interview. You'll have one or more questions from each section in your mock interview. For the purposes of the mock interview, we'll conduct the interview as if you were applying to work at Epicodus as a developer.
These are "get to know you" questions about yourself, and about your previous education, experience and motivations.
Your goal should be to explain the ways life has been preparing you to become a developer. General biographical information should be kept to a minimum. If you have prior programming experience you can talk about any coding you did as a kid or in school. If you're newer to coding you can emphasize parts of jobs where you worked with computers or spreadsheets, and tell about any computer skills you developed on your own.
Either way, make sure to emphasize the skills that have served you well as a student and developer, for example problem solving skills, critical thinking, organizational skills and so on. You want to show the interviewer you're passionate by illustrating how these skills have come up in different ways throughout your life.
These are discussion questions which give you a chance to showcase your knowledge about programming tools and concepts. This is different from a technical question.
The interviewer will want to know about your motivations and experiences in the workplace. These questions are a good chance to highlight your communication, teamwork, and work ethic.
Be well prepared for these interview questions and know how to answer them. These are generally less about your technical skill set and more about your work ethic and ability to collaborate with others. The general format they’re looking for is called S.T.A.R. It means:
Just about every interviewer will close out by asking if you have any questions. You should have at least a couple prepared ahead of time. The most effective ones show an interest in the company and in being a positive addition to it. Questions about the team and culture of the company and where you would fit in are also really good. It's important to have some questions prepared that will help you decide if this is a good fit for you. Make sure to ask about things that haven't been covered in previous conversation.
Before you walk into the interview, make yourself a physical or mental list of things you absolutely do not want to leave the interview without them knowing about you. These are not necessarily catch all things you spout off at every interview. Maybe you did a project that relates to what they’re working on. Maybe you have a lot of enthusiasm for a client they’re working with. As the interview is winding down, make sure you go through that list and that you’ve touched on all those things. Otherwise it can be really easy to walk out of an interview and only realize hours later that there were really important selling points you should have added.
This is not the time to ask about salary, vacation time, or other benefits. If they offer that information you can ask if those things are negotiable, but this is not the time to do the actual negotiating.
Be aware of non-verbal cues. It can tell you as much about how an interview is going as what the interviewer is saying. You can usually tell if you’re overstaying your welcome or if an interviewer is receptive to extended conversation by their expression or body language.
Above all else, remember that the employer came to you because they have a problem and they want you to be the solution. They’re investing time in interviewing you because they are in your corner and they want it to be a positive encounter.
When you participate in your mock interview, we'll be evaluating your performance, just like your code review. You will be reviewed on the following objectives: