This is my personal opinion here, but those don't sound like questions I would give an entry-level fresh graduate applying for a job at my company. Or, if I did give them, I would not be looking for very in-depth or insightful answers. Because, you're right -- design jobs/tasks are generally given after a person has a lot of experience in the professional world. No one in their right mind would plop down a new grad in a new job and tell them to go design a distributed archiving and indexing system.
I personally cannot recommend any really good design books. I haven't run across one. I'd actually be really curious if someone in this sub knows of one, but I also wouldn't be surprised if it didn't exist because design considerations are often very specific to the type of application, the expected results/features, the tech stack chosen, the environment, the industry, etc. I would expect a mid level or senior candidate to come in to an interview and be able to impress me with their design skills (giving me a robust, adaptable, resilient system design) without having read a book telling them exactly how to do it. In fact, a major difference marker between entry-level and higher-experience candidates is their design skills, because they generally need to be learned from experience.
Read full article from Is there an equivalent of the "Cracking the Coding Interview" kind of book for system design / testing interviews? : cscareerquestions
No comments:
Post a Comment