Alternate Questions
I ask because I came up with a couple you could use, maybe for a digital humanities kind of position:
- How many people, throughout history, have actually been named "Flee-From-Sin"? I feel like you see this as a jokey Puritan first name in books like Good Omens or the Baroque Cycle, but was it a name that some non-negligible number of people actually had?
- Out of all the people currently within New York City limits, have more of them written a sonnet or a dating profile? What's the ratio?
** It's hard to tell these things sometimes even if you listen to lots of people discuss hiring and recruiting. "Five Worlds" and its decade-later ramifications apply to work culture, not just software development methodology. Stripe's engineering interview aims to "simulate the engineering work you'd do day-to-day" (link via Julia Evans) so I think you can expect your interviewer won't show up wearing a question-mark costume and screeching, "Riddle me this, Batman!" This software engineer, who's just been through scads of hiring interviews, doesn't mention puzzle questions. This level of detail ain't exactly on the "How to Become a Computer Programmer" page in the Occupational Outlook Handbook from the US Department of Labor -- but then again we already knew that the assessment vacuum in software engineering skills is a huge problem.
* That's right, two subtitles. That's how you know you're getting a lot for your $16.00 MSRP.
[Cross-posted to Cogito, Ergo Sumana. I'm doing this just now for new Dreamwidth followers, but usually I don't cross-post from there to here; check out sumana_feed if you want to follow that blog.]
no subject
no subject
Almost none of the questions I've been asked during tech company interviews have been "sizing questions" (Lindsey Kuper pointed out that term to me after reading my post, and she's right, a sizing question is somewhat different from other sorts of puzzles and brainteasers, even though the general reason interviewers ask any of them is to hear you think aloud as you work to solve it and demonstrate your approach to this sort of question). The only interview I can remember that included a sizing question is the Fog Creek one in late 2005. I can't remember whether my interviewer asked about phone booths or something else -- stoplights? stop signs? -- but it was something where the physical geography of the city was my jumping-off point. I started reasoning about the number of street intersections in Manhattan and how often people needed that thing, and multiplying stuff out based on guesses of various kinds, thinking aloud when various numbers seemed too small or too big and refining my guesses, and so on. I'm pretty sure my interviewer didn't know the actual number. It must have been a good enough performance; I got passed along to the next interviewer, and then I was hired.