crackingthecodinginterview

[crackingthecodinginterview]

cracking the coding interview pdf 8th edition

Tips for evaluating the coded interview As COVID-19 continues to change the hiring landscape, we partnered with Gayle Laakmann McDowell, author of Cracking the Coding Interview, via LinkedIn Live to discover tips and best practices for remote interviews. The conversation focused on tips for cracking the coding interview pdf 8th edition  developers currently looking for new roles. With more than 3,000 participants tuned in, the audience shared their interview questions remotely, from participating in video interviews to unconsciously browsing and negotiating salaries. Here are the highlights Gayle shared for both job seekers and interviewers:

Preparing for a technical interview seems like a daunting task. But at a high level, there are two rounds you need to be prepared for in a technical interview: Prepare for the problem solving round The first round you should prepare for is a problem-solving round, which generally involves questions about algorithms and data structures. For this round, there are many resources you can practice. You can start with Gayle's book, Cracking the Coding Interview, or try the Interview Prep Kit in the HackerRank community. Gayle also suggests trying the Cracking the Code Interview video series, a series in which Gayle describes key concepts from her book in 5 to 12 minute quick buttons.

Prepare for the system design round The second round you need to prepare for is the system design review. One way to prepare for this round? Gayle suggests calling your developer friends. Take a look at the architectural decisions you had to make to design your final project and see what questions you have about the process. It will help you answer questions that you may receive from an interviewer during the system design round.

Think carefully about languages And when it comes to languages: try not to stick to just one language. Instead, plan to enter the interview by focusing on one or two languages ​​that you already know well. As a backup, plan to have a few other familiar options in your back pocket. It does not matter to some extent what language you master (eg the stigma of some of them against .NET). But instead of focusing on what you already know, in the interview, it is important to remember that you can continue to learn more languages ​​over time. Don't identify yourself by the languages ​​you are most familiar with, such as calling yourself a Java engineer. If there is a gap in your language skills, make it clear that you should be able to add any language to your arsenal, for a month. As you move from a scene to a virtual interview, some biases may be removed from the interview equation (for example, body language, clothing, and the like). But in a remote interview, new biased factors can also be applied, such as your work from home, family life or contextual cues of your origin. Candidates: Think about the background of the interview. For candidates, Gayle recommends setting up a professional training or trying virtual training: if your personal environment is not professional, a virtual training is recommended. Sit in a quiet place, get a good microphone, and be sure to inform your family members or roommates that you will not be available during the interview period.

Employers: identification and mitigation of bias factors As for employers, Gayle says companies need to be diligent to eliminate bias as much as possible at this stage. She recommends that employers test video interviews to eliminate biased visual cues. And no matter what: be kind, considerate, and empathetic. Interruptions will occur as children in the background, but should not be charged against the candidate. Note that silence is almost less comfortable than in person. Be sensitive to this discomfort and don't be afraid of a long pause. Candidates may need time to formulate their ideas,   and video delays may indicate that their responses are coming in more slowly than they would in a personal setting.