Exercise Thursday

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:

Technical Interview Questions


  • Walk through the differences between a one-to-many and a many-to-many database relationship.
  • Describe a use case for a many-to-many relationship. What about a one-to-many?
  • What is the purpose of a join table? What should be included in a join table? What shouldn't be?
  • What is a join statement?
  • Walk through how a join statement works. What information needs to be included? What does our database do with this information?
  • Under what relationship does an object contain the id of another object?
  • Talk about the steps needed to take in information from a user in the browser, save it to a server, and display that information back. What kinds of data types are we using? How do we use our PHP class constructor in different ways throughout this process?

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!").

Have you heard of the SHARE technique? It's a useful guideline for telling stories and giving examples that demonstrate your capabilities in an interview. It works like this:

  • 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....

  • You faced issues working with a partner or team. What did you do to resolve it? How did it work out?
  • You became incredibly frustrated with your code. What was the issue? What did you do? Would you have done anything differently?
  • You refactored really well. How did you do it? Why? What led you to refactor?

If you come up with a story or example you feel good about; jot it down somewhere! Seriously! 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.