From a Student Partner to a Leapfrogger: How I Learned to Leap

If someone had told me a few years ago that I would one day call myself a Leapfrogger, I probably would have smiled, nodded, and quietly wondered, “What exactly is a Leapfrogger?”

Fast forward to today, and here I am.

Looking back, becoming a Leapfrogger wasn't a single leap. It was a series of small hops, unexpected turns, challenges, opportunities, sleepless nights, questionable decisions, and countless moments of learning. And strangely enough, it all started with LSPP.

When I joined the Leapfrog Student Partnership Program, I thought I was stepping into an opportunity to learn more about technology. I didn't realize I was stepping into an environment that would gradually reshape the way I learned, worked, collaborated, and looked at my own abilities.

LSPP wasn't simply about learning how to code or getting better at technology. It was about being around people who constantly challenged me to think beyond what I already knew. It gave me opportunities to build, experiment, communicate, collaborate, make mistakes, receive feedback, and try again. Somewhere between all of that, it sharpened my skills and, perhaps more importantly, started building the confidence that would eventually carry me much further than I had imagined.

At the time, I thought I was simply taking my first step.

I didn't know I was already beginning to leap.

The First Hop

Starting LSPP felt like stepping into a completely different pond.

As a student, there is always that tiny voice somewhere in your head asking, “Am I good enough?”, “Do I actually know enough?”, or the classic, “What if everyone else is better than me?” Apparently, the human brain comes with an unlimited supply of these questions. No installation required.

But LSPP gave me something far more valuable than answers—it gave me a place to figure things out.

I began to understand that learning technology wasn't just about knowing a framework, solving a programming problem, or making something work on your screen. There was a much bigger world around it: understanding problems, working with people, communicating ideas, taking responsibility, accepting feedback, and learning how to keep moving when things didn't go according to plan.

I slowly became more comfortable with being uncomfortable.

And I think that was one of the earliest lessons that stayed with me. Growth rarely happens when everything feels familiar. Sometimes, you have to walk into a room where you aren't sure whether you belong, sit down anyway, and start learning.

So, I hopped.

When Learning Turned into Building

There is a strange difference between knowing something and actually building something.

You can watch ten tutorials about React and still stare at your screen wondering why that one component refuses to behave. You can read about teamwork and still discover that working with an actual team is an entirely different sport. You can understand a concept perfectly in theory, only to discover that applying it to a real problem comes with an entirely different set of challenges.

LSPP helped me make that transition from simply learning to actually doing.

I wasn't just collecting knowledge anymore; I was learning to apply it. Every project, discussion, challenge, mistake, and piece of feedback slowly pushed me toward becoming someone who could take what I knew and turn it into something useful.

And somewhere along the way, I noticed that my confidence was changing too.

Not the “I know everything” kind of confidence—thankfully, that version never arrived. Instead, it became the much more useful kind:

“I don't know this yet, but I'll figure it out.”

That mindset would become important later, because software engineering has a funny way of constantly reminding you that there is always something you don't know.

One Leap Leads to Another

One of the major milestones along the way was Revampathon.

A two-week hackathon where we took on the challenge of revamping Tootle into a cutting-edge product sounded exciting, ambitious, and, looking back, slightly terrifying. There were ideas to discuss, things to build, problems to solve, things that broke, things that had to be rebuilt, and plenty of moments where the solution seemed obvious until we actually tried implementing it.

But that was also what made it special.

Somewhere between the collaboration, the debugging, the iterations, and the inevitable “let's just try this once” moments, we managed to bring the idea together. And then came the moment that made all of it even more memorable:

🏆 Revampathon Winner

We won.

It was a major achievement, and one I am genuinely proud of. But beyond the recognition, Revampathon became one of those moments that reinforced something I had already begun to feel during LSPP: I could actually build things, contribute meaningfully, and be part of something bigger than myself.

It was one of those little moments that quietly tells you, “Maybe you're doing better than you think.”

And sometimes, that's all the encouragement you need to take another leap.

The Leap into the Real World

When LSPP eventually came to an end, I could have looked at it as the closing of a chapter.

Instead, it turned out to be the beginning of another one.

The experience, exposure, and confidence I gained through LSPP eventually paved the way for me to join Leapfrog Technology as an Associate Software Engineer in March 2025.

That transition still feels a little surreal when I think about it.

Not too long ago, I was a student trying to understand how things worked. Suddenly, I was part of a professional environment where the things I built, the decisions I made, and the problems I solved carried real responsibility.

The questions changed too.

It was no longer only, “How do I learn this?” It became, “How do I build this properly?”, “How do I make this maintainable?”, and eventually, “How can I make this better?”

The learning didn't stop when I got the job.

If anything, it accelerated.

Working alongside people who were much more experienced than me was both humbling and inspiring. There was always someone who knew something I didn't, another problem I hadn't solved before, another perspective I hadn't considered, or another way something could be done better.

Instead of making me feel like I didn't belong, it made me want to learn more.

I was no longer simply learning what software engineering was.

I was living it.

Another Leap: From Associate to Software Engineer

Then came another milestone.

After a year of learning, contributing, taking on new responsibilities, making mistakes, improving, and gradually finding my footing, I was promoted from Associate Software Engineer to Software Engineer in March 2026.

On paper, it is just another line in a career timeline.

For me, it represented something much bigger.

It was a quiet reflection of the distance I had traveled since those early days of LSPP. The student who once wondered whether they knew enough was now trusted with greater responsibility and a new role as a Software Engineer.

And yet, strangely enough, the feeling of being a beginner never completely disappeared.

The title changed, but the mindset remained.

There was still more to learn, more to build, more to improve, and more problems waiting to be solved. Maybe that's one of the things I have come to appreciate most about this journey: every milestone gives you a moment to look back, but it also quietly points you toward the next challenge.

Becoming an Associate Software Engineer taught me how to step into professional software development.

Becoming a Software Engineer reminded me that growth doesn't stop once you get comfortable.

It simply gives you a bigger place to grow into.

The Journey Between the Dates

If I were to reduce the whole journey to a few dates, it would look surprisingly simple:

April 2023
    ↓
LSPP
    ↓
Learning • Building • Growing
    ↓
Revampathon Winner
    ↓
March 2025
    ↓
Associate Software Engineer
    ↓
March 2026
    ↓
Software Engineer

Clean. Simple. Almost like a perfectly maintained Git history.

My actual journey was anything but.

There were bugs, mistakes, doubts, things I didn't understand, things I thought I understood but absolutely did not, and enough “why isn't this working?” moments to fill an entire repository.

There were also people who helped me, opportunities that pushed me, projects that challenged me, and small victories that kept me moving.

A résumé can capture titles and dates.

It cannot capture everything that happened between them.

And for me, the space between those milestones is where most of the growth happened.

From “Do I Belong Here?” to “I'm Here.”

Perhaps the biggest thing this journey gave me wasn't a technical skill or even a job title.

It was confidence.

Not the confidence that tells you that you know everything, but the confidence to walk into a room where you don't know everything and still believe that you have something to contribute.

There was a time when I hesitated before entering rooms where I thought everyone else was more experienced, more knowledgeable, or simply better than me.

Today, I understand something I wish I had understood earlier:

You don't have to know everything to belong. You just have to be willing to learn.

Leapfrog didn't simply open doors for me. It helped me realize that I belonged in rooms I once hesitated to enter.

And perhaps that is one of the most valuable things this journey has given me—not just skills, not just experience, but the confidence to look at the next challenge and think, “Alright. Let's figure this out.”

From LSPP to Leapfrogger

When I look back at the journey now, I don't see one giant leap.

I see a collection of smaller ones.

The first leap was joining LSPP. Then came the leap from learning to building, the leap into Revampathon, the leap from being a student partner to becoming an Associate Software Engineer, and then another leap from Associate Software Engineer to Software Engineer.

None of them felt enormous while I was taking them.

But standing here now, looking backward, I can finally see how far they carried me.

They turned a student into a professional. They turned hesitation into confidence. They turned “I don't know if I can” into “I'll figure it out.”

And eventually, they turned an LSPP student partner into a Leapfrogger.

I am deeply grateful to Leapfrog for giving me that first opportunity through LSPP and for continuing to provide an environment where I can learn, contribute, and grow. The people I've worked with, the challenges I've faced, the opportunities I've received, and the lessons I've learned have all shaped the person and engineer I am today.

If there is one thing this journey has taught me, it's that you don't need to know where every leap will take you.

Sometimes, you just need to take the first one.

And then another.

And another.

From LSPP to Associate Software Engineer.

From Associate Software Engineer to Software Engineer.

From a student partner to a Leapfrogger.

The journey wasn't one giant leap.

It was every leap along the way. 🐸