Some really smart co-workers (who got cut in a brutal layoff), and there is always something to learn from them.
Free food (less and less offered every day).
Lipstick on a pig. It looks fine on the surface, but there are lots of politics underneath. This is especially true in very large teams where 20 people might report to one manager.
Expect zero transparency from the rest of the company, especially the leadership. Since this has already been the norm for so many years, I highly doubt this culture will change once we all finally move to the "new, centralized" office in Santa Monica. This also means you might not know if a cut is coming until the day it comes. Surprise!
I saw a lot of good engineers get laid off just because they were not part of their managers' favorite cliques. These poor folks then get labeled as 'poor performers'. This is what the company has evolved to over the years.
Beware of any folks who might be joining now just because of the tempting new vesting schedule (25-25-25-25). There might be more layoffs coming up. Some folks were cut this time right before their vesting date, just to save the company some money. Smart move by Snap to break even!
Sinking Ship? Management should jump off themselves.
Maybe Evan, Imran, et al should reinvest their $698+ million executive bonuses back into the "troubled" company.
The interview included two graphs, similar to a course schedule. It wasn't too bad. The style was a mix of technical and behavioral questions. Just be sure to study the graphs a lot and be able to express your experience, and you should be fine.
Two coding interviews on separate days, with a bit of light behavioral at the beginning. No OA. There might be an additional person on the call just watching you, which I thought was weird.
I had a one-hour session with an interviewer. They asked me a couple of background questions about myself and graphics. Then, there was a C++ coding round, which lasted only for the last 15 minutes. However, the interviewer generously gave me an ex
The interview included two graphs, similar to a course schedule. It wasn't too bad. The style was a mix of technical and behavioral questions. Just be sure to study the graphs a lot and be able to express your experience, and you should be fine.
Two coding interviews on separate days, with a bit of light behavioral at the beginning. No OA. There might be an additional person on the call just watching you, which I thought was weird.
I had a one-hour session with an interviewer. They asked me a couple of background questions about myself and graphics. Then, there was a C++ coding round, which lasted only for the last 15 minutes. However, the interviewer generously gave me an ex