The architecture of their system is very large and complex, which is equally challenging to navigate and capable of a lot. With that said, it feels very mature compared to the architectures I've worked with at previous companies, and I like it so far. The tech stack is a bit dated, but there are efforts underway to update things.
From a benefits perspective, they are pretty good. They have great parental leave, with a lot of nice resources for parents. 401k, health care, and other basic benefits are all pretty much in line with other places I've worked. Cash bonuses are not offered at the level I'm at, but they do offer RSUs and a very solid base salary.
Complex architecture is a double-edged sword. It's very capable and resilient, but also difficult to get started with. The onboarding process took some time, and I'm still running into issues with various little things.
So far, I don't have any specific gripes to share.
My only real complaints relate to compatibility issues with the M1 chip Mac I was given as a work computer, which is more of a headache than anything.
Stick with x86 systems until the tech stack is updated enough to be fully compatible.
I was interviewed by Grubhub after being contacted by a recruiter. The whole process took 4 weeks. An initial phone screening consisted of a regular LeetCode medium question. The onsite consisted of 4 rounds: a LeetCode question, Java/OOP design, a
Three steps: * Behavioral screen with the recruiter. * Followed by a technical screen with an engineer. * Followed by a virtual onsite with LeetCode-style questions, in addition to system design and behavioral interview rounds.
Among the bad experiences I had: * An interview that started without clear requirements, leading to a perfect solution for the problem, but with incompatible results.
I was interviewed by Grubhub after being contacted by a recruiter. The whole process took 4 weeks. An initial phone screening consisted of a regular LeetCode medium question. The onsite consisted of 4 rounds: a LeetCode question, Java/OOP design, a
Three steps: * Behavioral screen with the recruiter. * Followed by a technical screen with an engineer. * Followed by a virtual onsite with LeetCode-style questions, in addition to system design and behavioral interview rounds.
Among the bad experiences I had: * An interview that started without clear requirements, leading to a perfect solution for the problem, but with incompatible results.