The first significant moment came when I was dragged to a career fair during high school.
Standing nervously in a community college gymnasium under buzzing fluorescent lights, surrounded by booths and company brochures, I was unsure of myself. Yet, I loved solving technical puzzles; it gave me confidence and purpose.
At that time, I realized that specializing was not my path--I wanted diversity.
I hoped to build a career where I'd always be challenged by something new, never feeling stagnant or bored.
I imagined myself as versatile, a problem solver rather than a specialist. My aspirations weren't tied to money alone; I sought stimulation, continuous growth, and the chance to create something meaningful. I thought that pursuing a generalist approach could keep my career dynamic and fulfilling, always learning and never just punching the clock.
Fast-forward a decade, and I realize now that I was right.
Generalizing my software development knowledge led to a diverse and deeply fulfilling career.
What began as assembling fiber-optic transceivers in high school turned into developing firmware for Star Trek-inspired, fingerprint-activated pneumatic doors. Later, I created mobile apps at the Cleveland Clinic that genuinely helped people manage concussions, multiple sclerosis, and even navigate ventilator settings during COVID-19. The iPads we strapped to patients even earned us a front-page feature from Apple. My willingness to dive into augmented reality opened doors to pioneering AR healthcare applications on Magic Leap and HoloLens.
At Qr8 Health, flexibility paid off again as I picked up React and built a platform for early dementia detection, then moved to programming firmware in C for medical devices used to assess movement disorders. The constant shifting between languages and frameworks didn't exhaust me--it energized me.
An essential truth emerged throughout this journey: being a generalist doesn't mean being shallow. It requires rigor--obsessing over quality, writing solid unit tests, deeply understanding your code, and caring about the craft. It means embracing tools you initially resist - for me, that was C# - until you genuinely understand and even appreciate them.
Generalizing has sustained my passion for software engineering and enriched my life, allowing me to impact others and keep growing personally and professionally.
For me, the heart of this journey has been learning that true career fulfillment in software engineering often comes from versatility, dedication to quality, and an endless curiosity.