Great Interview Questions You Have Been Asked

I like the one where you ask the person to explain “what happens between when you type an address in a browser until you get something to show up” in as much details they can. It tells you a lot about people understand all the different concepts involving computing.

Describe event bubbling.

What would you do to radically improve test automation speed?

Describe accessibility in as much detail as you can.

In the context of web services explain full duplex service transmission.

What is something amazing you would suggest we implement with Node.js to reduce our operating expenses?

One of the most interesting question i was asked was: What is the biggest fire you created and how did you handle it?

The interviewer told me that the purpose of the question was to learn 1) are you willing to admit mistakes 2) what is the most responsibility you've been trusted with. After all the bigger the fire, the more you were likely trusted 3) how do you act under stress 4) can you learn lessons from your mistake.

I think it's a fantastic cultural fit type question.

I wish interviewers in Japan can throw away their textbooks to be a real person and have real conversation. Mostly only 3 question.

1. Why do you choose Japan? (so why pick me during screening if you want me out?)

2. Tell me the largest achievement of yours. (completely parallel to work ability and don't even reveal any personality)

3. What's your future plan? (want me to tell you that I will quit 5 years later just to get a PhD?)

These question must be so epic that everyone must ask once everytime.

In my first frontend interview at 18, the interviewer tested me on the most basic thing. He could have asked more difficult questions that I might have had the answer to, but instead he asked about markup.

“In this first line of HTML it says , what will happen if we remove it and why?”

Unfortunately, it discouraged me at that age to try again for a long time, but it stuck with me.

"ELI5 to me how I can order something on Amazon using an iPad"

Engineering is about clear communication of ideas and sometimes we have to _really_ dumb down some things for a non-technical audience (think board members).

Trying to ELI5 a subject you feel is your strongest is surprisingly difficult - but a vital skill when moving up the engineering ladder.

"it says here that you've been using technology X for a few years. What is the most frustrating thing about X? If you had the resources needed what would you do to fix it?"

The best one I know is asking to describe a system you worked on, and supposedly know well, and deep dive into it.

Emacs or Vi ? /s