4 ms·

In many companies the algo part is like 1/4th of the entire interview. The rest like code design, working with product simulations and coding challenges are pr

by mahyarm 11y ago

In many companies the algo part is like 1/4th of the entire interview. The rest like code design, working with product simulations and coding challenges are pretty relevant, even in CRUD land Its just the algo stuff you usually have to review before hand vs all the others

lostcolony 11y ago
'Its just the algo stuff you usually have to review before hand vs all the others' There's the problem. If it's something you have to review, it's not something you use that often. Unless the job is going to have you using it often, why is everyone's time being squandered on it?
- emodendroket 11y ago
  I guess the problem is you need it infrequently but when you do need it it is really helpful to know.
  - collyw 11y ago
    And easy enough to look up.
    - emodendroket 11y ago
      But what are you looking up? You have to know what class of problem you have to be able to look it up.
      - lostcolony 11y ago
        And if the interviewer will be satisfied with "Oh, this looks like an X kind of problem. I'd just google that and go from there", fair enough.
        emodendroket 11y ago
        A decent interviewer is probably willing to be cooperative and fill in some details for you. I guess some places are all about trying to play "gotcha" but the hell with them.
pc86 11y ago
This is almost exactly like Microsoft's response to the ribbon criticism when it first came out. They were so proud of themselves that a handful of those buttons were used 30% of the time or whatever, but ignored the fact that another handful was used <1% of the time yet were still visible by default on the default tab. Which is to say your justification is very much "75% of our interview process makes sense, it's only this 25% that you almost never needed any any previous job, you don't need at this one, and if you're self-taught you probably never learned in the first place, but we're going to ask you anyway because it makes the interviewer feel smart."

by mahyarm 11y ago

lostcolony 11y ago

'Its just the algo stuff you usually have to review before hand vs all the others' There's the problem. If it's something you have to review, it's not something you use that often. Unless the job is going to have you using it often, why is everyone's time being squandered on it?

emodendroket 11y ago
I guess the problem is you need it infrequently but when you do need it it is really helpful to know.
- collyw 11y ago
  And easy enough to look up.
  - emodendroket 11y ago
    But what are you looking up? You have to know what class of problem you have to be able to look it up.
    - lostcolony 11y ago
      And if the interviewer will be satisfied with "Oh, this looks like an X kind of problem. I'd just google that and go from there", fair enough.
      - emodendroket 11y ago
        A decent interviewer is probably willing to be cooperative and fill in some details for you. I guess some places are all about trying to play "gotcha" but the hell with them.

pc86 11y ago

This is almost exactly like Microsoft's response to the ribbon criticism when it first came out. They were so proud of themselves that a handful of those buttons were used 30% of the time or whatever, but ignored the fact that another handful was used <1% of the time yet were still visible by default on the default tab. Which is to say your justification is very much "75% of our interview process makes sense, it's only this 25% that you almost never needed any any previous job, you don't need at this one, and if you're self-taught you probably never learned in the first place, but we're going to ask you anyway because it makes the interviewer feel smart."