From Software Engineer to QA Team Lead: How Testing Became My Passion

Rimon Nassory — Sun, 25 Oct 2026 17:30:00 +0000

My journey through software development, entrepreneurship, leadership, and AI-driven automation.

When I started my career as a software engineer, becoming a QA Team Lead was never part of my plan. I simply loved building software, solving problems, and exploring new technologies.

But looking back, I can see how curiosity, entrepreneurship, and an increasing interest in automation gradually shaped my career.

From Software Development to Entrepreneurship

I started as a mobile developer, building applications for iOS and Android. While I enjoyed writing code, I was always curious about the bigger picture. How do companies make money? How do you turn an idea into a business?

That curiosity led me to pursue a master's degree in business innovation.

During my studies, I developed an idea inspired by my experience as a football referee: replacing pen and paper with a smartwatch application to manage match events.

What started as a university project eventually became a startup. I found myself not only developing software but also negotiating partnerships, understanding customer needs, and making business decisions.

It taught me something important: Great software isn't just about technology. It's about solving real problems.

Discovering the Value of Testing

Throughout my development career, I worked on several applications, including mobile apps, smartwatch solutions, and larger web applications.

Early on, testing wasn't something I fully understood. I wrote some tests, but I didn't appreciate their long-term value.

That changed as I gained experience building and maintaining real products.

I started seeing how automated tests could prevent regressions, improve confidence, and make software easier to maintain.

Eventually, testing became something I actively advocated for.

From Tech Lead to QA Leadership

When I became a Frontend Tech Lead, I noticed that automated testing wasn't consistently part of the development process.

I began introducing unit, component, and integration testing through regular knowledge-sharing sessions with developers.

My goal wasn't simply to increase the number of tests. It was to build a culture where quality became a natural part of development.

At the same time, I became increasingly interested in end-to-end automation and the possibilities of AI.

So when an opportunity to lead a technically focused QA team appeared, it felt like a natural next step.

Where AI Meets Quality Engineering

Today, I lead a QA team focused on automation, software quality, and AI.

One of my recent initiatives has been building a context-aware AI architecture using structured context, skills, rules, and prompts to help transform test cases into automated tests.

I'm now looking toward self-healing test agents and LLM-as-a-Judge approaches as the next areas to explore.

The goal isn't to replace engineers, but to help them spend less time on repetitive work and more time improving software quality.

Looking Back

If there's one thing my career has taught me, it's that you don't always need to know exactly where you're heading. Curiosity and a willingness to learn can open unexpected doors.

My journey from software developer to entrepreneur, technical leader, and QA Team Lead wasn't planned, but each experience helped prepare me for the next.

Through this blog, I hope to share what I've learned about software engineering, startups, leadership, testing, and AI automation.