Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "white board interviews"
-
About 18 months ago my non-technical Manager of Applications Development asked me to do the technical interviews for a .NET web developer position that needed to be filled. Because I don't believe in white board interviewing (that's another rant), but I do need to see if the prospective dev can actually code, for the initial interview I prepare a couple of coding problems on paper and ask that they solve them using any language or pseudo code they want. I tell them that after they're done we'll discuss their thought process. While they work the other interviewing dev and I silently do our own stuff.
About half way through the first round of technical interviews the aforementioned manager insisted we interview a dev from his previous company. This guy was top notch. Excellent. Will fit right in.
The manager's applicant comes in to interview and after some initial questions about his resume and experience I give him the first programming problem: a straightforward fizzbuzz (http://wiki.c2.com/?FizzBuzzTest). He looked as if the gamesters of Triskelion had dropped him into the arena. He demurs. Comments on the unexpectedness of the request. Explains that he has a little book he usually refers to to help him with such problems (can't make this stuff up). I again offer that he could use any language or pseudo code. We just want to see how he thinks. He decides he will do the fizzbuzz problem in SQL. My co-interviewer and I are surprised at this choice, but recover quickly and tell him to go ahead. Twenty minutes later he hands me a blank piece of paper. Of the 18 or so candidates we interview, he is the only one who cannot write a single line of code or pseudo code.
I receive an email from this applicant a couple of weeks after his interview. He has given the fizzbuzz problem some more thought. He writes that it occurs to him that the code could be placed into a function. That is the culmination of his cogitation over two weeks. We shake our heads and shortly thereafter attend the scheduled meeting to discuss the applicants.
At the meeting the manager asks about his former co-worker. I inartfully, though accurately, tell him that his candidate does not know how to code. He calls me irrational. After the requisite shocked silence of five people not knowing how to respond to this outburst we all sing Kumbaya and elect to hire someone else.
Interviews are fraught for both sides of the table. I use Fizzbuzz because if the applicant knows how to code it's an early win in the process and we all need that. And if the applicant can't solve it, cut bait and go home.
Fizzbuzz. Best. Interview. Question. Ever.6 -
I hate white boarding sessions. They feel unnatural to me. I simply don't work well when put on the spot and I have 3 ogres staring at me waiting for me to fuck up in front of them. Fight or flight engages, the adrenaline rush, my mind freezes. Suddenly it's like I forget how to code at all and I'm expected to solve a problem at once, correctly the right time, or I'm out.
I can't work like that. I need time to process a problem on my own, with my coffee in my one hand and a pencil and scratch paper in the other, not with some demanding employer standing over my shoulder the whole time scrutinizing my every key stroke. I get things wrong the first time sometimes, and more often than not have to google things I can't recall spontaneously. But I always figure it out, test it, make sure it's right before putting it into use.
I've been through several "probationary" periods when first starting a job. They just tell you, they're giving you a month to see if you can handle the job. If not, sayonara. I don't see what's so hard about evaluating candidates in a real world scenario.
So many employers have totally unrealistic expectations.2 -
It’s funny being on the other side of interviews. People say how complicated it is to get a job, and it is. But then they show up to a third round Senior Software Engineer technical interview and is unable to write a function on the white board in any language or even pseudo code to reverse a string. That isn’t complicated stuff...
Argh, very frustrating.2 -
I just don't get it.
Been looking for a new job for 2+ years and have failed at every opportunity. Numerous white board interviews, code challenges, hours upon hours wasted. Just can't seem to make the next move. I believe I have my soft skills down because I am able talk and do meetups just fine but either I'm too junior or something else is going on.
What started all of this was my latest rejection that I thought I had in the bag. Sailed through all their questions, did a live code thing, all of that being for 3+ hours. As it's called a final interview with them. Not to mention they're a startup, figured their standards might even be a bit lower than normal since they're needing people. Yet, still got rejected.
This sort of stuff, I'm seriously considering just leaving tech in general and probably just go do a outside job. With supposedly everything going for me like working in a hot job market, in a growing tech town, experience, and doing extra coding on my own time to beef up my portfolio. Doesn't matter. Still continious rejection. Lol in fact how I even got my current job was through completely unconventional means and based on that, I think it's done me more harm than good, which is why I'm trying to leave my current job and go into a place where I can be a better developer.
As of now, back to the grind of trying to find something.7 -
1) Learning little to nothing useful in formal post-secondary and wasting tons of time and money just to have pain and suffering.
"Let's talk about hardware disc sectors divisions in the database course, rather than most of you might find useful for industry."
"Lemme grade based on regurgitating my exact definitions of things, later I'll talk about historical failed network protocols, that have little to no relevance/importance because they fucking lost and we don't use them. Practical networking information? Nah."
"Back in the day we used to put a cup of water on top of our desktops, and if it started to shake a lot that's how you'd know your operating system was working real hard and 'thrashing' "
"Is like differentiation but is like cat looking at crystal ball"
"Not all husbands beat their wives, but statistically...." (this one was confusing and awkward to the point that the memory is mostly dropped)
Streams & lambdas in java, were a few slides in a powerpoint & not really tested. Turns out industry loves 'em.
2) Landed my first student job and get shoved on an old legacy project nobody wants to touch. Am isolated and not being taught or helped much, do poorly. Boss gets pissed at me and is unpleasant to work with and get help from. Gets to the point where I start to wonder if he starts to try and create a show of how much of a nuisance I am. He meddle with some logo I'm fixing, getting fussy about individual pixels and shades, and makes a big deal of knowing how to use GIMP and how he's sitting with me micromanaging. Monthly one on one's were uncomfortable and had him metaphorically jerking off about his lifestory career wise.
But I think I learned in code monkey industry, you gotta be capable of learning and making things happen with effectively no help at all. It's hard as fuck though.
3) Everytime I meet an asshole who knows more and accomplish than I do (that's a lot of people) with higher TC than me (also a lot of people). I despair as I realize I might sound like that without realizing it.
4) Everytime I encounter one of my glaring gaps in my knowledge and I'm ashamed of the fact I have plenty of them. Cargo cult programming.
5) I can't do leetcode hards. Sometimes I suck at white board questions I haven't seen anything like before and anything similar to them before.
6) I also suck at some of the trivia questions in interviews. (Gosh I think I'd look that up in a search engine)
7) Mentorship is nigh non-existent. Gosh I'd love to be taught stuff so I'd know how to make technical design/architecture decisions and knowing tradeoffs between tech stack. So I can go beyond being a codemonkey.
8) Gave up and took an ok job outside of America rather than continuing to grind then try to interview into a high tier American company. Doubtful I'd ever manage to break in now, and TC would be sweet but am unsure if the rest would work out.
9) Assholes and trolls on stackoverflow, it's quite hard to ask questions sometimes it feels and now get closed, marked as dupe, or downvoted without explanation.3 -
I been casually looking for a new job as a senior software engineer. I have about 7 years of experience, mainly back end, and it seems like everyone has a different way of doing technical interviews. What type of questions would you expect to be asked? I've gotten everything thing from white board code and solutions (expected), technical questions (expected), to code an API from scratch (not hard, but not really a good judge of skills). How do you identify whether a job is a sweatshop vs. a good job?2