I applied at an in-person hiring event at the University of Central Florida. About three weeks later, I received an email saying that I was chosen to follow up with the first round of interviews, which took place on my campus. The recruiting staff traveled back to my school to interview all the candidates. A month later, I received another email saying I had moved on to the second round of interviews, which took place at their main campus in Seattle, WA. They paid for all my travel and living expenses for the three-day trip. I was allowed to choose the arriving and departing dates from several options they gave me.

Once I arrived in Seattle, they gave me a day to explore the city on my own. The other day was used almost entirely for interviews, although they did let me out around 4 PM to do more exploring. I went through three interviews with different employees from the Microsoft Office team, each lasting about an hour. They all seemed to press firmly on the matter of testing code, with questions like:

• "How would you test this code?"
• "Did you ever run any tests to make sure it worked?"
• "How do you know this code works?"

Not all the interviews started out that way, but they did end like that.

Given a regular phone number dial pad, write code that will list out all the possible letter combinations that can be made from three numerical digits as input.

For example, the base function would look like this:

javascript function numberToChars(numbers) { // would return an array of different character combinations // if input was 123 // output: adg, adh, adi, bdg, etc... }

How would you test a function like this to make sure it works?

Imagine a function that takes in two file paths as parameters and then copies the contents of the first file path into the second one.