I met a recruiter at a career fair, and he set me up with a phone interview a few weeks later. The phone interviewer asked me about a past project I worked on, what I learned from it, and what was the most challenging problem I had to solve—questions of that nature. Then, he asked me an open-ended technical question about building an application on Google Glass. It didn't require any coding; I just described on a higher level how I'd use the hardware to design this application.

I was then offered an on-site interview, which I found strange as I had not done anything technical on my phone interview.

The on-site interview was very accommodating. They placed me in the Madison Concourse hotel, and I had dinner with an Epic employee the two nights I was in Madison.

The interview itself was very long. Mine began at 8:45 AM and I left the headquarters at around 4 PM. The technical aspect of the interview was all done on a computer. They had:

• A coding section
• A quick 20 questions section
• A math section
• A reasoning section that involved slowly being introduced to a new programming language and answering questions about it.

Since the coding part is done on the computer, it could really hurt candidates who don't remember a small piece of syntax.

The math section had brain teaser questions. I did not know companies still asked these kinds of questions; the use of dated interview questions reflected badly on me.

The other "interview" portion of my visit was a 20-minute interview with an employee about a project I had done. It was informal and pretty casual.

Find all the possible passwords, given the length of the password and that it is a well-ordered number (159 is well-ordered as 1 < 5 < 9).