In-office perks are good.
Colleagues (ICs) are friendly to work with.
Honestly, really terrible upper management across product and engineering. Poor decision-making in launching new products: not waiting for data and constantly trying to go "all in" on shiny new projects that haven't proven themselves yet.
The consequence is constant churn of engineering resources, a build-up of tech debt, poor WLB, and no good product to show for all of it.
Additionally, upper leadership in engineering, instead of pushing back on product themselves and evaluating whether product initiatives make sense, shifts this accountability to ICs. This is inefficient and doesn't make sense at all. Also, as part of this, performance evals have gotten stricter. Despite the public stance of no quotas for PIP, there actually are quotas during calibration discussions. Most engineering teams are underwater and unhappy.
For product leadership:
Dream big, but be smarter about failing fast and set reasonable expectations.
For engineering leadership (management specifically, not senior ICs):
Start taking more accountability and responsibility for decisions on what makes sense for product roadmaps. Stop shifting this to ICs to decide for you and blaming them for not "properly pushing back on product." This is a waste of time for ICs.
Also, stop lying publicly about performance review quotas.
It was a very standard interview. I aced the interview questions, as the interviewers ran out of them. Ultimately, I didn't get an offer because the projects I mentioned to one of the interviewers were too old, according to the recruiter. You coul
The interview process involved three phone screens, followed by five onsite technical rounds. The interview panel at the Bangalore office appeared bored, disinterested, and strangely full of ego. The most amusing part was the interview with the hir
Recruiter called. They were very professional. Phone screen: 2 questions. Onsite: 6 rounds. * 2 technical coding rounds (one basic question about merging intervals, the other about trees) * 1 design interview * 1 craftsmanship interview *
It was a very standard interview. I aced the interview questions, as the interviewers ran out of them. Ultimately, I didn't get an offer because the projects I mentioned to one of the interviewers were too old, according to the recruiter. You coul
The interview process involved three phone screens, followed by five onsite technical rounds. The interview panel at the Bangalore office appeared bored, disinterested, and strangely full of ego. The most amusing part was the interview with the hir
Recruiter called. They were very professional. Phone screen: 2 questions. Onsite: 6 rounds. * 2 technical coding rounds (one basic question about merging intervals, the other about trees) * 1 design interview * 1 craftsmanship interview *