Projects

What started as a frontend engineering role quickly evolved into something far more demanding. Two months in, the Tech Lead left the project leaving two SPAs with severe technical debt: logic embedded directly in components, no separation of concerns, and no clear architecture. On the new SPA that I had already started building independently, I applied everything from the previous project: Hexagonal Architecture, DDD, clean code and Doc as Code. I built scaffolding that could be reused across the entire business unit of ~20 engineers, onboarded two junior developers into the new architecture, wrote full documentation and led the technical direction of the frontend. Beyond architecture, I took on the full Tech Lead responsibilities: leading Scrum ceremonies, refining and estimating work, aligning with UX/UI, communicating directly with the client, supporting the QA team on pipeline issues and test case reviews, managing deployment guardia and representing the frontend perspective in backend and client meetings.

• Inherited two SPAs with significant technical debt after the Tech Lead's unexpected departure
• Applied Hexagonal Architecture and DDD to a new SPA first time at banking scale
• Built reusable scaffolding adopted by a ~20-person business unit across multiple products

• React
• TypeScript
• Hexagonal Architecture
• DDD
• TanStack Query
• Scrum

This project was a significant inflection point in my career. Built for the operators of a well-known dispenser brand, the platform handled incident reporting, internal support chat, real-time tracking and logistics coordination. Beyond the product itself, this was where I went deep on Hexagonal Architecture, DDD, clean code principles and Doc as Code applying them in a production environment for the first time. I also stepped into a more senior role: helping junior developers, taking ownership of architectural decisions, leading code reviews and explaining technical concepts that went beyond the immediate task. The use of TanStack Query taught me a fundamentally different way of thinking about server-state management.

• Designed and built the platform using Hexagonal Architecture and DDD first production application of these principles
• Implemented Doc as Code practices: living documentation aligned with the codebase structure
• Adopted TanStack Query for server-state management significantly improved data fetching patterns

• React
• Tailwind CSS
• TanStack Query
• Hexagonal Architecture
• DDD
• Unit Testing

Joined a project for a major textile company to build a logistics SaaS platform designed for warehouse operators to track truck shipments, manage quantities and monitor order flows. I built a large set of components and complete dashboard flows connected to live APIs. During this project I also explored mobile development setting up Android Studio and making fixes in Kotlin/Java before the client decided to go Android-only. Rather than follow a direction that didn't align with my web-first focus, I chose to move on. The experience gave me strong SaaS product intuition and a deeper understanding of data-driven UI design.

• Built a full SaaS dashboard with complex data flows connected to live logistics APIs
• Designed and implemented operator-facing UI for shipment tracking and inventory management
• Set up Android Studio and made fixes in Kotlin/Java before the client pivoted to mobile-only

• React
• Redux
• Sass
• REST APIs
• Android Studio
• Kotlin

Tasked with building a complete component library for a major insurance company, I started from zero: setting up Webpack configuration, solving integration challenges with a legacy stack running Node 10 and class-based React components, and designing a component API that could work across old and new codebases. Despite being nominally supported by a 15-person team across other products, I worked entirely alone. I had to self-define tasks, write my own specs, run refinements, estimate effort and make UX decisions independently after the UX Lead went on extended leave mid-project. I delivered the library with full Storybook documentation and a migration of one existing product flow. I left the engagement shortly after due to poor engineering practices and team ethics.

• Delivered a full component library from Webpack setup to Storybook documentation
• Solved complex integration challenges with a legacy stack: Node 10, old React, class components
• Self-managed the entire project lifecycle: task definition, refinement, estimation and delivery

• React
• Storybook
• Tailwind CSS
• CSS
• Webpack
• RTL

After completing my own frontend certification at Coderhouse, I was invited to stay on as a Technical Tutor. Rather than just correcting assignments, I went significantly further: I built and moderated an active Discord learning community, ran live coding and screen-sharing sessions broadcast on Twitch, led technical debates on topics the course didn't cover, and produced supplementary learning content. This experience was foundational for how I approach mentorship today with clarity, structure and a focus on long-term growth rather than just getting the exercise right.

• Completed multiple frontend certification projects covering HTML, CSS, JavaScript and React
• Built and moderated a Discord community that became an active peer-learning space
• Ran live coding sessions and screen-shares via Twitch explained concepts not covered in the curriculum

• JavaScript
• React
• HTML5
• CSS3
• Discord
• Twitch

Developed a set of production-ready boilerplates for a company looking to speed up delivery for their clients. The work involved building reusable React components and Tailwind-based layout systems that could be rapidly adapted per client. The environment was high-pressure with poor technical leadership which, ironically, accelerated my learning. I had to debug complex component issues independently, navigate unclear requirements and develop judgment about when to push back. A defining experience in understanding both React in depth and how dysfunctional team dynamics affect engineering quality.

• Built a library of reusable React components and layout templates with Tailwind CSS
• Developed independently under pressure with minimal guidance from senior engineers
• Gained deep hands-on experience with React component architecture and state patterns

• React
• Tailwind CSS
• JavaScript
• HTML5
• CSS3

One of my first real projects built collaboratively with a colleague while still studying. We designed and developed a complete e-commerce solution from scratch, covering the full product lifecycle: customer registration, order management, stock tracking and an admin panel. Despite using a stack that would be considered legacy today, the experience exposed me to the real complexity of shipping something end-to-end for an actual client. It was here I first understood what it meant to own a product rather than just write code.

• Built the full e-commerce flow: product catalogue, cart, checkout and order management
• Designed and implemented a stock and inventory management system
• Handled client requirements directly first exposure to stakeholder communication

• PHP
• HTML5
• CSS3
• Bootstrap
• JavaScript
• MySQL