TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Scala interview questions

61 pointsby sconxuabout 8 years ago

7 comments

csneekyabout 8 years ago
I think it is very telling about the state of interviews in the tech world when:<p>1. I can NOT off the cuff answer those all correctly (at least not without a little Googling).<p>2. I can, largely off the cuff, implement an IO monad in Scala using higher-kinded types and compose instances of them in a hand rolled non-blocking server.
评论 #14043787 未加载
评论 #14044302 未加载
评论 #14043959 未加载
评论 #14045268 未加载
andrabout 8 years ago
Related: The levels of Scala knowledge, according to Martin Odersky[1]<p>[1] <a href="http:&#x2F;&#x2F;www.scala-lang.org&#x2F;old&#x2F;node&#x2F;8610" rel="nofollow">http:&#x2F;&#x2F;www.scala-lang.org&#x2F;old&#x2F;node&#x2F;8610</a>
评论 #14042853 未加载
mrkgnaoabout 8 years ago
<p><pre><code> lazy val x = { println(&quot;computing x&quot;) 3 } </code></pre> unsafePerformIO, unsafePerformIO everywhere...
jonehollandabout 8 years ago
These are terrible. Not because they don&#x27;t test knowledge of scala, but because language trivia is a terrible way to identify a quality candidate.
评论 #14045282 未加载
评论 #14043754 未加载
pedrorijo91about 8 years ago
Original author here.<p>this post was never a &quot;memorize this and you will know scala&quot; statement, or that if you know those answers you will get a scala job. I simply found those questions a while ago and decided to provide answers by myself as an exercise. I do believe some answers may not be completely right (even completely wrong), and others may be a starter for a nice and productive discussion.<p>Also, knowing the answer to these questions doesn&#x27;t make someone a good&#x2F;better developer. These are just some small islands on the (scala) software developer knowledge!<p>In my opinion these are somehow basic concepts (that will only be valuable when applicable on &#x27;real life&#x27; code), and there is a lot more to explore, specially about the type system. To know more about the type system have a look at this awesome article I found: <a href="http:&#x2F;&#x2F;ktoso.github.io&#x2F;scala-types-of-types&#x2F;" rel="nofollow">http:&#x2F;&#x2F;ktoso.github.io&#x2F;scala-types-of-types&#x2F;</a><p>Unfortunately, these are questions often done in several scala-related job interviews (I had my share. Coincidence or not, I never accepted an offer from a company which did that kind of questions) :(<p>Feel free to provide feedback or discuss some topics.
harveywiabout 8 years ago
Those are generally pretty easy. Now ask me to recite all of the rules of implicit resolution, and I will be stumped. That is probably the only part of the language, other than delimited continuations, that I do not need to know for day to day things.
merbabout 8 years ago
Question two is outdated for Scala 2.12, a trait might be compatible with Java (but doesn&#x27;t need to)
评论 #14046328 未加载