## Posts Tagged ‘**Interview Questions**’

## Alphabetic Phone Number Generator SOLVED [Problem of the Week]

It’s been a while, huh? Well, for the second time, my apologies!

Anyway, the past problem was of medium difficulty, but there’s a trick that could make your life much easier. Do you know what a permutation is? This is a permutation problem. A definition of permutation is that a permutation of [ABC] is simply [ABC – ACB – BAC – BCA – CAB – CBA] .. all possible arrangements of the three letters. Think of our problem the same way, you just need all possible arrangements for the three characters corresponding to each number. Easier? Thanks to Abdalla Gamal for making our lives easier.

So, similar to the ACM problems, we’ll solve the standard permutation problem, where we get to print all possible arrangements of a set of digits. Then, we transform that to our problem. Read the rest of this entry »

## Alphabetic Phone Number Generator [Problem of the Week]

Mmm, not quite problem of the “week” since it has been a while since I last posted a problem – I had a busy few weeks, my apologies!

Anyway, let’s move to the problem – another Microsoft interview problem. Sure you’ve all seen how phone pads hold three letters of the alphabet for every number you can press (except for 1 and 0). Check the photo below to know what I mean …

The problem is simple. The input is a distinct, seven-digit number. The required output is all seven-character strings that could be generated from this number. Read the rest of this entry »

## Count Open Lockers SOLVED [Problem of the Week]

Seems this week’s problem was quite easy – five winners in less than two days!

Such problem is meant to look overwhelming. It would be very pointless if you thought of solving it by drawing a diagram of 100 lockers and literally ‘performed’ the 100 passes to know the solution. If this was an interview, be sure that you’ll be kicked out before you notice it!

First thing, forget the brute-force solution, since – again – it’s all about *how* you tackle the problem; that’s what the interviewer wants to see.

Go for a random number and give it a try – perhaps you could notice a sequence or a pattern. Let’s pick, mmm, 8?! Sounds good to me .. Read the rest of this entry »

## Count Open Lockers [Problem of the Week]

Last week’s problem was a mistake – I had to suffer LOTS of code tracing and compiling. I had a troublesome “code” week here and in work ..

Anyway, as a result, no coding this week – just pure brain-work!

This week’s problem is a brainteaser, also is asked in interviews. The main point behind it is to show your interviewer how you could think to solve difficult, vague problems. Here’s the problem ..

Suppose you are in a hallway lined with 100 closed lockers. You begin by opening all 100 lockers. Next, you close every second locker. Then you go to every third locker and close it if it is open or open it if it is closed (call this

togglingthe locker). You continue toggling everynth locker on pass numbern. After your hundredth pass of the hallway, in which you toggle only locker number 100, how many lockers are open?In a hall with

klockers, how many lockers remain open after passk?

I’m sure I’ll get tons of questions about that, so here’s a *second* explanation: Imagine this hallway of 100 lockers. You make “passes” on these lockers .. Read the rest of this entry »

## Link-the-Tree [Problem of the Week]

Seems that last week’s problem was a bit difficult as Fouad stated in his last problem, so this weeks it’s an easier one .. not that easy though. It should be easy for all ACMers .. we’ll see!

I first met this problem in a physical Microsoft technical interview (and solved it a7l), which stresses how being an ACMer helped me **a lot** in passing interviews. Actually, *that* Microsoft interview is broken into four interviews: three in problem solving (= ACM) and one in System Architecture, Analysis and Design.

Anyway, here’s how this problem goes ..

You have a binary tree, not necessarily complete, where each **Node** holds two pointers (left and right) and a character as an identifier. Read the rest of this entry »

## Secret Creator [Problem of the Week]

After the Design Patterns course has ended in FCIS, and following up with the wicked problems of my friend, Fouad, I decided to post a code design problem I heard lately …

`class Secret`

{

` // TODO: class body goes here ..`

}

`class Creator`

{

` // TODO: class body goes here ..`

}

You have two classes: **Secret** and **Creator**.

Code both classes such that no other class than **Creator **is allowed to instantiate a local object of Secret. In other words, I can create an object of **Secret** as long as this code is inside **Creator**. If I’m inside any other class than **Creator**, I can’t!!! Read the rest of this entry »