The problem CODEPLOY solves

Conducting coding interviews can be tricky business, especially when folks are distributed instead of sitting together in a conference room. Trying to communicate clearly, share code, and collaborate in real-time without good tools tends to get messy. Codeploy offers a friendlier approach.

One major headache Codeploy helps with is actually being able to code complex problems together in real-time during remote interviews. With its synchronized coding pad, multiple people can work on and discuss the same code at once. This creates a dynamic environment where candidates can show their stuff and interviewers can provide instant feedback.

Codeploy also flexes to handle spikes in interviews that happen during peak recruiting seasons. The system can fluidly scale up compute power to keep everything running smoothly for both interviewers and candidates when demand grows.

Communication is handled nicely too with integrated voice and chat features. This way people can talk naturally while coding and clarify anything that needs discussion.

In a nutshell, Codeploy brings easy collaboration, coding, and communication together to modernize clunky old interviewing. Interviewers can engage candidates better while candidates can shine in showing their skills. The end result is more effective and enjoyable for everyone involved.

Challenges we ran into

We used NodeJS for our backend to build fast. But NodeJS does not check types, so a small mistake by us (and lack of sleep) caused big problems.

We also had issues getting versions to match when trying to make things scale on Google Cloud.

We tried using Orkes to connect our few microservices. It fits our plans for the future project. But we hit some problems with Orkes itself. Using Orkes and Conductor would be best as we grow.

In short, going fast led us to pick tools that created issues later when building and launching. For our big idea ahead, using things like Orkes is the way to go.