How did designing engine components lead me to SQL tables and React components? Exploring the power of cross-disciplinary thinking in modern product development.
Many people ask me: “Erkan, how does a Mechanical Engineer who spent years designing V12 engines and sheet metal parts for Ford end up building software startups and writing React code?” On the surface, these two worlds seem miles apart. But if you look closer, they are driven by the exact same heartbeat: the art of structured problem-solving.
The Discipline of the “Physical” World
My journey started in the rigorous world of automotive engineering. At Ford Motor Company, I learned the precision of Body-in-White (BIW) design. Later, as an Engine Design Group Leader at BMC Power, I was responsible for the intricate architecture of military-grade V8 and V12 engines.
In these roles, there is no room for “bugs.” If a Master Section is wrong or a tolerance stack-up is miscalculated, the physical consequences are massive. This period taught me system thinking: how thousands of individual parts must synchronize perfectly to achieve a single goal.
The Bridge: PLM and Optimization
The real shift happened when I realized that the process of designing was just as important as the product itself. I saw teams struggling with outdated data and inefficient workflows. This led me to lead a PLM transformation program, where we reduced project lead times by 20%.
I wasn’t just designing engines anymore; I was designing systems of productivity. This curiosity eventually birthed StandardPLM, my own startup where I transitioned from being a user of CAD tools to a creator of software solutions.
Why Cross-Disciplinary Thinking is the Future
Today, I don’t see myself as “just” an engineer or “just” a developer. Whether I’m crafting a concept for a High-Speed Train or building a digital dashboard in React, I apply the same principles:
- User-Centricity: Whether it’s a driver in a cockpit or a user on a web app, the experience must be “delightful” and intuitive.
- Scalability: A well-structured SQL database is like a modular engine—it must be built to handle growth and stress without breaking.
- Efficiency: My background in Six Sigma and industrial design allows me to strip away the “noise” and focus on what truly adds value.
Conclusion
The transition from Sheet Metal to Source Code wasn’t a change of career; it was an expansion of my toolkit. In modern product development, the lines between hardware and software are blurring. To build the future—be it an electric vehicle or a SaaS platform—you need to speak both languages.
I’m Erkan, and I’m here to bridge that gap.