How are Scala programmers being interviewed? What are the aspects that the interviewer looks for when interviewing a Scala developer?
- Anybody can ask a question
- Anybody can answer
- The best answers are voted up and rise to the top
closed as too broad by MichaelT, Thomas Owens♦ Apr 5 '14 at 11:27
There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question.
First, I would say, think why you need a Scala developer. Is it really Scala that you need? Think about what comes along with Scala (IDE, build tools, libs, another layer of complexity above Java etc ...). Back to the question. It goes in two aspects: Theoretical understanding and practical abilities. don't let the "theory" thing fool you. It's as important in Scala as practicality is important in Java.
Theory and practice mingled
P.S: If you found a good Joe then please by all means let me know as we need some ;)
In a real-world interview, simply knowing Scala is half the battle won. Hiring a good programmer is always difficult, regardless of the language!
Scala programmers tend to come to the language because they were already at the top of their game in Java and wanted to “take it to the next level”.
If you have a plentiful supply of Scala developers available for interview, then consider yourself lucky. If not, the more relevant questions might be “What aspects should I look for in a programmer who I'll be training to use Scala?” and “What companies are currently able to provide training services?”
I like to see solutions to little problems like this: Make a histogram of the outcomes of throwing two six-sided dice 200 times.
See the comments here for some interesting answers: http://briccetti.blogspot.com/2011/01/dice-throw-simulation-in-java-and-scala.html
Someone with a solution like Daniel Sobral’s, or this one from Kevin Wright: http://ideone.com/8LFs3 would be worth a closer look.
If the answer looks like Java code, then the applicant might not be far enough along.
I would also like to see that the person is connected to the Scala community: Knows the books, authors, open source developers, user groups, interesting people.
I have never done any Scala hiring, but I'd look for an understanding of how implicits work, type class pattern, and basics of functional programming.
protected by gnat Apr 5 '14 at 7:57
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?