Glassdoor users rated their interview experience at Pocket Gems as 100% positive with a difficulty rating score of 5 out of 5 (where 5 is the highest level of difficulty). Candidates interviewing for Mobile Engineer and rated their interviews as the hardest, whereas interviews for Mobile Engineer and roles were rated as the easiest.
The hiring process at Pocket Gems takes an average of 42 days when considering 1 user submitted interviews across all job titles. Candidates applying for Mobile Engineer had the quickest hiring process (on average 42 days), whereas Mobile Engineer roles had the slowest hiring process (on average 42 days).
I applied online. I interviewed at Pocket Gems in Mar 2013
Interview
I was given hr interview and two technique phone interview. It really waste a lot of time(One or two month.). The questions are very simple. But the company is really irresponsible. They gave the result of the interview very late(couple days to one week. I even sent an email to the hr ask about the result). They change the date and time of the interview which makes great inconvenient to me. I answer all the questions in the two technique interview correctly. But I can not even get a chance to continue. Thus, I wonder if there is something wrong with this company. I think other candidates should consider carefully when you want to apply this company. It really waste a lot of time for nothing.
I applied through college or university. I interviewed at Pocket Gems in Oct 2013
Interview
Started the interview process from Oct 2013. Asked LCA and some other similar coding questions. Got the offer in Jan 2014, but I was already pursing other interviews at that time.
I applied through college or university. The process took 3 weeks. I interviewed at Pocket Gems (San Francisco, CA) in Feb 2012
Interview
I approached them at my school's career fair. They invited me to have dinner with them that night with a few other candidates. The next day they arranged interviews on campus, which where about 30-45 minutes and consisted of basic programming questions and writing some code on a white board.
Following the on-campus interview they scheduled a phone interview. The phone interview included more basic programming questions and writing some code in a shared Google Doc. It was about 20-30 minutes.
After passing the phone interview they flew me to their office in San Francisco. The interview lasted for seven hours, during which I sat in a conference room as various members of the development team came in and asked me questions. I was offered bathroom and water breaks but no food, nor was I told to bring anything to eat beforehand.
Most of the questions asked me to describe or write code for an algorithm on a whiteboard. Many of the questions were the sort that if you'd happened to learn them in school or seen them somewhere online you'd be able to answer them right away, but if not you were screwed. Not the kind that you could reason through in a few minutes if you'd never seen them before.
The last person to interview me was the lead programmer. I could tell from the minute he walked in that he didn't like me. While writing on the white board he would make comments about the syntax like "What language is that? C++? Because that's not C++." I knew at that point that this was definitely not the place for me (although the seven hours without food being bombarded with interview questions was another hint).
Interview questions [1]
Question 1
Describe how to sort integers read one at a time from an infinite stream.