The person
behind the work.

Most people introduce themselves with a job title. Engineer. Researcher. Manager. I have held all of those, and none of them alone has ever felt complete — because none captures the thing that has always driven the work: finding the most interesting problems at the edges of disciplines and building something useful there. Where physics meets biology. Where a research lab's rigour meets a product team's urgency. Where a language barrier hides an engineering opportunity that everyone else missed.

I am, at my core, a builder who thinks like a scientist.

I arrived in Japan at seventeen on a government scholarship, speaking almost no Japanese, enrolled at a technical college in Nara. Within a year I was studying in Japanese. Within five years I had earned an engineering degree in that language. By the time I finished my PhD at SOKENDAI — the Graduate University for Advanced Studies — every piece of formal education I had received was conducted in Japanese.

That is not a linguistic curiosity. It shaped how I think. Japanese engineering culture has a word — monozukuri — that roughly translates as "the art of making things," but implies something deeper: the patient mastery of fundamentals, the discipline to understand a system completely before changing it, the respect for process as much as outcome. That philosophy became my foundation long before I could articulate it.

My PhD work was in biosensors and measurement systems at the Institute of Molecular Science in Okazaki. I fabricated supported lipid bilayer biosensors using synchrotron radiation etching, designed microelectrode substrates at nanometre tolerances, and built measurement platforms to study how biological membranes respond to chemical and electrical stimuli. The work lived at the intersection of physics, chemistry, and biology — exactly where I wanted to spend my career.

Scientific training teaches you one discipline above all others: you do not claim to understand something until you can measure it, reproduce it, and honestly account for the failure modes.

One of the most clarifying projects of my early career happened not in a world-class laboratory, but in Bangladesh. I built a vehicle tracking system at a time when internet infrastructure outside Dhaka was unreliable and expensive. The technically ideal solution simply could not work in the real operating environment.

So we designed around the constraint. We built an SMS-based tracking system that functioned wherever cellular text messaging reached — almost everywhere, even when mobile data did not. It was not the most sophisticated technology. It was the most effective solution given actual conditions. That lesson never left me.

Innovation is not about deploying the most advanced technology. It is about understanding the actual constraints and building the most effective solution within them.

That path eventually put me in charge of the engineering build-out for HeartVoice — a digital-health venture inside Omron Healthcare that scaled into a $16M business — inside a 90-year-old Japanese manufacturer not historically known for taking those kinds of bets. Leading the team through regulatory clearance, ISO 13485, and commercial launch across Asia-Pacific was the hardest and most satisfying engineering problem I have worked on.

Artificial intelligence, for me, is not a pivot or a trend to ride. It is the natural next layer of the same work I have always done: building systems that can sense, interpret, and act on information in ways that help people make better decisions. A PhD in physics, it turns out, is unexpectedly useful preparation for that.