From Seeking Root Causes to Taking True Ownership: Working as a Product Manager at Recruit Today

Shoo Yonekawa

Product Manager & Product Designer

University of Toronto / Materials Science and Engineering

Shoo Yonekawa standing by a window overlooking the city at a Recruit office

Questioning the Norm and Tracing Back to the Root

I knew early on that I wanted to study engineering. I also knew that English would be essential: for studying, for finding information, and for connecting with people. But I didn't want to be in a university lecture hall learning crystal structures and thermodynamics in English I was still struggling with. So, I made a slightly unusual decision. I moved abroad for high school. High school would be for mastering English. University would be for engineering, and nothing else.

At the University of Toronto, I majored in Materials Science and Engineering and minored in Forensic Engineering, which is the study of why things fail. When a structure collapses or a part breaks, you don't stop at "it broke." You trace it back to the root cause. I didn't realize it then, but that habit would follow me into a completely different field.

Looking back, the experiences that shaped me most happened outside the classroom. There were two in particular. The first was a software engineering internship at a food delivery company back in Japan. I was asked to prototype a new feature for the inventory management system that restaurants used. At first, I tried to build it all by myself, and I got stuck. What finally got things moving was asking for ideas from the people who actually used the system and from other engineers. That was when I learned that building something good means bringing people in, whatever their job title.

The second came through my university's Japanese student association. Event sign-ups and payments were handled in separate systems, so attendance records slipped through the cracks and payments were missed. The team running the events had gotten used to it. But coming to it with fresh eyes, I thought: shouldn't this all be in one place? I proposed a fix, set up a new team, and rebuilt our web system so that event registration and payment were managed together. The lesson for me was this: "that's just how we do it" is never a good enough reason. You have to keep an ideal in mind, and you have to say it out loud.

A Shift to Product Management and a Culture of Logic

Having studied materials, I was naturally drawn to manufacturing. I also interned as a 3D printer operator and designer at a university-backed startup that 3D-printed soil substitutes for hydroponic farming. But my software internship changed my direction. I became fascinated by UI/UX design, which led me to aim for product manager or product designer roles.

My criteria were simple. First, a company that would allow me to be deeply involved in product creation with a high level of ownership from an early stage. Second, a place with a startup-like mindset, as I honestly wasn't sure if I could adapt to a rigid, hierarchical Japanese corporate culture.

One moment in my final interview at Recruit stuck with me. Out of nowhere, I was given an estimation question, the kind where you work out a rough number from scratch with nothing but logic. My answer wasn't the one the interviewer had in mind. But my reasoning held up, and the interviewer found my thought process interesting. What I took from it was this: here, if your reasoning holds up, your opinion gets heard, no matter how junior you are.

Career at a Glance

Oct 2024 – May 2026

HOT PEPPER Beauty WORK, Product Designer. Joined a job-matching platform for beauty professionals such as hairstylists. Planned and designed UI/UX improvements as part of the team focused on increasing job applications.

Jun 2026 – Sep 2026

HOT PEPPER Beauty WORK, SEO Product Manager. Led a KPI team focused on acquiring users through search, owning its strategy and initiatives.

Oct 2026 – Present

Recruit ID and Point, Product Manager and Product Designer. Moved to the shared account and loyalty points product used across Recruit's services.

Understanding the Decision-Maker's Perspective and Discovering a Culture of First-Principles Thinking

The biggest wall I hit was explaining things concisely and persuading people. To get an initiative approved, I usually have about 15 minutes in a meeting with the head of product. In that time, I need to cover the background, the problem and its scope, the proposed solution, the expected KPI impact, and the detailed requirements, before taking questions. Early on, I spent most of my time on the requirements. The questions piled up, and I often ran over.

What I was missing was a sense of what the decision-maker was aiming for and what they needed to see to get there. The head of product cares most about three things: how much an initiative will benefit our users and grow the product, how much it will cost, and where the risks are and how big they are. Understanding what leaders are always watching isn't just a trick for getting approval. It's essential to planning any initiative that truly grows a product.

On the other hand, one thing that turned out better than I'd imagined was how much freedom I have. Even when I'm asked to "do X," I'm encouraged to go back to the root of the problem, and if there's a better solution, we go with that instead.

That freedom grew even further when I was given my own KPI team. I could set the strategy and choose the initiatives myself. With that came the responsibility to deliver results, which meant reading the numbers across the whole product in much finer detail. Having learned how a single product works and what it needs from UI/UX, I've now moved to a product that connects multiple services. My next challenge: energizing Recruit's entire product ecosystem, not just one service.

Just Give It a Try: Every Experience Brings You Here

If something catches your interest, try it, or at least go and take a look. Every experience like that gives you more options later, and a better way to compare them. Materials labs, 3D printers, a delivery app, a student association: none of these were "the plan." But all of them brought me here.

Shoo Yonekawa talking at a long table in a Recruit office