Big engineering challenges but still small enough that individuals can make a real difference.
Surrounded by very talented engineers, designers, and data analysts that will take the time to answer your questions and from whom you can learn.
Management is incredibly transparent and open. Every Friday, there is a public Q&A with the CEO and senior management answering your anonymous questions. Every meeting with more than three people sends out notes so you can see what's going on with the rest of the company.
It's clear at every step that Ben (CEO) really cares about employees and wants them to share in success longer term and enjoy their day at work.
Like any company, there will be non-optimal groups or projects, but it seems pretty easy to switch groups if there is something else you want to do.
I've worked at 4 different startups/tech companies now, and this is by far the best company to work for out of all of them. The perks, culture, and engineering are great, but the opportunities and care for employees are even better.
They are growing very quickly, and you have to be ready to grow yourself as well as upgrade existing solutions that aren't scaling. The foundational changes to scale in raw numbers of users and internationalize the product aren't necessarily appreciated by everyone.
I've read a number of reviews complaining about a lack of engineering rigor, and in my experience, most of the problems they are describing are problems of growth, where the solutions that worked last year don't scale to this year's traffic. This growth leads to legitimate problems and challenges, but they are the kind of problems that you want—much better than the problem of not having any growth in users.
This was my second tech job, and the process was pretty standard. It began with a phone screen via CoderPad with one of their engineers, followed by a full-day onsite interview. The onsite was split between: * Data structures/algorithms * Beha
I was contacted by the University Recruiter. They were very helpful and provided resources for preparing for the technical challenges. The technical code challenge was on Karat.io. It was 4 hours to solve the challenge. I cleared the challenge and
I completed an interview test that had to be done in Python. You can find the question if you Google it, but they give you a week for it, so even if you don't know Python, you can figure it out. Then, I had a phone interview, followed by a full day
This was my second tech job, and the process was pretty standard. It began with a phone screen via CoderPad with one of their engineers, followed by a full-day onsite interview. The onsite was split between: * Data structures/algorithms * Beha
I was contacted by the University Recruiter. They were very helpful and provided resources for preparing for the technical challenges. The technical code challenge was on Karat.io. It was 4 hours to solve the challenge. I cleared the challenge and
I completed an interview test that had to be done in Python. You can find the question if you Google it, but they give you a week for it, so even if you don't know Python, you can figure it out. Then, I had a phone interview, followed by a full day