Software Engineer applicants have rated the interview process at Cyberscience with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 33.3% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 7 days to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at Cyberscience overall takes an average of 7 days.
Common stages of the interview process at Cyberscience as a Software Engineer according to 2 Glassdoor interviews include:
I applied through a staffing agency. The process took 1 week. I interviewed at Cyberscience in Jul 2019
Interview
Had a skype interview with a lead engineer where I worked on a coding exercise on a shared online editor.
Then we talked more generally about the role, my experience, etc.
Interview questions [1]
Question 1
Create an algorithm to find a named file from the root of a file system.
I applied through a recruiter. I interviewed at Cyberscience
Interview
First, I had a Skype call in which I was asked to do a trivial coding task followed by some less trivial, but still reasonably basic technical questions. This was followed by an on-site interview. At the on-site, I was first shown a demo of their product and this was followed by a coding challenge. The challenge was simple conceptually, but the bulk of it required you to learn how to use an external library to perform some task. You're allowed to use the internet as much as you want, but since the library changed so much over the years none of the code examples online work as they are written (they do warn you about it though). It threw me off-guard as it wasn't a problem solving question and I took longer than expected to complete it. After that I had a talk with the head of their development team and given a tour of the office. All the people were very nice to me.
Interview questions [1]
Question 1
I was asked to learn how to use an external library to perform a fairly simple task. The library changed so much over the years none of the code examples you find online actually work making the task slightly non-trivial.