I found out about DealerInspire through FlexJobs, a national web portal for remote and non-traditional positions. I applied in October of 2018 and didn't hear anything until two months later. They are not a fast organization. The interview process is about what one might expect – a first phone screen to ensure you’re not catatonic and can communicate, followed by a video interview to check your technical background. You then get a coding challenge rather than being sent to a service like HackerRank or IKM. The initial phone screen includes questions one might expect from any company – a request to describe your background, why you’re attracted to DealerInspire, what you know about the company, and so on. This usually goes about a half-hour. Most applicants should pass this first milestone. The second step is a tech screen in which you’re quizzed about various technical concepts, both general (e.g. object-oriented programming concepts) and specific (in my case, what I knew about the Android platform). This runs between 45 minutes to an hour, with a little time at the end to ask your own questions. The third step is a coding challenge. It seems that some places, in an attempt to weed out posers, have now gone to asking applicants to write a fully functioning app from start to finish. In my case, the app had to talk to one of two API’s for two major photo sharing platforms and allow the user to manipulate individual files. This required the successful applicant not only to write the app itself, but also to create test data in the form of accounts associated with each platform, and figure out how to make the API’s functional in code. I can say that I got stymied on the API’s mainly because of the arcane OAuth protocol for obtaining a digital certificate. I struggled to make OAuth work, with no success. Without OAuth working I couldn’t get the core API functionality working (accessing sets of images, folders, etc.), so I was toast at that point. That was not the only surprise I encountered. One of the API’s I’d been given to use had been decomissioned for public use – it had been deprecated. There was no way for sure to know that using that platform would have worked and had there been issues, no way to follow up – because it was no longer supported by the provider. The first two interviews won’t likely use up more than a couple of hours. But the coding challenge they created – if you plan on doing it right – may take a couple of days. In summary, be prepared to wait for a first response, and know OAuth. That may get you further than I got.