There's always more than one way to solve a problem.

Explain any shortcuts you took due to time constraints along with what you would normally do under similar circumstances. Don't add superfluous flow control or unused variables. Include comments for anything that warrants it. Clean-up things as you change your mind about implementation ideas. Pretend the code in the interview is going into production. Keep best practices in mind and try to stick to them in the code you produce in the interview.ĭebug! Good debugging skills and the use of print statements are a good thing. We like engineers who compile and fix often. Iterate, break the problem up and run your code every couple of minutes - compiler errors are part of the job so you don’t lose points for them. We're looking to see how you'd be as a teammate and we want to know how you vocalize your thoughts & approach. Talk us through your thought process and why you’re doing what you’re doing. Even if you think you do know them already, consider preparing for the interview by studying API docs beforehand. If you've done a lot of Java development for years, you should know commonly used libraries, such as the Java Collections Framework.

You are welcome to code in the language you are most comfortable with. We do not ask trick questions or try to trip you up.

All questions are rooted in both algorithms and real world production.

Signal messenger interview