News for hackers. Stuff that matters.
Re:Dear Startups: Stop Asking Me Math Puzzles to Figure Out ... by ColinWright on Monday August 03, 2015 @02:50PM (#9998827)
When I'm hiring I don't ask math stuff, puzzle stuff, and architectural stuff, to see if you can code. I ask you these things to see if you can do anything other than code. Coding is usually a relatively small part of the job. The ability to grok and manipulate the problem setting is more important, so how you react to puzzles tells me something.

Not being able to do the math, or the puzzles, or whatever, is not a "no hire" - it's a place to start talking about other strengths, abilities, interests, and potential contributions.

But I will also ask you to code.

Re:Dear Startups: Stop Asking Me Math Puzzles to Figure Out ... by karlkatzke on Monday August 03, 2015 @03:19PM (#9999062)
During my last round of interviews last fall, places that required knowledge of major math theorems in the interview resulted in rejections 100% of the time. Interviews that either provided a definition of the math required or provided some of the steps to solve the problem resulted in job offers 100% of the time.

Oddly, while I didn't need to be able to reference the language I was using exactly (pseudocode was good enough), they wouldn't help me out with the math knowledge, implying that it was "Algebra I stuff" and that "Everyone knows that."

The interviews (and my job as an Ops guy) in general don't require advanced math knowledge. Places that require memorized knowledge about things during an interview that are not part of the job field pull crappy things. I saw this in at least half of the interviews.