Skip to main content
Beautiful design isn’t just how something looks. It’s how it works. I focus on creating experiences that feel intuitive and delightful to use.
Speed and efficiency make products better to use. I optimize for both perceived and actual performance.
Details matter. From the first line of code to the final pixel, I focus on getting things right.At Aristo Software, we obsessed over performance and design for our power users. One user called our product the “Lamborghini of botting software” because of how much we cared about polish and speed. That reputation came from sweating the details.
I can move quickly on my own when needed. But the best work happens when we collaborate.At Microsoft, I worked across engineering, design, and sales teams to ship enterprise features for customers like Worldline. At my startups, I wore multiple hats but also led cross-functional teams. Knowing when to execute solo and when to bring people together is key.

​
How I Approach Problems

  1. Understand deeply: Talk to users, analyze data, research the problem space
  2. Define clearly: Articulate the problem (the what and why)
  3. Design thoughtfully: Create solutions that balance user needs, business goals, and technical constraints
  4. Build iteratively: Ship early versions, gather feedback, refine
  5. Measure impact: Track outcomes (both quantitative and qualitative) to drive decisions

​
How I Work In Practice

User research throughout, not just at the start I talk to users during discovery, mid-build to test designs, and post-launch to see how they actually use the product. At Lindy, I conducted 20+ customer calls that surfaced insights shaping our product roadmap. At Zyre, I did 50+ surveys and interviews to navigate the volatile crypto market. Combine data with judgment I add analytics and monitoring from day one. Data tells you what’s happening, users tell you why. At Aristo Software, I used SQL to analyze user behavior and pricing, which informed changes that increased revenue per user and conversion rates. Design systems for speed I build reusable components and patterns to move faster while maintaining quality. Create the component once, document it, and the whole team can use it. Ship small, ship often I ship small changes frequently rather than big changes rarely. Smaller changes are easier to test and debug. You get feedback faster and build momentum. At Lindy, I deployed dozens of agents by breaking complex workflows into shippable pieces.