5 ms·
They can't code because you are looking figuratively over their shoulder---the clock is ticking next to a hundred grand in a suitcase. A single question is pul
by mixmastamyk 8y ago
They can't code because you are looking figuratively over their shoulder---the clock is ticking next to a hundred grand in a suitcase.
A single question is pulled from subjects vast enough to fill up years of college and there is no time to research, as one would in the real world. Binary pass/fail with your pride/livelyhood/family on the line.
Please state your last exam conducted under such conditions?
Oh and your questions probably stink. I've gotten plenty of them with recursion that might take ten minutes in seclusion but simply not possible under the gun.
- bsder 8y ago> They can't code because you are looking figuratively over their shoulder---the clock is ticking next to a hundred grand in a suitcase. There is a difference between me asking you how to optimize a graph algorithm (good luck--I probably couldn't do that on the fly with references in front of me) vs giving me a basic FizzBuzz. If I let you pick your language for your FizzBuzz, you need to demonstrate at least some of the following things: I/O of any flavor (I'll even accept Logging if you don't do standard I/O or console I/O) String formatting Modulus Operator Nested-If statements (or equivalent--Matching, case/switch, etc.) I'm not looking for production code. I'm looking for 10-20 lines of "A High School senior with a computer class could pass this." This is not limited to programming, sadly. I used to have to interview VLSI designers with "Draw me an inverter", and 70% of them couldn't pass.
- bglazer 8y agoTo be totally honest, I always find these stats about some x% > 50% failure to program at all totally unbelievable. What do these people do all day, if not design and build software? Yet they're apparently completely unable to write code? How is that possible? I understand that there is always a certain amount of slack and underperformance but any workforce would be completely paralyzed by 70% completely incompetent workers. And yet companies everywhere still produce software.
- taneq 8y agoIt's because some large percentage of your time at work is spent in meetings, writing emails, discussing things, etc. where actual ability to do the core task isn't necessary. And then some large percentage of "enterprise software development" is just hooking up buttons and text fields to a database, and doesn't require any more algorithmic complexity than a few if() statements. And then some large percentage of the remaining work can be performed adequately by just picking some appropriate ready-made solution off Stack Overflow. Put them all together and chances are, you can skate by for years (and actually perform acceptably) without ever actually needing to write FizzBuzz-level code for yourself.
- bsder 8y ago1) Selection bias Good/excellent programmers rarely need to interview except as a formality. Consequently, you are, by definition, interviewing weaker programmers. 2) Tool use masquerades as programming Visual Basic 4/5/6 was one of the original sins in this genre, but it continues now with other tools and frameworks. Being able to point-and-click a tool and plumb it together isn't programming--but people will claim it is. Then when someone asks for an actual program--those people fail. This does not necessarily mean that those people are not productive. However, it does mean that they can't actually function in a position where they are expected to program.
- dunpeal 8y ago> What do these people do all day, if not design and build software? Indeed this is a fascinating question, and I explored it a few times. Some folks who have multiple years of "software engineering" on their resume worked in a place where they did some form of "paint by numbers" programming, producing some work by modifying templates with limited (at best) understanding beyond the specific blanks they were filling. An example is folks who work with large frameworks that are designed to be extended with little to no coding, such as WordPress and Drupal. Then they want to advance to software engineering, so they recast their experience - of essentially configuring and deploying software, i.e. sysadmin - as "programming", and get those 5 years represented as "a full time programming position". There's variants of that, basically "developers" doing very limited ant-work with large frameworks they don't understand and couldn't rewrite from scratch if their lives depended on it. There's also a bunch of languages and frameworks invented for the explicit purpose that someone with little to no CS knowledge of programming talent could produce useful work. Most of us here live in a bubble of startups where we often create products from scratch using lean (or no) frameworks. In reality, a scary amount of the "IT work" out there appears to be what I described above. Possibly a substantial majority.
- mixmastamyk 8y agoYou may get only those questions in a junior interview. I get the optimize a graph algorithm ones also. Now I certainly could do it in the course of a job within a week, with a day or two of research. But not under the gun. That is the tech interview failure in a nutshell.
- taneq 8y agoWe always get these kinds of responses when interview testing is mentioned. This isn't some high-level algorithm analysis on a whiteboard with a panel of examiners grilling you. This is a simple test of basic competence. It's like interviewing a candidate Formula 1 driver and asking them "so which bit's the brake pedal?" If they can't tell you that instantly then they shouldn't be applying for the position in the first place. > Please state your last exam conducted under such conditions? University entrance exams. University graduation exams. Any other test that you do which you need to pass to enter or continue your career.
- mixmastamyk 8y ago> We always get these kinds of responses… Perhaps you should start listening. > This isn't some high-level algorithm analysis on a whiteboard with a panel of examiners grilling you. Happened to me just three months ago. The req is still open, wonder why? To reiterate: - Exams have a topic known in advance. - Exams never have a person sitting there waiting for the answer. - Exams are never 1 or 2 questions binary pass/fail with incredibly high stakes in unfamiliar territory. Which is the brake pedal? If only.
- watwat1 8y agoNo point in being bitter.
- mixmastamyk 8y agoYou'll get bitter when the rent is due, watwat.
- taneq 8y agoWe're talking about "basic fizz-buzz level coding questions". It sounds like you had a bad experience with something else that we weren't talking about. (As for 'topic known in advance', I'd suggest that if you don't know what topics that you might be asked about in a job interview, maybe you shouldn't be interviewing for that job.)
- 8y ago
- Sophistifunk 8y agoOne possible way to address this issue is by asking candidates to talk about some existing code you give them, rather than trying to cook something up off the bat while under scrutiny and not having access to their familiar tooling.