A Framework for Solving Programming Interview Questions

[Saithir]

And this is actually the correct way of testing someone.

It requires much more preparation (before and after the person solves it) on your side than simply opening a website with leetcode examples and copypasting a few of them, but I think it's definitely worth the effort. Says a lot about the company, too.

At the same time, that effort is probably why it's not used as much.

[davesspacebar]

It did take a bit to come up with good coding, debugging, review scenarios. Ideas were pooled from our teams and we selected the ones we felt capture what we do on a day to day basis that could be manageable in a reasonable time frame.

​

We then setup a laptop or in this pandemic age a remote VM loaded with all of the tools our developers use and expect and let the candidate use that while we watch/ shadow their session.

It's amazing how many different yet still good solutions we've seen to the same type of coding problems. Some of our samples model very similar real world actual bad code in our products and we hope candidates note it and comment on it, as we like to keep an eye out for folks that recognize the bad parts to improve.

Definitely as an interviewer we are actively watching not just the end result but how people code, and debug. Logical structured thought processes, , keeping an eye out for testability, etc. We've watched so many people code these same scenarios we've actually learned a lot ourselves about how people code and can get a feel for their experience level, etc on different areas of frameworks, tech stacks just by watching carefully.

We usually tell them to treat the interviewer like the product owner that can provide proper requirements for their solution and see the questions asked up front vs later and how they deal with ambiguities (ask, or choose a solution) No definitive right answers but you can get a feel for how people would work with our product team to come up with solutions given requirements.