If anyone had told me two years ago that I’d be working on HPC cluster managers and complex identity workflows, I’d have laughed. Yet here I am, grateful for the rollercoaster journey from self-taught novice to tackling advanced tech in record time. I started learning HTML, CSS, and JavaScript on an iPad during lunch breaks, so you could say I hit the ground running.
A Grocery Manager with a Coding Dream
In early 2023, I’d already been working in retail for nearly six years, specifically as an assistant produce manager responsible for everything from inventory to display layouts. While the job had its own challenges—maintaining fresh produce, managing schedules, and juggling customer service—part of me craved something more creative and technical. So on breaks, I’d watch coding tutorials on YouTube and practice each snippet on SoloLearn. It was a modest beginning, but it gave me a taste of what was possible with code. By the time November rolled around, I’d landed my first junior web developer role—nervous, excited, and ready to absorb everything.
Stepping into the HPC World
My first role threw me into the deep end. The On-Demand Data Center (ODDC) platform allowed users to create custom images, spin up clusters, and manage deployments across AWS, GCP, Azure, and more. Though I was a junior, I found myself updating front-end code, refactoring messy scripts, and eventually spearheading a new Marketplace feature. Suddenly, HPC didn’t seem so foreign—I was learning the complexities of cluster management, environment provisioning, and HPC-friendly frameworks like E4S.
It was thrilling and daunting all at once. We’d hack together solutions for node sizing, IP allocations, and credentials management. I was also juggling UI logic—merging APIs, implementing pagination, and ensuring the marketplace could spin up a fully functional cluster in about 10 minutes. I realized how critical it is to understand both front-end usability and the nuts-and-bolts of HPC provisioning.
Pivoting to Identity Solutions
After about 8 months, I joined Fischer Identity. This time, my focus shifted to building Blazor front-ends and .NET Core backends. Instead of HPC, I was dealing with enterprise-level identity management—configuring external identities, enabling resource access, and overseeing admin workflows. It was a whole new skill set. Yet the process felt oddly familiar: I was once again connecting complex services to a user-friendly front end, only now it was about who could do what rather than how to spin up HPC jobs.
In many ways, identity was just as intricate as HPC. I had to merge data from multiple endpoints, handle advanced paging, and orchestrate different authentication flows. Developing the “Request Hub” (with access requests, sponsor changes, and dynamic permissions) taught me that front-end code can get complicated quickly when everything needs to be consolidated in one seamless interface.
Reflections on Rapid Growth
Moving from grocery management to HPC to identity solutions, all within roughly 14 months, has been a whirlwind. If there’s one thing I’ve learned, it’s that flexibility and curiosity can be a junior developer’s best assets. I’ve had to adapt to new frameworks and domains on the fly, leaning on colleagues, online communities, and trial-and-error to fill the gaps.
Sure, I don’t claim to be a deep expert in HPC or identity after such short stints. But even a cursory understanding of these advanced topics—coupled with solid front-end skills—has opened doors I never knew existed. It’s clear that technology rewards those willing to be thrown into challenging projects and learn as they go.
Lessons Learned Along the Way
Embrace the Unknown: Sometimes the best way to learn is to say “yes” to a project that feels just outside your skill set.
Stay Curious: HPC or identity might not be your main passion, but being open to complex problems expands your future career paths.
Front-End Matters: Even in HPC or identity-heavy projects, a clear, intuitive UI can make or break user adoption.
Ask for Help: Leaning on senior devs or online communities saved me countless hours and spurred faster growth.
What’s Next?
Today, I’m still at Fischer Identity, digging deeper into .NET, Blazor, and more advanced authentication flows. I’m also tinkering on personal projects—like the AI Helper Library—where I get to experiment with new technologies and put my lessons to work. Whether I end up specializing in DevOps, AI, or remain a generalist, I’m grateful for the breadth of experience these first 14 months have given me.
If you’re on a similar path—self-taught, pivoting careers, or feeling overwhelmed by fast-moving responsibilities—just remember that every project is a chance to learn something new, even if it’s messy at first. I used to code on an iPad at Starbucks; now I’m merging HPC endpoints and identity portals. Who knows what tomorrow will bring?