6 ms·

I like this idea, but still think that time and people watching you will add pressure. Most coding challenges that non-FAANG companies give aren't terribly har

I like this idea, but still think that time and people watching you will add pressure. Most coding challenges that non-FAANG companies give aren't terribly hard; they mostly want you to work through your process out loud, ask questions, interact. These soft skills are as important as technical aptitude in determining whether or not you'd be a good fit with the organization.

CharlieDigital 3y ago
> but still think that time and people watching you will add pressure When I conduct interviews, I always try to set a conversational tone from the very beginning. Code reviews in general lend themselves more to a conversational interaction and discussion rather than trying to read, process, construct, and respond in a coding challenge.
- shortrounddev2 3y ago
  It's admirable, but the interviewee is always under some kind of pressure to perform. if you are taking a conversational tone, they're going out of their way to be similarly nonchalant
nextlevelwizard 3y ago
But you will have people watching you work and you will be under time pressure in normal work as well, so if you just turn to spagetti at interview are you actually going to perform any better at day to day?
- baka367 3y ago
  When was the last time you had to nail out a fully working nlog(n) longest valid bracket sequence in to prod within 45 mins, without spending 3 weeks in meetings, design doc reviews, capacity plannings and allocations and alignments with the said bracket owners?
  - hcks 3y ago
    meetings, design doc reviews, capacity plannings and allocations and alignments are not supposed to be used as ways to hide mediocrity
  - nextlevelwizard 3y ago
    No one - literally no one - expects perfect implementation of anything in an interview, where are you even getting this notion? What actually *is* expected of you is to describe how you would approach the issue.
- shortrounddev2 3y ago
  I literally never have anyone watching me code, and the time pressure of an interview is way shorter than a 2 week development cycle
  - nextlevelwizard 3y ago
    So you have never worked in an office with other people? And yes couple hours of interview is different than two weeks sprint, but you are very naive if you think two week of work days means 80 hours of work. Plus I expect a lot more from you during a sprint than during an interview. During an interview I am fine with pseudo code as long as you can explain what you want to do. During actual sprint I actually expect tested deliverables.
    - shortrounddev2 3y ago
      > So you have never worked in an office with other people? I used to, but even then nobody actively watched me code. Everyone else had their own jobs to do > During an interview I am fine with pseudo code as long as you can explain what you want to do. During actual sprint I actually expect tested deliverables. So you're optimizing for the ability to write pseudocode under intense time pressure and social awkwardness. Is that the most important quality you seek in a candidate?
      - nextlevelwizard 3y ago
        [flagged]

CharlieDigital 3y ago

> but still think that time and people watching you will add pressure When I conduct interviews, I always try to set a conversational tone from the very beginning. Code reviews in general lend themselves more to a conversational interaction and discussion rather than trying to read, process, construct, and respond in a coding challenge.

shortrounddev2 3y ago
It's admirable, but the interviewee is always under some kind of pressure to perform. if you are taking a conversational tone, they're going out of their way to be similarly nonchalant

nextlevelwizard 3y ago

But you will have people watching you work and you will be under time pressure in normal work as well, so if you just turn to spagetti at interview are you actually going to perform any better at day to day?

baka367 3y ago
When was the last time you had to nail out a fully working nlog(n) longest valid bracket sequence in to prod within 45 mins, without spending 3 weeks in meetings, design doc reviews, capacity plannings and allocations and alignments with the said bracket owners?
- hcks 3y ago
  meetings, design doc reviews, capacity plannings and allocations and alignments are not supposed to be used as ways to hide mediocrity
- nextlevelwizard 3y ago
  No one - literally no one - expects perfect implementation of anything in an interview, where are you even getting this notion? What actually *is* expected of you is to describe how you would approach the issue.
shortrounddev2 3y ago
I literally never have anyone watching me code, and the time pressure of an interview is way shorter than a 2 week development cycle
- nextlevelwizard 3y ago
  So you have never worked in an office with other people? And yes couple hours of interview is different than two weeks sprint, but you are very naive if you think two week of work days means 80 hours of work. Plus I expect a lot more from you during a sprint than during an interview. During an interview I am fine with pseudo code as long as you can explain what you want to do. During actual sprint I actually expect tested deliverables.
  - shortrounddev2 3y ago
    > So you have never worked in an office with other people? I used to, but even then nobody actively watched me code. Everyone else had their own jobs to do > During an interview I am fine with pseudo code as long as you can explain what you want to do. During actual sprint I actually expect tested deliverables. So you're optimizing for the ability to write pseudocode under intense time pressure and social awkwardness. Is that the most important quality you seek in a candidate?
    - nextlevelwizard 3y ago
      [flagged]