I applied online. I interviewed at Keona Health in Sept 2020
Interview
There was a reasonably easy questionnaire as the first stage which was followed by a 30-min phone interview with four developers, including the technical lead and two senior devs.
I was asked to give my sales pitch and was then asked to rate my ability with a number of relevant technologies, accompanied by technical questions. I was also asked questions regarding older technologies that I had not used in a long time and could not recall in detail.
I did not feel like the interviewers did a great job of evaluating my expertise, but I take responsibility for not being better prepared to impress, and I understand why they chose not to move forward. I do not have a razor-sharp memory for minutiae, and have become accustomed to quickly searching online whenever I need a refresher on details I've forgotten, but this doesn't bode well for an interview. It would have been better to book up.
The most disappointing aspect of the process, however, and the reason I'm writing this review, was the lack of follow-up communication. I was told during the interview that I would hear either way by the end of the week, but I was completely ghosted, even though I sent a couple follow-up emails and specifically asked for clarification. A simple "Thank you but we have moved forward with a different candidate" would have been sufficient. Even better would have been a brief statement of what they felt I could improve on. Hopefully they will improve this in the future.
Interview questions [1]
Question 1
Q: Explain the generations of garbage collection in .Net.
I applied online. The process took 4 weeks. I interviewed at Keona Health in Sept 2020
Interview
1st - Sent an exercise to complete. Write some code (SQL, C#, JavaScript) not too tough. Also includes a few open-ended questions about project architecture and strategies.
2nd - Phone meeting with team. Some get to know you questions and some technical ones. All fair and pretty basic concepts (reference vs. value type, OOP concepts, Promises in JavaScript, etc.)
3rd - Live coding exercise, asked to write C# on a group video share using a plain text-editor (no IDE).
Decline to move forward to 3rd step. In my career I've never once had to, or been asked to write C# code in a plain text editor. Not sure what this would prove other than that the candidate has great muscle memory. I'm sure there was some utility to it but the idea seemed unhelpful to me in evaluating a candidate.
Also, they take a long time to respond to emails. Even after completing the exercise and being asked to participate in a 30 minute phone interview (2nd phase) it took two weeks to fix a time and I had to send three follow-up emails to see if they even wanted to meet still.
Asked for my availability for the 3rd phase. Sent some times but never heard back. Decided based on that and the nature of the 3rd phase to pass.
Interview questions [6]
Question 1
Name one event in the ASP.NET Webforms page lifecycle.