Good benefits and a cool campus.
Decent leadership.
Too much happening. Lots of change, people coming and going. Lots of unreliable teams and services. Lots of migrating from one thing to another instead of developing features.
Stick to one goal long enough that meaningful progress is made, and do not tolerate sub-par products. Expect more from your engineers. If they don't thoroughly document and in an easy-to-read way, get rid of them. The "you shouldn't comment your code" philosophy is killing Expedia.
I took a written test first, and after passing that, I attended their onsite recruiting event. First, I met with recruiters for some time to go over the day's schedule. Then, I met individually with four engineers. They each asked some behavioral que
A recruiter contacted me on LinkedIn, and we quickly jumped on a phone call to discuss the opportunity. I then completed a HackerRank test, after which I was invited for an onsite interview. * 2 technical/coding rounds * 1 design discussion *
I had a recruiter screen, an OA, and then a one-hour interview with the hiring manager. I was informed that I had cleared and would be heading to the virtual onsite round. However, the recruiter then started ghosting for no apparent reason. I tried r
I took a written test first, and after passing that, I attended their onsite recruiting event. First, I met with recruiters for some time to go over the day's schedule. Then, I met individually with four engineers. They each asked some behavioral que
A recruiter contacted me on LinkedIn, and we quickly jumped on a phone call to discuss the opportunity. I then completed a HackerRank test, after which I was invited for an onsite interview. * 2 technical/coding rounds * 1 design discussion *
I had a recruiter screen, an OA, and then a one-hour interview with the hiring manager. I was informed that I had cleared and would be heading to the virtual onsite round. However, the recruiter then started ghosting for no apparent reason. I tried r