Nice campus. Smart, capable engineers. Mature technical stack.
This place used to be a highly sought-after employer. Employees were proud to work here, encouraged to architect sound code, and collaborate on proper solutions to achieve success.
Now there is so much pressure on velocity that whoever can hack code the fastest gets rewarded. New features and offers are poorly vetted, rushed through to delivery, and produce disappointing outcomes.
The stack ranking policy that has been implemented recently will surely finish off the good culture and positive morale here.
After listening to the CEO and leadership brag about record company performance this year, we now get to see more terminations and the lowest RSU grants in years.
Using hollow metrics to measure an engineer’s worth will not keep the best talent around.
You can only execute on the stack ranking termination policy so many times before you start cutting into your useful engineers. Very short-sighted, considering how long it takes a new hire to become capable in this ecosystem.
Turn this around before you sour this company’s reputation further.
The process began with a recruiter phone screen focused on my background and interest in the role. Then, I had a technical phone interview where I solved a LeetCode-style medium question using a shared coding editor. After passing that, I was invit
Very well done. The interviewer was very quiet, though, and it took me some time to actually visualize the problem. I also don't think I had enough practice with DP problems in the first place.
The interview process typically began with a recruiter phone screen, followed by a technical phone interview. This led to a 6-hour virtual onsite interview, which included a craft demo and an "about me" presentation covering career highlights and pro
The process began with a recruiter phone screen focused on my background and interest in the role. Then, I had a technical phone interview where I solved a LeetCode-style medium question using a shared coding editor. After passing that, I was invit
Very well done. The interviewer was very quiet, though, and it took me some time to actually visualize the problem. I also don't think I had enough practice with DP problems in the first place.
The interview process typically began with a recruiter phone screen, followed by a technical phone interview. This led to a 6-hour virtual onsite interview, which included a craft demo and an "about me" presentation covering career highlights and pro