Very good work/life balance. Market leader. Financial outlook is good. If cons of the sort described below don't bother you, you can have a very successful, stable, stress-free 9-5 job.
Management (in San Francisco at least) has a systemic inability to recognize and correct bad decisions. It seems like they spend most of their time in meetings making excuses so they don't have to take a perceived political hit for making a bad choice, instead of owning it and doing something better.
This influence from the top has made its way into individual hiring decisions, where hiring managers make excuses for candidates and look down on anyone who gives negative interview feedback. This has created an engineering culture where people either blindly do what they're told and code exactly to spec (even if it's the wrong thing for customers and the company), or get frozen out, badmouthed, and belittled for speaking their minds and raising valid concerns.
Add to this a total lack of technical mentorship or career growth opportunities, and I guess what I'm saying is that it's definitely not an engineering-driven culture.
Fail fast, and do the right thing for the company and our customers.
Emphasize technical excellence instead of political savvy.
Take honest feedback in interviews instead of bullying folks into saying yes.
Great people. Great communication. Love the vibe. I hope I get the job. The LeetCode question on binary trees was WTF. It seems like a standard, simple question just to test me on data structures.
30-minute screening call with recruiter 1-hour hiring manager interview (behavioral and tech quiz-like questions) 3-hour virtual onsite (includes 3x 1-hour interviews: DS&A, system design, behavioral)
4 rounds: HR call with some behavioral questions. Coding round: went through one code problem with optimization. System design: designing a system that can handle a big amount of data. Manager round: some behavioral and tech questions.
Great people. Great communication. Love the vibe. I hope I get the job. The LeetCode question on binary trees was WTF. It seems like a standard, simple question just to test me on data structures.
30-minute screening call with recruiter 1-hour hiring manager interview (behavioral and tech quiz-like questions) 3-hour virtual onsite (includes 3x 1-hour interviews: DS&A, system design, behavioral)
4 rounds: HR call with some behavioral questions. Coding round: went through one code problem with optimization. System design: designing a system that can handle a big amount of data. Manager round: some behavioral and tech questions.