My career in tech wasn’t linear — and that’s exactly why I don’t regret it. I started in manual QA, moved through analytics and marketing leadership, and eventually became a full-stack developer. Each step taught me something that makes my code stronger today.
As a QA tester and software development analyst, I worked with CRM and back-office systems, wrote test scenarios, collaborated with developers, and used SQL to validate data and reproduce issues. That experience built my habit of thinking in edge cases, reliability and real user flows — long before I wrote production code.
From business impact to technical ownership
Moving into analytics and marketing gave me a different skill set: understanding how websites and internal tools affect real business outcomes. Later, when I transitioned into IT, that context helped me translate requirements into implementation — not just “build features”, but build the right ones.
Over time I focused heavily on frontend development — delivering responsive interfaces with clean, maintainable code — and gradually expanded back into full-stack work. Today, I develop and continuously improve internal web applications, including a company intranet used daily by roughly 600 employees.
"A non-linear path doesn’t mean starting over. It means stacking skills — testing for precision, marketing for impact, frontend for experience, and backend for architecture."
The result is a perspective I value: I don’t write code in isolation. I think about usability, performance, data integrity, and maintainability — because I’ve worked on every side of the product lifecycle. The detours didn’t slow me down. They made me better.