Juan Ignacio Gidoni
Frontend Architect & Tech Lead
Story
The human behind the code
I'm a Frontend Architect and Tech Lead working on scalable, multi-product platforms in high-complexity environments, mainly within banking and financial services. My focus is on designing frontend architectures that hold up over time, using approaches like Hexagonal Architecture, Domain-Driven Design, clear modular boundaries and predictable UI flows.
I lead engineering work across teams by defining technical direction, setting architectural standards and making decisions that reduce cognitive load and support long-term system evolution. I work closely with product, UX/UI, QA and backend teams to turn business requirements into sustainable technical solutions, often helping teams move from fragmented SPAs to more cohesive platform-level systems.
Beyond delivery, I spend a lot of time on team growth and engineering culture. That includes mentoring developers, improving documentation, refining developer experience and shaping cross-team practices. I don't see frontend architecture as diagrams or abstraction for its own sake, but as a practical way to help teams move faster and safer through clarity, structure and solid fundamentals.
How I like to work
Working principles
The habits and beliefs I bring to every team and project.
Technical Direction & Alignment
I provide architectural direction across multiple teams, making sure frontend decisions stay aligned with product goals, backend constraints and UX requirements. I help frame technical discussions, reduce ambiguity and create the clarity teams need to deliver consistently.
Team Leadership & Delivery
I coordinate engineering work across several SPAs, helping prioritize efforts, manage delivery risks and keep technical focus. I define standards, support day-to-day execution and help developers grow while keeping the team aligned with long-term architectural goals.
Engineering Mentorship & Growth
I mentor developers through code reviews, architectural discussions and real-world problem solving. I focus on practical learning paths based on real project workflows, helping teams improve code quality, autonomy and confidence when handling complexity.
Cross-Functional Collaboration
I work closely with product, UX/UI, QA and engineering teams to keep communication clear and decisions well framed. I encourage early visibility of blockers and constructive discussions, so teams can move faster with shared ownership.
Async by default
I write things down. Decisions, trade-offs, context. Good documentation outlasts any Slack thread and respects everyone's time.
Disagree and commit
I'll push back hard if I think we're going the wrong way. Once a decision is made, I execute it fully no passive resistance.