Fairly straightforward interview. An exercise to build a meter reading application. Paired with two people. Asked questions when I didn't understand something and explained my thought process. Previous steps of the interview included calls on the phone with recruiter and then with an engineer. Last but not least after the pairing exercise, had an interview with the head of engineering. Overall a straight forward process and quick turn around.
I applied through a recruiter. The process took 2 weeks. I interviewed at RVU
Interview
About 4.5 hours in total of initial screening, pairing exercise, tech Q&A, culture fit and CTO interviews. Thorough but exhausting process, especially when squeezed in with interviews elsewhere. Ran dangerously low on questions to ask by the time it got to the CTO interview.
In the pairing exercise, you're given some data and instructions, working through the steps with 2 of their engineers in whatever language/IDE you desire. In lieu of the pairing exercise, you can opt for a take-home test. The rest of the stages were as expected - a good chance for a conversation about the company, upcoming goals and how/where you'd fit in.
Interview questions [1]
Question 1
What would you be disappointed to see within 30 days of working here?
I applied through a recruiter. The process took 1 week. I interviewed at RVU (London, England) in Nov 2020
Interview
1. Interview with the recruiter
2. Interview with a tech lead
3. Tech test
The tech test is quite difficult and takes a lot of time. It is basically 3 pdf pages explaining it, I shared it with a few of my senior engineers' friends and no one could understand it after 3 readings so they gave up. I spent hours to understand it and to get the calculations right. I completed and sent it. Days later, the recruiter gave me really negative feedback making notes that had nothing to do with my tech test, so I questioned it and found out that the recruiter did not share my tech test but a different one(I could have lost this job for this if my test was up to their standards). They reviewed my test days later and I was then rejected but with reasonable feedback this time actually related to my code. In order to improve my own technical approach to problems, I asked nicely for an example of a good test, I have been ignored by the recruiter ever since.
Interview questions [1]
Question 1
General questions about architecture, integration, technical background etc..
Hi there - thanks for your review. We're really sorry for the initial mix up with your code test. Joe Miller has tried to reach out to you to discuss your second point regarding an example of a good test. Please feel free to email me on nick.hodgson@rvu.co.uk or Joe and we can try to set up a time to discuss. Thanks again.