Has some deep flaws, but generally a rewarding place to work with lots of potential.
Generally unimpressed with engineering/product middle management (e.g., director level/VP level).
Also, engineering VPs and CTOs are MIA to the lower levels.
R&D reorgs literally every quarter lead to a general sense of inefficiency, disorder, and lack of confidence that middle management can make up its mind and know what it's doing. Yes, we are adapting quickly as we learn more about the market, but the number of reorgs and product/management turnover is excessive. It's pretty common to have 3-4 different managers within the first 1.5 years of working here; that can't be efficient.
Middle management is very upwards-facing. Historically, they care more about delivering and showing execs flashy new features without substance, rather than doubling down and investing time into tech debt, making sure core functionality is reliable, and improving IC well-being.
This is getting better overall though, after several implosions with products failing to deliver core advertised functionality (that led to huge burnout and attrition).
An IC's overall experience and happiness is almost entirely team-based. Engineering managers can make or break your experience. What does this say about what middle managers are doing to lead and manage R&D culture?
Benefits could be better, especially accounting for all the new expenses employees are incurring after the prolonged WFH.
There's no makeup for lost transportation benefits, catered food, etc.
The layoff in 2020 is obviously a source of unhappiness, but also the lack of transparency around how those decisions were made.
Apparently, engineering managers/directors weren't consulted, and productivity "metrics" weren't used either. Some part of this must not be true because they definitely didn't pick people at random.
Continue to focus on investing in core functionality rather than flashy, unused, incomplete features that looked good on Figma.
Product and leadership need to define better mission statements and goals for each team rather than jumping from one flashy thing to another. Also, maybe take more time to develop next-gen hardware that does what it's intended to. It's not a good sign when the dev team hears about a new device version and jokes that it won't solve any new problems.
Invest more in the health and happiness of ICs, which also comes as a byproduct of having focused teams that are organized and feel productive. Investment in core functionality ensures that emergencies and burnouts are less common.
ICs don't really feel cared for by middle and upper management. Management chases dollars over employee happiness with not much balance.
They were awesome! A recruiter contacted me via Jumpstart. I then completed a coding challenge and had my screen interview, which involved a technical problem. My interviewer was great, and it was one of my best interviews.
Tough and difficult to some extent, which might make one doubt their ability to answer the questions. Practicing for a long time can get you up to speed and increase your chances of getting hired.
HackerRank Phone Screen: Super Day Super Day was kind of odd. They wined and dined you on Friday night by taking you out on a boat, then interviewed you on a Saturday. The Super Day itself consisted of three rounds: * One debugging * A CoderPad
They were awesome! A recruiter contacted me via Jumpstart. I then completed a coding challenge and had my screen interview, which involved a technical problem. My interviewer was great, and it was one of my best interviews.
Tough and difficult to some extent, which might make one doubt their ability to answer the questions. Practicing for a long time can get you up to speed and increase your chances of getting hired.
HackerRank Phone Screen: Super Day Super Day was kind of odd. They wined and dined you on Friday night by taking you out on a boat, then interviewed you on a Saturday. The Super Day itself consisted of three rounds: * One debugging * A CoderPad