The interview process began with general discussions. Afterwards information describing a project to build offline was sent, and a follow up technical screen was held to go over the results. The format of the technical discussion was to role play a sales engineer presenting a proof of concept to a customer, after which there would be a Q&A. I had a nearly identical scenario for an interview from a couple of years ago with a few important differences: Previous interview - 1. Most of the work building the POC focused on combining pervasive technologies with a minor portion integrating the proprietary software into the workflow. 2. An expected time required to complete the project was specified in advance. 3. The technical portion of the exercise verified the candidate had the proficiency to fulfill the role, and left learning other detail level product information to be done as needed on the job. The Q&A involved advocating for, and justifying feature level aspects of the product. NextMV interview - 1. The majority of the work building the POC involved learning NextMV specific details. 2. There was no time duration specified for the exercise. 3. The discussion tested knowledge of the NextMV product. Most of the questions in the Q&A were detail level questions about implementing with NextMV's software. Given the above, anyone undertaking this should be prepared to expend/lose time building a POC and gaining additional implementation proficiency specifically with NextMV's software. For any candidates going through this interview process, I suggest finding the expected duration for the project. It will help in providing a level playing field and setting shared expectations. If the time commitment is too high for the candidate, the process can be halted early.