3 ms·
> Imagine, you got a standard website the serves data from a database. When a customer types in the url into the browser bar what needs to happen until the cust
by retzkek 8y ago
> Imagine, you got a standard website the serves data from a database. When a customer types in the url into the browser bar what needs to happen until the customer see the website.
That's a favorite of mine too. It sets up a broad range of discussion without needing to spend much time setting up hypotheticals and lets the interviewee really delve into topics for which they have expertise and/or interest. It's also easily adapted or sets up follow-up questions for different positions or levels, e.g. "with TLS," or "how would you debug a problem with symptom x?"
- je42 8y agoexactly that you can have very interesting conversations. in a setting that the interviewee is most comfortable with, since the assumptions/details are determined by them. it put the pressure a bit on you as interviewer, since you need to adapt your questions. but in general i found it quite easy when you have a rough plan on the topics to ask.