Who I’ve Been (So Far)
I’ve spent the last decade building web applications that don’t just work—but scale, evolve, and actually make sense to the people using them.
My core strength is front-end engineering, especially with Angular, but over time I’ve naturally expanded into backend architecture, system design, and product thinking. I’ve worked in startups, large enterprises, and everything in between—which taught me how to adapt fast and deliver value regardless of constraints.
Full Stack Developer — Ness Digital Engineering
2023 – Present
At Ness, I work on early-stage products, taking them from idea to MVP.
This is the phase where most decisions matter the most—and are easiest to get wrong. I’m involved in shaping both the front-end and backend architecture (Angular + NestJS), making sure we move fast without building something fragile.
A big part of my role is keeping things simple under pressure: choosing pragmatic solutions, avoiding over-engineering, and building systems that can evolve as the product grows.
Full Stack Developer — We As Web
2022 – 2023
This was a classic “real-world software” situation: a legacy application, heavily based on jQuery, that needed to be modernized without breaking anything.
My job was to gradually refactor it into Angular while keeping the application stable and usable.
It wasn’t glamorous work, but it was important. I had to understand existing behavior in depth, preserve edge cases, and introduce structure without rewriting everything from scratch.
This is where I refined my approach to refactoring:
don’t fight the system—reshape it step by step.
Co-founder & Developer — Fire Flamingo Dev
2019 – 2022
Fire Flamingo was where I stopped thinking like “just a developer.”
I built and led a small team while working hands-on across the stack. We took over an existing ERP system, built custom solutions for clients, and launched our own products—including e-commerce platforms with real-time inventory syncing.
But the real value wasn’t the tech—it was learning how everything connects:
- product decisions
- technical trade-offs
- business constraints
This is where I became opinionated. I stopped chasing “perfect” solutions and started focusing on what actually works in production.
Front-End Developer — 3Pillar Global
2018 – 2019
At 3Pillar, I worked in a more structured, product-driven environment.
I contributed to:
- a mobile app built with NativeScript
- an Angular-based component library used to standardize UI and data handling
The second project had a big impact on how I think. It pushed me toward building systems, not pages—reusable components, consistent patterns, and predictable behavior across the application.
Front-End Developer — AROBS
2018
At AROBS, I worked on a document management platform for a US client.
This was a more enterprise-style environment, where the focus was on stability, structure, and integration with backend systems.
It helped me understand how to build interfaces that handle complex data and workflows, not just visuals.
Team Lead & Front-End Developer — NTT Data
2016 – 2018
I joined as a front-end developer and quickly moved into a Team Lead role.
On one project, I was the only front-end developer in a backend-heavy team, working on a legacy system for Virgin Media. I had to be self-sufficient, move fast, and still deliver consistently.
On another, I helped build an Angular-based platform from scratch for Legal & General UK—from initial requirements to final delivery.
This role taught me ownership:
you’re not responsible for code—you’re responsible for outcomes.
Front-End Developer — ArtSoft Consult
2013 – 2016
This is where I built my foundation.
I started on the backend (PHP), then moved to frontend as the need grew. I worked on multiple projects, often directly with clients—gathering requirements, translating them into features, and coordinating with backend developers.
It was less about “perfect code” and more about getting things done and making them work.
Full Stack Developer — Early Career (Madera, Baldemia Dev, CoDynamic)
2011 – 2013
My early years were chaotic in the best way.
I worked on:
- large-scale WordPress setups optimized for SEO
- custom CMS platforms
- automation scripts deploying sites across multiple servers
At one point, I was part of a team managing thousands of domains for a client in the domaining industry.
It wasn’t clean. It wasn’t structured. But it forced me to understand how systems actually behave at scale—and how to fix things when they break.
How I Work
Over time, I’ve developed a few principles that guide how I build software:
- I value clarity over cleverness
- I prefer simple, scalable architectures over over-engineered ones
- I treat codebases as long-term products, not short-term deliveries
- I focus on user experience as much as technical correctness
What I’m Focused On Now
Right now, I’m especially interested in:
- building clean, scalable Angular architectures
- improving developer experience in complex apps
- designing systems that are easy to extend and maintain