# From "I Just Make It Work" to Backend Engineer: Starting to Document the Process > Source: > Published: 2026-08-24 19:55:02+00:00 Hi, I'm Felipe. I'm a full-stack developer from Brazil, currently working as a software engineer at an enterprise environmental risk and compliance SaaS platform. I build multi-tenant architecture, auth systems, and AI-powered document processing pipelines for industrial clients. I've been doing this for about 3 years now, and here's an honest confession. I'm good at solving problems. Multi-tenant isolation, cache invalidation, entity resolution pipelines, that kind of thing. But I often can't name what I did with the formal, textbook vocabulary that system design interviews expect. I learned by doing, in production, under pressure. Not by reading Designing Data-Intensive Applications cover to cover. That gap is what I'm closing now. My goal is to move into backend and data engineering roles at international companies. To do that well, I need to go from "I can solve it" to "I can explain, defend, and teach it." If you're on a similar path, self-taught in production and now catching up on the formal side of things, I hope some of this is useful. And if you spot something wrong in what I write, please tell me. That's kind of the point. Next post: the first project. A REST API with proper auth, and everything I got wrong building it "the fast way" before. something wrong in what I write, please tell me. That's kind of the point. Next post: the first project. A REST API with proper auth, and everything I got wrong building it "the fast way" before.