|
I think you already have enough technical skill to be a good engineer. Like others and even yourself have said, the problem is the interview. What kind of post-mortem are you doing? Are there particular types of questions that give you more trouble, e.g. tree traversal, recursion, bit math, data structures, OOP concepts/design. If you're having a hard time figuring out what algorithm or data structure to use, you may have to get more familiar with common algorithms, like graph traversal, BFS/DFS, recursion, etc. Once you know the basic algos and data structures, they become your tools and building blocks to solve a problem. If speed is your issue, you'll need to practice solving problems to train your intuition to come up with working solutions quicker. You will start to recognize problem types and the algo and data structure to use. Also, being familiar with common data structures like lists, arrays, hash maps, trees and graphs is essential. Know their runtime and space complexities, so you can know when to use what. Sites like hackerrank are good places to get practice questions. Hope this helps. |