7+ years. 4 languages. 1 mindset: build systems that scale. I started my career writing Java code. Today, I design robust, scalable back-end systems that actually survive production. Over the last 7+ years, I’ve worked across: Java, Kotlin & Spring Boot (3.x) for high-performance APIs Node.js, NestJS & TypeScript for scalable, modern server-side applications Python for flexibility and productivity REST & GraphQL, always with clean resource modeling JWT, validation, versioning, OpenAPI/Swagger Hexagonal & Clean Architecture to keep code testable and future-proof React when full-stack ownership was needed What I’ve learned the hard way: Scaling software is less about frameworks And more about decisions, boundaries, and clarity Today, my focus is simple: Build systems that are easy to change APIs that are clear to consume Codebases that teams actually enjoy maintaining If you’re building products where performance, architecture, and long-term thinking matter, we should talk. Curious: what’s the hardest architectural decision you’ve had to make recently? #SoftwareEngineering #BackendDevelopment #Java #SpringBoot #NodeJS #NestJS #TypeScript #Microservices #CleanArchitecture #HexagonalArchitecture #APIDesign #GraphQL #REST #ScalableSystems #TechCareers #WomenInTech #BrazilTech #LinkedInTech
Good work! Those're principles to keep in mind
Nice job, thank you for sharing your thoughts regarding your personal experiences!
System design is hardest for me😬
Your focus on clarity and decision-making in software architecture resonates deeply; those principles often define long-term success more than any specific technology choice.