Feb 13, 2026

From Architecture to QA, Finding Joy in the Build 

Summary

From Uruguay to global tech teams, Marcela Meirelles found her path by following what felt genuinely fun. After exploring architecture and programming, she discovered QA, especially automated testing, where structure, logic, and curiosity meet. She shares early-career advice and what a healthy, trust-based team culture looks like.
Image of a clock min. read

Hi, I’m Marcela Meirelles. I’m from Uruguay, from a city called Salto, in the north of the country. I’ve been working in testing for around ten years, although if you had asked me years ago if this would be my path, I probably wouldn’t have known how to answer. 

My story with tech did not start with a clear plan. It started with curiosity, with trying things, and with paying attention to what felt genuinely fun. 

Trying many paths before finding one 

Before tech, I studied a little bit of everything. Architecture, Biochemistry, Design, and eventually Programming. Looking back, it might sound scattered, but at the time it was just exploration. I wasn’t chasing a specific job title; I was following interest. 

While studying Architecture, something unexpected kept happening. I spent more time fixing computers, configuring systems, and figuring out how to make software work properly than using the architecture programs themselves. I was always the one adjusting settings, solving technical issues, and making things run. 

Eventually, that curiosity pulled me toward programming. 

Once I started studying it and entering the tech world professionally, everything began to make sense. The environment, the problems, the collaboration across teams and countries, the technologies themselves. It all clicked in a way nothing else had before. 

How QA found me 

I didn’t choose QA with a clear intention. At first, I didn’t even know it was possible to work only in Quality Assurance. It happened gradually. I started learning, getting involved, and without realizing it, I was hooked. 

What I love most about QA is the balance. Understanding how systems work, thinking about edge cases, and building things that protect the user experience. Over time, I discovered a particular enjoyment in creating automated test suites. There is something deeply satisfying about structure, logic, and seeing tests run cleanly. 

QA became a space where curiosity, analysis, and patience come together. 

Learning from many people, not just one 

I don’t have a single role model. Every person I’ve worked with has taught me something. Some lessons were technical, others were about communication, teamwork, or perspective. It’s the collection of experiences, not one individual, that shaped how I work today. 

That variety is part of what keeps tech interesting. You’re always learning, often from unexpected places. 

Advice for anyone starting in tech 

If I had to share two things, they would be these. 

First, learn English. It opens doors in ways you don’t always expect. Some of my early opportunities came not because I knew more technology, but because I could communicate. 

Second, start. Send your CV, talk to recruiters, ask questions, and approach everything from a learning mindset. You don’t need to know everything to begin. You grow by doing. 

I never thought, “I want to work in tech.” I thought, “This is fun.” And that made all the difference. 

Life at Abstra 

My experience at Abstra has been very positive so far. From the first interview, I noticed kindness, transparency, and honesty. It feels like a company that trusts its people, focuses on getting the work done without micromanagement, and cares about employees feeling comfortable in their roles. 

That trust creates space to do good work. 

Running toward balance 

Outside of work, I run. Trail running, specifically. Even though Uruguay doesn’t have mountains, I still find my way to them. My last race was on November 30 in Villa La Angostura, Argentina. Around 30 kilometers, reaching a maximum altitude of 1,758 meters. 

Running in the mountains feels a lot like my career path. Challenging, unpredictable, sometimes uncomfortable, but deeply rewarding. 

Conclusion 

My path into tech wasn’t linear or planned. It was built through curiosity, trying different things, and noticing what made me want to keep going. Architecture, programming, QA, and even running share something in common for me: they are about building, adjusting, and moving forward. 

If you’re still figuring things out, that’s okay. Sometimes the right path doesn’t arrive with certainty. Sometimes it arrives disguised as fun.