You meet with the interviewer over video call and do a brief introduction of yourselves. The interviewer then asks about any interesting projects you've worked on.

Next, you move onto a classic computer science interview coding question, likely sourced from a book or the internet. It was a "move through the board" type question involving a two-dimensional array, one I've encountered at least five times throughout my career.

Normally, I excuse myself from these interviews as I don't want to waste my time or the interviewer's. The outcome can vary significantly depending on my cognitive state that day. However, I decided to proceed for my own amusement.

The interview lasted an hour and a half instead of the scheduled hour. This was because the first 30 minutes were spent debugging the Karat code editor. It was unable to run the code. We eventually discovered that the editor breaks if there are any comments included. I wanted to copy and paste some of my pre-written comments and formulas from the Karat editor into my local text editor for reference, but the interviewer stated that I could only work within the buggy code editor.

Karat is open to feedback on their interview process, and I provided an honest one. They subsequently offered a potential redo due to the editor's issues. I declined, as I did not want to dedicate another hour of my life to these types of "cookie-cutter" interviews.

If you want to pass, study standard coding interview questions (prepare about 10), have the solutions ready in your text editor, and be prepared to copy and paste them. You'll pass with flying colors.

Tell me about one interesting project you've worked on.