Challenging problems at scale. A lot of learning everyday, both systems and algorithms.
Sometimes too fast-paced, and mediocre work gets into production.
I had two phone screens, which were fairly simple. They asked questions such as: * What are the fundamentals of OOP? * What is the difference between OOP and scripting languages like PHP? Then, I went in for the on-site interview, which was all day
Applied at a career fair and received a phone interview. I was asked about basic concepts in Java and databases. A couple of weeks later, I went for an onsite interview, which consisted of four interviews: * The first interviewer asked about fin
Two technical phone screenings. One day onsite included three interviews: * The first two were technical. * The third was behavioral. Heard back within two days, a very fast turnaround. Recruiters were very nice and helpful.
I had two phone screens, which were fairly simple. They asked questions such as: * What are the fundamentals of OOP? * What is the difference between OOP and scripting languages like PHP? Then, I went in for the on-site interview, which was all day
Applied at a career fair and received a phone interview. I was asked about basic concepts in Java and databases. A couple of weeks later, I went for an onsite interview, which consisted of four interviews: * The first interviewer asked about fin
Two technical phone screenings. One day onsite included three interviews: * The first two were technical. * The third was behavioral. Heard back within two days, a very fast turnaround. Recruiters were very nice and helpful.