Skip to contentSkip to footer

Scala Developer Interview Questions

Salaries
Interviews

196 scala developer interview questions shared by candidates

standard interview questions During first stage: The questions are mainly a discuss on what I was looking for and about the role. The interviewer made it clear that it was hands-on. I had made it very clear that I was hands-on. The interviewer then assured me that it was hands-on. I think by this time you would assume the interviewer knew what I was looking for was hands-on scala work. During second stage: 1st interviewer was with data scientists - the person was late by 20-30 mins, did not know difference between svm's kernel svm's and structured svms' but kept going on about it. Asked me a lot of questions unrelated to role. 2nd interviewer was an architect - but kept asking me questions on Java again totally unrelated to role. You would assume person will ask you questions on Scala at this time. But, not a single question was on Scala. In fact, I kept directing to question towards scala trying to put the questions in context to the role of how I had used that language in projects as you would expect in a Scala developer interview. 3rd interviewer was a manager - asked me a lot of contradictory questions like we looking for a hands-on role but just to be clear this not a very hands-on role. Now I am wondering so you said on phone that this was going to be a hands-on role and you still have not asked me any scala questions or spark questions. It is just very pointless when interviewers just want to waste your time. In fact the feedback stated they were looking for a hands-on scala developer. A) which I was and was exactly looking for that which I made it very clear on phone and during the interview with all three interviewers with evidence of projects B) they never bothered to ask me about scala during interview and I kept relating projects towards that.
avatar

Scala Developer

Interviewed at IQVIA

3.7★
Mar 22, 2017

standard interview questions During first stage: The questions are mainly a discuss on what I was looking for and about the role. The interviewer made it clear that it was hands-on. I had made it very clear that I was hands-on. The interviewer then assured me that it was hands-on. I think by this time you would assume the interviewer knew what I was looking for was hands-on scala work. During second stage: 1st interviewer was with data scientists - the person was late by 20-30 mins, did not know difference between svm's kernel svm's and structured svms' but kept going on about it. Asked me a lot of questions unrelated to role. 2nd interviewer was an architect - but kept asking me questions on Java again totally unrelated to role. You would assume person will ask you questions on Scala at this time. But, not a single question was on Scala. In fact, I kept directing to question towards scala trying to put the questions in context to the role of how I had used that language in projects as you would expect in a Scala developer interview. 3rd interviewer was a manager - asked me a lot of contradictory questions like we looking for a hands-on role but just to be clear this not a very hands-on role. Now I am wondering so you said on phone that this was going to be a hands-on role and you still have not asked me any scala questions or spark questions. It is just very pointless when interviewers just want to waste your time. In fact the feedback stated they were looking for a hands-on scala developer. A) which I was and was exactly looking for that which I made it very clear on phone and during the interview with all three interviewers with evidence of projects B) they never bothered to ask me about scala during interview and I kept relating projects towards that.

Got a coding challenge where I was supposed to build an application from scratch. App should receive commands for creating a canvas, drawing lines, rectangles and Bucket fill. I used 1 1/2 day on this. This was apparently not enough since this was the feedback: * readme has design discussions Well, I have to convey my thoughts to you somewhere don’t I? Is that a MAJOR problem? * some validation working * reverse lines/rectangles work * (some) graphical acceptance tests * readme has no run instructions Is that a MAJOR problem? * easy to cause crash with incomplete/invalid commands: 'C' or 'L -1 -1', 'C 10 -1’ Sorry should have tested for negative values, easy to fix in one place. * can't refill or fill lines Is that a MAJOR problem? * test named: '"App" should "have tests"' with implementation: true should === (true) * no test coverage apart from acceptance tests (which don't exercise full set of commands) Is that a MAJOR problem? * control loop logic intermixed with parsing * canvas operations return an array of strings instead of the canvas. Sorry, this is unnecessary since I use toStringArray() later anyway so toStringArray is executed twice. * sealed class with "getters" used instead of case class Is that a MAJOR problem? * no encapsulation of fields or private methods within classes (Canvas/Cell) Obviously these was major concerns. ALL tests should be done and ALL possible errors should be catched. I think is is VERY much to demand for a initial coding challenge. Should you put one week of work to be able to talk to the company?
avatar

Scala Developer

Interviewed at Springer Nature

4★
Sep 5, 2016

Got a coding challenge where I was supposed to build an application from scratch. App should receive commands for creating a canvas, drawing lines, rectangles and Bucket fill. I used 1 1/2 day on this. This was apparently not enough since this was the feedback: * readme has design discussions Well, I have to convey my thoughts to you somewhere don’t I? Is that a MAJOR problem? * some validation working * reverse lines/rectangles work * (some) graphical acceptance tests * readme has no run instructions Is that a MAJOR problem? * easy to cause crash with incomplete/invalid commands: 'C' or 'L -1 -1', 'C 10 -1’ Sorry should have tested for negative values, easy to fix in one place. * can't refill or fill lines Is that a MAJOR problem? * test named: '"App" should "have tests"' with implementation: true should === (true) * no test coverage apart from acceptance tests (which don't exercise full set of commands) Is that a MAJOR problem? * control loop logic intermixed with parsing * canvas operations return an array of strings instead of the canvas. Sorry, this is unnecessary since I use toStringArray() later anyway so toStringArray is executed twice. * sealed class with "getters" used instead of case class Is that a MAJOR problem? * no encapsulation of fields or private methods within classes (Canvas/Cell) Obviously these was major concerns. ALL tests should be done and ALL possible errors should be catched. I think is is VERY much to demand for a initial coding challenge. Should you put one week of work to be able to talk to the company?

Viewing 121 - 130 interview questions

Glassdoor has 196 interview questions and reports from Scala developer interviews. Prepare for your interview. Get hired. Love your job.