3 ms·
> You can't make that mistake in production. They were right to fail you. shrug I kinda agree, sorta. It's certainly not what I would imagine is the intent of
by wyldfire 10y ago
> You can't make that mistake in production. They were right to fail you.
shrug I kinda agree, sorta. It's certainly not what I would imagine is the intent of the test. But I definitely made it so I could not complete the test objectives.
> But you can't overlook a mistake like that.
I dunno, would you fire me if I'd done it at Amazon? Seems like a simple recovery. Note that the position I was interviewing for was not a support or sysadmin job. I'm a design engineer. I'd have been designing the tests most likely! I even imagined how I could spin it into a feature I could work on to recover/reset the system, scoring that event however they deemed appropriate.
Where I've worked, if anyone ever bork'd a system you reload it and move on. We're not supporting customers, so there's never any discipline that would result. The worst you could do is brick a $1-2k devboard or a limited-run early prototype production unit. The latter could cause delays but it's always chalked up to mistakes and that's why they build more than one prototype.
- quesera 10y agoWell of course I'm coming from my own context, where remote mission critical servers are the norm. The problem is that the mistake you made was not knowing your tools, and being careless. That can't be an acceptable combination. On the other hand, automated grading is useless, and your role might never involve the same concerns about recoverability. It's a big industry, but in my little corner of it, a person who locked themselves out of root during an interview would be very hard to support in a hiring meeting.