About

Today

I am a Technical Lead at NearForm, leading engineering teams and delivering complex enterprise solutions for global clients. My role combines technical strategy, architecture ownership, team leadership, and hands-on engineering. Previously Staff Software Engineer at NearForm (2023–2025).

In parallel, I am Founder & CEO of Montecha, a remote-first software development company helping startups and enterprises build scalable digital products. I also co-founded Goocha as CTO (2023–2026), a creator economy platform where I led technology from concept through pre-seed funding to acquisition.

I have mentored and onboarded 100+ engineers throughout my career and spoken at 15+ international conferences including Øredev, O’Reilly Fluent, Full Stack London, and Web Rebels.

I am open to conversations about CTO / VP Engineering roles, fractional or advisory CTO work, and strategic consulting where deep technical judgement matters. The fastest way to see how I present professionally is my LinkedIn profile—roles, recommendations, and recent focus are always current there.

Background

I’ve been writing code since fourth grade, after I got my first computer. The first language I used was Visual Basic 6—I wanted something visual and usable, not textbook algorithms for their own sake.

After Visual Basic 6, I moved to .NET and Visual Basic 2005, then C and C#. In primary school I built FNotepad, an upgraded Windows Notepad that was downloaded more than 10,000 times and was featured on Softpedia and Brothersoft.

The web pulled me in: HTML, CSS, JavaScript, and for a long time a lot of PHP. Since 2010 I’ve earned my living building software across startups and larger companies, with a strong tilt toward JavaScript ecosystems, architecture, and how teams work together—especially remote-first.

I still love to teach, speak, and write about engineering. I travel when I can and speak at meetups and conferences. This site is where longer-form technical writing lives; for career narrative and endorsements, LinkedIn is the source of truth.

How I work

• Outcomes first — roadmap and delivery tied to measurable business value, not busywork.
• Calm communication — stakeholders, product, and engineering aligned with honest trade-offs.
• Quality as a habit — testing, observability, and maintainability baked in, not bolted on at the end.
• Remote by default — async-friendly, written culture, and respect for time zones.