I recently did a phone interview with the team at Services and thought it might be wise to recap my experience for future candidates coming down the road. On the introductory call with the CEO was the CTO and the current (and only one) mobile developer. They described a tech stack (or back-end setup) that sounded incredibly mature (or perhaps too-good-to-be-true?) for the company only being in existence since the beginning of 2015, where they use natural language processing to allow bots to guide customers into providing information and answers that humans (the people who are the actual bridges between end users and the companies they have issues with) can then pick up and run with. I never did get too much of an introduction to the mobile app itself, so I don’t know if it’s a simple front end into the web services or if there’s actual processing going on within the app. After the phone interview, they sent me a link to an iOS coding questionnaire which I’ll recap some of which for you below (so you can see what they care about). The exam (hosted on a website) requires the candidate to answer 19 multiple-choice questions within 45 minutes. Officially, you’re not supposed to use the keyboard (the exam supposedly detects it and then locks the candidate out of the exam if the user tries to use the browser to look up anything) and these questions should be answered from memory, so I didn’t feel the test was entirely fair as some of the questions went pretty well beyond iOS fundamentals (i.e. how many iOS devs are going to know off the top of their heads that there are different coordinate systems between UIKit and CoreGraphics) and into esoteric, WTF-do-they-want-their-iOS-dev-to-know-about-this technical trivia territory. I’ve included a few questions (and their multiple choice answers) below, and the rest of the questions included code examples that quizzed the candidate on blocks with potential retain cycles, NSURLConnection running within an NSOperation, Objective-C class inheritance and singletons, GCD and when to show UI (i.e. in the main queue/thread). For myself, despite their extensive (yet vague) FAQ on their site, I kept wondering “how is this company ever going to make money?”. Corporations usually like to keep tight controls on their customer support & CRM set-ups, and disruptors like getservice.com may have a tough time getting traction. Were I seriously considering a job here, I’d be seriously worried about their VC funding having the rug pulled out from under them when the economy goes through a down cycle. Hopefully my experience flunking the Service Technologies interview process will help you to prepare to pass your interviewing day. If you find any of the information in this review helpful, please let me know by voting "Yes" on the "Helpful?" question below (this helps to motivate me to be as detailed as possible).