Try First, Then Choose: From Humanities to Engineering to Technical Product Management at Recruit
Shohei Yoshikawa
Technical Product Manager (TPM)
San Jose State University / Software Engineering
Discovering Software Engineering in Silicon Valley
In Japan, students usually choose between a humanities track and a science track early in high school, and that choice largely determines which entrance exams they take and what they can study at university. I was on the humanities track, but I wasn't sure I could decide my whole future at that age. At American universities, students can take classes across different fields before choosing a major, which I felt would give me more room to figure out what I wanted. So I decided to study in the United States.
I ended up at San Jose State University, right in the middle of Silicon Valley. People around me worked in tech and my classmates were building their own apps. The more I saw, the more I wanted to build software myself, so I switched to software engineering, something that would have been very difficult at a Japanese university once I had enrolled.
It was the first time I chose a direction based on something I had actually tried. It wasn't an easy switch, though. Without a science background, I had a lot of catching up to do, and I spent most of my time in college studying.
Seeking Early Responsibility and Long-Term Growth
As graduation approached, I had job offers in the United States and Japan. My student visa would let me work in the U.S. for a limited time after graduating, and I couldn't see where my career would go after that. I wanted to build it somewhere I could stay for the long term, and that meant Japan.
What drew me to Recruit in particular was the sense that I would be trusted with real responsibility from my first year. I didn't want to spend years waiting for my turn. I wanted a place where I could grow by doing the work myself.
Career at a Glance
2019 – 2021
Study Sapuri, iOS Engineer. Joined Recruit as a new graduate and worked on the iOS app for Study Sapuri, an online learning service used by students and schools across Japan.
2021 – Present
Study Sapuri, Technical Product Manager (TPM). Tried the role through an internal program in 2021, then moved into it full-time. Manages projects through from technical design and requirements to release. Led delivery of a single sign-on (SSO) feature for students across iOS, Android, and the web, released in March 2025.
From iOS Engineer to Technical Product Manager
Recruit was everything I had hoped for. Working as an iOS engineer, I was never given a detailed list of instructions. I was expected to work out what needed to be done and move it forward myself, and that kind of freedom suited me.
Then, in 2021, came my biggest turning point. At the time, there was a growing demand for technical product managers (TPMs) within the company, and an internal mobility program allowed employees to take on assignments in a new role while continuing their current engineering responsibilities. I volunteered. I hadn't planned to leave engineering, but I wanted to try the role before deciding whether it was right for me.
It turned out to be a better fit than I expected. I loved seeing a project run smoothly from proposal to release, and I liked being the person my teammates trusted to sort things out. I moved into the TPM role full-time, and I've been doing it ever since.
A TPM, or Technical Product Manager, moves product development forward from an engineering perspective. Product managers decide what to build, while TPMs are responsible for how it gets built and delivered. In practice, that means assessing technical feasibility and effort at the planning stage, building a plan together with multiple engineering teams, designers, and the business side, and managing progress through development, testing, and release.
Figuring Out the Pieces: Delivering the SSO Feature
One project I'm especially proud of is a single sign-on (SSO) feature for students who use Study Sapuri at school. It was released in March 2025. Instead of a separate Study Sapuri ID and password, students log in with their Microsoft, Google, or Apple accounts. That meant three login methods across three platforms (iOS, Android, and the web), which gave us nine combinations to build and test. And because schools don't like changing how they work partway through the year, we had to launch before the new Japanese school year starts in April.
My primary focus was driving the project to an on-time launch. I got involved early, during validation, to reduce uncertainty before development began. Once development was underway, I joined the engineers' daily stand-ups so I could catch problems early and adjust plans or staffing quickly. We also tested in stages rather than leaving it all to the end, prioritizing the early detection and resolution of issues to prevent any delays. We launched on time, and password reset requests went down afterward. One local government even told us SSO was a deciding factor in choosing learning materials for its schools.
The part I enjoy most is figuring out how all the pieces fit together. Study Sapuri runs on many systems built up over the years, and every new feature has to work with all of them. I dig into how those systems actually behave, then pin down the technical design, requirements, and operations, and see each project through to release. My engineering background shapes how I do all of this, and I draw on it every day.
Keep Your Options Open
You don't have to decide your whole career now. I started on the humanities track, became an engineer, and then moved into a role I'd never planned for. At each step, I found out what suited me by trying things and not overthinking them.
So, keep your options open, and when a chance to try something new comes along, take it. If you want meaningful work early in your career, with room to change direction as you grow, I'd encourage you to talk with people at Recruit about where your career could go here.