2 ms·
Funny enough, my curent position did not give me a coding interview. Rather they asked difficult technical questions about the technologies I used, and asked me
by icepat 3y ago
Funny enough, my curent position did not give me a coding interview. Rather they asked difficult technical questions about the technologies I used, and asked me to justify my use of them. I found this was a far better test, because coding out an algorithm is something you can just memorise.
Example: "You've used k8s, how and in what context?" "Ok, great, so you've AWS EC2 instances, how did you manage cost and performance there?" "You're listing Clojure here, what were your thoughts on X feature/limitation"? It was a rather fluid discussion about the ins and outs of technologies, stacks by engineers.
Sometimes actually interrogating someone's knowledge of a system works just as well. I code a lot of things slowly, and need to think through my designs with a pad of paper. I really can't do it when someone is hovering over my shoulder.
- kokizzu5 3y agosame here '__') last 2 was easy 1 time interview "given this architecture diagram, what you would do if you have to debug/explain to junior how to debug a problem with this sympthom" or "how you would design an architecture with this kind of requirement" oh but there's 1 coding challenge, just simple date addition/subtraction tho