Good office perks, interesting coworkers, and solid compensation.
You are very much a small cog in a big machine. It takes forever to ramp up to the codebase.
It was a 1-hour technical phone interview. Questions covered algorithms and certain data structures, such as hash maps. You actually coded with the interviewer on a Google Doc. Ask questions if something is unclear; they want to know that you're thin
I was interviewed for a Software Engineer position. The process involved two phone screens, followed by an on-site interview with five engineers. Everything went extremely well. I solved all the whiteboard coding problems and also tackled a non-codin
It was really good, and I had a really fun time trying to answer their very hard questions. It was a good learning time for me because I felt I could improve.
It was a 1-hour technical phone interview. Questions covered algorithms and certain data structures, such as hash maps. You actually coded with the interviewer on a Google Doc. Ask questions if something is unclear; they want to know that you're thin
I was interviewed for a Software Engineer position. The process involved two phone screens, followed by an on-site interview with five engineers. Everything went extremely well. I solved all the whiteboard coding problems and also tackled a non-codin
It was really good, and I had a really fun time trying to answer their very hard questions. It was a good learning time for me because I felt I could improve.