Lots of employee perks.
Beautiful office.
Amazing food.
Still a good chunk of smart people remaining at the company, though this is changing quickly.
Coworkers were really nice and generally had strong character.
Zero product direction -- the CEO has had lots of trouble strategically and has effectively stepped back from that role, meaning that no one with power over multiple orgs is steering the company.
High-level goals are dumped at the feet of inexperienced senior managers, who are then responsible for vague product goals ("more collaboration!") and can't translate them into a product roadmap.
Projects are often too safe, and amount to UI tweaks (a giant overhaul of the barely-used website, for example) or moonshot projects with no strategy or go-to-market that eventually die before reaching customers.
A recent de-emphasis on business/sales objectives in favor of shiny consumer toys, despite major strategic pitfalls.
Chart a course more concrete than "collaboration" or "the best place to get work done" -- something that directly translates into a product roadmap with a clear go-to-market and value proposition for customers.
Put customer problems first and business problems second.
The interview process was a coding assessment and a phone screen. The coding assessment was a design question consisting of four parts. It increased in difficulty and involved designing a system to do a certain task.
Phone interview: The question was to find all duplicate files in a file system. Follow-up questions included: * What if files are large? * What if files are small? The interviewer was kind of indifferent.
After the resume screen, the second stage was a coding interview. I was asked one question related to recursion, specifically to find a duplicate file in a filesystem. This was conducted in a browser-based text editor.
The interview process was a coding assessment and a phone screen. The coding assessment was a design question consisting of four parts. It increased in difficulty and involved designing a system to do a certain task.
Phone interview: The question was to find all duplicate files in a file system. Follow-up questions included: * What if files are large? * What if files are small? The interviewer was kind of indifferent.
After the resume screen, the second stage was a coding interview. I was asked one question related to recursion, specifically to find a duplicate file in a filesystem. This was conducted in a browser-based text editor.