Cool benefits:
Sometimes our goals are too aggressive, and we end up sacrificing quality for ship time.
Experiencing growing pains, which are the cause of some organizational issues and underdeveloped engineering conventions/documentation.
Sometimes it feels like we need to pull long hours because of our aggressive goals. However, I also just really like working on Pokemon Go, so that's also a factor.
From what I've heard, experience varies quite a bit from team to team, with perception of cost center versus profit center.
Despite our efforts towards transparency, we are not fully transparent, e.g., about upcoming project codenames.
Meetings can sometimes feel a bit pointless for some attendees.
Much support up to the interview, and the interviewer was kind and thoughtful throughout. Asking extra questions to assist in making the interview a smooth process. Questions were light for the first round, and the second consisted of a live code int
Technical screening phone call: * Directly coding question * Two Sum * LRU They prefer Python, but other languages are acceptable. No behavioral or general questions. Positive feedback moves to the next stage.
Reasonable for a tech interview. The interviewers were technically competent and very interested in hearing my take on a range of issues. They really didn't ask me that many questions about sorting!
Much support up to the interview, and the interviewer was kind and thoughtful throughout. Asking extra questions to assist in making the interview a smooth process. Questions were light for the first round, and the second consisted of a live code int
Technical screening phone call: * Directly coding question * Two Sum * LRU They prefer Python, but other languages are acceptable. No behavioral or general questions. Positive feedback moves to the next stage.
Reasonable for a tech interview. The interviewers were technically competent and very interested in hearing my take on a range of issues. They really didn't ask me that many questions about sorting!