TLDRocket
Sign in

Inside Sakana AI's Product Team

Sakana AI

Sakana AI laid out how its product team works, from office habits to who gets hired. The big surprise: engineers get wide room to move, but the team still runs tightly on-site.

Based on reporting by Sakana AI — read the original for the full story.

Summary, retelling and take written by AI under human oversight; images are AI-generated illustrations. How we work · Report an error

Sakana AI has opened up the curtain on its Product Team, the group that takes research output and turns it into products. The company says the piece is based on interviews with team members and on the questions candidates keep asking during hiring. It reads less like a glossy recruitment page and more like a map of how the team actually works.

The team is broad by design. As of September 2026, it includes product managers, engineers, designers and sales, with a mix of nationalities. Face-to-face work is encouraged, and many people are in the office most of the week, but the schedule is flexible. There are no core hours. The standard day is 10:00 to 19:00, though some people show up around 11:00 or 12:00 and leave near 17:00. Remote work is possible, but the company makes clear that anyone working that way has to fill in the information gaps themselves.

That same mix of structure and freedom runs through the rest of the team. The all-hands Product Team meeting now happens about once a month. Individual product groups set their own rhythm, with some doing daily syncs and others weekly retrospectives. Separate meetings cover KPIs and progress with Sota, the Head of Product, and there are also sessions with CEO David to talk product direction.

The roles themselves are deliberately wide. Engineers are expected to handle everything from infrastructure and application code to monitoring, QA, testing, data governance, security and stakeholder communication. Sakana says it has relatively few software engineers for the number of products it runs, so the environment may suit people who like working broadly across the stack. Applied Research Engineers on the Product Team focus on general-purpose products for a wide user base, while their counterparts on the Applied Team tailor systems to specific customers.

Sakana is also leaning hard into a collaborative model between research and product. The research team creates the core technology, but the product team may customize it, and the research team may work directly on products too. When a product looks useful for a customer problem, the Applied Team comes in to customize it further. The company wants the Product Team to build general tools and the Applied Team to turn them into something more distinctive for each client.

Hiring is shaped around that same reality. Sakana says it looks for people who can judge quickly across competing constraints like accuracy, latency, cost and UI/UX, and who can design useful evaluations instead of just solving tasks. It also wants candidates who can explain their choices in their own words, rather than offloading everything to AI. The Product Team is currently hiring for ARE, SWE, Data Engineer, PM, Designer and Sales roles, among others.

My take — AI-written commentary, not fact-checked reporting

Sakana is doing the sensible thing: giving product engineers real scope instead of pretending a tidy org chart does the work. The catch is that “wide autonomy” plus “mostly on-site” is a very particular bargain, and it won’t suit people who want neat boundaries and remote bliss. Still, this is the kind of messy, practical setup more AI teams should admit to having.

Read more about this at: Sakana AI

Related stories

The daily briefing

Every AI story that matters, in your inbox by 8am.

TLDRocket reads all relevant sources, removes duplicate coverage, and summarises the day in two minutes. Follow companies and topics for alerts, or get the briefing in Slack. Free, no spam, unsubscribe anytime.