4 ms·
That’s exactly the path I would have gone, ask clarifying question to confuse the interviewers: - Is my boat actually floating in the lake? - Is the lake filled
by fetzu 2mo ago
That’s exactly the path I would have gone, ask clarifying question to confuse the interviewers:
- Is my boat actually floating in the lake?
- Is the lake filled with water?
- If yes, what is the temperature gradient of that water from top to bottom?
- How deep is the lake at the spot the ball is dropped?
- What is the current time and phase of the moon, and what are the exact coordinates of the ball drop?
- Are we doing this during some « end of the world gravitational collapse » event?
This would show them three things (which they did were not trying to find out, or maybe):
1. I think these questions are stupid.
2. I know that clear requirements and edge-cases are important
3. I’m an asshole and possibly not fun at parties
- kjellsbells 2mo ago> I’m an asshole and possibly not fun at parties I got this vibe at AWS, interviewing in 2020. They asked me to design a stock price tracking webapp. I started asking questions and sketching things out and at each question (fairly basic ones, too, like, how many users are we supporting, how frequently do they request updates, and how timely does the data need to be). Seemed reasonable to me but I think my line of questions annoyed them because they said, "just design the app!" Maybe they thought I was stalling? Hmm, ok, but it'll fall over on day 2. I turned down the offer.
- throwaway2037 2mo agoThis is starting to sound like the old joke about a coconut laden swallow from (the film) The Holy Grail. I would pay to see the interviewer sweat as you ask the follow-up questions! You sound like fun at a party!