What was the scope of their involvement?
We had two engineers working for us. One was primarily focused on reorganizing our AWS services to be more container-based, versus having individualized machines for every service. The second one was helping us build new services and going through existing ones—they’re all Java-based—and integrating them into a runtime dashboard, which we put on a TV monitor in our office. This lets us see the application health statistics.
We’ve also had people working our ad software development kits (SDKs) and other small projects. Our SDK is primarily C++ and had to be integrated with iOS and Java for Android. They were responsible for writing the adapters into the actual platform.
In terms of initial requirements, it was different for everyone. The AWS guy liked abstract conversation, so I allowed him to pitch how he wanted to remodel the app, and then let him work. The other backend engineer was preferred two-way conversation, laying out the specs, and reviewing the code. He suggested some changes, like a big data processing idea using Apache Spark analytics, and we’d see some test data.
What is the team composition?
We’ve had two consistently work for us, and then we’ve had two others for between four and six months. There was also a UX designer for a month or two.
How did you come to work with AVRspot?
We had another team out of Romania, but they didn’t work out. AVRspot was recommended to us by one of our investors, and I was introduced to Andrew, the CEO.
How much have you invested with them?
They bill in a flat rate, which, for us, was $150,000—$160,000.
What is the status of this engagement?
We worked together from September 2017 until August 2018.