12+ years
Experience
Building web, mobile, backend, automation, and developer experience systems.
Career timelineEngineering leader · full-stack architect
I’m Santiago Molina, an engineering leader and full-stack architect based in Medellín. I build products, improve the systems behind them, and help teams do their best work.
Available for tech lead, staff-level full-stack, and engineering leadership roles

12+ years
Building web, mobile, backend, automation, and developer experience systems.
Career timeline14 people
Largest cross-functional team led across product, design, frontend, and backend.
Void.GG · What I led60%
01The shape of the work
A working model of what I care about, where I can help, and why the details matter.
Based in Medellín, Colombia, I have spent the last decade-plus shipping products across commerce, SaaS, gaming, real estate, and media.
Across these projects, I focus on architecture that can evolve, delivery pipelines that catch problems early, and team habits that make decisions clearer.
I like being close to the product and close to the code. The best technical leadership I have seen is practical, calm, and specific enough that teams can move faster without guessing what “good” means.
Architecture and modernization for products that need to keep shipping.
Developer experience, automation, testing, linting, and CI/CD systems that reduce review noise.
Technical leadership for teams that need clearer standards and calmer decisions under pressure.
02Collaboration
The places where hands-on engineering and technical leadership can make the biggest difference.
01
Best fit when a team is shipping, but needs clearer standards, calmer releases, and stronger technical decision-making across the stack.
Useful for product teams that need leadership without losing hands-on depth.
02
Useful when a platform needs to get faster, more accessible, and easier to evolve without freezing delivery for months.
Strong match for rebuilds, migrations, architecture cleanup, and performance-heavy work.
03
I improve linting, testing, CI/CD, and documentation so teams spend less time on repeated fixes and release friction.
Best when the team already feels the friction every week and wants a calmer default.
03Context
Commerce, SaaS, gaming, real estate, and community. Each brought a different problem to solve.

Technical leadership across esports web, mobile, backend, and real-time delivery at Void.
Read case study
Product engineering shipped across Team Liquid, NurtureBoss, and Stardust.gg client work.
Read case study
AI martech dashboards and campaign workflows supporting brands including Rappi and Subway.
Read case study
High-traffic sports media platform and programmatic ad infrastructure for one of the world’s most recognized extreme sports brands.
Read case study
A faster, more accessible headless commerce experience for Marcone and its product teams.
Read case study
Luxury real estate web, back-office, and mobile experiences that improved broker workflows.
Read case study
A boutique software studio behind 10+ client launches and measurable organic growth.
Read case study
Client web, Android, and commerce work across Rails, AngularJS, Java, and WordPress.
Read case study
Community talks, workshops, and mentorship through one of Medellin’s most active React groups.
Read case study04Principles
The principles I come back to when a product is moving fast and the team needs decisions that hold.
01
The best automation removes toil — repetitive, low-judgment work that slows teams down. It should never replace the thinking that makes products worth building.
Read the approach
Automating quality checks02
The developer experience of a codebase shapes how fast and confidently the team can move. Bad DX compounds. Good DX compounds too — invest early and measure it.
Read the approach
Measuring developer experience03
A good tech lead reduces ambiguity before it becomes risk. Clear standards, good tooling, and systems that fail loudly are how you protect a team's velocity at scale.
Read the approach
Standards that scale04
Speed isn't a tech concern, it's a user concern. Every kilobyte and every render-blocking resource is a choice that affects real people on real connections.
Read the approach
Fast content-heavy sites05
The goal is to solve the problem, not to use the newest tool. Stable, well-understood solutions let the team focus on the actual product.
Read the approach
Choosing tools for the job06
A consistent codebase with some imperfections beats an inconsistent one with pockets of brilliance. Conventions compound. Exceptions cost.
Read the approach
Shared responsive standards05Outside work
New cities, long walks with my dogs, and a camera roll full of small discoveries. A few things that keep me curious.
06Recommendations
Communication, reliability, and helping people do better work together—in their own words.
Keep exploring
The portfolio has the project evidence; the blog has the thinking behind the decisions.