interview-questions | Interview questions from multiple tech companies | Pub Sub library

interview-questions is a Python library typically used in Messaging, Pub Sub, MongoDB, Kafka, Example Codes applications. interview-questions has no bugs, it has no vulnerabilities and it has low support. However interview-questions build file is not available. You can download it from GitHub.

Job interviews sometimes can be a daunting task. Especially when you're confronted with those problems with algorithms and data structures. I'm sure you've been through a lot when you were in school. Linked lists, binary trees, directed acyclic graphs, hash maps, greedy algorithm, divide and conquer, dynamic programming, depth-first search, breadth-first search, and all those good stuff. Not to mention space and time complexity analysis. Even though computer science classes were a pain in the ***, somehow you managed to complete them all and made your friends and family proud of you. You will definitely remember all those all-nighter days with your classmates trying to build a compiler, a file system, and a network router. It was traumatizing. You realized you can push yourself much further than you thought possible. Even with years of hard work, you probably wouldn't claim yourself as a master of computer science, because you know there is much more to be learned. But at least you had some level of confidence that you understand the fundamentals of computer science. Soon after you got yourself a job as a software engineer. You started building awesome stuff. Years have passed by, and things got rusty. Even though you were writing code on a daily basis, you weren't always concerned with implementing algorithms and data structures yourself. In many cases, you were working on the top of some libraries and frameworks to get things done. More years have passed by, and you started thinking about taking a different set of challenges outside your company. You started responding to recruiting messages on LinkedIn that you have been ignoring. Writing a new resume, phone screening, and online coding tests are usual hurdles to jump over. Then here we go. You made all the way through the final round of your hiring process and you were invited to an on-site interview. You are standing in front of a big whiteboard. Your interviewer is asking you to write some code to merge two lists of sorted integers. It is supposed to be an easy problem, but writing code on a whiteboard without syntax highlighting, without auto-complete, without any assistance from a compiler or an interpreter whatsoever is a completely different experience when compared to writing code with a highly advanced integrated development environment (IDE) that reads your mind to write as much as half of the code on your behalf. I recently had serveral job interviews with different companies. Some interviews went well, others were a bit more challenging than they are supposed to be. I've got a few offers and one rejection so far. Some are still in progress and one of them is highly likely going to turn out as a rejection. I was very lucky that one of the companies that I had an interview with gave me detailed feedback. They shared comments from each of the four interviewers, which is very unusual. In essence, they had a positive evaluation of the behavioral interview (communication skills, personality, cultural fit, leadership, etc.) and the system design interview (designing scalable systems at extreme sizes), but they had some doubts about my coding abilities. Regardless of the outcome, I sincerely appreciate that kind of feedback. That's what keeps me moving forward. It's okay to fail. It's okay to make mistakes. As Dr. Hong said, you can't always win, but you can always learn. I've created this repository in an attempt to learn from mistakes.