Jay Parikh
16 statements across 1 episodes · 7 bullish · 4 bearish · 1 people on the record · first statement Aug 27, 2026 by Jay Parikh · across every show →
On the record as a speaker too: Jay Parikh's record, appearances and statements → this page counts the times other people say the name.
Everything said about Jay Parikh, oldest first
Aug 27, 2026 negative
Dictating granular OKRs prevents engineering teams from thinking independently
“If you're, as an engineering leader, dictating, like, all of the 1051 OKRs for the team, then the team doesn't think on its own. So you've got to come with the right level of that abstraction of the strategy division, the North Star, or kind of maybe the Highe…”
Aug 27, 2026 positive
Parikh demands teams escalate 24-hour blockers directly to him, bypassing managers
“If you get stuck for more than 24 hours in anything that you're doing, you call me, right? Because I don't want this to be like, oh, we have to talk to our manager who talks to their manager who then comes to me two weeks later.”
Aug 27, 2026 positive
Parikh pushed Zuckerberg to prioritize engineering efficiency over pure product features
“You know, I remember talking to Mark and Mark was like, yeah, we can, you know, we have money, so we should just build features and we should put all the engineers working on product. And I said, cool, but I'm going to work on efficiency because I'm not going …”
Aug 27, 2026
Scaling organizations traverse their learning loops at slower speeds
“As an organization gets more people, as it gets more successful, it tends to be that, that, that circle, the diameter gets bigger, and you traverse that circle slower, right, and every kind of revolution around the circle is kind of one unit of learning, and t…”
Aug 27, 2026 negative
Aug 27, 2026 neutral
Off-the-shelf infrastructure could not match Facebook's massive scaling requirements
“When I got to Facebook, we weren't building our own data centers, we weren't building our own hardware, we weren't laying around subsea cables, and, you know, those types of things, but over the years, as we saw, one, kind of the scale that we needed to operat…”
Aug 27, 2026 negative
Assigning large teams to new external senior hires causes 'organ rejection'
“We oftentimes make such a tragic mistake. You go out there and spend all this time and money to hire great people, and then you're like, they want here, you know, here's like a team of X hundred people, you know, go for it. And then there's all sorts of like, …”
Aug 27, 2026
Microsoft CoreAI runs manager-free 'brain trusts' of individual contributors
“One of the things that I do at Microsoft is I have these brain trusts. And they're in different parts of our stack, and these brain trusts are formulated with, like, six to eight senior ICs, mid-level ICs only, and no managers, right?”
Aug 27, 2026 positive
Even multi-year engineering projects must show quantifiable weekly progress
“And you can have big, that type of products or projects that may take a year or two to actually materialize, but you need to demonstrate week over week progress, right? And that is going to be something that is objective, quantifiable, that you're looking at h…”
Aug 27, 2026 positive
Parikh: Infrastructure teams must share fate and accountability with product teams
“If our part worked, and the product piece didn't work, then, like, we still failed. So, those teams had to be fused together, and it was sort of a shared fate. I had no tolerance for this, like, hey, just because you're in infra, you don't need to care about, …”
Aug 27, 2026 positive
Parikh: Facebook scaled deployment from daily to continuous release cadence
“When I was at Facebook, when I joined, we did, which was like, really fast at the time. We used to ship The main core of Facebook once a day, and it was like a Herculean effort that, you know, most of the time went okay, but sometimes it didn't go okay, and, b…”
Aug 27, 2026
Microsoft CoreAI tracks engineering focus time via internal quantitative dashboards
“I'd say there's like a set of data that needs to be collected, and it's what we did when I joined and we created this core AI team, right? Which is, first of all, get both qualitative and quantitative data in terms of what is going on in terms of like that pac…”
Aug 27, 2026 positive
Parikh: Major bets must span multiple teams to find global maxima
“Generally speaking, they should be cross-functional in nature, because if it's just a single team with some discontinuous thing, they may be seeking a local maxima, but you may be closing off a global maxima. So I push to have these big bets span multiple team…”
Aug 27, 2026 neutral
Facebook's infrastructure team controversially managed software up through the mobile stack
“At Facebook, the infrastructure team was not just the hardware. It was all of the software. And we actually went quite a bit up the stack to the end consumed, right? So The, a lot of the mobile stack even, in fact, was like run by the infrastructure team, righ…”
Aug 27, 2026 negative
Operational engineering toil stems from a leadership culture of learned helplessness
“The cause actually is Having built an organization and a leadership that has an ethos of maybe learned helplessness, where, hey, I can't do that, or hey, we would fix that if we had more people, or I could do this if we could, you know, like there's a lot of t…”
Aug 27, 2026 positive
Running competing technical bets in parallel resolves uncertainty and accelerates learning
“If I can do both and learn faster, versus do one, fail at it, and then do something else after that, and that takes me four months to figure that out, versus doing two in parallel, and I learn in two months what I would have done in four, that is like a trade …”