Flutterby™! : Interviewing

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics


2018-06-29 12:39:30.496798+00 by Dan Lyke 3 comments

RT Dave Josephsen @DaveJosephsen:

Interviewer: hmmm Can you think of any way we can make this faster?

Me: Sure, lets replace this array with a log-linear histogram

Interviewer: Uh..

Me: Sit the fuck down, your smug ass wanted to play fancypants with the datastructures. Now we're here for the night

Bonus: Hexing the technical interview.

comments in ascending chronological order (reverse):

#Comment Re: Interviewing made: 2018-06-29 17:22:54.87138+00 by: brennen

I have seldom read anything more beautifully crafted than "But Hacker News has read of you, in their snicker-slithing sussurential warrens, and word has spread".

#Comment Re: Interviewing made: 2018-06-30 00:00:35.047183+00 by: TheSHAD0W

With regards to "Hexing the technical interview"... Code performance, and coder's level of expertise is one thing. Maintainability is something else. :-P

#Comment Re: Interviewing made: 2018-07-01 09:24:28.708909+00 by: DaveP

I’ve seen two very talented guys get rejected from my team because (apparently) they didn’t pass the programming quiz that was part of the hiring process.

Thing is, I’m at the point in my career where I’m pretty sure it not worth the headache to even point this out to the appropriate manager. Plus since we got a lot of open recs for devs, but almost none for testers, it might be even better that we didn’t hire them.

Point? Don’t know that I have one, other than, "damn I’m glad I’m never going to interview for another technical job again."

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)

Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.

Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.