4 ms·
Till today I haven't asked anyone to write actual code on whiteboard. Recently I had a chance to interview a Stanford grad who had previously worked on embedded
by kulu2002 9y ago
Till today I haven't asked anyone to write actual code on whiteboard. Recently I had a chance to interview a Stanford grad who had previously worked on embedded sys in some start-up. I asked him to draw system level architecture of his product in OSI layer format like where HAL/ firmware, RTOS, insys mem, db, application, UI are placed and how they are communicating with each other ...and this guy was staring at me like I am asking him to jump down from 10th floor. Then I thought did I do something wrong... I mean if you have really worked on/experienced something then you should know that thing thoroughly and then you don't need any special prep for interviews
- _xczx 9y agoI've never felt comfortable answering questions like those, because the designs are owned by the business. Even if I made it, I don't feel like I have the right to hand a design for my current employer to my next employer.
- danesparza 9y agoIdeas (and the ability to convey them) aren't owned by a business. shakes head Our society is waaaay to litigious if an interview is going to be overshadowed by the legal team like this.
- kulu2002 9y agoI don't think drawing just a block diagram of system means giving away the trade secrets of your product. I didn't ask him to draw flow charts of algorithms and business logic. And I don't even do that. I have seen many interviews purposefully conducted by rival companies where interviewers are specifically asked by company's marketing team to drill down interviewee on particular functionality and get details of business algorithms, system performance etc. Offcourse this happens when there is cut-throat competition and few players.