Interviewed for a PM role at Two Sigma last quarter. Not for a research-track PM (which I don't think they call PM anyway), but for a product role on the internal tooling and platform side. Sharing because there's very little PM-specific info for Two Sigma out there.
First: Two Sigma doesn't have the same PM culture as a typical consumer tech company. The PM role there is closer to what some places call a technical PM or an enterprise PM. You're not owning a public-facing product with a DAU dashboard. You're working with researchers and engineers on internal systems, data platforms, tools that traders and quants use.
With that framing, here's what the interview actually asked:
Product sense round: Not "design a product for X user group." More like: here's an internal tool with X users and these pain points. How would you prioritize improvements? They gave me actual context on the tool (nothing proprietary, but specific enough). I had to ask clarifying questions before diving in, which they seemed to appreciate.
Analytical round: This was close to a data analysis case. Here's a system metric that degraded over this time period. Walk me through how you'd diagnose it. Needed SQL-level familiarity to talk through the query logic. I didn't write actual queries but I had to know what I'd be pulling.
Behavioral: Fairly standard senior PM behavioral. Projects you owned, cross-functional friction, prioritization calls you made that turned out to be wrong.
Hiring manager conversation: Less structured. My interviewer asked a lot about how I think about working with researchers and quantitative stakeholders. The PM-researcher dynamic there is different than PM-eng in most product companies.
Overall difficulty: harder analytically than most PM loops, lighter on execution/go-to-market stuff (makes sense given the role). If you're coming from consumer product and haven't thought about internal tools, the framing might feel unfamiliar at first.