ABOUT
I'm Juan Vistro, a software engineer and technical leader whose work spans product engineering, developer platforms, nonprofit leadership, and community-centered technology.
I care about what happens beyond the implementation: whether people understand a system, trust it, can maintain it, and have the ability to improve it themselves.
My career has taken me through different industries and responsibilities, but the central question has remained surprisingly consistent:
How do we build systems that make the people using them more capable?
01 / THE PATH HERE
My career has developed across software engineering and community leadership. I began building software in 2012, but some of my most formative leadership experiences came from outside technology organizations.
At EMW Community Space in Cambridge, I helped direct nonprofit programs and co-led East Meets Words, an Asian-American open mic. Bringing people together through storytelling and art taught me how to build trust, navigate competing needs, and create shared ownership.
My engineering career took me from customer-facing applications at DraftKings to internal platforms, developer tooling, and engineering systems in life sciences. Along the way, I took on broader responsibilities in mentoring, cross-functional coordination, technical decision-making, and interim engineering management.
Those experiences shaped how I approach technical leadership: **the strongest systems don't just work technically. They work for the people who depend on them.**
Nonprofit leadership, community organizing, and program development.
Customer-facing software, platforms, and developer tools.
Cross-team initiatives, technical strategy, and team enablement.
02 / HOW I WORK
This principle has shaped my work across engineering, community organizations, and nonprofit consulting.
Engineering decisions rarely happen in ideal conditions. Time, budgets, organizational priorities, and technical constraints all matter.
I try to make those constraints explicit, challenge assumptions when the evidence warrants it, and help people understand what they're choosing—and what they're giving up.
I believe effective technical leadership should leave teams more capable than it found them.
That means making knowledge accessible, mentoring engineers, creating useful standards, and designing systems that people can maintain and evolve without depending on a single individual.
I'm excited by what AI-assisted engineering makes possible, particularly in developer productivity, validation, and complex technical investigations.
But I don't see automation as a substitute for engineering judgment.
I care about knowing what can be verified, where uncertainty remains, and how people retain meaningful oversight when systems fail or encounter situations they weren't designed to handle.
03 / CURRENT ENDEAVORS
I'm the CTO and co-founder of Impact Innovations, a small nonprofit consulting firm where I lead technology strategy, platform evaluation, and architecture on a part-time basis.
The work has strengthened my ability to make technology decisions that balance organizational needs, financial constraints, and long-term sustainability.
Asterism is my collection of independent engineering projects exploring AI-assisted development, developer productivity, observability, and reliable automation.
It's where I experiment with architectures, test emerging approaches, and take responsibility for technical decisions from concept through implementation.
04 / WHAT'S NEXT
I'm interested in engineering leadership roles that combine technical depth with meaningful responsibility for people, delivery, and organizational outcomes.
I particularly enjoy environments where I can work closely with engineers, product partners, and stakeholders to turn ambiguous problems into clear priorities and dependable systems.
My longer-term ambition is to lead technology at an organizational level, with responsibility not only for architecture and execution but also for developing the teams and practices that make great engineering possible.
I don't believe leadership means having all the answers. I believe it means creating the conditions for people to find better answers together.
Interested in discussing engineering leadership, technical strategy, or work at the intersection of product and technology? I'd welcome the conversation.
