4 ms·

I know this is a joke but an Amazon recruiter sent me prep info for an interview last month ( I declined ) but it says no one does whiteboard coding. They give

I know this is a joke but an Amazon recruiter sent me prep info for an interview last month ( I declined ) but it says no one does whiteboard coding. They give you a laptop for those portions of the interview. They only use a whiteboard for systems design questions for software developer interviews. (not that James Gosling would get the standard interview, either)

moron4hire 9y ago
That must be a recent change. I interviewed with Amazon a year ago and it was 4 or 5 hours of pretty much nothing but whiteboard coding. I don't mind, though. I don't understand why people can't do whiteboard code. It's usually super simple stuff yet people get caught up on things like not remembering that for-loops take three parameters. I mean, yes, the compiler will stop you. But just how long have you been doing this job that you can't do THAT one in your sleep? What I did mind about Amazon was that clearly they were lying to me about the expectations of overtime, as well as the compensation package was ludicrously bad.
- pjmlp 9y ago
  You don't have Stack Overflow built into the whiteboard.
  - moron4hire 9y ago
    I know this is a super-unpopular opinion these days, but... Why can't you program the simple problems that interviewers use for whiteboard coding without Stack Overflow? It's not even like interviewers are looking for syntax-perfect code (which you wouldn't need Stack Overflow for anyway, the compiler is what catches that for you). I've never had an interviewer that would quibble over a missed semi-colon here or there. Hell, most of the time I end up using "begin/end" style pseudo-code instead of curly-braces, because curly-braces are stupidly hard to draw well on a whiteboard. And even if you don't know off the top of your head what "invert binary tree" means, every interviewer I've ever had has been more than willing to answer any questions I have about the problem. Ask questions about requirements and you should be able to figure it out. If, once you know what the inputs and outputs of "invert binary tree" should be and you still can't do it, I seriously gotta question what the hell you're doing interviewing for the job of programmer. I once passed an interview for a job I wasn't even applying for, even though I didn't know off the top of my head what "LRU cache" meant, by asking enough questions ("oh, LRU means least-recently used? Well then, something like this?") I tend to think of whiteboard coding problems as being ineffective for interviewing because the problems are so simple. To me, anybody should be able to solve these problems. I know a lot of people can't, and this serves as a quick filter to winnow them out. But they are so ludicrously easy I just don't get how you can say you need Stack Overflow to solve these problems. I'm with Jonathan Blow on this one: https://twitter.com/mxcl/status/608682016205344768 https://twitter.com/mxcl/status/608682016205344768
    - srdev 9y ago
      I'm with you on this one. I understand frustration at "trick" problems or problems that make use of little-known algorithms or approaches. But there seems to be this sentiment that doing basic traversal and manipulation on data structures like a tree is burdensome. I simply can't trust in your abilities as a software developer if you need Stack Overflow to traverse a tree. You do need some fluency with basic data structure and algorithms, along with the ability to adapt them, in order to do non-trivial software development.
    - pjmlp 9y ago
      I fully agree with you, and that was my point. Current generation developers don't seem to be able to program without doing "Stack Overflow driven programming". So when you put them in front of a whiteboard, it is like their knowledge just vanished. Now, what I am fully against is the complete disregard for the work experience of what one might have and reduce it to Data Structures & Algorithm exercises that many haven't done in several years, eventually decades.
      - moron4hire 9y ago
        > haven't done in several years, eventually decades. This is the part I don't understand. What is your job that you never do anything related to data structures or algorithms? I'd like to know so I can stay away from such jobs. I just can't imagine being happy with such a dead-end job that doesn't require me to think of solutions to problems. If these jobs can be done by any monkey with a brute-force approach, then let any monkey do them. I've got better things to do.
        pjmlp 9y ago
        Enterprise consulting for Fortune 500 companies, working with distributed teams that scale from a few developers up to a few hundreds. Sometimes there are actually cool projects, no issues with licenses for the likes of Oracle servers or Visual Studio Ultimate. Also I do get to enjoy life outside work with the people that actually matter to me. Downsides, well there are lots of politics, social skills matter as much as coding skills, sometimes projects go really wrong.
- stevenwoo 9y ago
  Someone else pointed this out to me as well, to clarify it may have been because this position was within their video game development studios/game engine/backend, not a general SDE position. The list of topics they gave me was a general CS background so nothing unusual there.
  - deleted 9y ago
    [deleted]
dgemm 9y ago
I don't know of any teams that will not ask you to write code on a whiteboard for an SDE position.
- stevenwoo 9y ago
  It was for a video game developer position. I specifically asked the HR point of contact if I will be asked to do a whiteboard coding question and it was emphatically denied. (there was an email query of interest from the HR rep and I sent back a response saying if there's a whiteboard coding question I decline to not waste any of our time.) I've had to do whiteboarding coding questions for video game positions in the 90's.

moron4hire 9y ago

That must be a recent change. I interviewed with Amazon a year ago and it was 4 or 5 hours of pretty much nothing but whiteboard coding. I don't mind, though. I don't understand why people can't do whiteboard code. It's usually super simple stuff yet people get caught up on things like not remembering that for-loops take three parameters. I mean, yes, the compiler will stop you. But just how long have you been doing this job that you can't do THAT one in your sleep? What I did mind about Amazon was that clearly they were lying to me about the expectations of overtime, as well as the compensation package was ludicrously bad.

pjmlp 9y ago
You don't have Stack Overflow built into the whiteboard.
- moron4hire 9y ago
  I know this is a super-unpopular opinion these days, but... Why can't you program the simple problems that interviewers use for whiteboard coding without Stack Overflow? It's not even like interviewers are looking for syntax-perfect code (which you wouldn't need Stack Overflow for anyway, the compiler is what catches that for you). I've never had an interviewer that would quibble over a missed semi-colon here or there. Hell, most of the time I end up using "begin/end" style pseudo-code instead of curly-braces, because curly-braces are stupidly hard to draw well on a whiteboard. And even if you don't know off the top of your head what "invert binary tree" means, every interviewer I've ever had has been more than willing to answer any questions I have about the problem. Ask questions about requirements and you should be able to figure it out. If, once you know what the inputs and outputs of "invert binary tree" should be and you still can't do it, I seriously gotta question what the hell you're doing interviewing for the job of programmer. I once passed an interview for a job I wasn't even applying for, even though I didn't know off the top of my head what "LRU cache" meant, by asking enough questions ("oh, LRU means least-recently used? Well then, something like this?") I tend to think of whiteboard coding problems as being ineffective for interviewing because the problems are so simple. To me, anybody should be able to solve these problems. I know a lot of people can't, and this serves as a quick filter to winnow them out. But they are so ludicrously easy I just don't get how you can say you need Stack Overflow to solve these problems. I'm with Jonathan Blow on this one: https://twitter.com/mxcl/status/608682016205344768 https://twitter.com/mxcl/status/608682016205344768
  - srdev 9y ago
    I'm with you on this one. I understand frustration at "trick" problems or problems that make use of little-known algorithms or approaches. But there seems to be this sentiment that doing basic traversal and manipulation on data structures like a tree is burdensome. I simply can't trust in your abilities as a software developer if you need Stack Overflow to traverse a tree. You do need some fluency with basic data structure and algorithms, along with the ability to adapt them, in order to do non-trivial software development.
  - pjmlp 9y ago
    I fully agree with you, and that was my point. Current generation developers don't seem to be able to program without doing "Stack Overflow driven programming". So when you put them in front of a whiteboard, it is like their knowledge just vanished. Now, what I am fully against is the complete disregard for the work experience of what one might have and reduce it to Data Structures & Algorithm exercises that many haven't done in several years, eventually decades.
    - moron4hire 9y ago
      > haven't done in several years, eventually decades. This is the part I don't understand. What is your job that you never do anything related to data structures or algorithms? I'd like to know so I can stay away from such jobs. I just can't imagine being happy with such a dead-end job that doesn't require me to think of solutions to problems. If these jobs can be done by any monkey with a brute-force approach, then let any monkey do them. I've got better things to do.
      - pjmlp 9y ago
        Enterprise consulting for Fortune 500 companies, working with distributed teams that scale from a few developers up to a few hundreds. Sometimes there are actually cool projects, no issues with licenses for the likes of Oracle servers or Visual Studio Ultimate. Also I do get to enjoy life outside work with the people that actually matter to me. Downsides, well there are lots of politics, social skills matter as much as coding skills, sometimes projects go really wrong.
stevenwoo 9y ago
Someone else pointed this out to me as well, to clarify it may have been because this position was within their video game development studios/game engine/backend, not a general SDE position. The list of topics they gave me was a general CS background so nothing unusual there.
- deleted 9y ago
  [deleted]

dgemm 9y ago

I don't know of any teams that will not ask you to write code on a whiteboard for an SDE position.

stevenwoo 9y ago
It was for a video game developer position. I specifically asked the HR point of contact if I will be asked to do a whiteboard coding question and it was emphatically denied. (there was an email query of interest from the HR rep and I sent back a response saying if there's a whiteboard coding question I decline to not waste any of our time.) I've had to do whiteboarding coding questions for video game positions in the 90's.