Each Thursday, we'll take a break from coding to practice interview questions with our partner. These questions will (primarily) revolve around the content we learned this week, and, much like a "real" interview, some will be more technical than others.
In addition to learning how to implement the new tools, technologies, and concepts, you want to become comfortable talking about them too, so you may accurately demonstrate and communicate these skills you've learned to potential employers in an interview.
Take turns answering the questions below with your partner. It may even be helpful to have each partner answer in their own words.
Technical Interview Questions
- When I access a webpage by browsing to it at the URL line what processes take place before we see a fully rendered page? What part does the PHP we've been writing play in this process?
- If you load a page from your app in the browser and you get a 404 error, what steps would you go through before calling a superior?
- Discuss the benefits of testing with your partner. Why should we write tests for our code? What can happen if we do not?
- What do the terms arrange, act and assert mean, in terms of testing?
- What is MVC and why is it a helpful paradigm for us to use when creating web applications? Discuss (research) positives and pitfalls of the MVC paradigm.
- What get's you excited about programming? In what ways has your previous work or life experience enhanced your learning experience at Epicodus?
Stories and Examples
Offering a tangible story or example that highlights your skills usually goes much further in an interview than simply telling your interviewer you're good at something. (ie: Telling a story about a time you tracked down a tricky bug versus simply saying "I'm good at problem-solving!").
Remember the SHARE technique? It's a guideline for telling stories that demonstrate your capabilities in an interview:
- S: Describe a situation you faced relevant to the interviewer's question.
- H: Outline the hinderances and challenges the situation presented.
- A: Describe the action(s) you took in response.
- R: Go over the results of your actions.
- E: Then, evaluate what you've learned.
Using the SHARE outline, give an example of a time....
- Made a group more efficient, productive, or motivated in tackling a challenge. What was the situation? How did you rally your group members? What was the result?
- You made a really tough decision relating to work (of any kind, not just development) or a project. What was it? How did you make your decision? What was the outcome?
- You tackled an especially challenging assignment or project. What was it? How did you approach it? What happened?
If you come up with a story or example you feel good about; jot it down somewhere! It's tough to come up with stories like this in an interview on the spot. Having a few tucked away to review before an interview will be a huge benefit to you later.