Got rejected for the job. Paired programming test fucked me over while my scores were pretty decent. Absolute fucking joke of an interview process that is. Get rejected because I feel rushed and it fucked my normal process and made it look like I just rush into coding when I felt rushed because 45 minutes just isnt enough for a solution. And just having to talk so much and try and think everything out loud. Fuck. Seriously am I just fucking not cut out cause I'm slow and rushed to do it and just am fucking dumb when they probably told me no rush or is this a neural typical thing or should i just never fucking bother in this industry cause in clearly fucking not cut out fuck.

@roxie **hug** Mmm, so, so many interviewers are utterly oblivious to just how much of an obstacle their process can present, even if *they* would feel fine undergoing it. That doesn't mean not ensuring people have the skills you're looking for; but it does mean being a lot more careful in an interview process' design than piling up some interviews and pair-programming and/or timed keylogged tests.

I once crashed out of an interview because of a "write this code whille you're on the phone with me and speak the code you'd write" test. He attempted to defend it on the basis that, oh, well, that's the kind of stress you'll be under at a startup.

The fuck it is. Yes, there can be crunch times, but that's a very different, transient matter. Plus, then, you've got *momentum* - you know the project, the code, the people you're working with, and your life is (hopefully) more or less fine, with a place of your own, or a room somewhere you like, with bills paid. Some or *all* of these may not be true for the applicant. The process must be designed with that in mind, else a company's throwing people aside who'd otherwise do very well.

@porsupah just like tired. just want one chance to actually show i can do the job in that environment and its just looking like the only job it looks like i can do doesnt want me