I applied online after reading the description for a Front-End position that directly matched my skills and years of experience. The recruiter called me, and we had a great conversation about the role. It matched exactly what I've been working on at other companies.

Something that stood out was their emphasis on an interview process that differed from others. They promoted it as being more about learning about your skills rather than solving "crazy PhD type problems."

I completed a tech screen, which was a pair programming interview. I was asked to build a game called Ken-Ken, which I had never heard of before. The interviewer had difficulty explaining the rules and tried to break them down into very small pieces of information.

At times, I felt I was progressing too quickly, thinking too far ahead for the interviewer to keep up. They repeatedly guided me back, asking me to focus on solving just one small part.

The interview was scheduled for an hour, yet they expected me to build a game I'd never encountered with very little description. In a way, this mirrors how work can be, but typically you have more time to design a feature or epic, not just one hour.

It would have been more beneficial if the game was already built but with some missing functions or elements to debug, especially for a Front-End position.

Do you know what Ken-Ken is?

We're going to build Ken-Ken.