3 ms·
The story of the problem being solved. Talking through what the expectations are, what you're thinking and what you're doing help cover points where you may ma
by IanCal 3y ago
The story of the problem being solved.
Talking through what the expectations are, what you're thinking and what you're doing help cover points where you may make a mistake and vitally where there's a disconnect with your understanding and theirs.
I've had paper problems to do that to solve the literal problem in front of me would be to write some very short code. But the problem looks like a shrunken version of a bigger system, and so explaining this shows I'm not just over engineering this toy problem I'm showing I understand (this was an early position) classes and inheritance and how to manage that.
Are you asking how I'd build systems to do this kind of thing? Are you asking what I'd do if the boss comes over and says they need this one off thing done asap?
You want to be seen as someone they could actually work with on something.
- bambax 3y agoExactly! Coding challenges are not about miraculously finding the right solution, which is boring (and extremely suspect). They are about describing a path from the problem to the solution, and dangers and pits along the way.
- nitwit005 3y agoGiven that some companies now have candidates do them on fully automated web pages, it's pretty clear they are often just about getting the right solution, and nothing else.
- bambax 3y agoIn that case they are simply trying to filter out the pool of candidates. But there will be a step downstream that involves storytelling.
- nitwit005 3y agoAll job interview steps are "simply trying to filter out the pool of candidates". If it is the filter that removes the most people, that actually makes it the most important part of the interview process.