The phone screen was a basic phone screen covering my experience and the recruiter elaborated on the company. In the first technical interview, we worked on a project, working through some requirements. In the second interview, we built on top of the project working through additional requirements. The last half hour we covered some scenarios where I was asked how I would approach each situation. In both technical interviews I was given designs I was asked to build out
Sent two algorithm problems to solve on Hacker Rank.
Create an algorithm to find the solution of a maze. The starting point could be anywhere inside the maze.
Huffman encoding
There are some general software development questions relevant to the mobile platform such as algorithm, OOP related, how you’d design and architect a mobile app given some hypothetical scenarios. You’d also be asked to work on a starter project and finish it. The questions and sample projects are fairly geared toward the level of proficiency you’re applying for.
Behavioral questions mostly were about my resume, innovation, and why I wanted to work at Clover.
Given a string with various types of parenthesis, check whether they are valid. For example ([]) is valid, but ([)] or ( and such are invalid.
The technical questions covered a wide range of areas which I appreciated. The areas included object oriented design, architecture design, problem-solving/algorithms, objective-c (blocks, view controllers, etc.), and mobile specific questions. The most difficult question I was asked was to design a document upload/fetcher system for mobile (kinda like dropbox for the iphone). The difficulty was really in all the details of the problem (caching, database modeling, security, sessions, etc). Algorithm questions ranged from binary tree search questions to array pattern searching. The most unexpected question was the interviewer gave me a stream of digits and asked me to find the pattern. I got really stumped on this problem, it was my last interview of the day and I just blanked out. I guess I did well enough throughout the day because I got the job. By no means an easy interview, but not extremely hard, I was extremely well prepared as I had been interviewing for a while. Id say its on the average to difficult scale, if you are bad at architecting systems then this interview would have been HIGH diff.
Given a mutable array and index. Output an array that any value smaller than the value of array[index] to the left side. Required optimal solution.
Since this was a software developer position, The over the phone interview questions were standard mainly around the work that I've done in my last positions, my role, things that I'm passionate about, some technical questions around HTTP requests. The in-person interview was very technical. I was asked about the Fizzbuzz challenge, Linked list nodes.
Viewing 401 - 410 interview questions