![]() Sometimes the interviewer hopes to get through chit-chat quickly. If you’re ever worried you’ve lost your interviewer just stop and ask, “Does that make sense?”īe excited yet direct. Practice helps a lot with this–try practicing with a friend or out loud to yourself. When you’re describing something you built, especially a technical challenge you faced, be clear and precise. Have you ever been asked to help debug an issue and been frustrated that the person asking for help couldn’t clearly explain what their code was supposed to do? Your interviewer wants to make sure you won’t be that person. For example, your interviewer may point to a specific project or job on your resume and say “this sounds interesting–tell me about some of the technical challenges you dealt with.” It’s just fine to say “Hmm, nothing comes to mind immediately for that project, but I do have a story about a technical problem from another project.” You can gently steer the conversation towards your more interesting stories (provided they are relevant, of course). Here are some tips for these bits of chit-chat before and after the coding exercises: This shows that you think about how to write code well. ![]() The engineering strategy (testing, Scrum, etc). This shows you’re interested in the company and you’re the kind of person who cares about why they are doing things, which is an important part of ownership. I recommend asking a question about at least one of: Later, after the coding challenges, when the interview is winding down and the interviewer asks if you have any questions, you have a chance to put some icing on the cake. “Tell me about a time you showed leadership or ownership on a project.” What’s something you really like about it? What’s something you’d change about it if you could?” “I see your favorite language is $programming_language. “If you could start $specifc_project over again, what would you do differently?” “Tell me about an interpersonal conflict you overcame.” “Tell me about a time you used a ‘hack’ to save time implementing a feature.” “Tell me about an interesting technical problem you solved.” It’s helpful to have something in mind for each of these standard questions: The questions are often open-ended, so they can catch you off-guard. Would chatting with you about a technical problem be useful or painful? Do you see your work through to completion? Do you fix things that aren’t quite right, even if you don’t have to?Ĭommunication. Many interviewers like to precede the coding challenge with some chit-chat about your previous jobs or projects.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |