3 ms·
> Personally I think "coding interviews" are just very insulting and speak of an awful state of the industry. Imagine giving an electrical engineer a 1st year u
by yencabulator 4y ago
> Personally I think "coding interviews" are just very insulting and speak of an awful state of the industry. Imagine giving an electrical engineer a 1st year undergrad assignment to make sure he really can calculate the properties of a basic circuit. Seems like a good reason to just walk out.
I don't want to defend whiteboard programming, not at all. But I think one can get a lot of value out of simple concrete questions.
Example: Person applying to C/C++ systems programming job -- think low-level file formats, kernel interaction, custom network protocol -- without understanding hex numbers.
Me, the interviewer, asking what 0x10 is in decimal (feel free to use pen & paper!) is a lot quicker than trying to sniff out a good bullshitter that you've allowed to be in control of the conversation.
No, I really don't think you can do the job without knowing hex.
Yes, I really think any background that would have prepared you to be successful at the job would have had you interacting with binary data in some form. (Saying you personally prefer octal would have been a plus, not a minus -- it would have communicated experience.)
- constantcrying 4y agoI absolutely agree, I even like the question. The difference to the coding interview is that nobodys time is wasted. It is a very quick question and if you get a slightly confused "16" back, you can just move on to more relevant matters. This is different to a 30 minute long question where you examine the applicants ability to solve first year undergrad homework. But that you are asking the question at all speaks by itself for major problems in employment.